Module 6

Software Verification & Validation

Method best to study the module 

• The lecture have to devided the students into a small group for discussion and Q&A session.
• Lecture have to give a lot off question and ask student to do it infront of the class
• Do some Q&A session at the end of the class.        

Suggestion on topics that should be added or dropped from the module.

• There are no suggestion to add or drop in this module.

Suggestion on any other teaching and learning technique to be used using lecture.

• The students must go infront of the class to draw the use cases that included in     this module.this can make student more understand the topic.
• The student must read the module before the class started to get some idea.
• At the end of class,the student must submit the task given by lecture and the lecture must take it as extra mark.

All the lesson learnt

Strategic approach to software testing

•           Verification and validation
•           Organization of software testing
•          Criteria for completing of testing
•          Software testing strategy

                                 i.            Unit testing

                                ii.            Integration testing

                              iii.            Validation testing

                               iv.            System testing

Unit testing.

1. Ø  Interface
2. Ø  Local data structure
3. Ø  Boundary conditional
4. Ø  Independent path
5. Ø  Error handling path

Integration testing

1. Ø  Bottom up integration
2. Ø  Top-down integration
3. Ø  Regression testing
4. Ø  Smoke testing

Validation testing

• Ø  Focuses on uncovering errors at the software requirements level.
• Ø  SRS might contain a ‘Validation Criteria’ that forms the basis for a validation-testing approach
• Ø  Validation test criteria:

§  all functional requirements are satisfied,

§  all behavior characteristics are achieved,

§  all content is accurate and properly presented,

§  all performance requirements are attained, documentation is correct, and

§  usability and other requirements are met.

System testing

• A series of different tests to verify that system elements have been properly integrated and perform allocated functions.
• Type of system testing

1. Ø  Recovery Testing
2. Ø  Security Testing
3. Ø  Stress Testing
4. Ø  Performance Testing
5. Ø  Deployment Testing

Software test documentation

• IEEE 829 2008 Standard for Software Test Documentation

• The documents are

1. Ø  Test Design Specification
2. Ø  Test Case Specification
3. Ø  Test Procedure Specification
4. Ø  Test Item Transmittal Report
5. Ø  Test Log
6. Ø  Test incident Report
7. Ø  Test Summary Report

Test case design

• Focuses on a set of techniques for the creation of test cases that meet overall testing objectives and the testing strategies
• For conventional application, software is tested from two perspectives

Ø                                                      White box testing

Ø                                                       Black box testing

Drawing flow graph

 Muhammad Hazwan Bin Abu Bakar (IS085737)