Build a business capability map that separates what the organisation does from its current systems.
Digital Transformation & Artificial Intelligence
Composable Enterprise Architecture with Packaged Business Capabilities
Prepares enterprise and solution architects to map business capabilities, adopt packaged business capabilities and govern a composable architecture built for rapid recombination.
🗓️Duration5 training days
📚Content4 modules · 8 sessions
🎓On completionAccredited attendance certificate
About the programme
Course Overview
Large application estates tend to freeze an organisation's structure from years ago, so that launching one new business model means renovating half a dozen tightly coupled systems first. Composable enterprise architecture answers this by treating packaged business capabilities as the unit of design: independently deployable, well-documented components that can be assembled and reassembled as strategy changes. This course starts from business capability mapping, so architecture decisions trace back to what the organisation actually does, then applies domain-driven design to set clean boundaries between capabilities and API-led, event-driven integration to connect them without recreating a new monolith. Participants evaluate real and legacy components against the criteria that make a capability genuinely composable, govern ownership and versioning across a growing landscape, and practise assembling existing capabilities into a new customer journey. The final sessions cover measuring whether composability actually shortened time to launch and reduced duplicated licensing, so the architecture's value can be demonstrated, not just asserted.
Expected Learning Outcomes
Assess whether a software component qualifies as a genuinely independent packaged business capability.
Design API-led and event-driven integration that keeps capabilities loosely coupled as they scale.
Apply domain-driven design to set capability boundaries that avoid duplicated logic and shared data conflicts.
Evaluate and rationalise packaged capabilities against interoperability, ownership and total cost of ownership.
Assemble existing capabilities into a new customer journey without commissioning new core development.
Measure time-to-launch and cost outcomes to demonstrate the value of a composable architecture.
Who Should Attend
Enterprise architects planning a move from a monolithic estate to a composable architecture.
Solution architects designing integration between newly adopted packaged business capabilities.
Application portfolio managers rationalising overlapping systems across business units.
Digital platform leads responsible for the API and event infrastructure connecting capabilities.
IT strategy and transformation leads building the business case for composable investment.
Product leaders who need new capability combinations delivered faster than a monolith allows.
Course Modules
Select any module to see its sessions and points.
01Principles of Composable Enterprise Architecture
2 sessions · 8 points
Session 1Business Capability Mapping as the Foundation for Composability
- Build a business capability map that separates what the organisation does from how it currently does it.
- Identify capabilities that are stable and shared against those specific to a single business unit.
- Score existing capabilities on business differentiation and technical maturity to prioritise composability efforts.
- Align the capability map with strategic objectives so architecture investment follows business priority.
Session 2Packaged Business Capabilities Compared With Legacy Modules
- Define the criteria a software component must meet to qualify as a genuine packaged business capability.
- Compare a packaged business capability against a legacy module by its API surface, autonomy and independent deployability.
- Assess a candidate capability's exposed interfaces for completeness before it is adopted into the architecture.
- Identify hidden dependencies that stop a supposedly independent capability from being deployed or replaced alone.
02Designing the Technical Foundation for Composability
2 sessions · 8 points
Session 1API-Led Integration and Event-Driven Communication
- Design an API-led integration layer that separates system, process and experience APIs by responsibility.
- Choose event-driven communication over point-to-point calls where capabilities must stay loosely coupled.
- Version APIs between capabilities so one team's release does not break another capability's integration.
- Apply an API gateway to enforce consistent authentication, throttling and monitoring across capabilities.
Session 2Applying Domain-Driven Design to Define Capability Boundaries
- Use domain-driven design to identify bounded contexts that map cleanly onto individual capabilities.
- Resolve shared data models between bounded contexts before they harden into a source of duplicated logic.
- Define the ubiquitous language for each domain so business and technical teams describe a capability consistently.
- Separate a monolithic application into candidate capabilities using domain boundaries rather than technical layers.
03Governing a Composable Architecture Landscape
2 sessions · 8 points
Session 1Selecting and Rationalising Packaged Business Capabilities
- Evaluate a packaged business capability against composability, interoperability and total cost of ownership.
- Rationalise overlapping applications that deliver the same capability through different, uncoordinated tools.
- Retire a legacy module only after its capability is confirmed present and tested in its replacement.
- Assess vendor lock-in risk for each packaged capability before it becomes embedded in core processes.
Session 2Managing Versioning, Ownership and Technical Debt
- Assign a named owner to each capability, accountable for its interface contract and version roadmap.
- Track technical debt separately for each capability so a stable one does not mask a fragile neighbour.
- Set a deprecation policy for capability interfaces that gives dependent teams time to adapt.
- Review the composable landscape on a fixed cycle to catch capabilities drifting out of architectural alignment.
04Realising Business Agility Through Composability
2 sessions · 8 points
Session 1Assembling and Recomposing Capabilities for New Business Models
- Assemble existing capabilities into a new customer journey without commissioning new core development.
- Recompose capabilities to support a new business model, such as a partner channel or a new market segment.
- Prototype a recomposed process in a test environment before committing it to full production traffic.
- Document reusable capability combinations so future initiatives are assembled rather than rebuilt from scratch.
Session 2Measuring the Agility and Cost Benefit of Composability
- Measure time to launch a new business capability before and after the shift to a composable architecture.
- Track the proportion of new initiatives delivered by recomposing existing capabilities rather than new builds.
- Compare licensing and integration cost of the composable estate against the legacy architecture it replaced.
- Report architecture agility and cost outcomes to sponsors in terms they can weigh against continued investment.
What the participant receives
4 course modules
A structured syllabus
8 training sessions
across 5 days
32 detailed points
Applied, detailed content
Accredited attendance certificate
On completing the programme
Complete your registration
We will contact you within one business day to confirm.
Ready to start?
Reserve your seat and start building the skill.