Aggregated enterprise architecture wisdom
I wrote a post on Chess and the Art of Enterprise Architecture about ways to look at self-service from an architectural perspective: “I, Robot” – there is no such thing as ‘Customer Self-Service’. In it, I argue that saying that … Continue reading →
Recently, Samuel Holcman published the short Outside-In vs. Inside-Out in Enterprise Architecture document and announced it on LinkedIn. The issue he raises is that the clients of organisations more and more seem to become the ones that perform the organisation’s processes (e.g. self-service), … Continue reading →
By Loren K. Baynes, Director, Global Marketing Communications, The Open Group Day two, February 3, kicked off with a presentation by Allen Brown, President and CEO of The Open Group, “What I Don’t Need from Business Architecture… and What I … Continue reading →
I’ve tried explaining my job as an Enterprise Architect to a number of people, including my parents, and after I’m done I get that “sure, whatever you say” kind of a look.
I’ll not delve into my job description here, except to say that a s…
TOGAF and ArchiMate are two standards managed by The Open Group and are adopted by more than 80% of the world’s leading enterprises. Our poster explains how these two can be used together to support your Enterprise Architecture work. Click here to view this resource.
By Loren K. Baynes, Director, Global Marketing Communications, The Open Group The Open Group San Diego 2015, with over 200 guests in attendance, had a powerful start on Monday, February 2 with a presentation by Dawn Meyerriecks, CIA Deputy Director … Continue reading →
Good e-Learning are offering a free trial of their online TOGAF 9 courses. Follow this link for further details https://www.goodelearning.com/Courses/Free_Trials? All you need to do to access a free trial is either log in or register as a member of Good e-Learning. As a member, you’ll also get access to their extensive library of free…
At the root of the IT transformation failures is the current culture of lack of governance and accountability. As a rule, those responsible must be accountable as well.
Imagine you are asked to define business requirements and constraints for a set of business rules as part of the design of a solution. What would be the approach you would use?
Okay, I’ll admit to a certain amount of frustration here… Yes, I’ve been talking a lot about toolsets for enterprise-architecture and the like, the ‘Why’ for a new type of toolset, the workflows within which such toolsets would appear and…
2014 was the year when digital became a significant priority for organisations, for the first time customers were becoming more advanced in the use of technologies and with this came a greater level of expectation. Customers (Including me) expected things in digital to be quicker, and just work. However most were left disappointed (including me) when Read More
|
|
A Historical Look at Enterprise Architecture with John ZachmanAn Open Group Blog |
The following is copy of the Open Group’s interview tih John A. Zachman in prepraration for his tutorial on the synergy between The Zachman Framework™ and TOGAF® for The Open Goup – Enabling Boundaryless Information Flow Conference in San Diego – February 2-5, 2015.
By The Open Group
John Zachman’s Zachman Framework is widely recognized as the foundation and historical basis for Enterprise Architecture. On Tuesday, Feb. 3, during The Open Group’s San Diego 2015 event, Zachman will be giving the morning’s keynote address entitled “Zachman on the Zachman Framework and How it Complements TOGAF® and Other Frameworks.”
We recently spoke to Zachman in advance of the event about the origins of his framework, the state of Enterprise Architecture and the skills he believes EAs need today.
As a discipline, Enterprise Architecture is still fairly young. It began getting traction in the mid to late 1980s after John Zachman published an article describing a framework for information systems architectures in the IBM Systems Journal. Zachman said he lived to regret initially calling his framework “A Framework for Information Systems Architecture,” instead of “Enterprise Architecture” because the framework actually has nothing to do with information systems.
