Application Portfolio Management Use Case

Objective: Transparency about applications and their business relevancy to improve business support and plan the roadmap to the target landscape. Import data from Excel sheets and ArchiMate XML. combine it and reuse it.

Key Questions

1. What does the overall application landscape look like?
2. In which Applications to invest, which to divest (application lifecycle management)
3. How well are Business Capabilities supported by applications?
4. Who is using Applications where: Do we have support gaps? Do we have redundancies?
5. Who is providing the Application: Is this an effective setup?
6. How does the Application portfolio evolve? Is this in line with our strategic business priorities?

Business Benefits

• Reduce Cost – Through Application rationalization
• Reduce Risk – Through better understanding of Application landscape's functional and technological risk profile
• Increase Agility – Through better support of strategic business demands

How does the overall application landscape look like? (1) A layered view

How does the overall application landscape look like? (2) With interactive domain views

Which servers (in detail) do support a specific application?

Who is the owner of a specific application?

In which Applications to invest, which to divest?

How well are Business Capabilities supported by applications?

Who is using Applications where: Do we have support gaps? Do we have redundancies?

Who is providing the Application: Is this an effective setup?

How does the Application portfolio evolve? Is this in line with our strategic business priorities?

How can I see and edit my imported and manually entered data?

How can I generate or draw an ArchiMate diagram using my data?

Back to Overview Use Cases

Application Landscape

Here is a step-by-step guide of how to create an Application Landscape that can be used for Application Portfolio Management.