E N D
1. EA Modelling Guidelines From Capabilities to Services
Version 2.5
2. Strategic Direction The HA’s strategy is to move away from purchasing “islands of technology” to the procurement of modular, loosely-coupled, managed services.
3. Historical system-based architecture
4. Service-Oriented Architecture (SOA)
5. The Service ModelAligning the Business and Technology Perspectives
6. A Layered View (End Game)
7. Relationship to Enterprise Architecture
8. Relationship to MSPBlueprint and TOGAF Stages
9. Relationship to ITILService Management
10. Capability Mapping
11. How the Capability view differs from other Business Architecture views Roots of contemporary performance problems are due to organisationally based operating model
Process models (though an improvement) are not the optimal view or management layer, and they expose “how” business is done
Capabilities manage “what service at what service level” – which is the most stable and concise level for design and management
12. Separation of Concerns
13. What is a Capability?
14. Definition of a Capability
15. Capability Mapping can provide much more relevant information
17. A High Level Capability Map linksInternal Capabilities with ExternalCapabilities
18. Each level of the Capability Map can be decomposed down into more detail
19. Mapping against the EAReference Model
20. Example Capabilities-EARM Mapping
22. Capability Mapping: the idealfoundation for SOA
23. Capability Mapping as the businessfoundation for SOA
24. The Service ModelAligning the Business and Technology Perspectives
25. Inputs to the Service Model
26. 10 steps to service definition
27. How Capability Maps can helpService Design