System Design with objectiF RPM

objectiF RPM provides UML and SysML diagrams for data, functions, behavior and interaction to visualize and trace architecture decisions.
Which architecture elements fulfill which requirements? You can answer this central question with the help of architecture models at all times.

from requirements to code

Traceability

Make architecture decisions traceable and obligatory

What are the effects of changing a requirement? This questions always leads in two directions. First: Which stakeholders and which goals are affected? Second: Which components must be adapted? With objectiF RPM, the answer is only a few mouse clicks away.

Because objectiF RPM provides, among other things, the following features:

configurable and filterable real-time queries of the repository
You can directly navigate to the affected elements from every query.

Visualize the relationship of requirements and architecture elements in design models
You can navigate from one diagram element to another diagram or another piece of information.

The requirement diagram is especially helpful here. It shows the way from stakeholders to their requirements to the system elements.

An example of a block diagram of the system architecture: The relationship to requirements is visualized and can easily be traced back.

A requirement diagram with navigable references to the system architecture.

Draft lightweight design models

Create relationships between a requirement and system components with forms.

System design also occurs in agile projects. However, architecture models do not emerge initially, but as they are needed. Defining the system architecture does not automatically mean modelling it with a diagram. With objectiF RPM, you can set focal points and only make graphic representations of as many aspects as you need to.

System elements can be created with forms instead of diagrams. There, they can also be connected to requirements. In this way, you also build traceable and – for example, directly from the forms – navigable paths between requirements and system architecture.