Enterprise Architecture - the key concepts
Learn about the key concepts and techniques in Enterprise Architecture, with examples, tips and practical guidelines from an EA expert.
A straightforward and common-sense introduction that explains what Enterprise Architecture is, and why we need it.
Learn about the key concepts and techniques in Enterprise Architecture that make it a unique and important discipline.
Master practical tips and examples that make it much easier to understand and explain what enterprise architecture (EA) is all about, and why it is so useful. This tutorial is aimed at all EA practitioners and anyone who wants to understand what Enterprise Architecture is, and why it is necessary.
Powerful and Practical Tips to Build Your Career as an Architect
Enterprise Architecture is increasingly recognized as a vital information-age discipline. And there are many well-established architecture frameworks and methodologies.
But certification and training programs don't always describe EA in a simple and straight-forward way.
This course fills that gap: giving you practical tips and examples that show you how to explain what Enterprise Architecture is, and how it delivers benefits and value. Many of the ideas in this course are missing in EA training courses.
The number of individuals gaining enterprise architecture through standard training programs is increasing by over 12,000 people per year! Training as an Enterprise Architect is therefore a smart career move.
Simply put - there has never been a better time to get trained as an Enterprise Architect. To stand out from the crowd you need to make sure that you know how to apply and use your EA skills.
Learn and master how to explain and justify Enterprise Architecture in this simple and straightforward course.
If you are already in an architecture role, or just starting out on a career as an architect, then this course will show you the most effective ways to talk about Enterprise Architecture with your stakeholders and sponsors.
Contents and Overview
I designed this course for two reasons:
This course explains what Enterprise Architecture is all about, and shows in detail exactly how to engage with stakeholders and explain it to them.
It explains the things in Enterprise Architecture that are confusing, and gives you practical and useful materials that you can use in your day-to-day work as an enterprise architect.
Above all, this course explains Enterprise Architecture so that it makes sense, and so that you can become confident in applying your EA knowledge in the real world.
What are the requirements?
What will you get from this course?
What is the target audience?
Roger Evernden
Section overview
What is an architecture framework?
Why are there so many architecture frameworks?
Using a metaframework
Key Learning Points
The Eight Fundamental Factors
The Eight Factors - Extract from "EA - the Eight Fundamental Factors
Section overview
Stakeholders, Viewpoints and Concerns
A link to the ISO 42010 standard
Concerns versus architecture requirements
Viewpoints and Views
An ArchiMate description of Architecture Viewpoints
Managing Views and Viewpoints
Section overview
Architecture, Description, Process, and Discipline
Architecture as Description
Presentation Types
Architecture as Process
Architecture as Discipline
TOGAF® Architecture Skills Framework
Section overview
FREE PREVIEWCommon Domains and Sub-Domains
Two ways to present domains
Domain Analysis - Layers and pillars
Domain Analysis - Separation of Concerns
Architecture Domains - Key Learning Pointa
Separation of Concerns
Ping Pong Process
Section overview
FREE PREVIEWThe Metamodel
What are meta levels?
An example using the meta levels
Why do we need meta levels?
Meta Levels - Key Learning Points
Section overview
FREE PREVIEWEveryone has their own viewpoint
Every model has its own conventions
What the metamodel has to cover
Key Learning Points
Section overview - common pitfalls to avoid with Enterprise Architecture
#1: What are the common pitfalls in EA?
#2: What do you mean by "architectural advice"?
#3: How does EA work in a smaller organization?
#4: How can we make the transition from architecture to solution?
#5: How do we balance future needs versus immediate solutions?
#6: How do we get useful artifacts from the EA team?
#7: At what stage should we introduce EA?
#8: At what level of maturity should we use an EA framework?
#9: How can we measure the performance of the EA team?
#10: Common EA Pitfalls - a summary
Overview of Exercise - Pitfalls
EXERCISE - Which EA pitfalls does your EA team need to avoid?
EXERCISE DISCUSSION - EA Pitfalls
EXERCISE DISCUSSION - Closing the Gap
EXERCISE DISCUSSION - New EA Team Roles