EA Flashcards

1
Q

What are the five CORE components of EA

A

As-is = current state of organisation
to- be = future state (main focus of EA)
migration plan = from as-is to to-be
principles - guidelines for users of the architecture
decisions log = key part of ‘living’ architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

what other theory is linked to EA

A

Strategic Alignment theory. Both address how designs of business and IT affect performance.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

How is EA linked to the business model of a firm?

A

The Business Model of a firm defines the Value Proposition (what value is offered
to whom) and the Operating Model of a firm (how is the value created).
Business Models &Enterprise Architecture both define how, who, what, when, and where value is created (operating model) and for which markets (value proposition).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

EA as a framework (Zachman). Draw and explain the picture.

A

Y-axis: Scope/contextual (planner view), enterprise model(conceptual) owner, system model(logic) designed

X- axis Data(what), Function(how), Network(where)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

The Open Group Architecture Framework (TOGAF) process (phases). Explain the flow.

A
  1. prelim. framework and principles
  2. architecture vision
  3. business architecture
  4. IS architecture
  5. Technology architecture
  6. Opportunities and solutions
  7. Migration Planning
  8. Implementation Governance
  9. Architecture change management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Article 1992 Sowa and Zachman:

What does Zachman’s framework do?

A

It provides a systematic TAXONOMY or concepts for relating things in the real world to the representations in the computer. It provides a way of viewing a system from many perspectives and showing how they are all related.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Article 1992 Sowa and Zachman: rules of the framework.

A

Rule 1. Columns have no order. Order implies priority.
Rule 2. Each column has a simple, basic model. Columns are abstractions of real-world for convenience of design.
Rule 3. The basic model of each column must be unique.
Rule 4. Each row represents a distinct unique perspective.
Rule 5&6. Each cell is unique but they are related to other cells of the same column.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Article 1992 Sowa and Zachman: what tool/ method can you use to represent column B of the framework?

A

Petrinets can be used to represent processes.

Also any E-R diagram can be translated into a conceptual graph.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Article 2013 Kappelmann and Zachman: what is architecting/ architecture and why is it important?

A

Architecting is a kind of modeling. Every object has an architecture regardless if its explicitly written down or not.

If you can’t describe an object you can’t create it. If you need a team to help you create, change or manage the object and you can’t explain it, they cannot help.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Article 2013 Kappelmann and Zachman: when is architecture imperative ?

A

Only when the object you are trying to create is complex/ very complex.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Article 2013 Kappelmann and Zachman: zachman quadrant structure.

A
  1. resource ideas
  2. behavior ideas
  3. resource reality
  4. behavior reality

IT is more concerned about resource reality while management is more concerned about ideas.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Article Groot, Smits 2015: explain model with EA fit included.

A

Emerging business problem -> requires IT project proposal -> which results in IT projects portfolio -> which results in IS applications portfolio.

Emerging b. problem influecens internal drivers, which together with external drivers influence the architecture development process -> leading to enterprise architecture, which is the norm for both IT project proposals as well as for IT projects Portfolio.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Article Groot, Smits 2006: How does EA help emerging business problems?

A

without EA emerging business problems lead to complexity of the IS application portfolio and
design debt
• Such complexity of IT, high IT costs, or the emerging business problems, and poor IT flexibility are
internal drivers to start using EA
• External drivers for using EA can be legislation, standardization, or supervisory institutions
• EA development makes use of design principles (‘agreements between business and IT’)
• After establishing the IST and SOLL EA,

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Article Groot, Smits 2015: Problem situation

A

IS portfolio is complex (esp after merger or acquisition)
Low IS flexibility & failing IS projects
Decentralized IS budget

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Article Groot, Smits 2006: Challenge and solutions

A

How to redesign IS portfolio
How to reduce IS complexity

Solution:
PICTURE APPROACH
1. Process
2. Products
3. Decisions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Picture Approach as EA method. Summary

A

PA is a method:

  • helps analyze, redesign and combine system complexdes / portfolios
  • fitting all in one as-is picture
  • helps improve business - IT alignment

FOCUS of PA:

  • process architecture
  • information architecture
  • organization architecture (who decides on what)
  • IT architecture
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

The Picture Approach - EA process

List and describe the steps:

A
  1. establish support from PM and senior management
  2. make “photo-shoots” of core process, applications, documents, actors
  3. review the “photos” (models) by management team
  4. Detail the models by adding “fact sheets” that define: sustainability, functionality per app, process support, costs and benefits (per app), risks (per app and total)
  5. Freezing the photos of “as is”
  6. Choosing the target EA (“to-be” EA) using multi criteria decision analysis (analytical hierarchy planning).
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Article Groot, Smits 2006: how many pictures needed?

