Keywords: , , , , , , , ,

David Mayo and Michael Tiemann


Enterprise Architecture, widely used in commercial ventures and federal agencies, has been viewed primarily as an IT discipline and has been relegated to the office of the Chief Information Officer or the Chief Technology Officer. In this paper, the authors argue that EA has the potential for far-reaching impact on an organization’s “bottom line.” In many organizations, the EA is the only repository of enterprise-wide abstractions of the business. To begin to realize its potential, the EA needs to be exploited by enterprise management processes and should be organizationally re-located where its influence can be far more pervasive. By positioning the EA as a repository for enterprise management, it can integrate discrete business operations and strategies to enable a more efficient, more agile organization.


service oriented architecture, adaptive enterprise, enterprise architecture repository, enterprise management, effectiveness

About the authors

David Mayo is co-founder and Vice President of Everware, a professional services firm specializing in enterprise architecture, serviceoriented architecture, and software application development using component-based me~hod~. He i.s a waduate of the University of California at RiverSide and received his M.A. in economics from the University of British Columbia in 1978. His research interests inclu~e the business value of EA, IT strategic planning, and methods for dramatically accelerating the development of business software applications. Mr. Mayo chairs the Components Subcommittee of the Industry Advisory Council’s Enterprise Architecture Shared Interest Group and has co-authored several papers on EA topics. He is currently a senior advisor to the EA program of the U.S. Department of Homeland Security.

Michael Tiemann is the Enterprise Architecture Practice Manager at AT&T Government Solutions. A graduate of Texas A&M University, where he earned a bachelor’s degree in architecture, Mr. Tiemann also holds an M.S. in Systems Management from University of Southern California. Prior to joining AT&T, he completed a distinguished career in the federal government, including the position of Chief Architect for the Department of Energy. He was DOE’s representative to the Federal CIO Council’s Architecture and Infrastructure Committee and was the founding Chair of the F~deral Architecture Working Group. Mr. Tiemann, who currently chairs the Governance Subcommittee of the Industry Advisory Council’s Enterprise Architecture Shared Interest Group, has wntten and lectured widely on various aspects of EA.


International Business Machines (1988). B~siness Systems Planning for StrategiC Alignment. IBM Corporation, NY, 1988.

Martin, J. and Finkelstein, C. (1981). Information Engineering. Savant Institute, Carnforth: Lancs, UK, 1981.

Prahalad, C., Krishnan, M., and Ramaswarmy, V. (~0?2). “The Essence of Business Agility,” Optimize Magazine, September 2002, Issue 22.

Spewak, S. H. (1992). Enterprise Architecture Planning: Developing a Blueprint for Data. Applications. and Technology. Wiley & Sons NY.

Stevenson, DA (1996) “Component Based Enterprise Architecture.” Unpublished masters degree di~sertation, University of Cape Town, South Afnca.

United States Congress (1996). The ClingerCohen Act of 1996. (Public Law 104-106).

United States Congress. The Sarbanes-Oxley Act of 2002, (HR 3763). Sarbanes, P. and Oxley, M. (Public Law 107-204).

United States Government Accountability Office (2003). Information Technology: A Framework for Assessing and Improving Enterprise Architecture Management (Version 1.1) (GAO- 03-584G), April 2003.

United States Office of Management and Budget (2005). Budget of the United States Government. Fiscal Year 2006. February 2005.

United States Office of Management and Budget (2002). Circular A-130, Revised; Transmittal Memorandum NO.4.

United States Office of Management and Budget (2001). OMB Memorandum No. M-97-16, Information Technology Architectures, Jun 1997

Zachman, J. ”The Zachman Framework for Enterprise Architecture.” Zachman International 2002.

Journal of Enterprise Architecture

Leave a Comment