2. Software Requirements Analysis Phase Activities
The covered activities are those performed by personnel working on a program set (the largest single aggregate of software within a [sub]system). Though these activities cluster in the Software Requirements Analysis Phase, they may occur outside this phase in the form of preliminary work during the previous phase(s) or re-work during the succeeding phase(s).
The system hierarchy may contain multiple logical levels. Systems are composed of child systems or subsystems. Each system level except the lowest is called a system. The lowest level is called a subsystem and allocates and requirements to software program sets, hardware assemblies, and operational procedures.
The activities stated below result in intermediate products that are used in later efforts or are parts of deliverable products. Intermediate products are the results of management or technical activities that occur within a phase. For example, intermediate products such as requirements lists, data definitions, and traceability matrices can be packaged as part of a Software Requirements Document (SRD) (deliverable product).
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| Software Requirements Analysis Phase.pdf | application/pdf | 617.98 KB | English | DOWNLOAD! |
Provides definitions
Cover images
Introduction
1. Introduction
1.1 Purpose
This document establishes the JPL Standard for certain activities, products, and reviews that constitute a Software Requirements Analysis Phase. This Standard is subordinate to and supports directives contained in the Level I Software Management Standard (D-4000).