A
  • ONE picture to represent as-is architecture.
  • min 1, but also 2-4 for to-be

For every picture, 5-6 factsheets needed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

How does the Analytical Hierarchy Planning (AHP) help chose the optimal TO BE architercture?

A

AHP calculates ‘the best choice of two options’ given weights and performs a sensitivity analysis.

It uses a comparison matrix for Three TO BE architectures: it compares A with B and C, B with C for each subcriterion.

You need to ask MANAGERS and EXPERTS questions in order to evaluate/ set the weights.
“ How important do you think performance is for ICT architecture? what about Scalability, migratability, maintainability?”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What other PWC tools are there to reduce EA complexity? (explain number 1 with mapping)

A

1) Mapping applications (systems) to business processes.

Find out which apps (and how many) are used per business process.

Find out which apps are used by multiple b. processes

Which b. processes use similar apps (to reduce redundancy).

This finds out which apps could be taken out, which merged and how to prioritize apps. -> leads to changing the app portfolio

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What other PWC tools are there to reduce EA complexity? (explain number 2 with portfolio)

A

2) Quality of the apps portfolio (PWC).

Model supports analysis of app portfolio:

It maps out apps based on technical quality (ask IT), functional quality (ask business) and costs (ask finance).

How?

XY graph with Y = functional quality (low to high); X = Technical Quality (low to high). Size of circles indicates yearly costs.

Y low, X low = replace
Y high, X low = technical improvements
Y low, X high = functional improvements
Y high, X high = healthy

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What are the 3 EA approaches to reduce complexity?

A
  1. Zachman approach: develop the right models for each cell 5x6
  2. Picture approach (PWC): focus on the right modelling process
  3. The practical approach: two models for IS application portfolio management.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

How to deal with complexity when you dont know the architecture of complex object? 4 options

A
  1. reverse engineer artifacts (costly)
  2. trial and error (risky)
  3. make assumptions
  4. just tear down and start over.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

How do you asses size and complexity of software? + rule of thumb?

A

Make use of Function Point Analysis.

A function point measures amount of business functionality an IS provides to users.

Rule of thumb (Capers Jones): One function point requires on avg 100 lines of code.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

How to estimate software renewal time (build from scratch)?

A

Capers Jones shows that larger systems costs more developer time per FP.

The more FP, the more decrease of productivity (exponential).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

How to approximate the cost of a Function Point (FP)?

A

The more complex and reliable a system needs to be, the higher the FP cost.

2000 eur vs 12000 euro (practitioner vs military).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

Types of complexity of IS app portfolio (groot, smits, kuipers)/ difference between the types?

A

Objective complexity: components (apps), interfaces, functions

Subjective complexity: perceived effort that is required, to understand and cope with the portfolio.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

Internal Drivers for EA (why do some companies do EA?)

A
  • audit purposes
  • to manage the IT system portfolio
  • reduce complexity
  • prepare a merger or acquisition
  • etc
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

Explain what design debt is.

A

quick fixes increases complexity almost exponentially

Architectural debt/ design debt accumulates when quick fixes are applied without proper refactoring.

Debt accumulates interest over time, increasing TC required to pay the debt.

30
Q

Design principles to guide the EA process:

list the 5 CORE components of an EA

A
  1. as-is
  2. to-be
  3. migration plan
  4. principles
  5. decision log
31
Q

Article 2013 Legner: EA design principles .

What are the main questions addressed in the research?

A
  1. What are suitable principles to guide EA design and evaluation?
  2. What usage do EA principles have for practitioners?
  3. Which propositions can be derived regarding EA principles?
32
Q

Article 2013 Legner: EA design principles.

What should EA principles be used for?

A
  • ! to limit design space and guide design decisions !
  • to find architecture design decision pots to harmonize IT projects towards predefined goals.

Principles are pervasive in nature and
their direct implication should be followed by low-level governance means, for instance
standards and guidelines

33
Q

Article 2013 Legner: EA design principles

Meta-principles:

A

Modularity: decomposition of business and apps
Integration

Interoperability: compatibility and connectivity amount all hw, sw, communication

Standardization: standards for data exchange, standardization of programming languages

Data consistency: shared vocabulary and data definition

Compliance: law, standards, regulations
Reusability: common use apps

Portability: operability in diff hw and sw platforms

Usability: shared look-and-feel, ease of use

