Organizations are finding that computer systems are very complex and seldom do these systems produce a real business value to the organization (Session, 2007). Businesses are searching for an answer and that answer may be for an organizational to develop an enterprise architecture (EA). The complexity and constant change that occurs in business may be controlled by developing an EA, and this will facilitate alignment between the business objectives, business processes, and information systems (Ylim & Halttunenb, 2007). This may reduce the redundancies of system functions, the data redundancies that exist, and help to integrate the data into meaningful information for various levels within the organization. Developing a useable EA is no
…show more content…
This article described the 6 by 6 matrix in its entirety, which was the first time publication expanded beyond the first three columns. It also mentions that this framework is classification schema, meaning it organizes documentation that describes the organization, a system, or staffing, which means it is flexible. This framework is six rows by six columns and there needs to be an artifact in every cell. If columns and or rows are left out, then this is no long a Zachman Framework (Zachman, 2004). Shah and Kourdi (2007) states, “These frameworks simplify the architecture’s development and ensure complete coverage of the architectural dimensions of the designed solution through a common terminology” (p.37). The Zachman Framework consists of 36 cells that collect non-redundant primitive artifacts into each one of the cells. Bahill, Botta, and Daniels (2006) states, “This process helps to ensure complete coverage of the architectural dimensions of an organization” (p.2). Each row and column has a specific purpose within the framework follows.
Bahill et al.,( 2006) states, “The Zachman Framework is a normalized six by six classification schema for organizing descriptive representation of an enterprise , while the columns depict different areas of interest within those perspectives (p. 2). This allows the various views of the subject under consideration, from the stakeholder to the implementation individuals. Because this model is normalized,