The service interface design canvas fully describes the elements needed to describe a product.
Edit me
The service interface design canvas fully describes the elements needed to describe a product, service or API delivered by a team. It describes the service from the outside-in including the consumption economics, service level agreements and dependencies.
| Area | Description | Links To |
|---|---|---|
| Dependencies | Other products, services or teams upon which the service depends. May also be used for dependencies on roadmap elements or external products. | Roadmaps, Agile Team Canvas |
| Value Proposition | What are the value elements the service provides. How does it deliver value? How is it measured as successful? This is separate from its quality attributes. | Benefits Card, OKR, Lean Business Case |
| Interactions | The managed interface descriptions to the service including commands, queries, and other access options such as input values. | |
| Consumers | Describes the consumers of the service and how they interact with it. Who or what will use the service? How will they use it? How often will they use it? | |
| Rules/Policies/Conventions | Principles, guidelines, and rules pertaining to using the service. For example any business rules it implements, any common conventions or allowed/disallowed usage. | |
| Quality Attributes | The quality | |
| Information, Validation & Exceptions | ||
| Developer Consumer | ||
| Development, Support & Cost | ||
| Metrics & Analytics | ||
| Consumption Economics |