Skip to main content
Version: 0.7.0

Stable-business profile

Purpose​

The profile connects a working IT landscape to stable products and operations. It suits a company with several teams, formal services, and a need to coordinate changes across organizational boundaries.

Required extension​

Compared with a startup, these become independent objects:

  • channel;
  • process;
  • capability;
  • information object;
  • system and component as different decomposition levels;
  • integration with direction, state, and transferred information.

An interface is introduced for significant contracts. Infrastructure is detailed for critical systems, availability requirements, and incident investigation.

Useful questions​

  • Which systems support a critical capability?
  • Which processes and channels will a system change affect?
  • Who owns the service, information, and integration?
  • Where is information duplicated, and which source is authoritative?

Profile boundary​

There is no need to model every endpoint, pod, or VLAN. If contract, network-zone, current/target, and regulatory governance become ongoing multi-team activities, use the enterprise profile.