Zachman framework CTC - Cambridge Technical …

1 Warren Singer 1 The Zachman Enterprise FrameworkThe Origins and Purpose of the Zachman Enterprise FrameworkThe Zachman enterprise framework was invented by John Zachman in 1980 for IBM,and is now in the public domain. The framework borrows from business designprinciples in architecture and manufacturing and provides a way of viewing an enterpriseand its information systems from different perspectives, and showing how thecomponents of the enterprise are today s complex business environments, many large organisations have great difficultyresponding to change. Part of this difficulty is due to a lack of internal understanding ofthe complex structure and components in different areas of the organisation, wherelegacy information about the business is locked away in the minds of specific employeesor business units, without being made explicit.

2 The Zachman framework provides a means of classifying an organisation s is a proactive business tool, which can be used to model an organisation s existingfunctions, elements and processes - and help managebusiness change. The framework draws on Zachman sexperience of how change is managed in complexproducts such as aeroplanes and buildings. Although the framework can be used for informationsystems architecture (ISA) and is widely adopted bysystems analysts and database designers, John Zachmanhas stressed that it extends to the entire enterprisearchitecture, and is not restricted to simply informationarchitecture. The Zachman enterprise framework is represented and promoted by the ZIFA( Zachman Institute for framework Advancement) organisation. It is not a standard andthere are similar enterprise frameworks that have been derived from it, such as theFederal Enterprise architecture framework (FEAF), The Open Group ArchitectureFramework (TOGAF), and the Department of Defence architecture framework (DoDAF).

3 The framework provides a consistent and systematic way of describing an enterprise andhas been employed in many large organisations, such as Volkswagen, General Motors,Bank of America and Health Canada. Enterprise architecture isthe process used by abusiness to make explicitrepresentations of enterpriseoperations and resources,rather than relying on implicitnotions or understanding inindividual managers heads. Stan Loche Warren Singer 2 Relevance to Technical CommunicationsTechnical communicators are closely involved in information design and management,whether at the level of the user, the designer, the integrator or the builder. Traditionally,their role has been associated with the Information/IT architecture side of analysts are currently the main providers of enterprise architecture , given the depth of business knowledge and information managementexperience many Technical communicators can offer, documenting an enterprise sarchitecture is potentially a service that Technical communicators with a good level ofbusiness understanding could provide.

4 In addition, the way the Zachman model is structured, in terms of a clear breakdown ofinformation by audience and by standard questions, will be familiar to those working inthe communications disciplines, such as Technical the Zachman framework for a Knowledge Management ProjectI was first introduced to the Zachman Enterprise architecture in a project to documentthe architecture , processes and technology deployed in the IT department at a large,distributed organisation. The task was broader than the traditional Technical communicator s role of documentinga specific product or service. It involved managing a broad spectrum of knowledge andfinding the most efficient way to capture and store information about the enterprise sprocesses, procedures, systems, applications and first requirement was therefore the need for a suitable framework for organising theenterprise s information.

5 The Zachman enterprise model was suggested as a suitableframework for the project. How it worksThe easiest way to understand the Zachman Enterprise architecture framework is to viewit as a classification scheme represented visually as a table or matrix, with columns androws. Each cell within the matrix provides a unique model or representation of theenterprise. The information in each row of the matrix would be relevant to the particularperson in the enterprise viewing it. See Figure 1. Warren Singer 3 Figure 1: Adaptation of the Zachman Enterprise architecture FrameworkThe framework offers a set of descriptive representations or models relevant fordescribing an cell in the table must be aligned with the cells immediately above and below it. Allthe cells in each row also must be aligned with each other.

6 Each cell is the cells in one row forms a complete description of the enterprise from ColumnsThe columns represent the interrogatives or questions that are asked of the are: What (data) what is the business data, information or objects? How (function) how does the business work, , what are the business processes? Where (network) where are the businesses operations? Who (people) who are the people that run the business, what are the business unitsand their hierarchy? When (time) when are the business processes performed, , what are the businessschedules and workflows? Warren Singer 4 Why (motivation) why are the processes, people or locations important to thebusiness, , what are the business drivers or business objectives?The framework enables complex subjects to be distilled into systematic categories, usingthese six basic questions.

7 The answers to these questions will differ, depending on theperspective or audience (represented in the rows).The columns can be presented in any order. Table 1 provides an example of the contents in the Who or People ExampleAgentWork1 PlannerOrganisation listClass of agent2 OwnerOrganisation chartOrganization unitWork product3 DesignerHuman interface architectureroleDeliverable4 BuilderHuman/technology interfaceuserJob5 SubcontractorSecurity architectureidentityTransactionTable 1 : Contents of Cells in the People (Who) ColumnMatrix RowsEach row represents a distinct view of the organisation, from the perspective of differentaudiences. These are ordered in a desired priority row is allocated to each of the following audiences: Planner understands the business scope and can offer a contextual view of theenterprise.

8 Owner understands the business model and can provide a conceptual view of theenterprise. Builder - develops the system model and can build a logical view of the enterprise. Designer produces the technology model and can provide a physical view of theenterprise. Integrator (sub-contractor) will understand detailed representations of specificitems in the business, although they will have an out-of-context view of the enterprise. User provides a view of the functioning enterprise, from the perspective of a user ( ,an employee, partner or customer). Warren Singer 5 The first matrix row the Planner s ViewThis is the first row in the matrix. The planner s view of the enterprise is contextual. Theplanner looks at external requirements and business drivers, and is concerned withrepresenting the business functions.

9 The following information is of interest to theplanner:What or DataHow or ProcessWhere ornetworkWhen orscheduleWho or peopleWhyPlanner sviewA list of objectsthat the Enterpriseis interested in. A list of processesor functions thatthe organisationperforms. The businesslocations. The cycles andevents related toeach function..A list oforganisationsimportant to list example:Research areas,markets, products,services whatever isimportant at ahigh level to , testing,manufacturing,documenting,sellin g,distributing, list of businessoffices or regionsin which ,partners,resellers,contractors andother third partiesHigh-levelgoals andtargetsTable 2: Example of the Planner's viewPutting the framework into PractiseA logical point to start would be at the top left of the matrix and work your way downand across the table.

10 The relevant business information or models used to represent aspecific area of the business may already exist in formalised business plans, projectschedules, system specifications, procedure guides, organisation charts and othercorporate documents. As you go through the rows and columns of the matrix, there will be gaps that need to befilled, where implicit information known only to a single person or a few experts needsto be made explicit and available to a wider audience. There may be instances of overlapor a Technical communicator your role would be to ensure the information you gather iscomprehensive, reliable and appropriately categorised. At the same time, the businessobjective in this would be to gain a better understanding of the organisation sarchitecture, with the goal of managing change and reducing redundancies and information could be stored in a database or other file management system thatallows easy retrieval.