UTD Project Management Plan

Software Project Management Plan

1- Introduction
In the TradeK project a system has to be designed to support electronic shopping
system. The software application to be made consists of at least three main functions,
which must interact using the internet. The application may involve the basic e-commerce
activities, such as members’ login, browsing, buy and sell activities. The entire system
has to be developed (in JAVA) in a way that it is easy to maintain and extend.

I. Project overview
This project is to create a prototype Online Purchasing System for TradeK Cake House. It
is an online application likewise virtual shop on the Internet where customers can browse
the products catalog and select products of interest. The selected items may be collected
in a shopping cart. At checkout time, the items in the shopping cart will be presented as
an order. At that time, more information will be needed to complete the transaction.
Usually, the customer will be asked to fill or select a billing address, a shipping address, a
shipping option, and payment information such as credit card number. An e-mail
notification is sent to the customer as soon as the order is placed.

II. Project deliverables

1. Preliminary Project Plan 01.06.2016

2. Requirements Specification 10.06.2016
3. Analysis [Object model, Dynamic model, and User interface] 17.06.2016
4. Architecture Specification 26.06.2016
5. Component/Object Specification 09.07.2016
6. Source Code 18.07.2016 - 31.07.2016
7. Test Plan 01.08.2016 - 07.08.2016
8. Final Product w/ Demo 08.08.2016 - 12.08.2016

III. Evolution of this document

This document will be updated as the project progresses. Updates should be expected in
the following sections:
i. References - updated as necessary
ii. Definitions, acronyms, and abbreviations - updated as necessary
iii. Organizational Structure will be updated as the team leaders are assigned
for each phase.
iv. Technical Process - this section will be revised appropriately as the
requirements and design decisions become clearer
v. Schedule – as the project progresses, the schedule will be updated
accordingly

Revision History
Revision Date Updated By Update Comments
0.1 01.05.2016 Sakinah Binti Mohd Azam First Draft
0.2 01.07.2016 Tham Mei Yee

IV. References

@ Advance Software Eng class project Page 1 of 5

UTD Project Management Plan

i. Team Website http://wwwis.win.tue.nl/2M390/projects/spingrid/spmp.pdf

ii. Project Scope http://wwwis.win.tue.nl/2M390/projects/spingrid/spmp.pdf
iii. Case Studies
 http://allrecipes.com/recipe/10926/cake-mix-cookies-iv/
 http://www.costco.com/cakes-cookies.html
 http://www.cakescookiesandcraftsshop.co.uk/

V. Definitions, acronyms, and abbreviations

i. UML - Unified Modeling Language

ii. AD - Architectural Design
iii. ADD - Architectural Design Document
iv. ATP - Acceptance Test Plan Client Monitor, Agent or Submitter
v. CM - Configuration Management
vi. Customer - TradeK Cake House
vii. DD - Detailed Design
viii. DDD - Detailed Design Document
ix. ITP - Integration Test Plan Monitor Application that either monitors
dispatchers
x. PM - Project Manager
xi. QAM - Quality Assurance Manager
xii. SCMP - Software Configuration Management Plan
xiii. SM - Senior Management SPMP Software Project Management Plan (this
document)
xiv. SQA - Software Quality Assurance
xv. SQAP - Software Quality Assurance Plan
xvi. SR - Software Requirements
xvii. SRD - Software Requirements Document
xviii. STD - Software Transfer Document
xix. STP - Software Test Plan Submitter Application that submits jobs to
dispatchers
xx. SUM - Software User Manual
xxi. SVVP - Software Verification and Validation Plan
xxii. TR - Transfer Phase
xxiii. UR - User Requirements
xxiv. URD - User Requirements Document
xxv. UTP - Unit Test Plan
xxvi. VPM - Vice Project Manager
xxvii. VQAM - Vice Quality Assurance Manager

2- Project organization
I. Process model

@ Advance Software Eng class project Page 2 of 5

UTD Project Management Plan

