Professional Documents
Culture Documents
acqnotes.com/acqnote/careerfields/software-development-plan
The Software Development Plan (SDP) describes a developer’s plans for conducting a
software development effort. The SDP provides the acquirer insight and a tool for monitoring
the processes to be followed for software development. It also details methods to be used
and the approach to be followed for each activity, organization, and resource.
The purpose of the SDP is to communicate to team members and stakeholders the approach
to be taken when developing software on a program and how a Program Manager will utilize
direct resources.
1/4
There are six steps associated with the development of an SDP. These six steps are:
Step 1: Form Your Team: Gather the subject matter experts you will need to develop
the SDP.
Step 2: Develop Plan Approach: Figure out how you are going to write the plan and
who is responsible for each section.
Step 3: Develop Outline: Start with an outline or a template. This step needs to
ensure all required information is addressed in the SDP.
Step 4: Prepare Draft: Write the first draft of the SDP.
Step 5: Submit for Review: Submit the first draft to all team members that will utilize
the plan for their feedback.
Step 6: Finalize SDP: Submit the final SDP to the team
There are eight sections that an SDP should have. These sections are:
Section 1: Scope
Section 2: Reference Documents
Section 3: Overview of Required Work
Section 4: Plans of General Software Development Activities
Section 5: Plans of Performing Details Software Development Activities
Section 6: Schedule
Section 7: Organization
Section 8: Notes
2/4
System overview, including system and software architecture.
Overview of required work, including:
Requirements and constraints on the system and software to be developed.
Software products and related deliverables.
Requirements and constraints on project documentation.
The program/acquisition strategy, resources, and schedules
Additional requirements and constraints such as project security, privacy,
methods, standards, interdependencies in hardware and software development.
Known software-specific risks.
Project organization and resources:
Plans for performing general software development activities, including:
Software development processes.
Software Development Approaches
Software development methods.
Software development standards
Reusable software products and Commercial-off-the-Shelf (COTS)
Software types/categories (i.e., operational software, test software, support
equipment software) and associated processes, controls, and documentation.
Handling of critical requirements (such as safety, security, and information
assurance).
Incremental development approach, planning, and management/oversight.
Establishing the system/software engineering environment.
Computer resources utilization and reserve capacity/growth management.
Software-related development processes, including:
Overall development methodology.
Prototyping and simulations.
System requirements analysis and design, including requirements definition and
allocation
Software requirements analysis.
Software preliminary and detailed design.
Software unit integration and testing.
Software component integration and testing.
Supporting processes and information, including:
Software risk management.
Approach to requirements traceability.
3/4
Updated: 6/10/2021
Rank: G1
4/4