Previous
¶ Requirement Verification
¶ What it is
It is the task to verify that the modelled requirements and designs have been defined correctly. It requires the business analyst and key stakeholders to sign off. This is the basis for production.
¶ Why it is useful
Requirement verification aims to ensure that the requirements, design specifications, and models all meet the quality standards and are usable for the purpose they try to serve.
¶ When to use it
Before the requirements and designs are handed over to the production teams.
¶ How is it done
- Check for compliance with the acceptance criteria and performance standards for business analysis.
- Check for the correct use of modelling notation, templates, or forms
- Check for completeness within each model
- Check that the terminology in the requirement is understandable, especially by its target users.
- Add examples wherever needed.
- Review the verification results and update the requirements if needed
- Finally, iterate the Product Requirements Document as one of the results of the requirements verification
¶ Do's & Don't
Do's
Follow the following criteria for verifying requirements:
- Atomic: independent and self-contained to be understood
- Complete: including all components in the proper level of detail for work to be continued
- Consistent: aligned with the agreed needs and requirement models
- Feasible: feasible enough to investigate further through experiments or prototypes
- Testable: able to be verified that the requirement has been fulfilled
Don't
- Don’t mix requirements verification with requirements validation - the former is to verify if they are aligned with internal stakeholders and can support further work, while the latter is to test and validate with the end users.
- Don’t forget to update the corresponding requirements models and designs, with the verification feedback recorded for future reference.
¶ Tools needed
- Word for requirements documentation
- Miro for discussion and voting
- Excel for checklists of quality control when doing verification on requirements and designs
¶ Example
