A brief overview of the project By Group 2 Barry Amir Bhumi Shubh

1. A brief overview of the project By Group 2 Barry Amir Bhumi Shubh

2. Project Introduction • Develop an e-commerce website called Books2U selling various book types to students and the general public online. • Project duration: minimum of 3 and a half months • Involves the participation of 4 students, all with specific roles and responsibilities. • 5 different steps according to the system development lifecycle: Planning, Analysis, Design, Implementation and Support.

3. Roles and Responsibilities

4. Project Client • Mr. Johnson Coles • Owner of the shop. • Willing to spend $10,000 to see the project developed. • Responsible for providing all necessary information regarding project development i.e. clients’ information previously.

5. Project Scope • The traditional store equipped with only one computer and spreadsheet software to store client’s records. • Completely obsolete and customers were not served quick enough creating frustration of some of them. • Size of store was not big enough to store all the categories of book requested by most of our customers. • Renting another shop is also out of budget. • An alternative is required to provide better services to customers but also new categories of book. • Inconvenient for customers living far away from our bookstore as they have to travel all the way to shop.

6. Project Objectives • Creating an e-commerce website to replace the traditional store that will provide quality services such faster sale processing, larger number of books, and sells electronic copy of books as well hardcopy including a faster delivery. • Following the popularity of online shopping which have overtaken traditional brick-and-mortal stores. • Payment will be made through the use of electronic payments methods i.e. Master, Visa, and PayPal by following easy steps.

7. Project Constraints • It is assume that customers have to create an account in order place an order. • The website will be available on the World Wide Web. • Data previously stores in the spreadsheet will be transfer to a database to avoid the lost of customers’ information. • Secure login system is provident to all customers. • The biggest constraints to be aware of will be project submission date the 10/10/2013 • The project team members are required to work together regardless of the commitment of each member to deliver the final product before deadline.

8. Deliverables • Software Project Management Plan (SPMP) • Work Breakdown Structure (WBS) • Status Reports • Milestone Reports • Software Requirements Specifications (SRS) • Software Architecture Design Document (SADD) • Software Design Document (SDD) • Test Plan • Quality Assurance Plan • Risk Management Plan • Source and Object Code

9. Risk Management • Risks with respect to the work to be done. • Risks with respect to the management. • Risks with respect to available resources. • Risks with respect to the client.

10. Internal Reviews Procedures • The team or the PM requests an Internal Review. • A team member will nominate themselves to conduct the review. • The team will review the document within a time frame set by the PM. • The PM will print a hard copy and make suggestions on the hard copy. • The PM will contact the client and discuss any quality issues. If the client is not satisfied, the team will be consulted at the next meeting.

11. Summary of Schedule

12. Milestones as at Aug 5, 2013

13. Tools & Technologies • Microsoft Word for project documentations • Microsoft Project for drawing schema such as WBS, Gantt chart, etc. • HTML and CSS for the development the website including interface; • MYSQL to develop the database which will store data; • PHP to develop functions and query the database. • Enterprise Architect for use case, ER diagram, etc.

14. Design Schema • Sequence diagram • Use case diagram • Entity Relationship diagram • UML diagram

15. Work Breakdown Structure

17. Gantt Chart