Simplicity: minimal dependencies between diff modules and apps

Centralization: consolidate and centralized hw and sw

34
Q

Article 2013 Legner: EA design principles

Summary and conclusions (main points/ propositions)

A

1) EA principles should be defined such that they impact design decisions and limit design space
2) EA principles should be pervasive, enduring and have a high level of granularity
3) should be an enabler to reach EA goals
4) should be understandable by key stakeholders and have support from org key members

35
Q

Article 2020 Haki and Legner: EA principles

When was the notion of architecture applied to it landscapes?

A

Since the 1980s, practitioners and academic scholars have propagated the notion of architecture as an approach to systematically plan and develop IT landscapes

36
Q

Article 2020 Haki and Legner: EA principles

Normative vs Scientific principles

A

Normative principles are declarative statements that define artifact properties (what should be), while scientific principles are rules that govern the working artifact (what is).

Normative principles are inductive (based on expert knowledge/experience) while scientific principles are deductive (derived from laws of nature).

37
Q

Article 2020 Haki and Legner: EA principles

Mechanics of EA principles:

A

EA principles contribute to achieving EA outcomes by generating EA capabilities that underlie the intended outcomes.

38
Q

Two theoretical perspectives to EA:

A
  • Resource based view: where you acquire VRIN resources and develop capabilities
  • Business network theory: organizations work together in business networks to outperform other business networks.
39
Q

Stable EA versus Agile Enterprise

A

Top performing companies create a stable base:
- they digitize their core processes and embed them into a foundation for execution.

This stable foundation for execution makes them more AGILE and more efficient than competition.

40
Q

What is Foundation for Execution?

A

“routine tasks need to be automated so that they are executed reliably and predictably without any thought”.

FfE digitizes routine processes to provide reliability and predictability.

FfE is the IT infrastructure + digitized business processes that together automate a company’s CORE capabilities.

2015 Ross & Weill address FfE as ‘DIGITAL TRANSFORMATION’

41
Q

Why use Foundation for Execution?

A
  • reduce complexity
  • enhance business agility!!!
  • fulfill needs for regulatory and legal compliance
42
Q

EA as a strategy: what is an operating model (the two dimensions)?

A

The Operating Model defines the necessary level of business process integration and
standardization

43
Q

EA as a strategy: Operating model matrix.

A

XY graph where Yaxis= BPI and Xaxis = business process standardization

for (low, low) => diversification
(high, high) => unification
(low bpi, high stand) => replication
(high bpi, low stand) => coordination

44
Q

Main structure of Weill & Ross Book

A
  1. Operating model > 2. Enterprise Architecture > 3. IT Engagement Model.
45
Q

RBV: resources, competences and capabilities. Explain

A
  1. resources are things like HW, SW licenses, people, data (also VRIN resources).
  2. Competence = ability to use the resources (knowledge and skills)
  3. Capability = capacity * ability
    capacity = how much a firm has (of some resource)
    ability = a person that can do
46
Q

Layers in ARCHIMATE

A
  1. business layer (2)
  2. Application layer (2)
  3. Infrastructure layer (2)

Each main layer has (2) layers. One for services and one for processes.

47
Q

Maturity Model: Capability Maturity Model (CMM)

Levels

