The Software Development Process is the structured approach to developing software for a system or project. There are a number of approaches (see Software Development Approaches) that can be used to include waterfall, spiral and incremental development. These different approaches will focus the testing effort at different points in the development process. However, each is approach composed of the same basic steps of development. The incremental development approach typically forms the basis for software development within the larger systems-level of Evolutionary Acquisition (EA). [1,2]
Software Development Process Steps
The software development process consists of four major steps. Each of these steps is detailed below.
- Step 1: Planning
- Step 2: Implementing
- Step 3: Testing
- Step 4: Deployment and Maintenence
Step #1: Planning
An important task in creating a software program is Requirements Analysis. Customers typically have an abstract idea of what they want as an end result, but not what software should do. Skilled and experienced software engineers recognize incomplete, ambiguous, or even contradictory requirements at this point. Frequently demonstrating live code may help reduce the risk that the requirements are incorrect. Once the general requirements are gathered from the client, an analysis of the scope of the development should be determined and clearly stated. This is often called a Statement of Objectives (SOO). 
Step #2: Implementation
Implementation is the part of the process where software engineers actually program the code for the project.
Step #3: Testing
Software testing is an integral and important phase of the software development process. This part of the process ensures that defects are recognized as soon as possible. It can also provide an objective, independent view of the software to allow users to appreciate and understand the risks of software deployment. Software testing can be stated as the process of validating and verifying that a software program/application/product: [1,2]
- meets the requirements that guided its design and development;
- works as expected; and
- can be implemented with the same characteristics.
Step #4: Deployment and Maintenance
Deployment starts after the code is appropriately tested, approved for release, and sold or otherwise distributed into a production environment. This may involve installation, customization, testing, and possibly an extended period of evaluation. Software training and support are important, as the software is only effective if it is used correctly. Maintaining and enhancing software to cope with newly discovered faults or requirements can take substantial time and effort, as missed requirements may force a redesign of the software. 
Software Development Plan (SDP)
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 software development process should be detailed in the SDP.
Software Development Approaches
The Software Development Approaches below show how the various tasks related to software development can be organized. Typical approaches or paradigms encountered in DoD software development include waterfall, incremental, and spiral as described below. The incremental development approach typically forms the basis for software development within the larger systems-level of Evolutionary Acquisition (EA).
Types of Software Development Approaches
There are three main types of software development approaches. These are:
- Waterfall Approach
- Incremental Approach
- Spiral Approach
Development activities are performed in order, with possibly minor overlap, but with little or no iteration between activities. User needs are determined, requirements are defined, and the full system is designed, built, and tested for ultimate delivery at one point in time. A document-driven approach best suited for highly precedence systems with stable requirements.
The waterfall model is often also referred to as the linear and sequential model, for the flow of activities in this model are rather linear and sequential as the name suggests. In this model, the software development activities move to the next phase only after the activities in the current phase are over. However, like is the case with a waterfall, one cannot return to the previous stage.
Determines user needs and defines the overall architecture, but then delivers the system in a series of increments
(“software builds”). The first build incorporates a part of the total planned capabilities, the next build adds more capabilities, and so on, until the entire system is complete.
A risk-driven controlled prototyping approach that develops prototypes early in the development process to specifically address risk areas followed by an assessment of prototyping results and further determination of risk areas to prototype. Areas that are prototyped frequently include user requirements and algorithm performance. Prototyping continues until high-risk areas are resolved and mitigated to an acceptable level.
During each iteration or loop, the system is explored at greater depth and more detail is added. Appropriate for exploratory projects that are working in an unfamiliar domain or with unproven technical approaches. The iterative nature allows for knowledge gained during early passes to inform subsequent passes. Requires low up-front commitment.
Software Development Process Metrics
Software metrics should be an integral part of the software development processes. Program Management Offices (PMO) should gain insight into proposed metrics during source selection, and developers should commit to the consistent use of those metrics, including collecting, analyzing, and reporting. Metrics chosen for use should be defined in the Software Development Plan (SDP). Software metrics should: 
- Be integral to the developer‘s processes.
- Clearly portray variances between planned and actual performance.
- Provide early detection or prediction of situations that require management attention.
- Support the assessment of the impact of proposed changes on the program.
AcqLinks and References:
- USAF Weapon Systems Software Management Guidebook – 15 Aug 2008
- Mil-STD-498 “Software Development and Documentation” – 5 Dec 1994
- MIL-STD-498 “Application and Reference Guidebook” – 3 Jan 1996
- Software Development Plan Information Outline
- Template: Software Development Plan – SPAWAR