Software verification and validation activities check the software against its specifications. Every project must verify and validate the software it produces. This is done by:
· checking each software item before it is used as an input to another activity
· ensuring that checks on each software item are done, as far as possible, by someone other than the author
· ensuring that the amount of verification and validation effort is adequate to show each software item is suitable for operational use. Project management is responsible for organising software verification and validation activities, the definition of software verification and validation roles (e.g. review team leaders), and the allocation of staff to those roles.
Verification focuses on the correctness of the system, its outputs and consistency in the context of the designers’ understanding of the requirements specifications, function and performance tests are best for verification testing. The function test takes the integrated system and checks that it performs all functions described in the functional requirements properly. The performance test checks the system against the nonfunctional requirements, that the system is fast enough, secure enough, and reliable enough to satisfy these requirements.
Validation focuses on ensuring the system actually satisfies the users needs and intentions, acceptance and installation tests verify the working system meets these requirements. The acceptance test allows the customer the validate that the system built according to the requirements is actually what they need. The installation test allows the user to test-drive the system in the environment where it will actually be used, further validating that it will work as needed
Whatever the size of project, software verification and validation greatly affects software quality. People are not infallible, and software that has not been verified has little chance of working. Typically, 20 to 50 errors
per 1000 lines of code are found during development, and 1.5 to 4 per 1000 lines of code remain even after system testing
To be Continue Software Verification and Validation Part 2
Related Article
1.What is Software Verification and Validation
1 comment:
each software item is suitable for operational use. Project management is responsible for organising software verification and validation activities.
click here
Post a Comment