The developer shall participate in system requirements analysis in
accordance with the following requirements.

Note: If a system is developed in multiple builds, its requirements may not
be fully defined until the final build. The developer's planning should
identify the subset of system requirements to be defined in each build and the
subset to be implemented in each build. System requirements analysis for a
given build should be interpreted to mean defining the system requirements so
identified for that build.

5.3.1 Analysis of user input. The developer shall participate in analyzing
user input provided by the acquirer to gain an understanding of user needs.
This input may take the form of need statements, surveys, problem/change
reports, feedback on prototypes, interviews, or other user input or
feedback.

5.3.2 Operational concept. The developer shall participate in defining and
recording the operational concept for the system. The result shall include all
applicable items in the Operational Concept Description (OCD) DID (see 6.2 ).

5.3.3 System requirements. The developer shall participate in defining and
recording the requirements to be met by the system and the methods to be used
to ensure that each requirement has been met. The result shall include all
applicable items in the System/ Subsystem Specification (SSS) DID (see 6.2 ). Depending on CDRL provisions,
requirements concerning system interfaces may be included in the SSS or in
interface requirements specifications (IRSs).

Note: If a system consists of subsystems, the activity
in 5.3.3 is intended to be performed iteratively with the activities in 5.4
(System design) to
define system requirements, design the system and identify its subsystems,
define the requirements for those subsystems, design the subsystems and
identify their components, and so on.