| |
|
SWE.5.BP3 Develop specification for software integration test |
SWE.5.O.3 A specification for software integration test according to the software integration test strategy is developed that is suitable to provide evidence for compliance of the integrated software items with the software architectural design, including the interfaces between the software units and between the software items |
| |
|
SWE.5.BP2 Develop software integration test strategy includingregression test strategy |
SWE.5.O.2 A software integration test strategy including the regression test strategy is developed to test the software unit and software item interactions |
| |
|
SWE.5.BP5 Select test cases |
SWE.5.O.5 Test cases included in the software integration test specification are selected according to the software integration test strategy, and the release plan |
| |
|
SWE.5.BP4 Integrate software units and software items |
SWE.5.O.4 Software units and software items are integrated up to a complete integrated software according to the integration strategy |
| |
|
SWE.5.BP1 Develop software integration strategy |
SWE.5.O.1 A software integration strategy consistent with the project plan, release plan and the software architectural design is developed to integrate the software items |
| |
|
SWE.5.BP6 Perform software integration test |
SWE.5.O.6 Integrated software items are tested using the selected test cases and the results of software integration test are recorded |
| |
|
SWE.5.BP7 Establish bidirectional traceability |
SWE.5.O.7 Consistency and bidirectional traceability are established between the elements of the software architectural design and the test cases included in the software integration test specification and between test cases and test results |
| |
|
SWE.5.BP8 Ensure consistency |
SWE.5.O.7 Consistency and bidirectional traceability are established between the elements of the software architectural design and the test cases included in the software integration test specification and between test cases and test results |
| |
|
SWE.5.BP9 Summarize and communicate results |
SWE.5.O.8 Results of the software integration test are summarized and communicated to all affected parties |
| |
|
01-03 Software item |
SWE.5.O.4 Software units and software items are integrated up to a complete integrated software according to the integration strategy |
| |
|
01-50 Integrated software |
SWE.5.O.4 Software units and software items are integrated up to a complete integrated software according to the integration strategy |
| |
|
08-50 Test specification |
SWE.5.O.3 A specification for software integration test according to the software integration test strategy is developed that is suitable to provide evidence for compliance of the integrated software items with the software architectural design, including the interfaces between the software units and between the software items |
| |
|
08-50 Test specification |
SWE.5.O.5 Test cases included in the software integration test specification are selected according to the software integration test strategy, and the release plan |
| |
|
08-52 Test plan |
SWE.5.O.1 A software integration strategy consistent with the project plan, release plan and the software architectural design is developed to integrate the software items |
| |
|
08-52 Test plan |
SWE.5.O.2 A software integration test strategy including the regression test strategy is developed to test the software unit and software item interactions |
| |
|
13-04 Communication Record |
SWE.5.O.8 Results of the software integration test are summarized and communicated to all affected parties |
| |
|
13-19 Review Record |
SWE.5.O.7 Consistency and bidirectional traceability are established between the elements of the software architectural design and the test cases included in the software integration test specification and between test cases and test results |
| |
|
13-22 Traceability record |
SWE.5.O.7 Consistency and bidirectional traceability are established between the elements of the software architectural design and the test cases included in the software integration test specification and between test cases and test results |
| |
|
13-50 Test result |
SWE.5.O.6 Integrated software items are tested using the selected test cases and the results of software integration test are recorded |
| |
|
13-50 Test result |
SWE.5.O.8 Results of the software integration test are summarized and communicated to all affected parties |
| |
|
17-02 Build list |
SWE.5.O.4 Software units and software items are integrated up to a complete integrated software according to the integration strategy |
| |
|
17-02 Build list |
SWE.5.O.7 Consistency and bidirectional traceability are established between the elements of the software architectural design and the test cases included in the software integration test specification and between test cases and test results |
