What are the six principles of requirements validation?

Involve the right stakeholders, separate finding errors from fixing them, validate from different views, change the documentation type, build artifacts to validate against, and validate repeatedly.

Following these principles increases the quality of validation results:

1. Involvement of correct stakeholders: Right people must participate
2. Separating identification and correction of errors: Find errors first, then fix them (don't mix)
3. Validation from different views: Multiple perspectives catch more issues
4. Adequate change of documentation type: Use different formats (text, diagrams, prototypes)
5. Construction of development artifacts: Build something to validate against
6. Repeated validation: Validate multiple times throughout the project

Validation techniques mapped to principles:

Remember: Validation = "Are we building the right thing?" (vs. Verification = "Are we building it right?")

Go deeper:

• Verification and validation (Wikipedia) — the "right thing" vs. "thing right" distinction and the techniques for each.