A
  1. Business Silo’s (focus on creating insights and oversight in portfolio of applications and portfolio of IT competences
  2. Standardized Technology: focus decrease the number of platforms to be managed (no spaghetti)
  3. Optimized Core: from local data and apps to enterprise wide systems and enterprise wide data.
  4. Business Modularity: focus on strategic agility. create plug and play processes. IT for business modularity
  5. Dynamic enterprise: extending the concept of reusable modules to enable companies to rapidly reconfigure their portfolios of businesses. Look for opportunities to partner or to acquire.
48
Q

RetailCo lessons learned about EA

A
  1. Rebuild EA capability early
  2. establish strong EA mandate
  3. adopt a flexible approach to EA
  4. Build constructive EA- project relationships
  5. Adopt a service mindset for EA
49
Q

Implementing operating model via EA according to Ross & Weill. How detailed is the core diagram?

A

The EA core Diagram is “a one page drawing”.

“EA diagrams should not have too much detail”

It represents a high-level view of core processes, data and technologies, that constitute FfE

The Core Diagram helps managers discuss and understand their company’s EA

50
Q

How many types of EA core diagrams are there?

A

One core diagram per core model:

  • coordination
  • replication
  • diversification
  • unification
51
Q

Unification Core Diagram stages

A
  1. identify key customers
  2. identify key processes to be standardized and integrated
  3. identify the shared data
  4. identify automating and linking technologies

this diagram reflects highly integrated and standardized environment

52
Q

Diversification Core Diagram

A

low integration and low standardization

each BU runs independently (own data, own process)

to make a core diagram start with shared technologies and integrate processes, data, customer types only when needed.

This core diagram focuses on technologies and sharing technical infrastructure.

53
Q

Coordination Core Diagram

A
  • Integrated services per customer group. Integration results from shared data

steps:

  1. Identify shared customers
  2. identify key data that must be shared to serve this customer group
  3. identify the key technology that is key in data integration
  4. include business processes
54
Q

Replication Core Diagram

A

Key processes are standardized and supported by IT.

steps

  1. identify key processes to be standardized and replicated
  2. identify core technologies automating those key processes
  3. identify the linking technologies that can be shared
  4. identify shared data/ customers (if applicable)
55
Q

Enterprise Architecture models (McDonald)

A
  • Value Network Diagram: captures scope of enterprise
  • Capabilities Diagram: outlines relationships between capabilities
  • Capability blueprint: defines the scope of capability in terms of its elements.
56
Q

The Value Network Diagram: main points

A

A value network model describes the roles, relationships and capabilities used to deliver a value proposition to customers.

  • it is the highest level model in the architecture
  • there should be one value network for each market (helps manage complexity)

It answers:

  • Who are the customers and target markets?
  • Who are the trading partners?
  • How are capabilities sourced across trading partners?
57
Q

The Capabilities Diagram: main points

A

This diagram represents ONLY one firm in the network.

It adds capability definitions, information flows, interaction between internal capabilities, actors and customers.

It answers:

  • What is the operational scope of the enterprise?
  • How do capabilities work together to produce end-to-end results?
  • what interfaces are between capabilities and trading partners
58
Q

Capability blueprint

A

Answers:

  • what is the scope of each capability
  • what is the strategic performance context for each
  • what elements are involved in each
  • what are the relationships between capabilities
59
Q

Benefits of EA (based on Ross et al)

A
  • Reduced IT costs
  • Increased IT responsiveness
  • improved risk management
  • increased managemnet satisfaction
  • enhanced strategic business outcomes
60
Q

IT engagement model: what it is, purpose and main ingredients at top performers

A

Is a system of governance mechanisms

purpose: assure that business and IT projects achieve objectives

Three main ingredients:

  1. companywide IT governance
  2. Project management
  3. Linking mechanisms
61
Q

How to coordinate IT engagement?

A

IT engagement coordinates at 3 levels and two domains:

Levels: Company wide governance > Linking mechanisms > project management

62
Q

Lenses on digital transformation:

A
  • strategy development
  • strategy realization
  • sustainability
  • leadership for change
  • organizational engagement
63
Q

When was archimate developed?

A

was designed in 2002

64
Q

Why was archimate developed?

A

To model within the domain as well as across the domains.

65
Q

Archimate dimensions

A

columns:

  • Active structure (object/ things in the world that do smth)
  • Behavior: “predicate”
  • Passive structure: inputs and outputs of behavior

“john buys a bike”

active structure: john
behavior: buys
passive structure: a bike

66
Q

Archimate services: how and what?

A

ArchiMate services separate the what from the how.

67
Q

RBV and EA main idea

A

EA methods and models help acquire key resources and develop capabilities

Ea methods and models -> EA capabilities -> business value

68
Q

Decision Theory (DT) and EA main idea

A

EA methods and models help make better decisions on IT and business.

69
Q

Technology Acceptance Model (TAM)

A

EA methods and tools are technologies and they only bring value if are being USED.

Ease of use and usefulness of EA > Intention to use EA >use EA (EA value)

70
Q

TOGAF main categories for EA

A
  • Business architecture
  • Application architecture
  • Data architecture
  • Technical architecture
71
Q

TOGAF’s relationship with Zachman Framework

A

TOGAF is more of a process than a framework.

TOGAF compliments Zachman: Zachman framework tell you how to categorize your artifacts while TOGAF gives a process for CREATING them.

72
Q

AHP: GOAL, MAIN CRITERIA, SUB CRITERIA (if possible)

A

GOAL: best system complex

Criteria: ICT architecture, Systems functionality, Process Support, Costs and Benefits, Risks

Sub criteria: ICT: performance, scalability, migratability, maintanability

  • functionality: user friendliness, shared view
  • Process support: work flow support, change flexibility
  • costs and benefits: costs of migration, maintenance costs
  • risks: migration risks, IT risks