Zachman Framework

from Wikipedia, the free encyclopedia

The Zachman Framework is a domain-neutral framework for the development of information systems designed by John Zachman in 1987 . As the conceptual framework of the Management Frameworks group , it is one of over 50 frameworks available on the market.

It forms a guideline that contains suggestions as to which aspects should be taken into account from which perspectives in order to successfully set up the IT architecture of a company . With the help of this modeling, both the documentation and the planning of such a project can be supported if, for example, it is to be understood which decisions have led to which technical implementations.

construction

In contrast to similar frameworks, which often contain procedural models, the Zachman Framework does not show a process sequence to be followed, but focuses on the roles involved, to which it assigns objects to be viewed from different perspectives. No specific methods are specified, but only the view to be followed is pre-structured. The Zachman Framework is an aid to comprehensively consider all relevant aspects from all perspectives in system planning and development.

roll

Perspectives

  • What (data)
  • How (function)
  • Where (network)
  • Who (people)
  • When time)
  • Why (motivation)

Zachman Framework

DATA
What 		FUNCTION
Like 		NETWORK
Where 		PEOPLE
Who 		TIME
when 		MOTIVATION
Why
Objective / area
( context-dependent )
→ Role: planner 		List of important factors in business List of core processes List of business locations List of important organizations List of events List of business goals / strategies
Enterprise model
( conceptual )
→ Role: Owner 		Conceptual data model / object model Business process model Business logistics system Workflow model Schedule Business plan
System model
( logical )
→ Role: Designer 		Logical data model System architecture model Distributed Systems Architecture Human interface architecture Process structure Business rule model
Technology model
( physical )
→ Role: Builder 		Physical data / class model Technology design mock-up Technology architecture Presentation architecture Control structure Rule design
Detailed representation
( out of context )
→ Role: Programmer 		Data definitions program Network architecture Security architecture Time schedule Rule specification
Company
→ Role: User 		Usable data Intended use Usable network Work organization Included schedule Working method

rating

The perspectives “ what ”, “ how ” and “ when ” are taken into account in many different methods. The consideration of networking with the help of the “ where ” perspective and the reference to a reason why certain measures are necessary are taken up in the “ why ” perspective , which is novel.

The Zachman Framework is a generic concept with a low degree of formalization, which does not include any specific specifications about the methods to be used, but shows the objectives to be achieved in each case. By taking into account the different roles involved, it covers a large part of the phases of the software development process. However, the accompanying project management is hidden. Since this concept is an order scheme, the potential degree of automation is relatively low. Due to its methodological openness, however, it enables the inclusion of new methods, so that it can maintain its topicality in the long term.

literature

  • JA Zachman: A framework for information systems architecture . In: IBM Systems Journal . tape 26 , no. 3 , 1987, pp. 277–293 , doi : 10.1147 / sj.263.0276 ( research.ibm.com ( Memento from January 20, 2007 in the Internet Archive ) [PDF]).
  • JA Zachman: Enterprise Architecture, A Framework. Zachman Institute, 2004.
  • JF Sowa, JA Zachman: Extending and formalizing the framework for information systems architecture . In: IBM Systems Journal . tape 31 , no. 3 , 1992, p. 590-616 , doi : 10.1147 / sj.313.0590 .
  • WH Inmon, JA Zachman, JG Geiger: Data stores, data warehousing, and the Zachman framework. Managing enterprise knowledge. New York 1997, ISBN 0-07-031429-2 .
  • C. Filß, R. Höhn, S. Höppner, M. Schumacher, H. Wetzel: Framework for the selection of procedural models . Working report of the GI specialist group WI-VM, working group “procedural model types ”, March 2005. (www.faw.uni-linz.ac.at ( Memento from September 7, 2014 in the Internet Archive ); PDF; 1.17 MB)
  • U. Frank: Multi-perspective company modeling. Theoretical background and design of an object-oriented development environment. Oldenbourg, 1994, ISBN 3-486-22922-2 , pp. 150-158. (wi-inf.uni-duisburg-essen.de ; PDF; 2.28 MB)
  • Dirk Matthes: Enterprise Architecture Frameworks Compendium. Springer Science + Business Media , 2011, ISBN 978-3-642-12954-4 , pp. 210-213. (More than fifty frameworks for IT management are briefly presented with their respective benefits. Then Matthes describes in detail more than thirty frameworks available on the market - including the Zachman EA framework. The focus is on the representation of the respective framework meta-models with the architecture offered therein - and procedural reference models.) (springer.com)
  • Alexander Umek: Good IT is created in a flexible control loop . In: Computerwoche . No. August 31 , 2003 ( computerwoche.de ).

Individual evidence

  1. ↑ Dirk Matthes: Enterprise Architecture Frameworks Compendium. Over 50 frameworks for IT management. Springer Verlag, 2011, ISBN 978-3-642-12954-4 .
  2. ↑ C. Filß, R. Höhn, S. Höppner, M. Schumacher, H. Wetzel: Framework for the selection of procedural models . 2005, p. 206.
  3. ↑ C. Filß, R. Höhn, S. Höppner, M. Schumacher, H. Wetzel: Framework for the selection of procedural models . 2005, p. 204.
  4. ↑ C. Filß, R. Höhn, S. Höppner, M. Schumacher, H. Wetzel: Framework for the selection of procedural models . 2005, pp. 205f.

Web links