Enterprise Architecture Value Model - Glossary of Terms and Phrases
Enterprise Architecture Value Model
Glossary of Terms and Phrases
The following terms are used throughout this document with specific meanings as defined below.
| Term | Definition |
| Advisory Architecture | An architecture operating model in which the architecture function reviews, recommends, and governs without holding delivery accountability or operational ownership of the assets it governs. The dominant model at Levels 1 and 2 of the Architecture Value Ladder. |
| Architecture Modeling Tool (AMT) | A specialized software platform used by architecture functions to create, maintain, and publish architectural models, relationship maps, and capability inventories. AMTs carry significant licensing and operational costs and have a consistent track record of being decommissioned when organizations cannot demonstrate clear value from their use relative to their cost. |
| Architecture Value Ladder | The four-level model described in this document — Review, Advise, Embed, and Own — representing the spectrum of organizational positioning available to an architecture function. The model is organized along two axes: Increasing Perceptible Value and Increasing Architectural Accountability and Delivery Presence. |
| At-Risk Initiative | An initiative that has become endangered in flight due to architectural complexity, integration failures, unresolved dependencies, vendor underperformance, or other factors with architectural root causes. Distinguished from High-Risk Initiatives, which carry significant potential for failure before they begin. |
| Chief Architect | The senior leader within the architecture function responsible for architectural direction, standards governance, and the organization and advancement of the architecture team’s capabilities. In the Level 4 model, the Chief Architect co-leads with the Head of Software Engineering the platform engineering and horizontal ownership program. |
| Delivery Accountability | The organizational condition in which a function is measured by and responsible for delivery outcomes — not only the quality of its advisory contributions. A prerequisite for Levels 3 and 4 of the Architecture Value Ladder. |
| Economies of Scale | The cost and efficiency advantages that accrue when a capability, platform, or service is designed, built, and operated to serve many consumers simultaneously rather than being independently built by each. Horizontal ownership by the architecture function naturally produces economies of scale across all vertical portfolios that consume its platforms. |
| Elite Task Force | The organizational posture of the Level 3 embedded practice — a small, senior, delivery-credible team whose explicit mandate is to engage at-risk and high-risk initiatives, take accountability for architectural outcomes, and resolve delivery challenges that other teams cannot. The term conveys both the selective composition and the high-stakes nature of the engagement model. |
| Head of Software Engineering | The senior leader responsible for the software engineering capabilities within the architecture function — the team that builds, operates, and maintains the horizontal platforms the architecture function owns. In the Level 4 model, this role is co-equal in importance to the Chief Architect role. |
| High-Risk Initiative | An initiative that carries significant potential for failure before it begins, due to its strategic stakes, technical complexity, scale, dependency profile, or novelty. High-risk initiatives benefit from early architectural embedding to establish guardrails, surface dependencies, and provide decision authority before the conditions for failure compound. |
| Horizontal Solution | A technology platform, service, capability, or system that serves multiple vertical IT portfolios and business functions simultaneously rather than being dedicated to any single domain. Characterized by cross-portfolio applicability, shared infrastructure, reusable components, and the ability to drive economies of scale across the enterprise. |
| Infrastructure-as-Code (IaC) | The practice of managing and provisioning technology infrastructure through machine-readable configuration files rather than manual processes. A foundational software engineering discipline that enables consistent, repeatable, and version-controlled infrastructure management at scale. |
| IT Portfolio Management | The discipline of governing the enterprise’s IT investments, applications, technologies, people, and resources as a managed portfolio. As used in this document, vertical IT portfolios refer to the domain-specific IT organizations that collectively constitute the enterprise’s IT investment landscape. |
| Perceptible Value | The organizational visibility of a function’s contributions as experienced by the executive leadership and stakeholders who fund it. Distinct from actual value — a function can produce genuinely valuable work while scoring low on perceptible value because that work is invisible at the moments when organizational significance is assessed. |
| Platform Engineering | The discipline of designing, building, and operating internal developer platforms and shared infrastructure that enable engineering teams to deploy, run, and manage applications efficiently at scale. |
| Software Engineering | The application of engineering principles — systems thinking, mathematical rigor, disciplined design, structured construction, and rigorous testing — to the full delivery lifecycle of software systems: design, implementation, build, packaging, deployment, instantiation, operation, administration, and support. Software engineers bring the full-lifecycle technical depth and delivery accountability that the Level 4 architecture function requires. |
| Vibe Coding | An AI-assisted development practice in which developers use large language models to generate, modify, and iterate on code through natural language prompts. When deployed as a horizontal enterprise service owned by the architecture function, Vibe Coding platforms deliver AI-assisted development capabilities at enterprise scale across all vertical IT portfolios. |
| Vertical IT Portfolio | An IT domain organization focused on a specific area of business or technology capability. Vertical portfolios are the consumers of horizontal solutions and the primary stakeholders of the architecture function’s advisory services. At Level 4, the architecture function’s horizontal ownership creates structural interdependence with every vertical portfolio that consumes its platforms. |
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers