Service aspect
The service aspect describes a system (and its containers/components) in terms of the value it delivers: outcomes, users, and business rules.
What this aspect answers
Section titled “What this aspect answers”- Who uses the system, and for what outcomes?
- What is in scope vs out of scope?
- Which business rules and constraints shape the design?
Organization
Section titled “Organization”- Ownership and decision rights for priorities and change.
- Roles that represent users and stakeholders.
Process
Section titled “Process”- How work is sliced and accepted (clear “done” definitions).
- How trade-offs are recorded and revisited.
Technique
Section titled “Technique”- Domain/process models and explicit business rules.
- API/service contracts that make capabilities consumable.
Operationalization (where to go next)
Section titled “Operationalization (where to go next)”- Services and entry points: Platforms & services
- Architectural intent: Principles & guidelines
- Policies that constrain delivery: How we work → Policies