Doing a lot of reading about V&V, I would need to clarify the following.
A lot of definitions (less formal ones found in books) define verification like that:
Verification: The software should conform to its specification.
But then they speak about requirement verification, design verification etc. If I say that these items are "software" in terms of applying the definitions, what should I checked them against? What specification should requirements, which is the basic information, conform to?
And one more thing: shouldn't requirements also be validated? To make sure they meet the customer needs? All texts I have, speak only about SW validation on the end of the development process!
EDIT: Just to make it clearer, my main question is how the definition of verification apply to requirements. The bookss or e.g. ISO 12207:2008 mention that verification is a process that the product reflect the requirements. One of the process is requirements spec review. But how can requirements conform to requirements?