©ian sommerville 2004software engineering, 7th edition. chapter 22 slide 1 verification and...

©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 22 Slide 1

Verification and Validation


Topics covered

Verification and validation planning Software inspections Automated static analysis Cleanroom software development


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.

Verification vs validation


Is a whole life-cycle process - V & V must be applied at each stage in the software process.

Has two principal objectives• The discovery of defects in a system;• The assessment of whether or not the

system is useful and useable in an operational situation.

The V & V process


V& V goals

Verification and validation should establish confidence that the software is fit for purpose.

This does NOT mean completely free of defects.

Rather, it must be good enough for its intended use and the type of use will determine the degree of confidence that is needed.


V & V confidence

Depends on system’s purpose, user expectations and marketing environment• Software function

• The level of confidence depends on how critical the software is to an organisation.

• User expectations• Users may have low expectations of certain

kinds of software.

• Marketing environment• Getting a product to market early may be more

important than finding defects in the program.


Software inspections. Concerned with analysis of the static system representation to discover problems (static verification)• May be supplement by tool-based document and

code analysis Software testing. Concerned with exercising

and observing product behaviour (dynamic verification)• The system is executed with test data and its

operational behaviour is observed

Static and dynamic verification


Static and dynamic V&V

Formalspecification

High-leveldesign

Requirementsspecification

Detaileddesign

Program

Prototype Programtesting

Softwareinspections


Can reveal the presence of errors NOT their absence.

The only validation technique for non-functional requirements as the software has to be executed to see how it behaves.

Should be used in conjunction with static verification to provide full V&V coverage.

Program testing


Defect testing• Tests designed to discover system defects.• A successful defect test is one which reveals the

presence of defects in a system.• Covered in Chapter 23

Validation testing• Intended to show that the software meets its

requirements.• A successful test is one that shows that a

requirements has been properly implemented.

Types of testing


Defect testing and debugging are distinct processes.

Verification and validation is concerned with establishing the existence of defects in a program.

Debugging is concerned with locating and repairing these errors.

Debugging involves formulating a hypothesis about program behaviour then testing these hypotheses to find the system error.

Testing and debugging


The debugging process

Locateerror

Designerror repair

Repairerror

Retestprogram

Testresults

Specification Testcases


Careful planning is required to get the most out of testing and inspection processes.

Planning should start early in the development process.

The plan should identify the balance between static verification and testing.

Test planning is about defining standards for the testing process rather than describing product tests.

V & V planning


The V-model of development

Systemspecification

Systemdesign

Detaileddesign

Module andunit codeand test

Sub-systemintegrationtest plan

Systemintegrationtest plan

Acceptancetest plan

ServiceAcceptance

testSystem

integration testSub-system

integration test

Requirementsspecification


The structure of a software test plan

The testing process. Requirements traceability. Tested items. Testing schedule. Test recording procedures. Hardware and software requirements. Constraints.


The software test plan


Software inspections

These involve people examining the source representation with the aim of discovering anomalies and defects.

Inspections not require execution of a system so may be used before implementation.

They may be applied to any representation of the system (requirements, design,configuration data, test data, etc.).

They have been shown to be an effective technique for discovering program errors.


Inspection success

Many different defects may be discovered in a single inspection. In testing, one defect ,may mask another so several executions are required.

The reuse domain and programming knowledge so reviewers are likely to have seen the types of error that commonly arise.


Inspections and testing

Inspections and testing are complementary and not opposing verification techniques.

Both should be used during the V & V process. Inspections can check conformance with a

specification but not conformance with the customer’s real requirements.

Inspections cannot check non-functional characteristics such as performance, usability, etc.


Program inspections

Formalised approach to document reviews

Intended explicitly for defect detection (not correction).

Defects may be logical errors, anomalies in the code that might indicate an erroneous condition (e.g. an uninitialised variable) or non-compliance with standards.


Inspection pre-conditions

A precise specification must be available. Team members must be familiar with the

organisation standards. Syntactically correct code or other system

representations must be available. An error checklist should be prepared. Management must accept that inspection will

increase costs early in the software process. Management should not use inspections for

staff appraisal ie finding out who makes mistakes.


The inspection process

Inspectionmeeting

Individualpreparation

Overview

Planning

Rework

Follow-up


Inspection procedure

System overview presented to inspection team.

Code and associated documents are distributed to inspection team in advance.

Inspection takes place and discovered errors are noted.

Modifications are made to repair discovered errors.

Re-inspection may or may not be required.


Inspection roles


Inspection checklists

Checklist of common errors should be used to drive the inspection.

Error checklists are programming language dependent and reflect the characteristic errors that are likely to arise in the language.

In general, the 'weaker' the type checking, the larger the checklist.

Examples: Initialisation, Constant naming, loop termination, array bounds, etc.


Inspection checks 1


Inspection checks 2


Inspection rate

500 statements/hour during overview. 125 source statement/hour during

individual preparation.

90-125 statements/hour can be inspected. Inspection is therefore an expensive

process. Inspecting 500 lines costs about 40

man/hours effort - about £2800 at UK rates.

©ian sommerville 2004software engineering, 7th edition. chapter 22 slide 1 verification and...

Documents