Skip to main content
Version: 0.7.0

Enterprise profile

Purpose​

The profile is intended for a large or regulated landscape where changes cross many systems and owners and architecture statements must remain verifiable over time.

Full scope​

All 13 object types are used where applicable. In addition:

  • interfaces become the preferred endpoints of integrations;
  • a logical component is separated from each deployment;
  • compute resources and network segments are described concretely;
  • an information object specializes into a business object, data object, and message;
  • ownership, lifecycle, criticality, and current/target are recorded for significant objects and relationships.

Useful questions​

  • How does a business-object change propagate to messages and stores?
  • Which services and commitments are affected by interface retirement?
  • Where does each critical instance run, and through which network zones does it communicate?
  • How does target architecture differ from current, and who owns the transition?

Protection from over-modeling​

The enterprise profile does not mean maximum detail for every object. Depth is determined by the maturity level and area criticality. Unused information creates a false sense of control and quickly becomes stale.