Software Verification and Validation Lecture-02

1. Software Verification and Validation Lecture-02

2. SQA in SDLC • Requirements • Architectural design • Detailed design • Implementation • Testing

3. Requirements Phase • Senior QA/Manager ensures that the user/client requirements are captured correctly • Find out the risks in the requirement and decide how the system will be tested. • Properly expressed as functional, performance and interface requirements. • Review the requirement document and other deliverables meeting the standard • Prepare the formal test plan including the test tools are being used in the project.

4. Architectural Design Phase • Ensure that architectural design meets standards as designated in the Project Plan • Verify all captured requirement are allocated to software components • Verify all the design documents are completed on time according to the project plan and kept in project repository (ER Diagram, Process diagram, Use Case, etc). • Prepare the design test report and submit to the project manager.

5. Detailed Design Phase • Prepare the test objectives from the requirement and design document created. • Design a verification matrix or Check list and update on regular basis • Send the test documents to project manager for approval and keep them in repository

6. Implementation Phase • Verify the results of coding and design activities including the schedule available in the project plan • Check the status of all deliverable items and verify that all are maintaining the standard. • Getting updated with the tools and technologies used in the projects and provide the feedback to the team if any better solution is available. • Complete writing the check list/ test cases to start testing. • Verify that the components are ready to start test or not.

7. Testing Phase • Start testing individual module and stat reporting bugs • Verify that all tests are run according to test plans •  Verify all the bugs available in the bug tracking system are resolved. •  Compile the test reports and verify that the report is complete and correct • Certify that testing is complete according to the plan • Start creating the documentation and verify that all documents are ready for delivery

8. Verification & Validation (V&V) • Verification: "Are we building the product right?" The software should conform to its specification. • Validation: "Are we building the right product?" The software should do what the user really requires.

9. V&V Goals • Verification and validation should establish confidence that the software is fit for its purpose. • This does NOT mean completely free of defects. • Rather, it must be good enough for its intended use. The type of use will determine the degree of confidence that is needed.

10. Static vs Dynamic V&V • Code and document inspections - Concerned with the analysis of the static system representation to discover problems(static v & v) • May be supplement by tool-based document and code analysis • Software testing - Concerned with exercising and observing product behaviour (dynamic v & v) • The system is executed with test data and its operational behaviour is observed

11. Summary • SQA activities in different SDLC phases • Requirements phase • Architectural design phase • Detailed design phase • Implementation phase • Testing phase