sportsgoodies.com.au

Hunain Aslam - Project Manager / Programmer

Derin Mark - Programmer Navdeep Singh - System Analyst Rishu - Tester/QA Mukesh - Technical Writer

Roles & Responsibilities

Project Purpose and scope

Methodology Tools Cost/budget WBS Requirement

Traceability Matrix (RTM)

ER-Diagram DFD (Data flow

diagram)

Overview

Structured Chart 3-tier Architecture of

your System USE-Case diagram Class diagram Website Layout Conclusion References Q & A

The purpose of this project is to deliver an ecommerce website

Customers can create their profiles Customers can purchase products which

are to be delivered to them.

Purpose

Streamlined Business Processes Easy Accessibility World Wide Access More Diverse Products Global Market

Scope

SCRUM Methodology is used for this project.

Iterative & Incremental Approach Client Interaction Change in Project

Development Methodology

PHP HTML Java Script CSS Dreamweaver MySQL PhotoShop J Query AJAX

Tools & Technologies

Task name Cost

Requirements Analysis And Project

Planning

$35,000

Object and System Design $33 ,718

Implementing Testing $9,128

System Testing $6,000

Training and Set Up $3,000

Backup for any ongoing Change $10,000

  Total: $100,000

Cost & Budgeting

Work Breakdown Structure (WBS) is designed to break the project into steps and identify the project duration.

It also contains the process of Project management including Project Initiation Project Closure Meetings

WBS

Sports Goodies

Requirement

Gathering

System Design

Development

 

Testing

 

Deployment

 

Sequence

Diagram

Traceability Matrix

Activity Diagra

m

DB Desig

n

DFD

UC

SRSDB

Design

GUI Desig

n

Web pages

Design

DB Interfac

e

Integration

Website

Testing

Unit Testin

g

Domain

Creation

Website

Hosting

Integrate Database

Traceability Matrix correlates customer & functional requirements

It’s purpose is to see if the project requirements are being met

Also helps in project task planning.

Traceability Matrix

No. Customer Requirements Forward Traceability

U1 Customer Registration / Login S1

U2 Customer / Administrator uses his/her

login and password to access the

website

S2

U3 If Customer enters a wrong Customer

name and password

S3

U4 To logout the webpage user need to

click logout

S4

U5 To View in wish list S5

U6 To Select the Item in Shopping Cart S6

U7 To Checkout S7

U8 To insert / update / Delete Shopping

Cart

S8

U9 To verify address details S9

U10 To change or update System setting S10

U11 Admin Dashboard S11

No Functional Requirements Backward

Traceability

S1 Need to open signup page for new customer U1

S2 Existing customer can sign in by giving a username and

password that they already have.

U2

S3 If unable to login, Customer needs to get a message to

change the password or click on forget password to get

new password

U3

S4 After logout it need to show user logout message U4

S5 Brows in Catalogues to add in Customer wish list and

show those Designs there in wish list.

U5

S6 Need to add the Designs in the shopping cart U6

S7 Need to pay the amount by credit card or PayPal account

information

U7

S8 Admin can insert/ Update/Delete Designs from admin

panel in category

U8

S9 Admin can create or edit/ update category from admin

panel

U9

S10 Admin can change or update System setting from admin

panel

U10

S11 Need to login as Admin and the Admin home page is

Dashboard

U11

S12 Cross Browser compatibility is necessary. N/A

Gantt charts illustrate the start and finish dates of the terminal elements and summary elements of a project.

Gantt Chart

The purpose of ER Diagram is to clarify the database structure and relationship of the database entities.

It also has primary and foreign Key. Relations can be many-to-many, one-to-

one or one-to-many.

ER Diagram

Data flow diagram helps us in identifying the business processes.

It is a technique which gives the idea before we go through any process.

A data flow diagram tells us that how data flows through a system.

DFD

Activity Diagram

Three-tier or multi-tier architecture are often used when describing how clients connect to servers. Presentation Layer

GUI / Front End Business logic Layer

Development Logic Data Access layer

Database

3 Tier

Use case diagram shows a set of use cases and actors and their relationships.

Use cases represent system functionality, the requirements of the system from the user’s perspective.

Use Case Diagram

A class diagram is a type of static structure diagram that describes the structure of a system by showing the system's

classes attributes Operations / functions and the relationships among objects.

Class Diagram

Website layout

Within Time Completion Within Specified Budget Client Satisfaction Secure and bug free project Easily Upgradeable User Friendly Easy to Understand & Manage

Conclusion

[IEEE 1074] IEEE Standard for Developing Software Life Cycle Processes, ANSI/IEEE Std. 1074-1991.

"New New Product Development Game". Harvard Business Review 86116:137–146, 1986. January 1, 1986. Retrieved Dec 10, 2013

Cho, L (2009). "Adopting an Agile Culture A User Experience Team's Journey". Agile Conference: 416. doi:10.1109/AGILE.2009.76. ISBN 978-0-7695-3768-9

Leansoftwareengineering.com". Leansoftwareengineering.com. October 27, 2007. Retrieved December 01, 2013.

Reference

Thank You

Q & A