01
Model the landscape
Maintain systems, types, hierarchies and relationships as a basis for architecture decisions.
01
Maintain systems, types, hierarchies and relationships as a basis for architecture decisions.
02
Create model views and target drawings for specific tasks, then reconcile changes deliberately.
03
Maintain instances, stages, locations and deployment assignments separately, then review them alongside the architecture.
The following types are examples. Enabled types, names, hierarchies and permitted relations are defined by tenant and template configuration.
Organizational units and areas of responsibility.
End-to-end business processes.
Business capabilities as structural anchors.
Logical system boundaries, such as ERP or MES.
Business roles and user perspectives.
Application models, separate from concrete instances and deployments.
Technical components within an application.
A finer breakdown into functional modules.
Interface objects and integration points.
Modeled target environment for a deployment assignment.
Business or technical data artifacts.
Technical communication between systems.
Data exchanged between components or systems.
Business relationships independent of technology.
Implementation relationships between model elements.
Explicit deployment assignments to nodes.