Artifacts > Project Management Artifact Set > Software Development Plan
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:
Note: Although the RUP recognizes the possible need for an Infrastructure Plan, Documentation Plan, Subcontractor Management Plan, and Process Improvement Plan, they are currently outside of the scope of the process and no explicit guidance is provided for their creation or for their contents.
Developed during Inception phase, this artifact is updated at each major milestone.
The Project Manager is responsible for compiling the enclosed documents and making sure the latest versions are made available through the Software Development Plan.
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.
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:
A standard format promotes:
A key discriminator of a good Software Development Plan is its conciseness,
lack of philosophy, and focus on meaningful standards and procedures.
Rational Unified Process