Work Product (Artifact): Software Development Plan
var defaultQueryStr = '?proc={C85C9CC0-AD92-46C9-85BA-4C0672D6571E}&path={C85C9CC0-AD92-46C9-85BA-4C0672D6571E},{22B90B6F-6F9F-41CF-9A05-8F64BF39CD36},_CaSi_xi2Edq_uI8xTPML6g';
var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=null;
contentPage.preload(imgPath, backPath, nodeInfo, defaultQueryStr, false, true, false);
Work Product (Artifact): Software Development Plan
This artifact is a comprehensive, composite artifact that gathers all information required to manage the project. It encloses a number of artifacts developed during the Inception phase and is maintained throughout the project.
Purpose
The purpose of the Software Development Plan is to gather all of the information necessary to control the project. It
describes the approach to the development of the software, and is the top-level plan generated and used by the managers
to direct the development effort.
The following people use the Software Development Plan:
The project manager, to plan the project schedule and resource needs, and to track progress against the
schedule.
Project team members, to understand what they need to do, when they need to do it, and what other activities
they are dependent upon.
Main Description
The Software Development Plan encloses a number of artifacts developed during the Inception phase and is maintained
throughout the project.
Properties
Optional
Planned
Illustrations
Templates
Software Development Plan (Informal)
Examples
CSPS Software Development Plan - Elaboration Phase
Tailoring
Representation Options
There are situations when a standard is called out in a contract that stipulates the outline and contents of a Software
Development Plan. In this case, you would use that instead of the proposed outline shown in the HTML template, but you
should form a clear mapping of the information requirements of that standard to the outline in the template provided.
Additional Information
Good software development plans evolve. A useful Software Development Plan is periodically updated (it is not stagnant
shelfware), and it is understood and embraced by managers and practitioners.
The Software Development Plan is the defining document for the project's process. Prepare a single Software Development
Plan that:
complies with organizational standards for content
complies with the contract (if any)
provides traceability to, or waivers from, contract and organization requirements
is updated at each major milestone
evolves along with the design and requirements
A standard format promotes:
reuse of processes, methods, experience, and people
accountability for organizational expectations
homogeneous process objectives
A key discriminator of a good Software Development Plan is its conciseness, lack of philosophy, and focus on meaningful
standards and procedures.
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
contentPage.onload();
contentPage.processPage.fixDescriptorLinks();
Wyszukiwarka
Podobne podstrony:
rup project repository?215460rup project planFC81CDrup project management discipline?03DA84rup project plan?9CA030rup project managerY31915Brup project repository?932821więcej podobnych podstron