SOFTWARE REQUIREMENT ENGINEERING
REQUIREMENT VALIDATION
Requirement Document - complete version according to company standards
Organization knowledge - example : skills, people involve in developing the software
Organization standard (implicit / explicit)
List of problems - problems in requirement document
Agreed of documentation actions - response to the document
REQUIREMENT REVIEW
Group of people : analyze & read requirements, look for problems, meet & discuss
Steps : 1. Plan review - select team, time and place for review meeting to be discuss
2. Distribute documents
3. Prepare documents
4. Hold review meeting - comments / problems are discussed, actions agreed
5. Follow up actions - agreed actions have carried out or not
6. Revise document - revise to reflect the actions
PROBLEM ACTIONS
Requirement clarification
Missing information
Requirement conflict - negotiation to resolve the actions
Unrealistic document
REVIEW CHECKING
Reviewers are expensive - involve a number of people spending time reading, checking requirement document
Check document for straight-forward problems.
PROBLEM REPORT
Recheck the requirement document
Update requirement document - send to review team
Review team - involve at least a domain & end user experts
REVIEW CHECKLIST
Understandability
Redundancy
Completeness
Ambiguity
Consistency
Organization
Conformance to standards
Traceability
PROTOTYPING
Provide user documentation & training
Prototypes (validation) - demo requirements & help stakeholders discover problems
- should be complete, reasonably efficient & robust
- cater certain functions
---------------------------------- Order for full e-book ----------------------------------
