Session 4

Enterprise
Computing
EMIT-607
Session 4
Dr. Adel Bahaddad
Dbabahaddad10@kau.edu.sa
Part A: The CSVLOD Model of Enterprise Architecture
Session Outlines:  Dimensions for Classifying Enterprise Architecture Artifacts
 Six General Types of Enterprise Architecture Artifacts
 The Resulting CSVLOD Model of Enterprise Architecture
Part B: EA Considerations and Standards
 Considerations as a General Type of Enterprise Architecture
Artifacts
 Specific Enterprise Architecture Artifacts Related to
Considerations
 Standards as a General Type of Enterprise Architecture Artifacts
 Specific Enterprise Architecture Artifacts Related to Standards
Part C: EA Visions and Landscapes
 Visions as a General Type of Enterprise Architecture Artifacts
 Specific Enterprise Architecture Artifacts Related to Visions
 Landscapes as a General Type of Enterprise Architecture Artifacts
 Specific Enterprise Architecture Artifacts Related to Landscapes
2
Executive Master of IT
Part A: The CSVLOD Model of Enterprise Architecture
● Dimensions for Classifying Enterprise
Architecture Artifacts
● Six General Types of Enterprise Architecture

Artifacts
● The Resulting CSVLOD Model of Enterprise

Architecture
3
Part A: The CSVLOD Introduction:
 Widely known process models barely resemble successful EA
Model of Enterprise
practices, then how can an EA practice be conceptualized
Architecture and explained from the process perspective?
 Dimensions for  Previously, we presented the CSVLOD model which
Classifying Enterprise conceptualizes the notion of enterprise architecture as a set
Architecture Artifacts of six general types of EA artifacts:
1. Considerations (e.g. principles and policies).
 Six General Types of 2. Standards (e.g. technology reference models and guidelines).
Enterprise Architecture 3. Visions (e.g. business capability models and roadmaps).
Artifacts 4. Landscapes (e.g. landscape diagrams and inventories).
5. Outlines (e.g. solution overviews and options assessments).
 The Resulting CSVLOD 6. Designs (e.g. various solution designs).
Model of Enterprise
Architecture
4
Part A: The CSVLOD The Stack of EA Domains:
Model of Enterprise
Architecture
 Dimensions for
Classifying Enterprise
 Six General Types of
Enterprise Architecture
Artifacts
 The Resulting CSVLOD
Model of Enterprise
Architecture
5
Part A: The CSVLOD EA as Two States and Roadmap
Model of Enterprise
Architecture  Enterprise architecture consists of three components:
 Current (baseline, as-is, existing, etc.) state
 Dimensions for  Future (target, to-be, desired, etc.) state
Classifying Enterprise  Roadmap (or transition plan)
Artifacts
Model of Enterprise
Architecture
6
Part A: The CSVLOD
Model of Enterprise
Architecture CSVLOD Model
 Dimensions for
 The CSVLOD model is a novel conceptualization of
enterprise architecture from scratch that:
Architecture Artifacts  Emerged from research, not from marketing
 Six General Types of  Supported by evidence from real organizations
Enterprise Architecture  Reflects genuine industry EA best practices
Artifacts  Accurately describes empirical realities of EA
 Fills the critical gap in the EA discipline
Model of Enterprise
Architecture
7
Part A: The CSVLOD
Model of Enterprise
Architecture
 Dimensions for Dimensions for Classifying EA Artifacts
 The key element of the CSVLOD model is the taxonomy for
EA artifacts
 Six General Types of  The first dimension classifies all EA artifacts into rules,
Enterprise Architecture structures and changes
Artifacts  The second dimension classifies all EA artifacts into
 The Resulting CSVLOD business-focused and IT-focused
Model of Enterprise
Architecture
8
Part A: The CSVLOD
Model of Enterprise
Architecture
 Dimensions for Dimension One: What?
