Zachman’s is neither a framework nor an ontology, it is a development process
The vertical dimension describes the system development process beginning with the objectives establishment and conceptual design and ending with the Implementation.
Aggregated enterprise architecture wisdom
The vertical dimension describes the system development process beginning with the objectives establishment and conceptual design and ending with the Implementation.
What ontology-frameworks do we need, to make sense of the enterprise-architecture of a logistics-business? This is the first of five worked-examples of metaframeworks in practice – on how to hack and ‘smoosh-together’ existing frameworks to create appropriate tools to help…
If most of the frameworks we use in enterprise-architecture are ‘smooshed together’ from other frameworks, according to the needs of the context, then how do we do that ‘smooshing together’? More to the point, when and how and why should we…
Architects produce many types of models. One useful distinction is between AS-IS models (which describe the current situation) and TO-BE models (which describe some projected future situation). If we can compare an AS-IS model with a TO-BE model, we ca…
Defeat Darwinian Enterprise Model that is Adaptive, rather strive to achieve Generative Model that is transformative creating rich diversity from minimal sets. Connect – Strategy – Architecture / Operations – Implementation![]()
The real art of enterprise-architecture, and perhaps its hardest challenge, is in presenting the right level of detail. Not too little, not too much, but just enough. Just Enough Detail. To which people will, of course, immediately ask, “Okay, but how much detail is ‘Just Enough Detail’?”. And I’ll have to admit that there isn’t […]
Early this morning, while glancing through the latest tweets on my iphone, I was attracted by last post from Richard Veryard on slideshare: Preamble Good slideshow though, but since I felt that it is going a bit in many different directions, I felt that I had to react on this one, directly on my blog to […]![]()
Starting point Few weeks ago, I was on business trip, dining alone at my hotel restaurant in Gothenburg (sad story isn’t it ) I was using my favorite device: iphone 4 to read interesting Enterprise Architecture articles & papers, when, suddenly, my attention was caught by a direct reply on one of my tweets from […]![]()
Typically, the world of EA is boring. In this last few weeks, all bets are off as John Zachman goes to court and questions are raised about the near term and long term effects to the commercialization of EA Frameworks and the EA certification marketplace. It’s still early days, but challenges from the “father of EA” require consideration.
Typically, the world of EA is boring. In this last few weeks, all bets are off as John Zachman goes to court and questions are raised about the near term and long term effects to the commercialization of EA Frameworks and the EA certification marketplace. It’s still early days, but challenges from the “father of EA” require consideration.
The post John Zachman is Dead, Long Live John Zachman appeared first on Philip Allega.
My friend Nick Malik wrote a post – Zachman’s Fatal Flaw: No Row for Customer. Here is my response … Do I believe that Zachman’s Framework is fatally flawed? No. It all depends on your perspective and that to me is defined by your…
Yes, you need a LinkedIn Account. And yes, you have to be a member of Enterprise Architecture Network. But those two prerequisites are not very difficult to obtain. Meanwhile, there are a couple of very interesting discussions going o…