Examples
The same seven annotations describe products that look nothing alike. What changes is the meaning of subject, context, and responsibility. Usage, execution, and configuration stay the mechanism that keeps every variant understandable.
These six are modeled end to end. The first two are the setups a software house actually operates: a B2B product that is a little different for every customer, and a consumer finance suite where one person acts as several legal entities. The others use the same model for a large distributed platform, a monolith with several versions still in production, a physical product and its parts, and a fleet of devices.
| Example | Subject | Context | Responsibility |
|---|---|---|---|
| B2B SaaS | A business customer | An environment or instance | A module or service |
| B2C finance suite | A person | The legal entity they represent | A financial product |
| Distributed platform | A market | A cell | A service |
| Versioned monolith | A major version still in production | A channel pinned to that version | A module inside the process |
| Physical product | A product model | A trim, a plant, or a vehicle | A subsystem or part family |
| Device fleet | A site | A device | A capability on the device |
Each page has the catalog, the keys, one configuration story, and the questions the model answers on a normal day. Read Annotations first if the words are new, and How to model if you are about to name your own.
42for.net