described in forms and recorded with a consistent structure
Give structure to requirement descriptions and analyses
Requirement descriptions are created in objectiF RM using a form. This ensures that all requirements have the same structure.
In the requirements form you can:
- enter a descriptive text including diagrams,
- define relationships to other requirements and make them traceable,
- define relationships to stakeholders, goals, use cases, test cases and system components and thereby generate traceability,
- trigger events that lead to a state change for requirements and, if necessary, initiate notifications and actions in a workflow.
In case the requirement form doesn’t correspond to your needs, that’s no problem. In objectiF RM you can expand existing forms with properties or replace them completely with your own forms.
The information entered about requirements and their relationships can be
- evaluated with configurable queries in real time,
- exported to MS Excel as a table
- generated into MS word in the form of a specification document
How are all these elements affected if a stakeholder changes a goal or a requirement? objectiF RM provides the answers to these questions in lists and with direct navigation between dependent artifacts.
The requirement form shows all available information about a requirement from the objectiF RM real-time repository, no matter whether the information was directly entered or generated through modelling.
Model requirements and create traceability
With objectiF RM you can display relationships between requirements and other requirements engineering results in diagrams. objectiF RM provides UML or SysML diagrams, among other methods. These graphic mediums facilitate communication in teams and with stakeholders when analyzing requirements.
Diagrams in objectiF RM are more than images. Modelling means:
- With a few clicks, information about stakeholders, goals, requirements, use cases, test cases, etc., can be mapped graphically in a diagram
- By creating and editing graphic elements in diagrams, new artifacts can be generated in the repository of objectiF RM
- By sketching relationships between elements in diagrams, you can leave “traces” and define paths for navigating between artifacts
The most important way to visualize requirements and their relationships is the UML/SysML requirements diagram. Here are some examples of what can be represented. Each color-coded relationship creates a trace for requirements traceability.
Relationships allow context-orientated navigation, like here in this use case diagram. The answers to questions like “Which requirements are derived from this use case?” “Which stakeholder goals are fulfilled by this use case?” and “Are there test cases for this use case?” are just a mouse click away.
Prioritize requirements in the backlog
All requirements created with a form or within a diagram are automatically displayed in the domain backlog. Backlogs are especially useful for communicating with stakeholders, which is also possible with a browser over the internet.
In the backlog you can:
- create and modify requirements
- create relationships between requirements
- change the state of requirements
- prioritize requirements – the MoSCoW method is used by default
In order to ease the management of large amounts of requirements, you can also apply filters in the backlog view. It’s also possible to structure the backlog by grouping requirements according to properties.
A domain backlog. Relationships between requirements are also visible here. The same symbols are used as in the requirements diagram.
Table: Requirements analysis and requirements modeling
