A method to define an Enterprise Architecture using the Zachman Framework

ABSTRACT

The proliferation of IT and its consequent dispersion is an enterprise reality, however, most organizations do not have adequate tools and/or methodologies that enable the management and coordination of their Information Systems. The Zachman Framework provides a structured way for any organization to acquire the necessary knowledge about itself with respect to the Enterprise Architecture. Zachman proposes a logical structure for classifying and organizing the descriptive representations of an enterprise, in different dimensions, and each dimension can be perceived in different perspectives.In this paper, we propose a method for achieving an Enterprise Architecture Framework, based on the Zachman Framework Business and IS perspectives, that defines the several artifacts for each cell, and a method which defines the sequence of filling up each cell in a top-down and incremental approach. We also present a tool developed for the purpose of supporting the Zachman Framework concepts. The tool: (i) behaves as an information repository for the framework's concepts; (ii) produces the proposed artifacts that represent each cell contents, (iii) allows multi-dimensional analysis among cell's elements, which is concerned with perspectives (rows) and/or dimensions (columns) dependency; and (iv) finally, evaluate the integrity, dependency and, business and information systems alignment level, through the answers defined for each framework dimension.

REFERENCES

• 1: Ambler, Scott W., Agile Enterprise Architecture: Beyond Enterprise Data Modeling, 2002, http://www.agiledata.org/essays/enterpriseArchitecture.html
• 2: Beckhard, R. and Pritchard, W., Changing the Essence: The Art of Creating and Leading Fundamental Change in Organisations, Jossey-Bass, San Francisco, 1992
• 3: Melissa A. Cook, Building enterprise information architectures: reengineering information systems, Prentice-Hall, Inc., Upper Saddle River, NJ, 1996
• 4: Hay, David C., The Zachman Framework: An introduction, 1997, http://www.tdan.com/i001fe01.htm
• 5: http://www.eacommunity.com/resources/download/bolton_what.pdf
• 6: William H. Inmon , John A. Zachman , Jonathan G. Geiger, Data Stores, Data Warehousing and the Zachman Framework: Managing Enterprise Knowledge, McGraw-Hill, Inc., New York, NY, 1997
• 7: Kenneth C. Laudon , Jane P. Laudon, Management Information Systems: Organization and Technology, Prentice-Hall, Inc., Upper Saddle River, NJ, 1995
• 8: Niederman, Fred, Brancheau, James C. and Wetherbe, James C., Information Systemns Management Issues for the 1990s, MIS Quartely, Volume 14, Number 4, December 1991
• 9: Pereira, Carla Marques and Sousa, Pedro, Getting into the misalignment between Business and Information Systems, The 10th European Conference on Information Technology Evaluation, Madrid, Spain, September 2003
• 10: Steven H. Spewak , Steven C. Hill, Enterprise architecture planning: developing a blueprint for data, applications and technology, QED Information Sciences, Inc., Wellesley, MA, 1993
• 11: Stata, Ray, Organizational Learning - The Key to Management Innovation, Sloan Management Review, Volume 30, Number 3, 1989
• 12: Vasconcelos, André, Sousa, Pedro and Tribolet, José, A profile for modelling Information Systems, Architectures, Conferencia Iberoamericana en Sistemas, Cibernética e Informática (CISCI 2003) del 31 de Julio al 02 de Agosto 2003, Orlando, Florida
• 13: Young, Colleen, The Unexpected Case for Enterprise IT Architectures, Gartner Group Strategy, Trends & Tactics, 9 January 2001
• 14: John A. Zachman, A framework for information systems architecture, IBM Systems Journal, v.26 n.3, p.276-292, 1987

INDEX TERMS

General Terms:
Design, Documentation, Management

Keywords:
Application Architecture, Business Architecture, Enterprise Architecture, Information Architecture, Zachman Framework