Situation
Architecture Fellowship (AF), which is organized by SKL and Inera, has introduced a capability map which should be taken as the structure for presenting business descriptions.
The reason is that it is hard to get a cohesive image of which descriptions exist without risking that the user gets drowned in details. The map structure of the EA tool offers only one option to choose when it comes to how the different descriptions should be sorted, usually it is divided per dimension (process, information, application) but it is also common that it happens based on organizational unit.
Through sorting out per dimenstion, it provides a good overview of the whole which is specially important for information and application. The disadvantage is that it is hard for a specific business to find what is particularly relevant which is time taking and frustrating.
The capability map is considered go be the structure for taking care of this problem.
Problem
- How should the capability map modeled in the EA tool? A capability is a combination of process, organization, information, application and others.
- How does the capability map influence the structure of the EA tool?
- How do we create a beautiful packaging for the intranet so that it is easy to navigate the right business description with the capability map as the starting point?
- It takes time to sort all the descriptions per capability.
Complication
Solution
- Confguration of the EA tool for using Capabilities
- The capability map is modeled in the EA tool.
- Navigation diagram for capabilities in the capability map.
- Sorting of the existing EA diagram.
- Publication of the capability map on the intranet.
Interested?
It is a package of best practices and appliances in other organizations. Read more about Prime Arch Value Package.
Contact Patrik Hallén in aRway if you want to get complementary information, a demo or a cost estimation.