Enterprise Architecture, Governance, and Alignment Flashcards

A complete vocabulary set covering key Enterprise Architecture definitions, frameworks, strategic alignment concepts, operating models, IT initiatives, and modeling standards from the lecture slides.

Enterprise Architecture (EA)

A holistic approach to understanding, designing, documenting, and managing an enterprise by considering its organizational structure, business processes, information systems, technology, strategy, and their relationships

Lankhorst's Definition of EA

Coherent whole of principles, methods, and models used in the design and realization of an enterprise's organizational structure, business processes, information systems, and infrastructure

Kotusev's Definition of EA

Collection of special documents or artifacts describing organizational aspects from an integrated business and IT perspective to bridge communication between business and IT stakeholders, facilitate information systems planning, and improve business-IT alignment

Bernard's Definition of EA

The analysis and documentation of an enterprise in its current and future states from an integrated strategy, business, and technology perspective

Common Theme of EA Definitions

Emphasis on a holistic and integrated view of the enterprise rather than focusing on one isolated organizational or technical area

Holistic Nature of EA

Considers the enterprise as a whole by connecting different organizational aspects, stakeholders, domains, perspectives, and their relationships

Key Characteristics of EA

Involves inherent complexity, the need for structure, current and future states, continuous evolution, whole-enterprise involvement, mutual understanding of diverse perspectives, and communication

EA as a Process

A continuing lifecycle concerned with designing, using, managing, and changing the enterprise rather than reaching one permanent final state

EA as a Product

Produces mainly documents and artifacts that capture and communicate architectural knowledge about the enterprise

EA Process and Product Relationship

Both the ongoing process of developing and managing architecture and the resulting architectural documents or artifacts

EA Lifecycle Idea, Design, Use, Management

The architecture process moves from an initial idea toward design and use, followed by management and eventual modification or replacement as the enterprise evolves

Difference between EA and SDLC

EA is similar to a lifecycle but differs from SDLC (Software Development Life Cycle) because EA has a whole-enterprise scope and a continuous lifespan, whereas an individual system has a more limited scope and finite lifespan

Major EA Actors

Business executives and business unit managers, IT executives and project teams, EA architects, and external stakeholders

EA Architects

Acts as intermediaries between diverse stakeholders and connect business and IT perspectives while owning and managing EA artifacts and processes

EA Architect Responsibilities

They develop, update, peer-review, and approve artifacts, maintain the EA repository, support EA tools, and establish, run, and optimize EA processes

EA Is Not One-Size-Fits-All

EA cannot use one universal approach for every organization because organizations differ and continuously change, so an approach must remain applicable to the organization's situation and needs

EA Is Not Purely Technical Planning

It isn't limited to technology or IT because it also considers organizational, business, strategic, process, stakeholder, and other enterprise concerns

EA Is Not Just About Artifacts

Isn’t merely the production or maintenance of documents because the practice also involves communication, alignment, decisions, processes, and continuous organizational evolution

EA Cannot Transform Incompetent Decisions

Provides structure, information, and guidance but cannot automatically turn poor organizational decisions or actions into competent ones

EA Is Not One-Time Planning

Does not end after planning one future state because the enterprise continues to evolve and the architecture must be revisited and updated

EA Is Not Technology-Specific

Does not require commitment to one particular technology and is concerned with how technology supports the enterprise rather than focusing on technology for its own sake

EA Is Not About Implementing Frameworks

Frameworks are approaches that may support EA but should only be adopted when appropriate and useful for the organization

EA Is Not Enterprise Modeling or Engineering

EA is broader than modeling or engineering because modeling focuses on documenting through models while engineering has a more technical and quantitative orientation

Why EA Becomes Complex

Organizations are dynamic socio-technical systems involving many stakeholders, domains, relationships, dependencies, and continuously changing needs

Organizations as Socio-Technical Systems

Organizations are complex, organic, living entities in which social and technical aspects interact and evolve over time rather than systems that can simply be completely engineered and built once

Successful Organizational Evolution

Characterized by well-managed evolution because organizational change is continuous and cannot be completely planned in advance

Similarities of EA and City Planning

EA is analogous to city planning because both involve large-scale systems with many stakeholders, continuous development, multiple concerns, dependencies, and no single permanent final state

EA and Organizational Planning Limitations

Organizations cannot be perfectly planned in every detail because future needs can be anticipated but cannot be described completely in advance

Incremental Organizational Change

Organizations cannot usually be changed entirely at once and instead evolve through incremental modifications, while major changes take time

Multiple Paths to the Future State

There is no single best way for an organization to evolve because different possible paths can lead toward future states

