Verification and Validation During System Maintenance

Hello! Good to see you here
Today, we are going to discuss software verification and validation during the testing phase.

During maintenance phase of the Software Development Life Cycle, verification and validation procedures are also carried out using a maintenance plan.

Although it sounds kind of off-key to continue to carry out verification and validation for a completed software project, especially for me coming from a project management background, it’s still makes some sense.

This is because  there may be some changes or improvemenst that may occur during the maintenance phase as needed.

Software Maintenance Plan
This is one important tool used during maintenance. This contains things like:

  • bug reports and error logs
  • Software change records
  • Maintenance records

Some of the techniques used here includes
Data collection and analysis
Effect analysis
Program Slicing: This is one

What is Program Slicing
This is a situation such that only a part of the program is taking into consideration during the debugging process. The basis for slicing is to select statements form an executable subprogram that influence the value of slicing criteria which is given by C:
C = (V,I)
where V is a subset of the program variables and I is a statement selected from the program.

Static slicing results in smaller more manageable program that are easier to test
Backward slice is used to determine the statements that have an influence on an  erroneous value
Forward slice is used to determine the statements that are influenced by an erroneous value.
(Static Slicing is explained more in this video)

Dynamic Slicing
In case of dynamic slicing, the slicing is carried out based on the program path executed in case of a given input