The process used for this project will be a V-model such that each stage of the model
allows us to do testing after completing a phases. Referring to the diagram below, each
phase is tested after completion.

II. Organizational structure

Team Members –
i. Fatin Izzyan Binti Nasaruddin
ii. Tham Mei Yee
iii. Sakinah Binti Mohd Azam
iv. Nur Hidayah Binti Mazni
v. Rofithah Binti Omar

Days Deliverable Team Leader Deliverable Description

9 1 Fatin Izzyan Binti Nasaruddin Project Plan
7 2 Tham Mei Yee Requirements Specification
9 3 Sakinah Binti Mohd Azam Analysis
13 4 Nur Hidayah Binti Mazni Architecture Spec
9 5 Rofithah Binti Omar Component/Object Specification
14 6 Source Code
7 7 Test Plan
5 8 Final Deliverable

III. Organizational boundaries and interfaces

Team leaders throughout each development of the phases will be responsible for
coordinating team meetings, updates, communications, and team deliverables

@ Advance Software Eng class project Page 3 of 5

UTD Project Management Plan

IV. Project responsibilities

For the most vital responsibilities per phase of each team members, please refer to
segment 2.2. Ultimately the whole complete development of project team is responsible
for the successful delivery of the product. The team member tasks per deliverable
according to expertise and the phases below:
1. Project Plan – Whole Team
2. Requirements Specification – TBD
3. Analysis – TBD
4. Architecture Spec – TBD
5. Component/Object Specification – TBD
6. Source Code – TBD
7. Test Plan – TBD
8. Final Deliverable – Entire Team

3- Managerial process
I. Management objectives and priorities

The management objective is to deliver the product in time and of high quality. The PM
and QA work together to achieve this by respectively checking that progress is made as
planned and monitoring the quality of the product at various stages

II. Assumptions, dependencies, and constraint

In this project plan, a number of factors are taken into account. For these refer the
following list shows the way milestones on various project phases that have scheduled:

• The team budget of 5 persons x 365 hours = 1825 hours;

• The project deadline of August 12th
• The final presentation of August 12th
• The peer evaluation deadline of August 8th
• Other days the weekends holiday is closed (June 5th, June 12th, June 19th, June
26th, July 3rd, July 10th, July 17th, July 24th, July 31th, August 7th).

NOTE: Due to the deadline of 12th August 2016, running out of time will have its
reflection on the product, and not on the duration of the project. By assigning a priority
to every user requirement, a selection can be made of user requirements that may be
dropped out if time runs out.

III. Risk management

This section mentions any potential risks for the project. Also, schedules or methods
are defined to prevent or to reduce the risks as below:

i. Technology risk
ii. People risk
iii. Financial risk
iv. Market risk
v. Structure/process risk

IV. Monitoring and controlling mechanisms

The monitoring of progress is done by the PM using the following means:

@ Advance Software Eng class project Page 4 of 5

UTD Project Management Plan

i. Weekly project status meetings 

ii. Shared document repository
iii. Project tracking by MS project plan
iv. Tracking utilizing baselines in MS project

4- Technical process
I. Methods, tools, and techniques

The project will be implemented utilizing V-model methodology, and tools such as
Dreamweaver, Microsoft Project, Java, MySQL, QTP, and Load Runner will be utilized..
The risks for each category are listed to complete the project successfully. For each
risk, a description, a probability to occur, the action associated and the impact of the
risk are given.

II. Software documentation

Documentation such as project charter, Business Requirement Document, Functional

Specification document, Cost Benefit Analysis, Technical Specification document,
detail design document, Test Plan, Implementation Plan, and Benefit Realization
document.

III. Project support functions

All project support documents will be completed in applicable phases

5- Work elements, schedule, and budget

I. The project is accounted for project resources, technologies and tools required to
whole analysis, implementation, and test of the application.
II. The project lead will be rotated for each phase within 5 team members.
III. The document for all phases will be revised in subsequent phases if applicable

@ Advance Software Eng class project Page 5 of 5