During software project management, there are four main stages and those are software testing, software engineering and then the verification and validation stage. The verification testing is basically a process to check whether the software system meets its objectives and can carry out the purpose for which it is intended. This process of validating is conducted to check the work done by the development team in building an application.
IMPORTANCE OF VERIFICATION TESTING
- Verification confirms that's the product is built as per the requirements and also makes sure the specifications for the design are followed.
- In order to carry out this stage successfully they introduce virtual users, virtual users are used in this performance testing process, with the help of virtual user generator to provide virtual users and this is done to increase the user load on the application that is being put to test.
- The generator is capable to capture the requests and with this it's able to create a virtual user and go further ahead to read user operations.
- As part of the verification test, they carry out a few other tests such as the volume testing.
This is a non-functional testing also known as flood testing, with is they subject the software to a huge volume of data. This is because when developing only small amounts of data are used and the software deteriorates with the increasing amounts of data as time goes.
While verifying the software, the team of testers get answers to various questions. These are as follows:
- Are we creating the right software?
- Are we building the right product?
BENEFITS OF VERIFICATION TESTING
- Verification testing normally goes hand in hand with validation testing. This ensures a service or product or even system results into meeting the operational needs of the end user.
- Validation involves modelling flow and using simulations for predict any risks or faults or even loopholes which may lead to incomplete verification of the service/product/system.
- To effect this, a set of validation requirements/specifications are used as a criteria list, additional validations are made and these are mainly for the modifications made in order to ensure they meet the original requirements
- Validation is expressed with the term "are you building the right thing" and verification "are you building it right" it is therefore important to have both done even though to a lay man they may sound the like the same processes, its highly possible that a product/service/system can pass when its verified and fail when validated this happens in circumstances where a product is built according to the requirements and specifications but the specifications fail to carry out the end users needs hence little or no work done.
For these procedures to take place that is verification and validation, it is required to have written requirements for both processes and further formal procedures or protocols to determine compliance of the system. After the test goes as a success, the software is found to be 100 percent bug free.