Integrated Meta Model for Enterprise Modelling including Strategy, Business Architecture, Risk and Change

How can a single integrated meta model support strategy, business architecture, risk, and change across multiple EA frameworks — and why do existing approaches fall short?

These slides accompany the paper: Integrated Meta Model for Enterprise Modelling including Strategy, Business Architecture, Risk and Change

The major enterprise architecture frameworks each bring something valuable, but none are sufficient on their own. TOGAF covers IT domains reasonably well but lacks the contextual concepts — competitors, legislation, market forces, ecology — essential for genuine strategic planning. ArchiMate is more rigorous and consistent but weak on data modelling and context. BizBOK is focused but narrow. None of them, individually or together, provide a single coherent foundation for the full scope of strategy, business architecture, risk, change, and programme management that large transformation efforts demand.

This paper describes the development of HAL2023, the latest iteration of the Inspired Holistic Architecture Language — built by systematically analysing and synthesising TOGAF 10th Edition, ArchiMate 3.2, BizBOK 11, SABSA, MEMO, DODAF, and the accumulated Inspired consulting models. The result is a large but well-structured integrated meta model, expressed at three levels — rich pictures for executives, conceptual models for architects, and fully attributed models for tooling — and validated across projects in banking, telecommunications, assurance, retail, healthcare, and government. Notable enhancements in this revision include richer contextual coverage, rationalised relationship types, financial aspects, customer journeys, architecture scenarios, and improved integration with risk, governance, and initiative management.

Crucially, the paper is practical as well as theoretical: it explains how the model should be used incrementally rather than exhaustively, with teams populating only what is relevant to current goals — progressively expanding coverage as new questions arise, much like the way an ERP system delivers increasing value as more modules are adopted.

Originally published as a conference paper by Graham McLeod in the PoEM 2023 Companion Proceedings (16th IFIP Working Conference on the Practice of Enterprise Modeling), Vienna, 2023.

Extending and Automating Maturity Models for More Value

How can maturity models be extended beyond a simple rating to deliver recommendations, prioritised actions, and a path forward — and automated to remove the friction of doing so?

These slides accompany the paper: Extending and Automating Maturity Models for More Value

Maturity models are a staple diagnostic tool in enterprise architecture and information systems — but in practice, their value is often squandered. Organisations complete an assessment, receive a score, and are left to figure out what to do next. The friction of collecting data, calculating ratings, and managing results over time further discourages repeated use. This paper tackles both problems: how to extend the model itself to provide genuine guidance, and how to automate the process so that the effort of running an assessment becomes trivial.

The paper presents a generic domain model for maturity assessment, developed and validated at Inspired.org, which supports not just scoring across multiple dimensions but also recommendations tied to each gap between maturity levels, with relative effort ratings and dependency relationships between recommended actions. An algorithm prioritises recommendations by combining score gaps, effort, and dependency order — producing a ranked, actionable improvement plan rather than a list of observations. The domain model was implemented in the EVA platform in approximately two hours, with the full online assessment flow — including Kiviat chart scoring, recommendation presentation, action selection, and Gantt chart export — delivered in under a week. APIs were subsequently added to support integration with partner systems, adding around three days of effort.

The paper concludes with a reflection on Return on Modelling Effort (ROME): working at the domain concept level, rather than writing custom application code, enabled rapid delivery, easy adaptation, and high reuse — making this a compelling case for meta model-driven, low-code approaches to enterprise tooling.

Originally published as a journal article by Graham McLeod in the EMISA Journal (Enterprise Modelling and Information Systems Architectures), with a companion presentation at the Models at Work stream, PoEM 2022.

The Power of Principles

Why are architecture principles the highest-return activity in enterprise architecture — and how do you define good ones?

Architecture principles are among the most powerful tools available to enterprise architects — yet they are frequently underdefined, poorly worded, or neglected altogether. This 2014 presentation by Graham McLeod makes the case that well-crafted principles, spanning business, application, information, and technology domains, represent the highest return on effort of almost any EA activity: a relatively small investment that shapes decisions across the entire organisation for years. Drawing on experience across banking, assurance, and telecommunications, the presentation covers what distinguishes a principle from a rule, how to structure principles effectively using the short name, statement, rationale, and implications format, and how to engage stakeholders in the definition process. A particularly useful concept is the "stealth payload" — the idea that while principle statements tend to be irrefutable, the implications are where the real architectural direction is embedded. The presentation also addresses compliance monitoring, showing how architecture assets can be mapped against principles and tracked over time to drive meaningful governance.

