| |
|
08-50 Test specification |
SWE.4.O.2 Criteria for software unit verification are developed according to the software unit verification strategy that are suitable to provide evidence for compliance of the software units with the software detailed design and with the non-functional software requirements |
| |
|
08-52 Test plan |
SWE.4.O.1 A software unit verification strategy including regression strategy is developed to verify the software units |
| |
|
13-04 Communication Record |
SWE.4.O.5 Results of the unit verification are summarized and communicated toall affected parties |
| |
|
13-19 Review Record |
SWE.4.O.3 Software units are verified according to the software unit verification strategy and the defined criteria for software unit verification and the results are recorded |
| |
|
13-19 Review Record |
SWE.4.O.4 Consistency and bidirectional traceability are established between software units, criteria for verification and verification results |
| |
|
13-22 Traceability record |
SWE.4.O.4 Consistency and bidirectional traceability are established between software units, criteria for verification and verification results |
| |
|
13-25 Verification results |
SWE.4.O.3 Software units are verified according to the software unit verification strategy and the defined criteria for software unit verification and the results are recorded |
| |
|
13-25 Verification results |
SWE.4.O.5 Results of the unit verification are summarized and communicated toall affected parties |
| |
|
13-50 Test result |
SWE.4.O.3 Software units are verified according to the software unit verification strategy and the defined criteria for software unit verification and the results are recorded |
| |
|
13-50 Test result |
SWE.4.O.5 Results of the unit verification are summarized and communicated toall affected parties |
| |
|
15-01 Analysis report |
SWE.4.O.3 Software units are verified according to the software unit verification strategy and the defined criteria for software unit verification and the results are recorded |
| |
|
SWE.4.BP3 Perform static verification of software units |
SWE.4.O.3 Software units are verified according to the software unit verification strategy and the defined criteria for software unit verification and the results are recorded |
| |
|
SWE.4.BP2 Develop criteria for unit verification |
SWE.4.O.2 Criteria for software unit verification are developed according to the software unit verification strategy that are suitable to provide evidence for compliance of the software units with the software detailed design and with the non-functional software requirements |
| |
|
SWE.4.BP5 Establish bidirectional traceability |
SWE.4.O.4 Consistency and bidirectional traceability are established between software units, criteria for verification and verification results |
| |
|
SWE.4.BP4 Test software units |
SWE.4.O.3 Software units are verified according to the software unit verification strategy and the defined criteria for software unit verification and the results are recorded |
| |
|
SWE.4.BP1 Develop software unit verification strategy including regression strategy |
SWE.4.O.1 A software unit verification strategy including regression strategy is developed to verify the software units |
| |
|
SWE.4.BP6 Ensure consistency |
SWE.4.O.4 Consistency and bidirectional traceability are established between software units, criteria for verification and verification results |
| |
|
SWE.4.BP7 Summarize and communicate results |
SWE.4.O.5 Results of the unit verification are summarized and communicated toall affected parties |
