1. Role of The Software Development Plan (SDP)
Relevant
Software
Development
Standards
Specific Project
Implementation S D P
Guidance
on standards
use
Other
Requirements
RFP Requirements
Description of
Vendor’s Software
Management Philosophy
and Development Processes
Rev 3.0

2. Software Development Plan*
Scope
Referenced Documents
Software Development Management
Software Engineering
Formal Qualification Testing
Software Product Evaluations
Software Configuration Management
Other Development Functions
Notes
* in accordance with now obsolete DID-MCCR-80030A (DoD-Std-2167A)

3. Software Development Plan*
1. Scope
2. Referenced documents
3. Overview of required work
4. Plans for performing general
software development activities
5. Plans for performing detailed
6. Schedules and active network
7. Project organization and resources
8. Notes
A. Appendices
* in accordance with J-STD-016 (derived from DI-IPSC-81427, Mil-Std-498)

4. Software Development Plan*
1. Introduction
Overview
Deliverables
Evolution of plan
Reference materials
Definitions & acronyms
2. Project Organization
Process model
Org structure
Boundaries and interfaces
Responsibilities
3. Managerial Processes
Objectives and priorities
Assumptions, dependencies, & constraints
Risk management
Monitoring & controlling mechanisms
Staffing Plan
4. Technical Process
Methods, tools, & techniques
Software documentation
Project support functions
5. Work Packages, Schedules & Budgets
Work packages
Dependencies
Resource requirements
Budget and resource allocation
Schedule
* in accordance with ANSI/IEEE Std

5. Software Development Plan Evaluation Tips
Conformance to RFP requirements
Feasibility of approach
Feasibility of schedules
Adequacy of visibility
Concern for supportability

6. Software Development Plan Key Topics
Risk Management
Timing/Sizing Estimate(s) Rationale
Teaming/Subcontractor Relationships
Skill Levels & Availability
Reusability
Development Methodology
Test Approach & Philosophy
Tools and Metrics
Configuration Control
Development Facilities

7. Software Development Plan Recap
The SDP must match the Life Cycle methodology of the acquirer.
Do not specify specific requirements for the system in the SDP.
The SDP is the primary method of looking into how the developer will accomplish the job.
The SDP can help the integrator to focus on integration
A poorly written SDP is a warning sign.
SDP conformance can be leverage for award fee based contracts