Running Head: ZACHMAN FRAMEWORK complete model from the perspective of that row. Lastly the logic is relational between two instances of the same entity. The model is generic; it can be used to describe any object in detail (Zachman, J. P., n.d.). Below is a graphic depiction of the Zachman Framework. ( Zachman, J. A., n.d.) Strengths The Zachman framework provides the perspectives of all the various stakeholders involved in an EA modeling effort. Each stakeholder is assigned a view that they are most concerned with and this is followed with the business products/concerns that directly relate to that stakeholder’s view. This provides a good framework for defining the business and processes each unit is responsible for within
4 Running Head: ZACHMAN FRAMEWORK the organization. Additionally, the generic, broad model allows for the framework to work for any user with an EA need ( , n.d.) . Weaknesses While the Zachman framework has its strengths, it also possess’ weaknesses. One argument is the model forces a heavy documentation need on the organization that uses it. Each of the stakeholders require a documentation on, who, what, where, when, why, and how for their respective role within the framework. The documentation heavy approach can take away from the focus on current business problems facing the organization. Additionally, the sheer number of objects within the framework itself can create a large time and effort constraint for an organization ( , n.d.). Practical Examples: Government of Ontario The Zachman Framework was employed by the government of Ontario with great success. The goal was to improve overall communications between government and business while creating easier access to information. The use of the Zachman model helped defined the organizations respective parts and align the communications structure architecture. Some of the improvements were documented
You've reached the end of your free preview.
Want to read all 6 pages?