There are plenty of other courses that explain what is Enterprise Architecture. This one is different - because the course tutor is someone who has been at the leading edge of Enterprise Architecture since 1984, so he really knows his stuff and knows how to explain it simply and clearly.
This course will:
Welcome to the course! In this video I give a very brief introduction to the course.
This lecture gives you a brief outline of the course, its layout, and the questions that it will answer.
You might find it useful to watch my 6-minute introduction to Enterprise Architecture on YouTube, or to see some of the other sort introduction videos that are available on YouTube (in a YouTube Playlist). There are links to both of these in the Resources.
This lecture explains that "enterprise" can mean any human endeavour or undertaking.
An enterprise can therefore be:
In this lecture I'll describe the three key things that exist for any enterprise:
No enterprise exists in isolation. Enterprises collaborate with other enterprises. And all enterprises operate within a particular environmental and social context.
This lecture explains what that means for Enterprise Architecture.
In this lecture I'll describe the components that can be found in almost every enterprise.
In this lecture I explain how:
Finally in this section I explain how every enterprise has an enterprise architecture.
You might find a post I wrote on LinkedIn interesting: Enterprise Architecture Isn't Optional - there's a link in the resources.
This quiz will help you understand the meaning of "enterprise" when the word is used in Enterprise Architecture..
This quiz gives you a chance to review the things that Enterprise Architects include in their work.
In this lecture you will learn why it is important to see Enterprise Architecture as four things:
In this lecture you will learn about the key ingredients of enterprise architectures.
Remember - every enterprise has an architecture!
You will learn about Paradigms, Patterns, and Principles; Components or Building Blocks; and Architecture Domains.
I will also briefly explain the concept of a metamodel.
In this lecture you will learn about the main benefit and value from architecting an enterprise. This lecture you will introduce the idea of architectural thinking, and demonstrate how this provides us with several different levels of architectural understanding.
You will also learn the important distinction between architectural thinking and systems thinking.
In the resources you will find a link to a post I wrote on LinkedIn about the Levels of Architectural Understanding - which also includes some interesting comments and discussion.
This lecture will provide you with a clear and simple outline of what enterprise architects do.
This lecture will explain how architects balance the need to manage an enterprise architecture with other forces that are beyond their direct control.
I will introduce and explain the concepts of Architectural States, Enterprise Patterns, Strategic Vectors, Roadmaps, and Emergence.
This lecture will provide you with a simple overview of the skills and experience that enterprise architects need.
In this lecture you will gain an overview of some of the key techniques used by enterprise architects.
This lecture will provide you an understanding of how enterprise architects describe an enterprise architecture. In particular it will explain how architects describe building blocks, patterns, constraints, enablers, and options.
In this lecture you will learn why architecture frameworks are so important in Enterprise Architecture.
You will find out why there are several different architecture frameworks, and why this causes some confusion!
Finally you will gain a good understanding of how architecture frameworks are used by leading architects and architecture teams.
There are two useful links in the resources:
So, architecting an enterprise is a process. It requires experienced and skilled enterprise architects, applying a professional discipline called “Enterprise Architecture”. And it produces descriptions of the architecture of an enterprise (in its current and future states) that guide changes to the architecture.
In the downloadable resources you will find a PDF extract from my book, "Enterprise Architecture - the eight fundamental factors", which gives you a complete overview of the eight factors that are mentioned in this course.
There are several things that make Enterprise Architecture distinctive, but in this lecture I focus on the two most important characteristics that make it a unique and special discipline.
This lecture asks a key question: do we need Enterprise Architects?
Now that you've completed this course - what do you think? Do you agree with me or not? Do you think that enterprise architecture is needed or not?
Here is a brief exercise that you can do. It will help you think about the ideas we have covered in this section, and help you put them into your own words.
Roger Evernden has been an enterprise architect since 1984, specializing in the highly practical use of EA to manage organizational transformation. He acts as advisor, mentor, and coach on EA initiatives, leads training workshops, and writes regularly about strategy and architecture.
He provides a unique combination of training and tools to help architects and their teams throughout an EA program and at each capability level. His hands-on training workshops provide a thorough grounding of all key techniques, with practical examples, exercises, and demonstrations.
As architect of the Information FrameWork (IFW), Roger pioneered many contemporary EA techniques, including the use of industry reference models, business capability analysis, and component-based building blocks.
His work has been the basis for more than 400 business and IT architecture initiatives worldwide. Roger has written extensively about enterprise architecture and TOGAF®. His articles have appeared in major publications and books, including the seminal article on IFW in IBM's Systems Journal. He is the author of two books about EA: Enterprise Architecture — The Eight Fundamental Factors and 101 Lessons from Enterprise Architecture.
He is a Senior Consultant with Cutter Consortium's Business & Enterprise Architecture practice.