Classifying Enterprise  Classifies EA artifacts based on what objects they describe
 All EA artifacts can be classified into:
 Six General Types of  Rules - describe broad global rules defining an organization or its
Enterprise Architecture divisions
Artifacts  Structures - describe high-level structures of an organization or its
parts
 The Resulting CSVLOD  Changes - describe specific proposed incremental changes to an
Model of Enterprise organization
Architecture
9
Part A: The CSVLOD Rules, Structures and Changes
Model of Enterprise
Architecture
 Dimensions for
Artifacts
Model of Enterprise
Architecture
10
Part A: The CSVLOD
Model of Enterprise
Architecture Dimension Two: How?
 Dimensions for • Classifies EA artifacts based on how they describe objects
Classifying Enterprise • All EA artifacts can be classified into:
Architecture Artifacts • Business-focused - tend to be technology-neutral and use business
language (e.g. money, customers, capabilities, business goals,
 Six General Types of competitive advantages, etc.)
Enterprise Architecture • IT-focused - tend to be purely technical and use IT-specific
Artifacts language (systems, applications, databases, platforms, networks,
etc.)
Model of Enterprise
Architecture
11
Part A: The CSVLOD Business- and IT-Focused EA Artifacts
Model of Enterprise
Architecture
 Dimensions for
Artifacts
Model of Enterprise
Architecture
12
Part A: The CSVLOD The CSVLOD Taxonomy and Six Types
Model of Enterprise
Architecture
 Dimensions for
Artifacts
Model of Enterprise
Architecture
13
Part A: The CSVLOD CSVLOD Model of EA
Model of Enterprise
Architecture
 Dimensions for
Artifacts
Model of Enterprise
Architecture
14
Part A: The CSVLOD General Types and Narrow Subtypes
Model of Enterprise  Each general type represents a broad variety of different EA
Architecture artifacts with similar properties and purposes
 Dimensions for  However, for each general type there is a limited set of
Classifying Enterprise widely used narrow subtypes of EA artifacts
Architecture Artifacts  All subtypes of EA artifacts can be grouped into three
categories based on their relative popularity:
 Essential EA artifacts - used in the majority of EA practices
Enterprise Architecture  Common EA artifacts - used in ~25-50% of EA practices
Artifacts  Uncommon EA artifacts - used in approximately ~10-25% of EA
 The Resulting CSVLOD practices
Model of Enterprise  These subtypes of EA artifacts are often used under
Architecture different titles in different organizations
15
2/3/2019 16
Part B: EA Considerations and Standards
● Considerations as a General Type of Enterprise
● Specific Enterprise Architecture Artifacts Related to

Considerations
● Standards as a General Type of Enterprise

● Specific Enterprise Architecture Artifacts Related to

Standards
17
Part B: EA Considerations as an EA Artifact
Considerations and  Considerations describe global conceptual rules and
Standards considerations important for business and relevant for IT
 Considerations as a
General Type of Enterprise  Considerations represent planning decisions on how an
Architecture Artifacts organization needs to work from the IT perspective
 Specific Enterprise  They are developed collaboratively by senior business
Architecture Artifacts executives and architects and then used to influence all
Related to Considerations “downstream” architectural decisions
 Standards as a General  The purpose of all Considerations is to help achieve the
Type of Enterprise agreement on basic principles, values and aims
 The proper use of Considerations leads to improved overall
 Specific Enterprise conceptual consistency between business and IT
Related to Standards
18
Part B: EA Considerations as an EA Artifact Examples
Considerations and  Principles (Essential)
Standards
 Policies (Common)
 Considerations as a
General Type of Enterprise  Conceptual Data Models (Uncommon)
Architecture Artifacts  Analytical Reports (Uncommon)
 Specific Enterprise  Direction Statements (Uncommon)
Related to Considerations
 Standards as a General
Type of Enterprise
 Specific Enterprise
19
Part B: EA Principles Artifacts
Considerations and  Principles are specific Considerations defining global high-
Standards level guidelines influencing all decision-making and
 Considerations as a General planning in an organization
