Enterprise Architecture as a Business Strategy (320084)
All documents for this subject (13)
1
review
By: basvillevoye • 1 year ago
Seller
Follow
larsnuijten
Reviews received
Content preview
Lecture Summary Enterprise Architecture 2022-2023
Table of contents
Lecture 1: Introduction to the course ..................................................................................................... 2
Lecture 2: EA as a set of models .............................................................................................................. 7
Lecture 3: EA as a method for change (1) ............................................................................................. 13
Lecture 5a: EA as a method for change (2) ........................................................................................... 17
Lecture 5b EA as a method for change (3) ............................................................................................ 21
Lecture 6: EA as a business strategy...................................................................................................... 27
Lecture 7: EA Research Models and Myths over the years ................................................................... 35
1
,Lecture 1: Introduction to the course
Enterprise architecture challenges over the ages
• IT increasing complexity
• IT increasing migration speed
• Increasing business complexity
• Increasing Business transformation speed
What is Enterprise Architecture
• Business architecture: the business mission, strategy, line of businesses, organization structure,
business process models, business functions
• Information architecture (data architecture): defines what information needs to be made
available to accomplish the mission, to whom, and how.
• Application architecture (functional architecture): focuses on the application portfolio required
to support the business mission and information needs of the organization. At the next level of
detail, it addresses the common business components and business services that can be
leveraged by multiple applications
• Technology architecture: defines the technology services needed to support the application
portfolio of the business. It also documents the software, hardware, and network product
standards.
Core components of Enterprise Architecture
• As-is: the current state assessment of the organization
• To-be: the future state and, generally, the main focus of an EA assignment
• Migration plan: viable route from as-is to to-be architecture. Without a viable plan the
architecture has already failed
• Principles: the guidelines for users of the architecture, such as ‘buy not build’ or ‘adherence to
published data standards’
• Decisions Log: started during the development of the EA but a key part of the ‘living’ architecture
Linking Enterprise Architecture & Strategic Alignment
Strategic Alignment theory and Enterprise Architecture both addresses how the designs of business
and IT affect performance.
2
,Linking Enterprise Architecture & the business model of a firm
• The Business Model of a firm defines the Value Proposition (what 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).
What is architecture?
• Architect as Model: “a set of things”, “an artifact”
• Architect as Modelling: “a process of making things clear with models”, “reducing complexity
with models”
Architecture development: Changing the firm: moving from as-is to a to-be architecture
Business challenges triggering EA
Issues Triggers
Patchwork mentality Change patchwork culture
Anarchistic maintenance Change IT anarchy
Many people in IT rooms
Instability of systems Enhance 24/7 stability
Old systems Replace old parts/systems
No IS testing environment Enhance testing & delivery
No IS acceptance environment
Human-based knowledge Enhance human expertise
3
, Positioning Enterprise Architecture
Case: University Medical Center Groningen
UMCG architecture domains: processes
• Processes will be patient focused (not IT or doctor focused)
• Priority for IT that supports patient care
• IT is supportive and not a goal on its own
UMCG architecture domains: Information
• One source for information (authentic source)
• Clear definitions of concepts
• Clear hierarchy for replicating data
UMCG architecture domains: applications
• 1 = re-use, 2 = buy, 3 = build
• Best of breed, so multi-vendor policies
• Must fit the IT architecture and standards
4
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller larsnuijten. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $5.77. You're not tied to anything after your purchase.