A CMS always comes with two ends, frontend and backend. Similarly, an e-commerce CMS  has two ends too. The system we are going to build here is for an e-commerce grocery store.  The frontend will be open for everyone to access. The frontend (website) can be accessed through the store’s website address. Customers can view products and add them to basket. They can complete their order using a friendly checkout. Before checkout, each customer has to create an account on the website for delivery and billing addresses. After the order is complete, both store admin and customer will receive an email notification. The store admin can view these orders in the backend. The backend of the system will be accessible by a secure URL and login credentials. Only admin will have this access. Admin will be able to access following elements in the admin area.

· Dashboard: Store owner can view recent orders, highest selling products and new customers at one place.

· Products: Shop owners can add new products using the system. Shop owners can upload images using admin area. Each product page would have SEO related elements like meta title, description and SEO friendly URL.

· Categories: Store owners can add/edit/ delete product categories, assigning products to categories.

· CMS pages: Within this system, admin can add new pages. Each page will have a title, text editor for main content, image uploader, meta title and meta description.

· Media: Admin can add/edit/delete images in this section. Videos can be embedded via content editors (ideally WYSIWYG).

Project Risks

· Inaccurate project estimate: Time estimation to develop the software is challenging.

· Misunderstanding customers’ requirements: Customers requirements are very crucial as the system development is based on their requirements.

· Changing customers requirements: Customers requirements keep changing time to time sometimes this can become a cause for failing to deliver the project on time.

· Technical risk: It leads to delay time and affect the scope of the project. Sometimes it is not necessary to implement each functionality which increases technical complications unless if it is not dependant on other important functionality.

Website Risks

· Cross-platform compatibility: The system or website compatible with a browser, system screen size and orientation.

Hacking: If a website gets hacked then all user data could, and other valuable information on the website could be stolen which would be very expensive to resolve.

· Viruses: They are many unsecured websites which can bring viruses into your system and may also infect the website.

· Productivity risk: Risk due to poor design of the website which reduces the speed of page loading time.

· Security: Attacks like Denial of Service (DoS), Brute force, SQL injection and many others can easily hack the system and the website whose operator use weak passwords.

· Themes and plugins: Hundreds and thousands of plugins and themes were designed by the developers for custom use which can easily increase the vulnerability risk of the CMS.

The post CO4804: Masters Project appeared first on My Assignment Online.