O. vs. BP. vs. WP. - SWE.1 Software Requirements Analysis ()
O. vs. BP. vs. WP. - SWE.1 Software Requirements Analysis
SWE.1.O.1 The software requirements to be allocated to the software elements ofthe system and their interfaces are defined
SWE.1.O.2 Software requirements are categorized and analyzed for correctness and verifiability
SWE.1.O.3 The impact of software requirements on the operating environment is analyzed
SWE.1.O.4 Prioritization for implementing the software requirements is defined
SWE.1.O.5 The software requirements are updated as needed
SWE.1.O.6 Consistency and bidirectional traceability are established between system requirements and software requirements; and consistency and bidirectional traceability are established between system architectural design and software requirements
SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact
SWE.1.O.8 The software requirements are agreed and communicated to allaffected parties
SWE.1.BP3 Analyze software requirements
SWE.1.BP2 Structure software requirements
SWE.1.BP5 Develop verification criteria
SWE.1.BP4 Analyze the impact on the operating environment
SWE.1.BP1 Specify software requirements
SWE.1.BP6 Establish bidirectional traceability
SWE.1.BP7 Ensure consistency
SWE.1.BP8 Communicate agreed software requirements
11-04 Product release package
13-19 Review Record
13-21 Change control record
13-22 Traceability record
15-01 Analysis report
17-08 Interface requirements specification
17-11 Software requirements specification
17-50 Verification criteria
Overview - Process Reference Model
Overview - SWE.1 Software Requirements Analysis
SWE.1.BP3 Analyze software requirements SWE.1.O.2 Software requirements are categorized and analyzed for correctness and verifiability
SWE.1.BP3 Analyze software requirements SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact
SWE.1.BP2 Structure software requirements SWE.1.O.2 Software requirements are categorized and analyzed for correctness and verifiability
SWE.1.BP2 Structure software requirements SWE.1.O.4 Prioritization for implementing the software requirements is defined
SWE.1.BP5 Develop verification criteria SWE.1.O.2 Software requirements are categorized and analyzed for correctness and verifiability
SWE.1.BP5 Develop verification criteria SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact
SWE.1.BP4 Analyze the impact on the operating environment SWE.1.O.3 The impact of software requirements on the operating environment is analyzed
SWE.1.BP4 Analyze the impact on the operating environment SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact
SWE.1.BP1 Specify software requirements SWE.1.O.1 The software requirements to be allocated to the software elements ofthe system and their interfaces are defined
SWE.1.BP1 Specify software requirements SWE.1.O.5 The software requirements are updated as needed
SWE.1.BP1 Specify software requirements SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact
SWE.1.BP6 Establish bidirectional traceability SWE.1.O.6 Consistency and bidirectional traceability are established between system requirements and software requirements; and consistency and bidirectional traceability are established between system architectural design and software requirements
SWE.1.BP7 Ensure consistency SWE.1.O.6 Consistency and bidirectional traceability are established between system requirements and software requirements; and consistency and bidirectional traceability are established between system architectural design and software requirements
SWE.1.BP8 Communicate agreed software requirements SWE.1.O.8 The software requirements are agreed and communicated to allaffected parties
11-04 Product release package SWE.1.O.8 The software requirements are agreed and communicated to allaffected parties
13-19 Review Record SWE.1.O.6 Consistency and bidirectional traceability are established between system requirements and software requirements; and consistency and bidirectional traceability are established between system architectural design and software requirements
13-21 Change control record SWE.1.O.5 The software requirements are updated as needed
13-21 Change control record SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact
13-22 Traceability record SWE.1.O.1 The software requirements to be allocated to the software elements ofthe system and their interfaces are defined
13-22 Traceability record SWE.1.O.6 Consistency and bidirectional traceability are established between system requirements and software requirements; and consistency and bidirectional traceability are established between system architectural design and software requirements
15-01 Analysis report SWE.1.O.2 Software requirements are categorized and analyzed for correctness and verifiability
15-01 Analysis report SWE.1.O.3 The impact of software requirements on the operating environment is analyzed
15-01 Analysis report SWE.1.O.4 Prioritization for implementing the software requirements is defined
15-01 Analysis report SWE.1.O.7 The software requirements are evaluated for cost, schedule andtechnical impact
17-08 Interface requirements specification SWE.1.O.1 The software requirements to be allocated to the software elements ofthe system and their interfaces are defined
17-08 Interface requirements specification SWE.1.O.3 The impact of software requirements on the operating environment is analyzed
17-11 Software requirements specification SWE.1.O.1 The software requirements to be allocated to the software elements ofthe system and their interfaces are defined
17-50 Verification criteria SWE.1.O.2 Software requirements are categorized and analyzed for correctness and verifiability