Verifying and validating software requirements and design specifications
Every time the output of a process correctly implements its input specification, the software product is one step closer to final verification.
If the output of a process is incorrect, the developers are not building the product the stakeholders want correctly.
To ensure that the product actually meets the user’s needs and that the specifications were correct in the first place.
It may also be referred to as software quality control.
Note: Verification begins before Validation and then they run in parallel until the software product is released.
It would imply to verify if the specifications are met by running the software but this is not possible (e. Only by reviewing its associated artifacts, someone can conclude if the specifications are met.
Building the product right implies the use of the Requirements Specification as input for the next phase of the development process, the design process, the output of which is the Design Specification.
Then, it also implies the use of the Design Specification to feed the construction process.
Verification, from CMMI's point of view, is evidently of the artifact kind.