Most system test efforts focus on achieving stated program requirements. However, frequently, critical systems require a level of capability validation that goes beyond the developer product assessment activities. For these critical systems, the V&V effort expands to include the development and application of an independent test environment, used to isolate and separately execute the targeted critical software. The independent team is completely segregated from the developer test efforts and must not be compromised by any of the following nominal developer/IV&V -engagement tendencies:
A major focus of independent testing is to prove the robustness of the software. Initially, the V&V team generates a test plan based on potential risks in the software from the V&V risk and hazards analysis. The plan identifies the effort required to support an independent testing activity. The V&V team develops test cases that stress software requirements at their limits (i.e., throughput, boundary conditions, etc.) to verify that such cases are dynamically handled properly by the deliverable software. After the plan and test cases are approved, the V&V team executes the testing and analyzes the results. The final report includes evidence of the software performance during this testing exposing any defects, risks, or limitations.
Because of the isolated nature of independent testing, unique test environments are required to achieve the assessment objectives. Therefore, the independent test team comprises of both test and software team members.
GreenDart has successful experience developing and executing independent test efforts. How can we help you?
Author: Bedjanian
Comments