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

Project Introduction E-commerce website called Books2U for bookshop. Minimum of 3 and a half months 4 students, all with specific roles and responsibilities. The system development lifecycle: Planning, Analysis, Design, Implementation and Support.

Development methodology Rapid Application Development Breakdown step in small piece Faster development Low cost Easy to apply changes High involvement of client

Roles and Responsibilities RoleNamePosition SponsorKT LauConsultant StakeholderMr Johnson Coles/NadilSponsor Project ManagerBarry AbdoulayeProject Manager/System Analyst Team Member 1Amir Azhar Mohd NoorIT Specialist Team Member 2Bhumi RajWeb developer Team Member 3Shubhkarman SinghDatabase Administrator

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.

Project Scope Traditional store equipped (PC + spreadsheet). Long processing time. Size of store. Limited budget to rent a new shop. Distance away from customer Improve sale

Project Objectives Creating an e-commerce website to replace the traditional store. Faster sale processing Increase the storage volume Introduce ebook Follow new trend of estore. Facilitate payment process through electronic payment.

Project Constraints The biggest constraints submission date the 10/10/2013 Customers have to create an account in order place an order. Website will be available on the World Wide Web. Transfer of previous customers’ information to DB. Secure login system is provident to all customers. The commitment of each member to deliver the final product before deadline.

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

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.

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.

Summary of Schedule PhaseStartingEnding Initiation phase29/07/201331/07/2013 Planning phase1/08/201327/09/2013 Execution phase27/08/201324/09/2013 Controlling and testing 25/09/201327/09/2013 Closing phase28/09/201301/10/2013

Milestones as at Aug 5, 2013 MilestonesDateStatusResponsible Initiation05/08/2013CompletedALL Project Planning06/08/2013CompletedALL Create project management plan28/08/2013CompletedBarry (PM) Produce Software Requirement Specification 03/09/2013Draft completedAmir Produce Software Architecture Design Document 03/09/2013Draft completedShubh Execution04/09/2013OngoingALL Testing09/09/2013Not completedBhumi Closing02/10/2013Not completedALL

Database- ER diagram

Database-Data dictionary

Database-data dictionary(suite)

Use case diagram

Storyboard- Homepage

Storyboard- Session

Prototype

Tools & Technologies Microsoft Word for project documentations Microsoft Project for drawing schema HTML, Photoshop and CSS MYSQL to develop the database PHP to develop functions and query the database Enterprise Architect for use case, ER diagram, etc.

Design Schema Sequence diagram Use case diagram Entity Relationship diagram UML diagram

Work Breakdown Structure

Gantt Chart

Problem encounter Time management Programming language Design decision Font/colors choice

End Questions