CHAP 9 (REQUIREMENTS VALIDATION AND NEGOTIATION) (RISK NON VALID…
CHAP 9 (REQUIREMENTS VALIDATION AND NEGOTIATION)
RISK NON VALID REQUIREMENT
Subsequent errors in planning, architecture, design, test, implementation
Conflicts are not resolved.
Late error detection at during acceptance.
Client stop trusting the supplier
Schedule and budget overrun.
ASPECT OF RE
No premature design decision
Correctness and Adequacy
System border and context are not represented.
It is not evident, which actor triggers the function.
A data object is not defined but used in a function.
No function is defined that would effect the transition between two states.
Language defects exist.
Symbols with non standard notation are used with no explanation.
Table has empty cells.
Few or none quality requirements.
The measurement methods for quality requirements are insufficient or entirely not defined.
Agreed after changes
PRINCIPLES OF RE VALIDATION
Involvement of the correct stakeholders
Separating the identification and the correction of errors
Validation from different views
Adequate change of documentation type
Construction of development artifacts
DEFECT DURING RE CHECK
Superfluous requirements – not needed
TECHNIQUE RE VALID
(informal review, audit/commenting,
Matching of different notations
Focused validation using a checklist
Clear allocation of roles in the team
High error detection rate
Known and accepted rules of the game
Appraisal, no problem resolution
Boosts the team spirit
INSPECTION COMPOSITION OF TEAM
Representative of the area of expertise
Representative of the development team
Representative of the Requirements Engineers
Prototypes (behaviour, design, usability)
PERSPECTIVE BASED READING
Documentation of the conflict resolution
compromise,voting,def of variant, overruling,decision matrix
Avoid repeated treatment of conflicts
Questioning resolutions in case of later issues
Cause of the conflict
Opinions of the stakeholders
Means of resolving the conflict
Decisions and reasons for the decisions