Making the Grade: Decompose

Decompose the domain into sub-domains - loosely-coupled parts of the domain.

In reviewing the Domain Story defined during the Discover phase, we identify the boundaries around parts of the system that contain commonality amongst types of entities and their attributes

Applying Independent Service Heuristics

Next, we'll apply the concept of Independent Service Heuristics to our various subdomains / bounded contexts to help us validate and/or identify any gaps in our defined subdomains.

Grading

1. Sense-check: Could it make any logical sense to offer this thing "as a service"? Yes
2. Brand: Could you imagine this thing branded as a public cloud service (like AvocadoOnline.com 🥑)? Yes
3. Revenue/Customers: Could this thing be managed as a viable cloud service in terms of revenue and customers? Yes
4. Cost tracking: Could the organisation currently track costs and investment in this thing separately from similar things? Yes
5. Data: Is it possible to define clearly the input data (from other sources) that this thing needs? Yes
6. User Personas: Could this thing have a small/well-defined set of user types or customers (user personas)? Yes
7. Teams: Could a team or set of teams effectively build and operate a service based on this thing? Yes
8. Dependencies: Would this team be able to act independently of other teams for the majority of the time to achieve their objectives? Yes
9. Impact/Value: Would the scope of this thing provide a team with an impactful and engaging challenge? Yes
10. Product Decisions: Would the team working on this thing be able to "own" their own product roadmap and the product direction? Yes

Examination

1. Sense-check: Could it make any logical sense to offer this thing "as a service"? Yes
2. Brand: Could you imagine this thing branded as a public cloud service (like AvocadoOnline.com 🥑)? Yes
3. Revenue/Customers: Could this thing be managed as a viable cloud service in terms of revenue and customers? Yes
4. Cost tracking: Could the organisation currently track costs and investment in this thing separately from similar things? Yes
5. Data: Is it possible to define clearly the input data (from other sources) that this thing needs? Yes
6. User Personas: Could this thing have a small/well-defined set of user types or customers (user personas)? Yes
7. Teams: Could a team or set of teams effectively build and operate a service based on this thing? Yes
8. Dependencies: Would this team be able to act independently of other teams for the majority of the time to achieve their objectives? Yes
9. Impact/Value: Would the scope of this thing provide a team with an impactful and engaging challenge? Yes
10. Product Decisions: Would the team working on this thing be able to "own" their own product roadmap and the product direction? Yes

Exam Library

1. Sense-check: Could it make any logical sense to offer this thing "as a service"? Yes
2. Brand: Could you imagine this thing branded as a public cloud service (like AvocadoOnline.com 🥑)? Yes
3. Revenue/Customers: Could this thing be managed as a viable cloud service in terms of revenue and customers? Yes
4. Cost tracking: Could the organisation currently track costs and investment in this thing separately from similar things? Yes
5. Data: Is it possible to define clearly the input data (from other sources) that this thing needs? Yes
6. User Personas: Could this thing have a small/well-defined set of user types or customers (user personas)? Yes
7. Teams: Could a team or set of teams effectively build and operate a service based on this thing? Yes
8. Dependencies: Would this team be able to act independently of other teams for the majority of the time to achieve their objectives? Yes
9. Impact/Value: Would the scope of this thing provide a team with an impactful and engaging challenge? Yes
10. Product Decisions: Would the team working on this thing be able to "own" their own product roadmap and the product direction? Yes

User Management

1. Sense-check: Could it make any logical sense to offer this thing "as a service"? Yes
2. Brand: Could you imagine this thing branded as a public cloud service (like AvocadoOnline.com 🥑)? Yes
3. Revenue/Customers: Could this thing be managed as a viable cloud service in terms of revenue and customers? Yes
4. Cost tracking: Could the organisation currently track costs and investment in this thing separately from similar things? Yes
5. Data: Is it possible to define clearly the input data (from other sources) that this thing needs? Yes
6. User Personas: Could this thing have a small/well-defined set of user types or customers (user personas)? Yes
7. Teams: Could a team or set of teams effectively build and operate a service based on this thing? Yes
8. Dependencies: Would this team be able to act independently of other teams for the majority of the time to achieve their objectives? Yes
9. Impact/Value: Would the scope of this thing provide a team with an impactful and engaging challenge? Yes
10. Product Decisions: Would the team working on this thing be able to "own" their own product roadmap and the product direction? Yes

Reporting

1. Sense-check: Could it make any logical sense to offer this thing "as a service"? Yes
2. Brand: Could you imagine this thing branded as a public cloud service (like AvocadoOnline.com 🥑)? Yes
3. Revenue/Customers: Could this thing be managed as a viable cloud service in terms of revenue and customers? Yes
4. Cost tracking: Could the organisation currently track costs and investment in this thing separately from similar things? Yes
5. Data: Is it possible to define clearly the input data (from other sources) that this thing needs? Yes
6. User Personas: Could this thing have a small/well-defined set of user types or customers (user personas)? Yes
7. Teams: Could a team or set of teams effectively build and operate a service based on this thing? Yes
8. Dependencies: Would this team be able to act independently of other teams for the majority of the time to achieve their objectives? Yes
9. Impact/Value: Would the scope of this thing provide a team with an impactful and engaging challenge? Yes
10. Product Decisions: Would the team working on this thing be able to "own" their own product roadmap and the product direction? Yes