Planning and Stakeholder Perspectives

EA planning must consider multiple concerns, stakeholders, and perspectives and must bring these perspectives together

EA Communication

Communication is essential because different stakeholders and domains have different concerns, terminology, and perspectives that must be understood and aligned

Bottom-Up Alignment

This alignment provides support for incorporating the perspectives and concerns of major stakeholders rather than relying only on a top-down approach

Architectural Domains

Represent different areas or aspects of an organization that are relevant to business and IT and may be treated as distinct sub-architectures

Architectural Domains According to Kotusev and Bernard

Kotusev describes these as organizational aspects important to business and IT, while Bernard describes them as sub-architectures representing distinct functional areas

Integration of Architectural Domains

Very challenging because domains may use different languages, models, standards, stakeholders, and concerns, but integration helps provide a more connected understanding of the enterprise

Common Language in EA

Business and IT stakeholders often use different terminology, and shared terms help different domains communicate and integrate, so to align all parties together…

EA Models

Provide abstract and unambiguous representations of important aspects of the enterprise while limiting unnecessary detail to what is relevant for the intended purpose

Why Multiple Models Are Needed

A single model usually cannot satisfy every stakeholder and purpose, so multiple models may be needed to represent different aspects and perspectives of the enterprise

Architectural Frameworks

These frameworks organize and integrate architectural elements and can support EA, but their use is optional and should depend on whether they are applicable and useful to the organization

EA Drivers

Pressures or organizational conditions that create a need for architectural planning, alignment, structure, or change

Internal EA Drivers

Drivers that arise from within the organization and include organizational alignment, increasing complexity, and the need to coordinate organizational components

External EA Drivers

Drivers that arise outside the organization and may include competitive, regulatory, governmental, economic, or other environmental pressures that affect the enterprise

Organizational Alignment

This alignment ensures that different organizational components and levels work consistently toward shared objectives and that internal capabilities correspond with external needs

Business-IT Alignment

This alignment connects business strategy, business processes, and organizational needs with IT strategy, infrastructure, systems, and capabilities

Strategic Alignment Model

This alignment model by Henderson and Venkatraman connects business strategy, organizational infrastructure, IT strategy, and IT infrastructure to explain alignment between business and IT

Strategic Fit

The alignment between an organization's external strategic direction and its internal organizational and IT infrastructure and processes

Functional Integration

The integration between business processes and IT capabilities or infrastructure so that IT supports and connects with business operations

Four Areas of the Strategic Alignment Model

Business strategy, organizational infrastructure, IT strategy, and IT infrastructure

Nadler's Four Alignment Components

Work, People, Formal Organization, and Informal Organization as components that need to fit together within the organization

Work in Nadler's Model

In Nadler's Model, this refers to the jobs, tasks, roles, and related arrangements through which organizational activities are carried out

People in Nadler's Model

In Nadler's model, this model refers to the employees and individuals who perform organizational work

Formal Organization in Nadler's Model

In Nadler's model, this refers to formal structures, positions, hierarchies, and organizational arrangements

Informal Organization in Nadler's Model

In Nadler's model, this refers to the intangible and social aspects of the organization, including its culture and informal relationships

Vertical Organizational Alignment

This alignment connects higher-level organizational strategy and direction with the people, activities, and organizational levels responsible for carrying them out

Horizontal Organizational Alignment

This alignment concerns consistency across internal processes and their relationship with external customers or stakeholders

EA as a Management Instrument

This provides structured organizing logic for understanding, managing, and developing the enterprise rather than being a static organizational asset

Mission

Describes why an organization exists and expresses its fundamental purpose

Vision

Describes the desired future state or ideal condition that the organization seeks to achieve

Strategy

Describes how the organization intends to realize its mission and move toward its vision

Goals

These are concrete milestones or desired outcomes that translate strategy into more specific targets

Actions

The activities undertaken to achieve organizational goals and put strategy into practice

Culture in EA

This is the organizational context of shared values, behaviors, and intangible characteristics that influence how the enterprise operates and changes

EA and Operations

This provides structure and organizing logic that supports and guides operations while connecting strategic direction with organizational processes and IT

Key Business-IT Discussion Points

The operating model, business capabilities, specific business needs, business processes, and business requirements

Data Integration

Is concerned with whether organizational units share and integrate data and whether information can be maintained consistently across the organization

Operating Model

Defines the desired organization-wide levels of process standardization and data integration and provides a basis for organizing business processes and IT

Two Dimensions of the Operating Model

The operating model is based on process standardization and data integration, with each dimension ranging from low to high

Coordination Operating Model

