Professional Documents
Culture Documents
Coffee Cart Rewards Management System Project Plan
Coffee Cart Rewards Management System Project Plan
Coffee Cart Rewards Management System Project Plan
Issue:
1.4
Issue Date: 120Jul/14
Project Plan
ProjectPlan.pdf
Revision History
Date
Issue
Description
Author
24/June/14
1.0
Laura Pike
29/June/14
1.1
Laura Pike
06/July/14
1.2
Laura Pike
13/July/14
1.3
Laura Pike
20/July/14
1.4
Laura Pike
Confidential
Page 2 of 9
Issue:
1.4
Issue Date: 120Jul/14
Project Plan
ProjectPlan.pdf
Table of Contents
1. Object ives
2. Scope
3. References
4. Phase Plan
5. Schedule
7. Releases
8. Resource plan
Confidential
Page 3 of 9
Issue:
1.4
Issue Date: 120Jul/14
Project Plan
ProjectPlan.pdf
Project Plan
1.
Objectives
BeanTracker is an Android based application that provides all the necessary features to operate a coffee
cart rewards system. With this application the coffee cart manager can easily run a rewards program that
allows customers to accrue points based on the amount of money they spend and to get benets based on
their points."
2.
Scope
This Project Plan describes the overall plan to be used by BeanTracker system, including deployment of
the software product. The details of the individual iterations are be described below in the Phase Plan and
Objects of Each Iteration. The plans as outlined in this document are based upon the product requirement s
as defined in the Vision Document.
3.
References
Vision Document, 6300Sum14Pro ject2\Deliverable1\vision.pdf
Use-case Model, 6300Sum14Pro ject2\Deliverable1\UseCase.pdf
Risk Assessment, 6300Sum14Project2\ Deliverable1\ RiskAssessment.pdf
Planning a Project with the IBM Rational Unified Process:
http://www3.software.ibm.com/ ib mdl/pub/software/rational/web/whitepapers/2003/tp151.pdf
Rational Unified Process Best Practices for Software Development Teams
https://www.ibm.com/developerworks/rational/library/content/03July/1000/1251/1251_bestpractices_TP026B.pdf
Planning and Estimating a RUP project using IBM Rational SUM M IT Ascendant
http://www.ibm.com/developerworks/rational/library/4772.ht ml
M icrosoft Word Templates for RUP
http://sce.uhcl.edu/helm/RationalUnifiedProcess/wordtmpl/index.htm#sdp
4.
Phase Plan
Phase
Iteration
Inception
I1
Elaboration
E1
E2
Construction
Confidential
Primary Objective
(Risk/use cases
addressed)
C1
Scheduled
Start/End
Effort
Estimate
(Person
Hrs)
Percent
effort of
total
Staffing
6/23-29
30
20
6/30-7/3
23
15
7/4-7/7
23
15
7/7-8
23
15
Define vision
Initial use-case model
Initial risk assessment
Project plan
VIP Customer
Management
subsystem
Purchase Tracking
subsystem
VIP Customer
Management
subsystem
Page 4 of 9
Issue:
1.4
Issue Date: 120Jul/14
Project Plan
ProjectPlan.pdf
C2
Transition
Project
Summary
5.
T1
Purchase Tracking
subsystem
Deliver beta to
customers
Analyze comments
from beta
Apply corrections
Finalize users
manual
Deliver to customer
7/9-13
23
15
7/14-21
30
20
6/23-7/21
152
100
Schedule
Confidential
Page 5 of 9
Issue:
1.4
Issue Date: 120Jul/14
Project Plan
ProjectPlan.pdf
6.
State of
Artifact
Risk
Addressed
Starr/End Dates
Scheduled
Actual
Scheduled
Actual
Role
Responsible
Vision
Complete
6/24-29
6/24-29
10
10
Scott
Use-case
Model
Draft
6/24-29
6/24-29
10
10
Ben
Risk
Assessment
Draft
6/24-29
6/24-29
Laura
Project Plan
Draft
6/24-29
6/24-29
Laura
State of
Artifact
Risk
Addressed
Start/End Dates
Scheduled
Actual
Scheduled
Actual
Role
Responsible
Use-case
Model
Revised
6/30-7/3
6/307/3
Ben
Supplementary
Requirements
Complete
6/30-7/3
6/307/3
Laura
Software
Architecture
Complete
6/30-7/3
6/307/3
Ben
Design Model
Draft
6/30-7/3
6/307/3
Scott
Test Cases
Complete
6/30-7/3
7/4-7/7
10
Scott, Ben,
Laura
Prototype
Complete
7/4-7/7
6/307/3
10
Scott
Risk
Assessment
Revised
7/4-7/7
7/4-7/7
Laura
Project Plan
Revised
7/4-7/7
7/4-7/7
Laura
Users Manual
Draft
7/4-7/7
7/4-7/7
Ben
Upgrade
SDK
Use-Case
Model
Confidential
State of
Artifact
Complete
Risk
Addressed
Starr/End Dates
Scheduled
Actual
Scheduled
Actual
7/7-13
7/7-13
Role
Responsible
Ben
Page 6 of 9
Issue:
1.4
Issue Date: 120Jul/14
Project Plan
ProjectPlan.pdf
Traceability
information
on some use
cases
Complete
7/7-13
7/13
Laura
Android
Program
Beta
7/7-13
7/7-13
38
64
Scott,
Laura, Ben
System Test
Results
Draft
7/7-13
7/12-13
Scott,
Laura, Ben
Users
Manual
Revised
7/7-13
7/13
.5
Ben
7.
State of
Artifact
Risk
Addressed
Starr/End Dates
Scheduled
Actual
Scheduled
Actual
Role
Responsible
Android
Program
Complete
7/14-21
7/14-21
30
36
Ben
Scott
Laura
Users
Manual
Complete
7/14-21
7/14-21
Ben
System
Test
Results
Complete
7/14-21
7/14-21
Ben
Scott
Laura
Project
Plan
Complete
7/14-21
7/14-21
.5
Laura
Releases
Brief descriptions of each release, whether demo, beta, etc.
Product
State of Product
End Date
Prototype
7/7
Beta
7/13
Complete
7/21
Confidential
Page 7 of 9
Issue:
1.4
Issue Date: 120Jul/14
Project Plan
ProjectPlan.pdf
8.
Project Organization
8.1
Organizational Structure
Laura Pike
Project Manager
8.2
8.3
Scott Dickerson
Ben Chung
Documentation Lead
Development Lead
External Interfaces
Person
Brad
LameDucks, Co-Owner
Janet
LameDucks, Co-Owner
Laura Pike
and to a lesser extent the following roles :
Design Reviewer
Implementer
Code Reviewer
Tester
Scott Dickerson
Documentation Lead
Project Reviewer
Requirements Reviewer
Technical Writer
and to a lesser extent the following roles:
Confidential
Page 8 of 9
Issue:
1.4
Issue Date: 120Jul/14
Project Plan
ProjectPlan.pdf
Design Reviewer
Implementer
Code Reviewer
Tester
Ben Chung
Development
LeadC:\Users\laura\process\workers\wk_sysan.htm
Requirements Specifier
User Interface Designer
Software Architect
Design Reviewer
Test Manager
and to a lesser extent the following roles:
Project Reviewer
Requirements Reviewer
Technical Writer
Confidential
Page 9 of 9