ArchiMate for Portfolio Rationalization Programs

⏱ 5 min read

Executive summary

Portfolio rationalization requires a defensible map from business value to IT spend and risk. ArchiMate provides a consistent language for modeling relationships among business domains, enabling enterprises to represent how capabilities are supported by application services and realized by application components. The ArchiMate standard is positioned to support clear relationship modeling across layers, and capability mapping viewpoints are commonly used to create structured capability overviews that can be heatmapped for investment decisions. ArchiMate training

A rationalization method then overlays portfolio data (cost, lifecycle, risk) onto capability-to-application mappings to identify redundancy and prioritize consolidation. This becomes actionable when the model ties to governance decisions (keep/retire/replace) and to implementation roadmaps (work packages/plateaus), allowing portfolio leaders to see not only the target state but the migration sequence. TOGAF roadmap template

• Modeling pattern: capability → application service → component
• Analytics overlays: cost, risk, lifecycle, usage
• Roadmaps: plateaus, gaps, work packages
• Governance and decision capture
• Pitfalls and anti-patterns

• ArchiMate 3.2 standard framing.
• Capability map viewpoint (heatmap investment use).
• Sparx ArchiMate viewpoint examples.
• ADR concept (decision capture discipline).
• TOGAF governance/compliance concept for portfolio oversight.

The five-step rationalization workflow

Portfolio rationalization is not a one-time cleanup — it is a structured program that uses ArchiMate as the analytical backbone. The workflow follows five steps that progressively build the evidence base for retirement and consolidation decisions. ArchiMate tutorial for enterprise architects

Step 1: Map capabilities. Build a Business Capability map as the stable anchor. Capabilities like "Payment Processing," "Customer Management," and "Regulatory Reporting" exist regardless of which applications support them. This becomes the language that business and IT share for rationalization discussions.

Step 2: Inventory applications. Map every Application Component to the capabilities it supports via Serving relationships. Tag each application with Annual TCO, User Count, Technology Stack, Lifecycle Status, and Business Criticality. This creates a queryable portfolio linked to business value.

Step 3: Score and rank. For each capability with multiple supporting applications, score each application on technical fitness (modern stack, maintainable, scalable) and business alignment (meets requirements, good user satisfaction). Applications with low scores on both dimensions are rationalization candidates.

Rationalization scoring in practice

Step 4: Decide. Each overlapping application gets an explicit decision: Keep (the fittest, most cost-effective option), Retire (the duplicate being decommissioned), Migrate (data and users moving to the kept system), or Replace (both retired in favor of a new solution). Model each decision as an Assessment element linked to the affected Application Components.

Step 5: Execute roadmap. Build Migration views showing the transition from current state to target state. Define Plateaus (stable states during migration), Gaps (what changes between plateaus), and Work Packages (projects that close the gaps). Each plateau must be a viable operational architecture — you cannot retire a system before its replacement is ready.

// jArchi: Find duplicate applications per capability
$("business-function").forEach(function(cap) {
    var apps = [];
    cap.inRels().filter(function(r) {
        return r.type === "serving-relationship";
    }).forEach(function(r) {
        apps.push(r.source.name);
    });
    if (apps.length > 1) {
        console.log("OVERLAP: " + cap.name + " → " + apps.join(", "));
    }
});

Applying these patterns in practice

The value of ArchiMate modeling is realized not through comprehensive coverage of every element type, but through disciplined application of a few core patterns that answer recurring stakeholder questions. Three patterns account for the majority of architecture communication needs. ArchiMate layers explained

The Layered View pattern shows how business processes depend on applications, and how applications depend on infrastructure. Build this view by placing Business Processes at the top, Application Components in the middle, and Technology Nodes at the bottom. Connect them with Serving and Realization relationships. This single view demonstrates cross-layer traceability — when a server is decommissioned, trace upward to see which applications and business processes are affected.

The Cooperation View pattern shows how application components interact through interfaces and data flows. Place the core application in the center and its integration partners around it, connected by Flow relationships labeled with the data exchanged. This view reveals integration dependencies that are otherwise buried in technical documentation.

The Motivation View pattern connects strategic goals to architecture decisions. Stakeholder concerns drive Goals, Goals are realized by Outcomes, Outcomes are enabled by Capabilities, and Capabilities are realized by Application Components. This chain answers the question executives always ask: "Why are we building this?"

If you'd like hands-on training tailored to your team (Sparx Enterprise Architect, ArchiMate, TOGAF, BPMN, SysML, Apache Kafka, or the Archi tool), you can reach us via our contact page.

Frequently Asked Questions

What is enterprise architecture?

Enterprise architecture is a discipline that aligns an organisation's strategy, business operations, information systems, and technology infrastructure. It provides a structured framework for understanding how an enterprise works today, where it needs to go, and how to manage the transition.

How is ArchiMate used in enterprise architecture practice?

ArchiMate is used as the standard modeling language in enterprise architecture practice. It enables architects to create consistent, layered models covering business capabilities, application services, data flows, and technology infrastructure — all traceable from strategic goals to implementation.

What tools are used for enterprise architecture modeling?

Common enterprise architecture modeling tools include Sparx Enterprise Architect (Sparx EA), Archi, BiZZdesign Enterprise Studio, LeanIX, and Orbus iServer. Sparx EA is widely used for its ArchiMate, UML, BPMN and SysML support combined with powerful automation and scripting capabilities.