SWE.4 Software Unit Verification

Commencez. C'est gratuit
ou s'inscrire avec votre adresse courriel
Rocket clouds
SWE.4 Software Unit Verification par Mind Map: SWE.4 Software Unit Verification

1. Purpose: The purpose of the Software Unit Verification Process is to verify software units to provide evidence for compliance of the software units with the software detailed design and with the non-functional software requirements.

1.1. SWE.4.BP1: Develop software unit verification strategy including regression strategy.

1.1.1. Define Test strategy for Unit Testing and Regression strategy. Test Strategy should cover - Test methods used to verify the Software Design, Test data that needs to be used for testing derived from Software Detailed Design, Test Coverage Goals, Entry / Exit criteria for Software Detailed Design and approach to handle failed test cases as part of Regression and static verification (Handling the MISRA errors and warnings)

1.1.2. Outcomes: Test plan

1.2. SWE.4.BP2: Develop criteria for unit verification

1.2.1. Develop Test specification for verifying the Software Detailed Design. Define Acceptance criteria for Software Unit Testing completion and goals for ex: Test coverage should be 80%, MISRA warnings <=2 etc..

1.2.2. Outcomes: Test Specification

1.3. SWE.4.BP3: Perform static verification of software units.

1.3.1. Perform Static verification using Polyspace and ensure compliance to MISRA standards. Ensure that all Warnings and Errors are reported in test report and communicated to Software Engineers.

1.3.2. Outcomes: Review record,Test results, Analysis report

1.4. SWE.4.BP4: Test software units.

1.4.1. Execute the test cases identified in the test specification and verify the .exe files and capture the test results in test summary report. For Failed test cases perform Regression testing as per strategy

1.4.2. Outcomes: Review record,Verification results, Test results

1.5. SWE.4.BP5: Establish bidirectional traceability

1.5.1. Traceability between Software units and static verification test results / Software detailed design and software unit test spec / Unit test spec and test results

1.5.2. Outcomes: Traceability record, Review record

1.6. SWE.4.BP6: Ensure consistency

1.6.1. Traceability between Software units and static verification test results / Software detailed design and software unit test spec / Unit test spec and test results

1.6.2. Review of the Test spec and Test results

1.6.3. Outcomes: Traceability record and Review record

1.7. SWE.4.BP7: Summarize and communicate results

1.7.1. Communicate the Unit test results to all stakeholders - Test summary report should be consolidated and communicated

1.7.2. Outcomes: Communication record

1.8. Sample Work Products

1.8.1. Test Plan

1.8.2. Test Specification