Skip to content
GitHubLinkedIn

Service aspect

The service aspect describes a system (and its containers/components) in terms of the value it delivers: outcomes, users, and business rules.

  • Who uses the system, and for what outcomes?
  • What is in scope vs out of scope?
  • Which business rules and constraints shape the design?
  • Ownership and decision rights for priorities and change.
  • Roles that represent users and stakeholders.
  • How work is sliced and accepted (clear “done” definitions).
  • How trade-offs are recorded and revisited.
  • Domain/process models and explicit business rules.
  • API/service contracts that make capabilities consumable.