Revision Chart
Preface
Contents
1. Introduction
1.1 Project Overview
1.2 Project Deliverables
1.3 Evolution of the Software Project Management Plan
1.4 Reference Materials
1.5 Definitions and Acronyms
2. Project Organization
2.1 Process Model
2.2 Organizational Structure
2.3 Organizational Boundaries and Interfaces
2.4 Project Responsibilities
3. Managerial Process
3.1 Management Objectives and Priorities
3.2 Assumptions, Dependencies, and Constraints
3.3 Risk Management
3.4 Monitoring and Controlling Mechanisms
3.5 Staffing Plan
4. Technical Process
4.1 Methods, Tools, and Techniques
4.2 Software Documentation
4.3 Project Support Functions
5. Work Packages, Schedule, and Budget
5.1 Work Packages
5.2 Dependencies
5.3 Resource Requirements
5.4 Budget and Resource Allocation
5.5 Schedule
6. Additional Components
7. Index
8. Appendices
|
Version |
Primary Author(s) |
Description of Version |
Date Expected |
|
Draft |
Antony |
Initial draft created for distribution and review comments |
10/4/01 |
|
Preliminary |
Antony |
Second draft incorporating initial review comments, distributed for final review |
10/10/01 |
|
Final |
Antony |
First complete draft, which is placed under change control |
10/19/01 |
|
Revision 1 |
Antony |
Revised draft, revised according to the change control process and maintained under change control |
10/22/01 |
|
Revision 2 |
Antony |
Revision of schedule |
10/24/01 |
|
Revision 3 |
Kevin |
Revision of entire document
to reflect new quarter |
1/14/02 |
|
Revision 4 |
Sean |
Revision of entire document
for stage 3 |
2/15/02 |
����������� The software product to be produced is the Sokoban videogame with customer-desired enhancements.� Sokoban is a puzzle solving game, challenging both the user�s mental ability as well as his ability to work as part of a team.�
Sokoban will take place in a 2-dimensional environment in which a user controlled robot will be able to manipulate its environment (move boxes around) in order to complete its task.� Sokoban will provide additional value by allowing cooperative play over the internet and including features such as instant replay and the ability for users to create their own levels with a level editor.�����
�Storyboard (User Interface Prototype)
�System Requirements Specification (SRS) C-Req
�System Requirements Specification (SRS) D-Req
�Proof of Concept
�High Level Design
�Detailed Design
�Stage 1 Implementation
�Stage 2 Implementation
�Stage 3 Implementation
�Post Mortem & Final Submission ����
�Project Management Documents - Web site, SPMP, SQAP, Review Summaries, metrics
|
Version |
Primary Author(s) |
Description of Version |
Date Expected |
|
Draft |
Antony |
Initial draft created for distribution and review comments |
10/4/01 |
|
Preliminary |
Antony |
Second draft incorporating initial review comments, distributed for final review |
10/10/01 |
|
Final |
Antony |
First complete draft, which is placed under change control |
10/19/01 |
|
Revision 1 |
Antony |
Revised draft, revised according to the change control process and maintained under change control |
10/22/01 |
|
Revision 2 |
Antony |
Revision of schedule |
10/24/01 |
|
Revision 3 |
Kevin |
Revision of entire document
to reflect new quarter |
1/14/02 |
|
Revision 4 |
Sean |
Revision of entire document
for Stage 3 |
2/15/02 |
None as of yet.
This Project will use a Spiral Development Process.
|
Work Product Name |
Planned Completion Date |
Placed Under Change Control? |
Deliverable to Customer? |
People Who Must Sign Off on the
Work Product |
|
Software
Project Management Plan This is
the controlling document for managing a software project, and it defines the
technical and managerial processes necessary to deliver the project
requirements. |
TBD |
Yes |
No |
Project
Manager, Engineering Lead, QA Lead, Documentation Lead |
|
Web Page |
Ongoing |
Yes |
No |
None |
|
Features
List |
10/4/01 |
Yes |
No |
Customer |
|
UI
Prototype |
10/16/01 |
Yes |
No |
Customer |
|
Training
Plan |
10/4/01 |
Yes |
No |
None |
|
C-Req |
10/18/01 |
Yes |
No |
Customer, QA person |
|
D-Req |
10/21/01 |
Yes |
No |
QA person |
|
SRS |
10/25/01 |
Yes |
Yes |
Customer QA person |
|
Proof of
Concept |
11/1/01 |
No |
No |
Instructor |
|
Class
Diagram |
11/8/01 |
Yes |
No |
None |
|
High
Level Design |
11/15/01 |
Yes |
No |
QA person |
|
Detailed
Design |
11/29/01 |
Yes |
No |
QA person |
|
Stage 1
Implementation |
12/4/01 |
No |
Yes |
Customer QA persom |
|
Stage 2
Implementation |
2/14/02 |
No |
Yes |
Customer QA person |
|
Stage 3
Implementation |
3/10/02 |
No |
Yes |
Customer QA Person |
|
Final
Submission |
3/12/02 |
No |
Yes |
Instructor |
|
Kevin |
Design
& Integration |
786-4329 |
kblomset@calpoly.edu |
|
Josh |
Testing |
756-8986 |
jnthomps@calpoly.edu |
|
Antony |
Configuration
Management |
784-9045 |
ageorge03@hotmail.com |
|
Kamil |
Quality
Assurance & Web |
489-7560 |
kbaranow@calpoly.edu |
|
Sean |
Manager |
542-0455 |
smpinto@calpoly.edu |
The analyst shall be in charge of staying in contact with the customer. This is to ensure that the product is what the customer wants. This will be accomplished by regular meetings with the customer.
The manager shall be in charge of staying in contact with the course instructor. This includes scheduling deadlines and making sure the project falls under the instructor�s guidelines.
|
|
Manager |
QA |
Analyst |
Designer |
Integration |
Configuration Manager |
|
Liaison Responsibility |
VP Engineering |
|
Customer |
Software engineering lab |
|
|
|
Document Responsibility |
SPMP, Staged Delivery Plan |
SQAP |
SRS |
SDD |
Integration Plan |
Change Control Plan |
|
Other Responsibilities |
|
FTR's |
|
|
|
CVS
Repository |
For this project quality is management�s primary goal. The schedule of this project is limited, and will be determined by our detailed schedule. The goal is turn all milestones in on time.
We are dependent on the wishes of the customer and the dates determined by the instructor.
Report any risk that you believe may be a factor now or later to the manager as soon as possible.� We will address risks as very important issues and therefore try to resolve them as soon as possible.
A weekly status report shall be sent to the team email account listing the activities done for the week and the amount of time spent on the activity.
Lab activities will be recorded in a project journal updated by the manager.
The team will be composed of five members, each with a specific role or roles. All roles are explained in section 2.4 The jobs will changed midway through the quarter.
The program will be written using JAVA following the coding standard given to us by the instructor. Together will be used to create class diagrams, and CVS will be used as a code repository.
Configuration Management Plan
We will have a very simplified plan: Each document produced will have a table at the bottom showing Change History. The history shows the Date, Person, and Description of Change. Whenever you make a change to a document you must update the change history.
5.0
Work Packages, Schedule, and Budget
We do not have a specific schedule past our detailed schedule
and the time restraints given by our instructor/customer and 10-week quarter.
Not enough information at this time.
Not enough information at this time.
Not enough information at this time.
Not enough information at this time.
None at this time.
None at this time.