Delivery Process: ENG.4 Software requirements analysis
The purpose of the Software requirements analysis process is to establish the software requirements for the system.

Activity diagram: ENG.4 Software requirements analysis Assess Generic Practices Capability Level 5 Assess Generic Practices Capability Level 4 Assess Generic Practices Capability Levels 1,2 and 3 ENG.4.BP1: Identify software requirements. ENG.4.BP2: Analyze software requirements. ENG.4.BP3: Determine the impact on the operating environment. ENG.4.BP4: Prioritize and categorize software requirements. ENG.4.BP5: Evaluate and update software requirements. ENG.4.BP6: Ensure consistency and bilateral traceability of system requirements to software requirements. ENG.4.BP7: Ensure consistency and bilateral traceability of system architectural design to software requirements. ENG.4.BP8: Communicate software requirements.

As a result of successful implementation of this process:

ENG 4.1 the software requirements to be allocated to the software elements of the system and their interfaces are defined

ENG 4.2 the software requirements to be allocated to the software elements of the system and their interfaces are defined

ENG 4.3 the impact of software requirements on the operating environment is evaluated

ENG 4.4 prioritization for implementing the software requirements is defined

ENG 4.5 the software requirements are approved and updated as needed

ENG 4.6 consistency and bilateral traceability are established between system requirements and software requirements; and consistency and bilateral traceability are established between system architectural design and software requirements

ENG 4.7 changes to the software requirements are evaluated for cost, schedule and technical impact

ENG 4.8 the software requirements are baselined and communicated to all affected parties

NOTE: For software requirements specifications, the IEEE-Standard 830- 1998, Recommended Practice for Software Requirements Specifications might be used.



 

Key Considerations
NOTE 1: Requirements may be categorized in terms of feasibility and risk.
More Information
Checklists
Guidelines
Supporting Materials

Licensed Materials - Property of IBM
©  Copyright IBM Corp. 1987, 2015.  All Rights Reserved.