5.0 Detailed Requirements

The order of the requirements in this section is not intended to specify the order in which they must be carried out. Many of the activities may be ongoing at one time; different software products may proceed at different paces; and activities specified in early subsections may depend on input from activities in later subsections. If the software is developed in multiple builds, some activities may be performed in every build, others may be performed only in selected builds, and activities and software products may not be complete until several or all builds are accomplished. Figure 1 provides an example of how each activity may be applied in one or more builds. Non-mandatory notes throughout section 5 tell how to interpret each activity on a project involving multiple builds. A project involving a single build will accomplish all required activities in that build. Appendix G provides guidance for planning builds, determining which activities apply to each build, and scheduling these activities.

Activity	Builds
	Build 1	Build 2	Build 3	Build 4
5.1  Project planning and oversight	x	x	x	x
5.2  Establishing a software development environment	x	x	x	x
5.3  System requirements analysis	x	x
5.4  System design	x	x	x
5.5  Software requirements analysis	x	x	x	x
5.6  Software design	x	x	x	x
5.7  Software implementation and unit testing	x	x	x	x
5.8  Unit integration and testing	x	x	x	x
5.9  CSCI qualification testing		x	x	x
5.10  CSCI/HWCI integration and testing		x	x	x
5.11  System qualification testing			x	x
5.12  Preparing for software use	x	x	x	x
5.13  Preparing for software transition				x
Integral processes:
5.14  Software configuration management	x	x	x	x
5.15  Software product evaluation	x	x	x	x
5.16  Software quality assurance	x	x	x	x
5.17  Corrective action	x	x	x	x
5.18  Joint technical and management reviews	x	x	x	x
5.19  Other activities	x	x	x	x

Figure 1: One possible mapping of MIL-STD-498 activities to multiple builds.