The specification of requirements is the basis for developing and verifying a software system. Requirements describe in detail which functionality and which nonfunctional characteristics of the system (for more details please check ISO 9126) will be implemented in a specific module. aqua requirements are organized in a hierarchical order. We distinguish between top items, middle items and bottom items. The name directly describes the position in the hierarchy, which is displayed graphically in a tree diagram (comparable to Windows File Explorer). Each requirement can be integrated into a project plan and in doing so, it automatically allocates the respective resources (human resources) assigned to the respective requirement. Additionally, the planned time budget is also listed. Based on the defined and documented requirements, you can run reports and data analysis.
Inside the requirement, you can create UML diagrams describing a special process flow. Additionally, aqua provides the option to automatically derive test cases from this diagram. These test cases are automatically connected to the requirement, similarly to “free” test cases which can be manually connected to one or several requirements. Furthermore, aqua supports the connection between test scenarios, requirements and defects.
1. Ribbon bar with context related buttons
2. Index (tree structure) for requirements
3. Requirements details to be specified
4. Requirements text
Ribbon bar Buttons
The ribbon bar in the requirements section shows some additional and for this section specific new buttons. The following table explains the functionality of each button:
Button
Description
Change the status of the requirement.
Add users to get notifications about changes.
See dependencies of items.
View history of items to see who changed what and when.
