Strength of Zachman Framework
The Zachman framework has several strengths:
* The framework is known and is an accepted concept for enterprise architecture by the data community.
* The Zachman framework explains all the angles that an organisation should consist of. This can be applied within the Enterprise Unified Process (EUP).
* The Zachman framework clearly states that there are many stakeholders, such as suppliers, business partners and customers and not only architects or developers for that matter. (Wambler, S, 2002).
Weaknesses of Zachman Framework
On the other hand, the framework bears several weaknesses:
* The framework consists of 36 cells where every cell can hold more than one model thus making the approach a heavy load for …show more content…
Figure 17: Information Systems Architecture - A Framework (1984)
The framework was first introduced in 1984, where it was named “Information Systems Architecture – A Framework” and contains only three columns; the data, function and network while all six rows where accounted for from the first time the framework was created by John Zachman. Furthermore, John Zachman was unsure about the framework he created since the Enterprise Architecture had not come to light at that time (Zachman, J, 2009).
Figure 18: Framework for Information Systems Architecture (1987)
As mentioned the framework was first thought of in 1984 but was published by IBM Systems Journal in 1987, being the original version of the framework. It was named “Framework for Information Systems Architecture”. The three columns; organisation, timing and motivation, known today were not necessarily important at that time since the framework was intended for Information Systems (IS) (Zachman, J, 2009).
Figure 19: Framework for Information Systems Architecture/The Zachman Framework …show more content…
We notice that rows one till 5 have been named differently changing to “Planner”, “Owner”, “Designer”, “Builder”, and “Sub-Contractor” respectively. In addition, columns 4, 5 and 6 have the same ideas in each of their cells since back in the day the information systems community lacked the experience and knowledge, thus all the data provided are John’s own models (Zachman, J, 2009).
Figure 20: The Zachman Framework: Enterprise Architecture - A Framework (1993)
In 1993 John Zachman named the framework as “Enterprise Architecture” since he sensed that people would change their minds regarding information systems and start accepting the idea of an Enterprise-wide architecture. Furthermore, Zachman still used the three columns framework for his lecture back then since the Information Systems (IS) idea was more dominant (Zachman, J, 2009).
Figure 21: The Zachman Framework
The Zachman framework has several strengths:
* The framework is known and is an accepted concept for enterprise architecture by the data community.
* The Zachman framework explains all the angles that an organisation should consist of. This can be applied within the Enterprise Unified Process (EUP).
* The Zachman framework clearly states that there are many stakeholders, such as suppliers, business partners and customers and not only architects or developers for that matter. (Wambler, S, 2002).
Weaknesses of Zachman Framework
On the other hand, the framework bears several weaknesses:
* The framework consists of 36 cells where every cell can hold more than one model thus making the approach a heavy load for …show more content…
Figure 17: Information Systems Architecture - A Framework (1984)
The framework was first introduced in 1984, where it was named “Information Systems Architecture – A Framework” and contains only three columns; the data, function and network while all six rows where accounted for from the first time the framework was created by John Zachman. Furthermore, John Zachman was unsure about the framework he created since the Enterprise Architecture had not come to light at that time (Zachman, J, 2009).
Figure 18: Framework for Information Systems Architecture (1987)
As mentioned the framework was first thought of in 1984 but was published by IBM Systems Journal in 1987, being the original version of the framework. It was named “Framework for Information Systems Architecture”. The three columns; organisation, timing and motivation, known today were not necessarily important at that time since the framework was intended for Information Systems (IS) (Zachman, J, 2009).
Figure 19: Framework for Information Systems Architecture/The Zachman Framework …show more content…
We notice that rows one till 5 have been named differently changing to “Planner”, “Owner”, “Designer”, “Builder”, and “Sub-Contractor” respectively. In addition, columns 4, 5 and 6 have the same ideas in each of their cells since back in the day the information systems community lacked the experience and knowledge, thus all the data provided are John’s own models (Zachman, J, 2009).
Figure 20: The Zachman Framework: Enterprise Architecture - A Framework (1993)
In 1993 John Zachman named the framework as “Enterprise Architecture” since he sensed that people would change their minds regarding information systems and start accepting the idea of an Enterprise-wide architecture. Furthermore, Zachman still used the three columns framework for his lecture back then since the Information Systems (IS) idea was more dominant (Zachman, J, 2009).
Figure 21: The Zachman Framework