Type of Enterprise  Principles are formulated as brief written statements
Architecture Artifacts defining what is important for an organization
 Specific Enterprise  Principles are very abstract and can be interpreted broadly
Architecture Artifacts depending on the context
 Organizations usually establish ~10-20 guiding Principles
 Standards as a General agreed by senior business and IT leaders
Type of Enterprise
20
Part B: EA Principles (Schematic View)
Considerations and  Principles act as
Standards underpinning drivers
 Considerations as a General of all IT-related
Type of Enterprise decision-making:
Architecture Artifacts  Newly developed
EA artifacts
 Prioritize proposed
Architecture Artifacts IT initiatives
Related to Considerations  Decision on
 Standards as a General implementation
options
Type of Enterprise
21
Part B: EA Policies
Considerations and  Policies are specific Considerations defining overarching
Standards norms typically of a restrictive nature providing compulsory
 Considerations as a General prescriptions in certain areas
Type of Enterprise  Policies can be considered as a common subtype of
Architecture Artifacts Considerations often found in EA practices
 Specific Enterprise  They can be called security policies, cloud policies, access
Architecture Artifacts policies, etc.
 Policies are formulated as textual descriptions usually
 Standards as a General specifying what an organization must or must not do
Type of Enterprise
Architecture Artifacts  Policies are rather clear, unambiguous and not a subject of
much debate, reinterpretation or controversy
22
Part B: EA Policies (Schematic View)
Considerations and  Policies act as limiting
Standards constraints of all IT-
 Considerations as a General related decision-
Type of Enterprise making processes
 strict and compulsory,
deviations from them
Related to Considerations are often not
discussable
Type of Enterprise  Adherence to Policies
Architecture Artifacts is often checked and
 Specific Enterprise ensured during the
Architecture Artifacts approval of other more
Related to Standards specific EA artifacts
23
Part B: EA Conceptual Data Models
Considerations and  high-level data-focused rules
Standards shaping all architectural decisions
 Considerations as a General related to data management
Type of Enterprise  Conceptual Data Models
Architecture Artifacts influence the logical design of all
business applications, storage
 Specific Enterprise systems and integration platforms
Architecture Artifacts manipulating with data
Related to Considerations  All IT systems should be
 Standards as a General compliant with the established
Type of Enterprise Conceptual Data Models
Architecture Artifacts  Conceptual Data Models typically
 Specific Enterprise also provide the basis for
developing more detailed, low-
Architecture Artifacts level and platform-specific Logical
Related to Standards Data Models 24
Part B: EA Analytical Reports
Considerations and  Analytical Reports are specific Considerations providing
Standards executive-level analyses of relevant technology trends and
 Considerations as a General their potential impact on the business
Type of Enterprise  Analytical Reports can be considered as an uncommon
Architecture Artifacts subtype of Considerations used relatively rarely
 Specific Enterprise  They can be called whitepapers, position papers, strategy
Architecture Artifacts papers, etc.
 Analytical Reports reflect a business-oriented analysis of the
 Standards as a General organizational technology environment
Type of Enterprise
Architecture Artifacts  Analytical Reports describe the influence of technology
trends as well as the desirable reaction on these trends
25
Part B: EA Analytical Reports (Schematic View )
Considerations and
Standards
 Considerations as a General
Type of Enterprise
Type of Enterprise
26
Part B: EA Direction Statements
Considerations and  Direction Statements are specific Considerations describing
Standards conceptual messages communicating major organization-
 Considerations as a General wide decisions with profound impact
Type of Enterprise  Direction Statements can be considered as an uncommon
Architecture Artifacts subtype of Considerations
 Specific Enterprise  They can be called architecture strategies, governance
Architecture Artifacts papers, position papers, strategic papers, etc.
 Direction Statements represent the results of strategic
 Standards as a General decision-making processes regarding the desired future
