1. Verification
- process of checking that software achieves its goal without any bugs
- set of tasks that ensures that the software correctly implements a specific function
- ensure whether the product that is developed is right or not
- verifies whether the developed product fulfills the requirements
- also called Static Testing : checking whether we are developing the right product or not also whether our software is fulfilling the customer’s requirements or not
activities involved in verification
1. Inspection :
- structured, formal, team of 3-6 people express their views, potential faults and critical areas.
- final report is prepared after meeting after incorporating necessary suggestions
2. Review
- informal peer review
- SRs, SDD and program verification
3. walkthrough
- formal, systematic
- Author of the software presents the document to others.
2. Validation
- process of checking that requirements define the system that the customer really want
- confirming that the documented requirements match their stakeholder’s needs
- Quality of SRS is validated if its a good SRS or Not
- overlaps with elicitation and analysis, as it is concerned with finding problems with the requirements.
- The cost of fixing a requirements problem by making a system change is usually much greater than repairing design or coding errors.
it involves
- Validity checks
- consistency checks
- completeness checks
- realism
- verifiability