|
Kunal Bhat
Entrepreneur, India
|
Enterprise Architecture Implementation Methods
I have been trying to understand various methods to develop/streamline the EA for an organization and realized that the Zachman framework is useful in identifying key entities/areas and outcomes. What I am now looking for is the process or methodology to get the implementation in place in a simplified and traceable manner - keeping standards and practical feasibility in sight.
X
Sign up for free
Welcome to the Enterprise Architecture (Zachman Framework) forum of 12manage.
Here we exchange knowledge and experiences in the field of Enterprise Architecture (Zachman Framework).
❗Sign up now to gain access to 12manage. Completely free.
X
Continue for free
Please sign up and login to continue reading.
Here we exchange knowledge and experiences in the field of Enterprise Architecture (Zachman Framework).
❗Sign up now to gain access to 12manage. Completely free.
| |
|
|
| |
|
Phillips, United States
|
|
Enterprise Architecture Implementation H I Kunai, TOGAF provides a a method to develop EA. See this link.
The output of EA ia a proposed IT architecture that will meet your future business needs (so your business goals and strategy is the starting point - and then you devise an architecture to enable it, or at least that wont prevent it).
|
| |
|
Kunal Bhat
Entrepreneur, India
|
|
EA Implementation: TOGAF Thanks Mr. Phillips for your inputs. following your suggestion I looked at TOGAF and also looked at the Zachman framework a little more closely.
I have been able to achieve a blend between to two to achieve some of my key goals.
However, I noticed that in each instance, there is no single standard of merging the two and one needs to look them up all over again from the perspective of the problem at hand to arrive at a 'custom' and 'usable' end blend.
|
| |
|
Robert Logie
Consultant, South Africa
|
|
EA Implementation: TOGAF Hi Khunai - I think the key difference you need to realise is that TOGAF is essentially a methodology, but at the outset does not define what deliverables/artifacts need to be available in order to achieve completion - those outputs are selected when the project/process is initiated by the high level process is being tailored.
Zachman is essentially a matrix of possible artifacts that can be used to give you insight into an enterprise, but does not tell you what methodology to use in order to take an existing organisation into the future.
This is where these two perspectives become complimentary because by using the TOGAF process you can deliver the Zachman documents at the appropriate time and with the relevent perspective ("as-is" versus "to-be"), but be aware that there are other deliverables as views that Zachman does not include that you may want to add in the TOGAF outputs as well as the fact that concepts like "contracts for delivery" do not exist in Zachman.
Hope this helps.
|
| |
|
Kunal Bhat
Entrepreneur, India
|
|
Enterprise Architecture Implementation: TOGAF Robert, thanks. This is quite helpful.
|
| |
|
Dave Woods, United States
|
|
Enterprise Architecture Maturity Levels Kunal, it may be helpful to honestly assess the maturity of your organization and its ability to adopt enterprise architecture. The method and approach you take is highly dependent on your organization's ability to value it. Since the value is determined by your customers, you may need to work bottom-up or middle-out to show the enterprise relationships and dependencies. I would not recommend top-down if you are just beginning to gain supporters.
Enterprise Architecture Maturity Levels:
- INITIAL (chaotic, ad hoc, individual heroics) - the starting point for use of a new or undocumented repeat process.
- REPEATABLE - the process is at least documented sufficiently such that repeating the same steps may be attempted.
- DEFINED - the process is defined/confirmed as a standard business process, and decomposed to levels 0, 1 and 2 (the latter being Work Instructions).
- MANAGED - the process is quantitatively managed in accordance with agreed-upon metrics.
- OPTIMIZING - process management includes deliberate process optimization/improvement.
|
| |
|
Anonymous
|
|
TOGAF - the Method is ADM When Robert speaks of TOGAF as a method, he is specifically referring to the ADM, the Architecture Development Methodology. This is not dependent on the entire TOGAF framework and hence is useful for achieving the most appropriate artefacts, e.g. zachman if that has been decided to be a good starting point - personally, I tend to think Zachman often is. Compared to the Overall TOGAF framework, the ADM is more practically applicable and it is more easily recognisable how progress is achieved. That recommendation should prove worth your while.
|
| |
|
Johan Brynte
Business Consultant, Sweden
|
|
A Comparison of the Top Four Enterprise Architecture Frameworks (Zachman, FEAF, DoDAF, TOGAF) Worth considering before taking on any EA framework is reading this article. Challenge is how do we get real value out of EA? Make it simple and useful for the business and the IT organization, not just satisfying the top management.
"A comparison of the top four enterprise architecture frameworks" by Svyatoslav Kotusev includes:
- Zachman Framework (John Zachman and Steven Spewak)
- Federal Enterprise Architecture Framework (FEAF)
- Department of Defense Architecture Framework (DoDAF)
- The Open Group Architecture Framework (TOGAF)
Here is a link to the critical article.
Quoting: "... too many EA teams to lock themselves in their ivory towers, snowed under by hundreds of models that no one is able to keep up to date".
|
|
|
|
|
More on Enterprise Architecture (Zachman Framework)
|
|
|
Log in
Comments by date▼