Skip to main content
Version: 0.7.0

System

Definition​

A system is a logical application-responsibility boundary that combines components, data, and behavior to support business capabilities.

Boundaries​

A system keeps its identity when its version, technology, or placement changes. It is not a server, repository, or environment instance. Its boundary is defined by accountability, lifecycle, and agreed purpose.

Minimum characteristics​

  • purpose;
  • system class or kind;
  • owner;
  • lifecycle state;
  • criticality when needed.

Relationships​

A system supports capabilities, consists of components, and interacts through integrations. In the startup profile it may be an integration endpoint without component detail.

Example​

SYS-CRM is the customer relationship management system supporting case management.

Common mistakes​

  • creating a system for every environment;
  • treating a library as a system;
  • combining unrelated products solely because one team owns them.