Enterprise Architecture as a Business Strategy (320084)
Tous les documents sur ce sujet (13)
1
vérifier
Par: basvillevoye • 1 année de cela
Vendeur
S'abonner
larsnuijten
Avis reçus
Aperçu du contenu
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
Les avantages d'acheter des résumés chez Stuvia:
Qualité garantie par les avis des clients
Les clients de Stuvia ont évalués plus de 700 000 résumés. C'est comme ça que vous savez que vous achetez les meilleurs documents.
L’achat facile et rapide
Vous pouvez payer rapidement avec iDeal, carte de crédit ou Stuvia-crédit pour les résumés. Il n'y a pas d'adhésion nécessaire.
Focus sur l’essentiel
Vos camarades écrivent eux-mêmes les notes d’étude, c’est pourquoi les documents sont toujours fiables et à jour. Cela garantit que vous arrivez rapidement au coeur du matériel.
Foire aux questions
Qu'est-ce que j'obtiens en achetant ce document ?
Vous obtenez un PDF, disponible immédiatement après votre achat. Le document acheté est accessible à tout moment, n'importe où et indéfiniment via votre profil.
Garantie de remboursement : comment ça marche ?
Notre garantie de satisfaction garantit que vous trouverez toujours un document d'étude qui vous convient. Vous remplissez un formulaire et notre équipe du service client s'occupe du reste.
Auprès de qui est-ce que j'achète ce résumé ?
Stuvia est une place de marché. Alors, vous n'achetez donc pas ce document chez nous, mais auprès du vendeur larsnuijten. Stuvia facilite les paiements au vendeur.
Est-ce que j'aurai un abonnement?
Non, vous n'achetez ce résumé que pour €5,39. Vous n'êtes lié à rien après votre achat.