6.4.2

De 12207.

6.4.2
Title : System Requirements Analysis Process
Process group : 6.4
Lower-level process of : none
Replaced by process : none
Specialization of : none
Conforming instance of : none

Purpose : The purpose of System Requirements Analysis is to transform the defined stakeholder requirements into a set of desired system technical requirements that will guide the design of the system.

Activities : 6.4.2.3.1 et 6.4.2.3.2

List of outcomes : As a result of successful implementation of System Requirements Analysis:
a) a defined set of system functional and non-functional requirements describing the problem to be solved are established;
b) the appropriate techniques are performed to optimize the preferred project solution;
c) system requirements are analyzed for correctness and testability;
d) the impact of the system requirements on the operating environment are understood;
e) the requirements are prioritized, approved and updated as needed;
f) consistency and traceability are established between the system requirements and the customer’s requirements baseline;
g) changes to the baseline are evaluated for cost, schedule and technical impact; and
h) the system requirements are communicated to all affected parties and baselined.

NOTE The System Requirements Analysis Process in this International Standard is a specialization of the Requirements Analysis Process of ISO/IEC 15288. Users may consider claiming conformance to the 15288 process rather than the process in this standard.

Faits relatifs à 6.4.2 — Recherche de pages similaires avec +.Voir comme RDF
Id6.4.2  +
IsConformingInstanceOfnone  +
IsLowerLevelProcessOfNone  +
IsPartOf6.4  +
IsReplacedByNone  +
IsSpecializationOfnone  +
OutcomeAs a result of successful implementation of System Requirements Analysis:  +, a) a defined set of system functional and non-functional requirements describing the problem to be solved are established;  +, b) the appropriate techniques are performed to optimize the preferred project solution;  +, c) system requirements are analyzed for correctness and testability;  +, d) the impact of the system requirements on the operating environment are understood;  +, e) the requirements are prioritized, approved and updated as needed;  +, f) consistency and traceability are established between the system requirements and the customer’s requirements baseline;  +, g) changes to the baseline are evaluated for cost, schedule and technical impact; and  + et h) the system requirements are communicated to all affected parties and baselined.  +
TitleSystem Requirements Analysis Process  +
Outils personnels