Type of Enterprise direction of an organization or its major business units
27
Part B: EA Direction Statements (Schematic View)
Considerations and  Strategic imperatives provided by
Standards Direction Statements drive all
 Considerations as a General subsequent decision-making
Type of Enterprise processes
Architecture Artifacts  Developing more specific Visions
 Specific Enterprise  Technology selection and on the
Architecture Artifacts overall evolution of the IT
Related to Considerations landscape
 Standards as a General  Approval of corresponding EA
Type of Enterprise artifacts
 Direction Statements are often
 Specific Enterprise temporary EA artifacts with a
Architecture Artifacts limited lifespan
28
Part B: EA Standards as EA Artifacts
Considerations and  Standards are IT-focused rules EA artifacts, describe global
Standards IT-specific rules, permanent defined by architects
 Considerations as a General  Standards represent proven reusable means for IT systems
Type of Enterprise implementation
 The general purpose of all Standards is to help achieve
 Specific Enterprise technical consistency, technological homogeneity and
Architecture Artifacts regulatory compliance
 Key organizational benefits of using Standards include:
 Standards as a General  Faster initiative delivery
Type of Enterprise  Reduced costs
Architecture Artifacts  Mitigated risks
 Specific Enterprise  Lowered complexity
Architecture Artifacts  Improved technical and logical interoperability
29
Part B: EA Standards as EA Artifacts Examples
Considerations and  Technology Reference Models – essential EA artifacts
Standards  Guidelines – essential EA artifacts
 Considerations as a General  Patterns – common EA artifacts
Type of Enterprise
 IT Principles – common EA artifacts
 Logical Data Models – uncommon EA artifacts
Type of Enterprise
30
Part B: EA Technology Reference Models
Considerations and  Technology Reference Models are specific Standards
Standards providing structured graphical representations of all
 Considerations as a General technologies used in an organization
Type of Enterprise  Technology Reference Models map all technologies and
Architecture Artifacts products used in an organization to the respective technical
 Specific Enterprise functions they fulfil or support
Architecture Artifacts  It refers to technology standards, technical reference models,
Related to Considerations technology reference architectures or split into separate
 Standards as a General domain-specific reference models
Type of Enterprise
31
Part B: EA Technology Reference Models (Schematic View)
Considerations and
Standards
Type of Enterprise
Type of Enterprise
32
Part B: EA Guidelines
Considerations and  Guidelines are specific Standards providing IT-specific
Standards implementation-level prescriptions applicable in narrow
 Considerations as a General technology-specific areas or domains
Type of Enterprise  Guidelines are formulated as brief written statements
Architecture Artifacts providing actionable recommendations regarding the usage
 Specific Enterprise of particular technologies in IT solutions
Architecture Artifacts  Guidelines are typically very concrete, unambiguous and
Related to Considerations technical in nature
 Standards as a General  Examples: how application deployed, protected, encryption,
Type of Enterprise who access info, when to archive…
33
Part B: EA Guidelines (Schematic View)
Considerations and
Standards
Type of Enterprise
Type of Enterprise
34
Part B: EA Patterns
Considerations and  Patterns are specific Standards providing generic reusable
Standards solutions to commonly occurring problems in the design of IT
 Considerations as a General systems
Type of Enterprise  Patterns can be considered as a common subtype of
Architecture Artifacts Standards often found in successful EA practices
 Specific Enterprise  They can be also called reference architectures
Related to Considerations  Patterns represent proven reusable components for IT
solutions addressing some common problems or needs
Type of Enterprise  Essentially, patterns offer complete logical “bricks” or
Architecture Artifacts building blocks from which new IT solutions can be
constructed
35
Part B: EA Patterns (Schematic View)
Considerations and
Standards
Type of Enterprise
Type of Enterprise
36
Part B: EA IT Principles
Considerations and  IT Principles are specific Standards defining global high-
Standards level IT-specific guidelines influencing all IT-related
 Considerations as a General decisions and plans in an organization.
