Search Results for: Crossing the Enterprise Architecture Chasm
Crossing the Enterprise Architecture Chasm
Enterprise Architecture Chasm What is the Enterprise Architecture Chasm? First, a quick Google search didn’t find any previous references to the term Enterprise Architecture Chasm, at least not in the context I’m using it. So what am I talking about? We need … Continue reading
Crossing the EA Chasm: Automating Enterprise Architecture Modeling #2
[Updated November 6, 2016: Added Database/Web Services Farm Example #2] In the previous article Crossing the EA Chasm: Automating Enterprise Architecture Modeling, I included a simple example of how a current state enterprise architecture model can be created and maintained automatically. The … Continue reading
Crossing the EA Chasm: Automating Enterprise Architecture Modeling #1
If you have been following my Crossing the EA Chasm blog series (and related articles), you’ll have noticed a number of common themes: How to challenge the Enterprise Architecture Chasm (and The Strategy Chasm) Use of Open Repository Strategies for unlocking and automating … Continue reading
Crossing the EA Chasm: Enterprise Architecture Diagrams Your Grandmother (and CIO) Will Love
[Updated October 13, 2016] PLEASE POST A COMMENT ABOUT WHY THIS PAGE IS IMPORTANT TO YOU. This particular page is 1 of my top 5 most viewed pages (ever) and I’d like to understand why. Thank you! Let’s face it … Continue reading
Crossing the EA Chasm: Open Repository Strategies for Enterprise Architecture
[Updated October 27, 2016] In a recent posting (Crossing the Enterprise Architecture Chasm), I offered a definition for the term Enterprise Architecture Chasm, the practical gap that will always exist between enterprise architecture and an organization’s systems, strategies, assets, and processes … Continue reading
Crossing the Chasm: Progressive Enterprise Architecture Model (PEAM)
[Updated October 5, 2016] Inspired by Gerben Wierda’s thoughtful discussion about how the full framework is depicted in the new ArchiMate* 3.0 specification (An AchiMate 3 Map (Layers? What Layers! — 1)), I’m going to suggest there’s another level of improvement that can … Continue reading
Michael Herman, Blockchain Developer, Enterprise Architect and Data Scientist: #Graphitization Inventor
COPYRIGHT © 2016-2017 by Michael Herman, Seattle, Washington and Toronto, Canada. All rights reserved. Michael Herman is an expert when it comes to the mathematical modeling, analysis, and visualization of almost everything: Large enterprise organizations, Commercial, global-scale, cloud services platforms, … Continue reading
What are the differences between improving the design (and operation) of a smart city, an aircraft engine, a muscle car, a large enterprise, and/or an integrated commercial global cloud services platform …all running at hyperscale?
COPYRIGHT © 2016-2017 by Michael Herman, Toronto, Canada. All rights reserved. [Updated June 16, 2018] Question: What are the differences between improving the design (and operation) of: a smart city, an aircraft engine, a muscle car, a large enterprise, and/or … Continue reading
Crossing the EA Chasm: #Graphitization of ArchiMate 3.0 – Iteration 2
COPYRIGHT © 2016-2017 by Michael Herman, Toronto, Canada. All rights reserved. First Draft: April 5, 2017 This article documents a number of parallel efforts to improve the usability, understandability, utility, and correctness of the ArchiMate 3.0 Specification. In particular, this … Continue reading
Filed under ArchiMate, Architecture Reference Models, Automated Enterprise Architecture Modeling, Crossing the EA Charm, Definitions, Domain Specification Languages (DSL), Enterprise Architecture, Enterprise Architecture Chasm, graph database, Graphitization, ModelMate, ModelMate Information Architecture for ArchiMate, ModelMate Information Architecture for Languages, Progressive Enterprise Architecture Map (PEAM), The Open Group
Crossing the EA Chasm: ArchiMate 3.0, fix it or re-purpose it?
COPYRIGHT © 2016-2017 by Michael Herman, Toronto, Canada. All rights reserved. It is the end of January 2017 and, recently, there has been a lot of discussion in the LinkedIn ArchiMate group about the ArchiMate language for enterprise architecture (EA), … Continue reading