Please enable JavaScript.
Coggle requires JavaScript to display documents.
Principles of Requirements Validation (Principle 1: Involvement of the…
Principles of Requirements Validation
Principle 1: Involvement of the correct stakeholders
Independence
of the auditor
it should be avoided that the author of a requirement is also the person to validate it.
Internal vs. external auditors
Internal audits are performed by stakeholders that are members of the developing organization and can be used to validate intermediate results or preliminary requirements
Principle 2: Separating the identification and the correction of errors
the flaws identified are documented immediately. After that, each flaw identified is double-checked to determine whether it really is an error.
allows auditors to
concentrate on the identification
Principle 3: Validation from different views
Perspective-based
validation
Principle 4: Adequate change of documentation type
uses the strengths of one documentation type to balance out the weaknesses of other documentation types.
Transcribing a requirement that is already documented in another
form of documentation simplifies finding errors
Principle 5: Construction of development artifacts
Constructing development artifacts aims at validating the quality of requirements that are meant to be the basis of creating design artifacts, test artifacts, or the user manual
Principle 6: Repeated validation
a positive validation of requirements does not guarantee that requirements are still valid at a later point in time
should occur multiple times if
Lots of innovative ideas and technology used in the system
Significant gain of knowledge during requirements engineering
Long-lasting projects
Very early requirements validation
Unknown domain
Requirements that are to be reused