Type of Enterprise  IT Principles can be considered as a common subtype of
Architecture Artifacts Standards often found in successful EA practices.
 Specific Enterprise  They can be often called simply principles.
Related to Considerations  IT Principles are conceptually similar IT-oriented
counterparts of business-focused Principles.
Type of Enterprise  IT Principles are formulated as brief written statements
Architecture Artifacts defining what is important for IT and how IT needs to work.
37
Part B: EA IT Principles (Schematic View)
Considerations and
Standards
Type of Enterprise
Type of Enterprise
38
Part B: EA Logical Data Models*
Considerations and  Logical Data Models are specific Standards providing logical
Standards or even physical platform-specific definitions of the key data
 Considerations as a General entities and their relationship
Type of Enterprise  Logical Data Models can be considered as an uncommon
Architecture Artifacts subtype of Standards used relatively rarely
 Specific Enterprise  They can be also called logical information models, canonical
Architecture Artifacts data models, data schemas, etc.
 Logical Data Models define main data types with all their
 Standards as a General fields, often including exact titles, types and formats
Type of Enterprise
Architecture Artifacts  Logical Data Models may also explain where and when these
data objects are generated and consumed
39
Part B: EA IT Principles (Schematic View)
Considerations and
Standards
Type of Enterprise
Type of Enterprise
40
2/3/2019 41
Part C: EA Visions and Landscapes
• Visions as a General Type of Enterprise
• Specific Enterprise Architecture Artifacts
Related to Visions
• Landscapes as a General Type of Enterprise
• Specific Enterprise Architecture Artifacts
Related to Landscapes 42
Visions as EA Artifacts
Part C: EA Visions
and Landscapes  Visions are business-focused structures EA artifacts
 Visions provide high-level business-oriented descriptions of
 Visions as a General an organization developed collaboratively by senior business
Type of Enterprise and IT stakeholders
Architecture Artifacts  Visions represent shared views of an organization and its
 Specific Enterprise future agreed by business and IT
 The proper use of Visions leads to improved strategic
Related to Visions
alignment and better effectiveness of IT investments
 Landscapes as a General
Type of Enterprise  Visions allow addressing four aspects of alignment:
 How much money to invest in IT
 Where to invest IT dollars
 What types of IT investments are needed
Architecture Artifacts  When IT investments should be made
Related to Landscapes
43
Visions EA Artifacts Examples
Part C: EA Visions
and Landscapes  Business Capability Models – Essential EA artifacts
 Roadmaps – Essential EA artifacts
 Visions as a General  Target States – Common EA artifacts
Type of Enterprise  Value Chains – Uncommon EA artifacts
Architecture Artifacts  Context Diagrams – Uncommon EA artifacts
Related to Visions
Type of Enterprise
44
Business Capability Models*
Part C: EA Visions
and Landscapes  Business Capability Models are specific Visions providing
structured graphical representations of all organizational
 Visions as a General business capabilities and their hierarchy
Type of Enterprise  Business Capability Models can be considered as an essential
Architecture Artifacts subtype of Visions found in most EA practices
 Specific Enterprise  Sometimes they can be also called business capability maps
Architecture Artifacts or capability reference models
Related to Visions
 Business Capability Models represent high-level views of an
 Landscapes as a General organization from the perspective of its capabilities
Type of Enterprise
 Essentially, Business Capability Models briefly describe
everything that an organization can do
45
Business Capability Models (Schematic View)
Part C: EA Visions
and Landscapes
 Visions as a General
Type of Enterprise
Related to Visions
Type of Enterprise
46
Roadmaps*
Part C: EA Visions
and Landscapes  Roadmaps are specific Visions providing structured
graphical views of all planned IT initiatives in specific
 Visions as a General business areas having direct business value
Type of Enterprise  Roadmaps can be considered as an essential subtype of
Architecture Artifacts Visions found in the majority of successful EA practices
 Specific Enterprise  They can be called investment roadmaps, capability