In the operating model, this combines low process standardization with high data integration and involves decentralized, diverse, but interdependent business units that share important data

Unification Operating Model

In the operating model, this combines high process standardization with high data integration and involves centralized, similar, and interdependent business units with strongly integrated processes and data

Diversification Operating Model

In the operating model, this combines low process standardization with low data integration and emphasizes decentralized units, independence, flexibility, and local autonomy

Replication Operating Model

In the operating model, this combines high process standardization with low data integration and involves decentralized units that are similar but largely independent

Importance of the Operating Model

This model shapes reporting structures and levels of organizational autonomy and represents fundamental considerations that are not expected to change frequently

Business Capability

The general abilities of an organization to perform business activities, supported by the underlying processes, people, knowledge, and resources needed to carry them out. They serve as relatively consistent building blocks of business functions and typically change substantially only when the organization’s core business model changes.

Specific Business Needs

These concerns address a particular business problem through IT in order to achieve improvements and provide a practical discussion point between business and IT

Business Processes

A sequence of activities performed by specific actors with defined inputs and outputs, helping identify needed IT systems and activities that may need to change

Standardization of Business Processes

This is the degree to which business processes are performed consistently across different organizational areas or units

Business Requirements

Detailed functional and non-functional requirements for a specific information system that describe desired system behavior

Planning Horizons of Key Discussion Points

Operating models have a very long-term horizon, business capabilities a long-term horizon, specific business needs a medium-term horizon, business processes a short-term horizon, and business requirements an actionable horizon of about 6–12 months

Strategic Management

These produce high-level business strategy that defines long-term organizational direction through elements such as mission, vision and values, strategic goals and objectives, competitive or environmental analysis, and key performance indicators

Strategic Management Cycle

Iterative and repeating, with organizations revisiting and updating their high-level strategy over successive planning cycles

Balanced Scorecard

A strategic management approach that clarifies vision and strategy through four perspectives: Financial, Customer, Internal Business Processes, and Learning and Growth

Balanced Scorecard Structure

Each Balanced Scorecard perspective can be organized through mission, objectives, and measures, with measures used to assess performance

EA and Balanced Scorecard

EA is especially useful in the Internal Business Processes and Learning and Growth perspectives because it helps structure processes, information, technology, and organizational capabilities

Business Model Canvas

Developed by Osterwalder and Pigneur provides a high-level template for describing new or existing business models and has seven parts arranged in an intuitive layout

Business Architecture

Provides a blueprint and common understanding of an organization and helps align strategic objectives with tactical demands by translating strategy into action

Capability-Based Planning

This focuses first on the capabilities the organization needs or wants to have before determining how those capabilities should be implemented

European Foundation for Quality Management (EFQM)

This provides principles, measures, and indicators for assessing organizational performance against best practices and supports continuous learning, innovation, and improvement

EFQM and Balanced Scorecard

EFQM complements the Balanced Scorecard by providing a broader performance perspective and supporting continuous improvement of organizational objectives and measures

ISO 9001

Outlines criteria for a good quality management system and requires processes to be designed and documented so that their performance can be controlled

ISO 9001 and EA

EA can support ISO 9001 by helping identify and document processes and by providing architectural artifacts useful in the quality-management certification process

Control Objectives for Information and Related Technology (COBIT)

An IT control framework that bridges business risks, control needs, and technical issues while providing control-related guidance, critical success factors, key goal indicators, and a maturity model for IT governance

COBIT and EA

EA focuses on business and IT structures and processes while COBIT focuses on how IT should be organized and controlled, making them complementary governance instruments

IT Infrastructure Library (ITIL)

ITIL is a widely accepted set of best practices for IT service delivery and support that provides guidance on the provision and management of good IT services

COBIT and ITIL Relationship

COBIT identifies control objectives and what should be achieved in IT governance, while ITIL provides guidance on how IT service delivery and support can be implemented

Capability Maturity Model Integration (CMMI)

This enables assessment of the maturity of software engineering processes and provides practices for increasing process maturity through five maturity levels

EA and CMMI

EA provides context, constraints, and guidelines for individual software projects and becomes particularly useful as organizations reach higher process-maturity levels

IT Initiatives

Planned efforts involving IT that address organizational needs, improve business or IT capabilities, respond to urgent demands, or improve the overall IT landscape

Local Initiatives

These initiatives address specific needs within a particular organizational area, may not directly relate to organization-wide strategy, and are proposed bottom-up before being reviewed and prioritized based on their organizational importance

Urgent Initiatives

These initiatives arise from unanticipated and unpredictable business needs, are often triggered by external conditions, and are typically proposed bottom-up because they require timely action