Originally presented by Graham McLeod at the Enterprise Architecture Conference Europe 2014 & Business Process Management Conference Europe 2014, June 2014.

Should Banks Outsource Operations Processing? Drivers, Constraints, and the EA Angle

What drives and constrains outsourcing decisions in corporate and investment banking — and what role should enterprise architects play?

Outsourcing operations processing is a live and recurring challenge for executive leaders in corporate and investment banking — and the decision is rarely as simple as comparing internal and external costs. This 2013 presentation by SJ van der Westhuizen, delivered at the Inspired TOGAF/EA Forum in Johannesburg, draws on research across thirteen banking organisations to map the full set of forces at play, distinguishing clearly between what drives outsourcing and what constrains it.

On the driving side, the research identifies capability maturity, capital preservation, management focus, and the formalising effect of contracts as significant positive forces. On the constraining side, organisational form complexity, responsiveness to change, reputational risk, management culture fit, and capability maturity concerns about prospective vendors all emerge as meaningful brakes. Cost and revenue, often assumed to be the dominant drivers, are shown to be more nuanced than executives typically expect.

A particularly valuable thread running through the presentation is the specific contribution enterprise architecture can make at each decision point — from capability-based planning and CMMI assessment, to operating model design, TOGAF governance frameworks, and the business model canvas. The central conclusion is direct: the greater the level of EA maturity in an organisation, the greater the number of business objectives achievable through outsourcing.

Originally presented by SJ van der Westhuizen at the Inspired TOGAF/EA Forum, Johannesburg, July 2013.

A Business and Solution Building Block Approach to EA Project Planning

How can enterprise architects bring clarity to project scope, release planning, and stakeholder communication across complex, interdependent programmes?

These slides accompany the paper: A Business and Solution Building Block Approach to EA Project Planning

When multiple projects are running in parallel — each with its own business analyst, development team, and agile backlog — it becomes surprisingly easy for scope, dependencies, and release content to become invisible to the people who most need to understand them: sponsors, stakeholders, and programme managers. This paper documents exactly that problem at a rapidly expanding South African telecoms company, where two major projects (Quoting and Billing) were underway with little consensus on scope, no agreed release breakdown, and a growing disconnect between business expectations and development plans.

The solution was a structured building block approach, distinguishing Business Building Blocks (BBBs) — capability-level components independent of technology choices — from Solution Building Blocks (SBBs), representing the actual systems, data sources, and infrastructure chosen to implement them. A facilitated workshop produced a BBB diagram showing capabilities, dependencies, and release groupings at a glance; a release matrix then mapped capability and content coverage to delivery timelines. Both were formalised in a meta model and implemented in the EVA Netmodeler repository, enabling traceability from business requirements through to agile backlogs and programme milestones.

The approach was well received across all stakeholder groups — sponsors, strategists, and programme managers reported that they finally had a clear, shared picture of what each project would deliver and when. The paper includes the full meta model, visual examples, and an honest reflection on adoption challenges, making it a practical reference for any EA function working to improve programme visibility and stakeholder alignment.

Originally published as a conference paper by Graham McLeod, Inspired.org / University of Cape Town, circa 2013–2014.

Engaging Real Business People in Real Business Architecture

Why do business executives avoid enterprise architecture — and how do you get them genuinely engaged?

The complaint is common among IT architects: business executives won't engage with enterprise architecture, leaving the whole effort directionless. But as this 2009 presentation by Graham McLeod argues, the real problem lies with what is typically presented to business people as "business architecture" — a technically framed, detail-heavy, IT-grown discipline that offers little of immediate relevance to the executives who actually own the business. Delivered at The Open Group EA Practitioners Conference in London, the presentation sets out both a diagnosis and a remedy. The diagnosis: most EA has grown upward from IT rather than downward from business strategy, and neither TOGAF nor most frameworks at the time adequately captured the full scope of genuine business architecture — context, markets, products, channels, customers, scenarios, and cross-cutting concerns like cost, risk, quality, and governance. The remedy: a comprehensive business architecture meta model, drawn from Inspired and PROMIS experience across banking, healthcare, assurance, telecommunications, and government, that gives executives models they recognise as their own. A particularly practical section addresses how architects must shift their role — from technical experts presenting conclusions to skilled facilitators asking good questions, holding up a mirror, and ensuring that models and content belong to the business rather than the architecture team. The presentation closes with specific suggestions for how TOGAF should expand its treatment of business architecture.