Architecture Artifacts roadmaps, application roadmaps, etc.
Related to Visions
 Roadmaps describe IT delivery schedules for different
 Landscapes as a General business areas agreed by business and IT leaders
Type of Enterprise
 Essentially, they show everything that IT plans to deliver for
the business in the foreseeable future
47
Roadmaps (Schematic View)
Part C: EA Visions
and Landscapes
Type of Enterprise
Related to Visions
Type of Enterprise
48
Target States
Part C: EA Visions
and Landscapes  Target States are specific Visions providing high-level
graphical descriptions of the desired long-term future state
 Visions as a General of an organization
Type of Enterprise  Target States can be considered as a common subtype of
Architecture Artifacts Visions often found in successful EA practices
 Specific Enterprise  They can be called target architectures, future state
Architecture Artifacts architectures, business reference architectures, etc.
Related to Visions
 Target States represent the ultimate destination of an
 Landscapes as a General organization from the perspective of its business and IT
Type of Enterprise
 Essentially, Target States explain what an organization is
trying to achieve with IT in the long-term future
49
Target States (Schematic View)
Part C: EA Visions
and Landscapes
Type of Enterprise
Related to Visions
Type of Enterprise
50
Value Chains
Part C: EA Visions
and Landscapes  Value Chains are specific Visions providing structured
graphical representations of the added value chain of an
 Visions as a General organization
Type of Enterprise  Value Chains can be considered as an uncommon subtype
Architecture Artifacts of Visions relatively rarely found in EA practices
 Specific Enterprise  They can be called value reference models, business
Architecture Artifacts activity models, etc.
Related to Visions
 Value Chains represent holistic views of an organization
 Landscapes as a General from the perspective of its value-adding activities
Type of Enterprise
 Value Chains describe all primary and supporting activities
that an organization performs to deliver value
51
Value Chains (Schematic View)
Part C: EA Visions
and Landscapes
Type of Enterprise
Related to Visions
Type of Enterprise
52
Context Diagrams*
Part C: EA Visions
and Landscapes  Context Diagrams are specific Visions providing high-level
graphical descriptions of the current operational flows of
 Visions as a General an organization
Type of Enterprise  Context Diagrams can be considered as an uncommon
Architecture Artifacts subtype of Visions relatively rarely found in EA practices
 Specific Enterprise  They can be called business context diagrams, application
Architecture Artifacts diagrams, concepts of operations, etc.
Related to Visions
 Context Diagrams represent high-level views of an
 Landscapes as a General organization with its essential elements and relationships
Type of Enterprise
 Context Diagrams explain on a single page how the
business operates and clarify how an organization works
53
Context Diagrams (Schematic View)
Part C: EA Visions
and Landscapes
Type of Enterprise
Related to Visions
Type of Enterprise
54
Landscapes EA Artifacts Examples
Part C: EA Visions
and Landscapes  Landscapes are IT-focused structures EA artifacts, provide
high-level IT-specific descriptions of the organizational IT
 Visions as a General landscape useful for architects
Type of Enterprise  Landscapes represent a knowledge base of reference
Architecture Artifacts materials on the IT landscape
 Specific Enterprise  Landscapes enable the accumulation, storage and
Architecture Artifacts exchange of the technical knowledge on the IT landscape
Related to Visions
 The purpose of all Landscapes is to help understand,
 Landscapes as a analyze and modify the structure of the IT landscape
General Type of
 Key organizational benefits of using Landscapes include:
 Increased reuse of IT assets
Artifacts
 Reduced duplication of IT assets
 Specific Enterprise  Decreased dependence on legacy IT systems
Architecture Artifacts  Improved IT agility. 55
Related to Landscapes Executive Master of IT
Landscapes EA Artifacts Examples
Part C: EA Visions
and Landscapes  Landscape Diagrams – Essential EA artifacts
 Inventories – Common EA artifacts
 Visions as a General  Enterprise System Portfolios – Common EA artifacts
