Bos Software Development Plan

SampleCo
Bizcochos Ordering System

Software Development Plan
Version 1.0

BOS Software Development Plan.doc
Version:
1.0
Date: 12/11/2007
Revision History
Date
12/11/2007
Confidential
Version
1.0
Description
first release
Gabrielsw.blogspot.com , 2007
Author
Gabriel Claramunt
Page 2 of 7

Version:
1.0
Date: 12/11/2007
Table of Contents
1. Introduction
Purpose
Scope
Definitions, Acronyms, and Abbreviations
References
4
4
4
4
4
2. Project Overview
Project Purpose, Scope, and Objectives
Assumptions and Constraints
Project Deliverables
Evolution of the Software Development Plan
4
4
4
4
4
3. Project Organization
Organizational Structure
External Interfaces
Roles and Responsibilities
4
4
4
4
4. Management Process
Project Plan
Phase Plan
Iteration Objectives
Releases
Project Schedule
Project Resourcing
Iteration Plans
Project Monitoring and Control
Requirements Management Plan
Schedule Control Plan
Budget Control Plan
Quality Control Plan
Measurement Plan
Risk Management Plan
Close-out Plan
5
5
5. Technical Process Plans

Development Case
Methods, Tools, and Techniques
Infrastructure Plan
Product Acceptance Plan
6
6
6
6
6
6. Supporting Process Plans

Configuration Management Plan
Evaluation Plan
Documentation Plan
Quality Assurance Plan
Problem Resolution Plan
Subcontractor Management Plan
Process Improvement Plan
6
6
6
6
6
7
7
7
Confidential
5
5
5
5
5
5
5
5
6
6
6
6
6
6
Page 3 of 7

Version:
1.0
Date: 12/11/2007

1.Introduction
Purpose
This Software Development Plan document should provide an overall idea of how the project will be
developed.
Scope
This document is applicable only for the development of the Bizcochos Ordering System.
Definitions, Acronyms, and Abbreviations
Refer to BOS Glossary document.
References
BOS Development Case

BOS Glossary
RUP for small projects website
2.Project Overview
Project Purpose, Scope, and Objectives
The purpose of this project is getting all the team members working with RUP with confidence.
For a list of deliverables, see the Development Case
Assumptions and Constraints
The project will not take more than 6hrs/day to each member of the team.
Is assumed that no other project will interfere with this project.
Project Deliverables
See development case
Evolution of the Software Development Plan
At the end of the elaboration this plan will be updated.
This plan must be revised when any assumptions change.
3.Project Organization
Organizational Structure
The project will have a plain structure, everyone acting as a team member, with one RUP Mentor
External Interfaces
As now the project doesnt need to interface with external groups.
Roles and Responsibilities
Integrated team team with shared responsibilities. (This must be reviewed at the end of elaboration)
Confidential
Page 4 of 7

Version:
1.0
Date: 12/11/2007
4.Management Process
Project Plan
Phase Plan
ID
1
Task Name
I ncep ti on
Mon Dec 9
6 AM
12 PM
6 PM
Tue Dec 10
12 AM 6 AM
12/10
12 PM
6 PM
Wed Dec 11
12 AM 6 AM
12 PM
6 PM
Thu Dec 12
12 AM 6 AM
12 PM
i ncep ti on ki ck-off
inception kick-off
dev elop v ision
12/10
develop visi on
dev elop business case
12/10
develop busi ness case
identif y actors and use cases
12/11
i denti fy actors and use cases
create use case draf t
12/11
create u se case draft
architecture sy nthesis
12/11
architecture synthesis
LCO Mi l estone
LCO Milestone
12/11
Iteration Objectives
This project will have one iteration per phase, so the objectives of each iteration are reach the milestone
defined by the phase.
Releases
This project will have only one release at the end of construction.
Project Schedule
Phase
Number of
iterations
Start
End
Inception
Day 1
Day 2
Elaboration
Day 3
Day 5+2
Construction
Day 6
Day 7+2
Transition
Day 7
Day 7+1
Project Resourcing
Staffing Plan
Not applicable to this project.
Resource Acquisition Plan
Training Plan
Not applicable to this project. (This project is for training)
Budget
Iteration Plans
Refer to Phase plan.
Project Monitoring and Control
Requirements Management Plan
This project will informally manage requirements.
Confidential
Page 5 of 7
6 PM

Version:
1.0
Date: 12/11/2007
Schedule Control Plan

The RUP mentor in agreement with the team members will change the schedule as required.
Budget Control Plan
Not applicable to this project (dont have budget).
Quality Control Plan
Informal reviews will be executed, and only for the main artifacts..
Measurement Plan
Risk Management Plan
Refer to Risk List document
Close-out Plan
At the end of the project, a meeting will be held to to review all the techniques, tools, or methods. Project
deliverables will be archived to the Knowledge Management repository for future reference.
5.Technical Process Plans

Development Case
Refer to Development Case document
Methods, Tools, and Techniques
The standard guidelines in the RUP for small projects will be used.
Infrastructure Plan
This project will be developed at SampleCo which has appropriate servers and software already installed
Product Acceptance Plan
TBD
6.Supporting Process Plans

Configuration Management Plan
This project will use a single repository as a shared folder, containing the baselines for the projects
artifacts. the baselines will be created at the end of each iteration.
Evaluation Plan
At completion of the project, a meeting will be held to evaluate the product and the lessons learned.
Documentation Plan
Refer to Development Case
Quality Assurance Plan
Confidential
Page 6 of 7

Version:
1.0
Date: 12/11/2007
Problem Resolution Plan

Problems will be resolved by the team members and logged in a Problem Report excel sheet.
Subcontractor Management Plan
Process Improvement Plan
At completion of each phase, a Lessons Learned session will be held to capture improvements to the
process
Confidential
Page 7 of 7

Bos Software Development Plan

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Bos Software Development Plan

Uploaded by

Copyright:

Available Formats

SampleCo

Bizcochos Ordering System

Bizcochos Ordering System

Bizcochos Ordering System

5. Technical Process Plans

6. Supporting Process Plans

Bizcochos Ordering System

Software Development Plan

BOS Development Case

Bizcochos Ordering System

dev elop v ision

dev elop business case

develop busi ness case

identif y actors and use cases

i denti fy actors and use cases

create use case draf t

create u se case draft

Bizcochos Ordering System

Schedule Control Plan

5.Technical Process Plans

6.Supporting Process Plans

Bizcochos Ordering System

Problem Resolution Plan

You might also like