- About Requirements Assistant™
- Some output examples (1)
- Some output examples (2)
- Fuzzy terms
- Reviewing a requirements document
- References requirements engineering
- Useful links on requirements
- Requirements Assistant™ demo
- RAWeb
- White papers
- More info and contact
- Forum
Last update: May, 19th 2014About Requirements Assistant™
Reviewing requirements is recognized as a tedious and important task. It is tedious because reading a set of requirements of any reasonable size takes time, and it is hard to stay alert and remember the relevant information. It is important to review requirements because omissions and inconsistencies impact the success of product development.
Requirements should be complete, consistent, feasible and unambiguous but very seldom these criteria are met. The Requirements Assistant™ is a tool that is designed to meet these criteria in the requirements phase of a project, using text in natural language as input.
How are bad requirements recognized?
Examples:
A user-friendly man-machine interface will be easy to use. The ABC system shall do range tracking and target identification or radar mapping.
Requirements Assistant™ not only analyses requirements at sentence level, it also reviews paragraphs, and the document as a whole.
Adaptable?
Years of experience have shown that the Requirements Assistant™ is easily adapted to different domains of requirements.
Extendable?
When new error types are found during reviews the Requirements Assistant™ can add this knowledge, as a new rule. This update capability of the tool enables the user to incorporate the lessons learned.