Type of Enterprise  IT Roadmaps – Common EA artifacts
Related to Visions
 Landscapes as a
General Type of
Artifacts
56
Related to Landscapes Executive Master of IT
Landscape Diagrams*
Part C: EA Visions
and Landscapes  Landscape Diagrams are specific Landscapes showing
technical “boxes and arrows” schemes of different scopes
 Visions as a General and granularities describing the IT landscape
Type of Enterprise  Landscape Diagrams can be considered as an essential
Architecture Artifacts subtype of Landscapes found most EA practices
 Specific Enterprise  They can be called simply an architectural repository or
Architecture Artifacts used under very diverse titles, e.g. relational diagrams
Related to Visions
 Landscape Diagrams represent snapshots of different parts
 Landscapes as a General of the organizational IT landscape
Type of Enterprise
 Landscape Diagrams show what IT assets support different
business areas and how they are interrelated
57
Landscape Diagrams (Schematic View)
Part C: EA Visions
and Landscapes
Type of Enterprise
Related to Visions
Type of Enterprise
58
Inventories*
Part C: EA Visions
and Landscapes  Inventories are specific Landscapes providing structured
catalogs of currently available IT assets describing their
 Visions as a General essential properties and features
Type of Enterprise  Inventories can be considered as a common subtype of
Architecture Artifacts Landscapes often found in successful EA practices
 Specific Enterprise  They can be also called asset registers or architectural
Architecture Artifacts repositories
Related to Visions
 Inventories represent comprehensive directories of
 Landscapes as a General organizational IT assets with their detailed descriptions
Type of Enterprise
 Essentially, they list all IT assets owned and maintained by
an organization and describe their key attributes
59
Inventories (Schematic View)
Part C: EA Visions
and Landscapes
Type of Enterprise
Related to Visions
Type of Enterprise
60
Enterprise System Portfolios*
Part C: EA Visions
and Landscapes  Enterprise System Portfolios are specific Landscapes
providing structured high-level mappings of all essential IT
 Visions as a General systems to relevant business capabilities
Type of Enterprise  Enterprise System Portfolios can be considered as a
Architecture Artifacts common subtype of Landscapes used rather often
 Specific Enterprise  They can be called application portfolios, application
Architecture Artifacts models, IT system value maps, IT strategy maps, etc.
Related to Visions
 Enterprise System Portfolios represent comprehensive
 Landscapes as a General abstract views of the entire organizational IT landscape
Type of Enterprise
 Essentially, Enterprise System Portfolios can be considered
as a “landscape on a page”
61
Enterprise System Portfolios (Schematic View)*
Part C: EA Visions
and Landscapes
Type of Enterprise
Related to Visions
Type of Enterprise
62
IT Roadmaps*
Part C: EA Visions
and Landscapes  IT Roadmaps are specific Landscapes providing structured
graphical views of all planned IT initiatives of a technical
 Visions as a General nature having no visible business impact
Type of Enterprise  IT Roadmaps can be considered as a common subtype of
Architecture Artifacts Landscapes
 Specific Enterprise  IT Roadmaps can be called technology roadmaps, platform
Architecture Artifacts roadmaps, infrastructure roadmaps, etc.
Related to Visions
 IT Roadmaps are IT-oriented counterparts of Roadmaps
Type of Enterprise  IT Roadmaps reflect purely IT-specific efforts intended to
improve the technical quality of the IT landscape without
delivering any new business functionality or benefits
63
IT Roadmaps (Schematic View)
Part C: EA Visions
and Landscapes
Type of Enterprise
Related to Visions
Type of Enterprise
64
Executive Master of IT 65

Session 4

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Session 4

Uploaded by

Copyright:

Available Formats

Enterprise

● Six General Types of Enterprise Architecture

● The Resulting CSVLOD Model of Enterprise

● Specific Enterprise Architecture Artifacts Related to

● Standards as a General Type of Enterprise

● Specific Enterprise Architecture Artifacts Related to

You might also like