Even agile projects need to design systems. However, architecture models do not emerge initially, but as needed. Defining the system architecture does not automatically mean modelling it with a diagram. With objectiF RPM, you set focuses and only graphically map the aspects that you need.
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.