a brief overview of the project by group 2 barry amir bhumi shubh

A brief overview of the project

By Group 2BarryAmir

BhumiShubh

Project IntroductionE-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 MethodologyRapid Application Development

Breakdown step in small piece

Faster development

Low cost

Easy to apply changes

High involvement of client

Roles and ResponsibilitiesRole Name Position

Sponsor KT Lau ConsultantStakeholder Mr Johnson

Coles/NadilSponsor

Project Manager

Barry Abdoulaye Project Manager/System Analyst

Team Member 1

Amir Azhar Mohd Noor

IT Specialist

Team Member 2

Bhumi Raj Web developer

Team Member 3

Shubhkarman Singh Database Administrator

Project ClientMr. 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.

Customers (website visitors/users) who will buy the books.

Project ScopeTraditional store equipped (PC + spreadsheet).

Long processing time.

Size of store.

Limited budget to rent a new shop.

Distance away from customer

Improve sale

Project ObjectivesCreating an e-commerce website to replace the

traditional store. Faster sale processing

Increase the storage volume

Introduce e-book

Follow new trend of e-store.

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 ManagementRisks 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 ProceduresThe 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.

All reviews are measured against IEEE standards.

Summary of SchedulePhase Starting Ending

Initiation phase

29/07/2013 31/07/2013

Planning phase

1/08/2013 27/09/2013

Execution phase

27/08/2013 24/09/2013

Controlling and testing

25/09/2013 27/09/2013

Closing phase 28/09/2013 01/10/2013

Milestones as at Aug 5, 2013Milestones Date Status Responsib

leInitiation 05/08/201

3Completed ALL

Project Planning 06/08/2013

Completed ALL

Create project management plan

28/08/2013

Completed Barry (PM)

Produce Software Requirement Specification

03/09/2013

Draft completed

Amir

Produce Software Architecture Design

Document

03/09/2013

Draft completed

Shubh

Execution 04/09/2013

Ongoing ALL

Testing 09/09/2013

Not completed Bhumi

Closing 02/10/2013

Not completed ALL

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 SchemaSequence diagram

Use case diagram

Entity Relationship diagram

UML diagram

Work Breakdown Structure

Gantt Chart

Problems Encountered

Time management

Programming language

Design decision

Font/colors choice

The End

Thank you for your attention.

Any questions?