Originally presented by Graham McLeod at The Open Group EA Practitioners Conference (EAPC), London, UK, April 2009.

Service Orientation in Enterprise Architecture: Beyond Surface-Level Support

How should enterprise architecture frameworks and meta models be extended to provide genuine, deep support for service orientation?

Service orientation reshapes how applications are conceived, how systems are integrated, and ultimately how value is delivered to customers — yet most enterprise architecture frameworks treat it as a technical implementation detail rather than an architectural concern that spans the full enterprise stack. This 2008 presentation by Graham McLeod, delivered in his role as CTO of PROMIS Solutions AG, argues that achieving deep support for service orientation in EA requires rethinking frameworks and meta models from the ground up. The presentation distinguishes carefully between technical, application, information, and business services, and between logical service definitions — independent of technology and implementation — and their physical realisation, insisting that the mapping between these two levels is essential for meaningful planning and governance. A key architectural insight is the treatment of modern applications not as monolithic systems but as malleable bundles of functions exposed as services, where components can be replaced without impacting overall service delivery — a view that has significant implications for how application architecture is modelled. The presentation also addresses what it calls "enrichment": the additional concepts needed to govern services effectively, including intent (benchmarks, goals, objectives), responsibility and ownership, cross-cutting concerns (risk, cost, quality), and built-in computation and analysis. Archimate is proposed as a candidate notation for distinguishing domains and logical versus physical layers, with worked examples showing how service cross-referencing and traceability can be achieved in practice.

Originally presented by Graham McLeod at an Inspired/PROMIS event, December 2008.

Linking Strategy, Enterprise Architecture and Programme Management

How do you create a coherent link between business strategy, enterprise architecture, and programme management — and why does it matter?

Organisations routinely struggle to translate strategic intent into delivered change — not because the strategy is wrong, but because the connections between strategy, architecture, and execution are poorly defined or missing entirely. This presentation by Graham McLeod, drawn from 15 years of cross-industry experience, addresses that gap with a structured framework for integrating strategy, enterprise architecture, and programme management into a coherent whole. Central to the approach is the concept of delta models — architecture views that show the net change required between current and future states, providing accurate scope for projects and a clear communication bridge between strategists, architects, and the project office. The presentation covers the full chain: from understanding current reality and setting architectural principles, through scenario development and filtering, to portfolio selection based on benefit ranking, risk scoring, cost estimation, and dependency mapping. A particularly useful section introduces the concept of organisational APIs — published, stable business service interfaces that facilitate rapid reconfiguration, outsourcing, and partnering, and that bring the discipline of software interface design to the boundary between business units. Case studies from telecommunications, a media group, an international bank, and a major assurer illustrate the approach in practice, showing how the integration of strategy, architecture, and programme management produces better-scoped initiatives, more informed investment decisions, and faster, lower-risk delivery.

Originally presented by Graham McLeod at an Inspired event, 2005.

Enhancing Enterprise Architecture Models with Cost, Quality and Risk Dimensions

How can enterprise architecture models be extended to capture cost, quality, and risk — and why does it matter?

Enterprise architecture models do an excellent job of mapping the structural relationships between business, process, application, information, and technology domains — but they have traditionally said little about cost, quality, and risk, the dimensions most relevant to the executives and managers who need to act on them. This 2003 presentation by Graham McLeod, delivered at the University of Cape Town in collaboration with Promis Solutions AG, makes the case that these dimensions are not separate concerns requiring separate tools — they can be woven directly into existing EA models. Drawing on the Inspired EA framework and its EVA repository, the presentation shows how cost centres can be linked to architecture elements and values derived through declarative formulas, how quality metrics can be attached to products, processes, applications, and platforms, and how risk can be incorporated as a further dimension of the model. A particularly useful insight is that most of the cost elements organisations need are already present in their architecture models — they simply need attributes added and a mechanism for accumulation and apportionment. The result is a single integrated view that allows strategic planners, architects, and business managers to evaluate current positions and future scenarios with proper appreciation for the full implications of their decisions.

Originally presented by Graham McLeod at the University of Cape Town, June 2003.