Keywords: , , , , , , , , ,

This study presents a general review and comparison of the emerging profession of the enterprise architect and the established profession of the traditional architect. This study is intended to establish a context for further research and publication on enterprise architecture as a profession and the applicable lessons from traditional architecture. Additionally, the findings suggest that the profession of the enterprise architect may be an extension of the roles of a traditional architect and the likenesses of each profession are noted.

Author Biographies

Professor Carolyn Strano teaches Enterprise Architecture for Managers as part of the Chief Information Officer, Enterprise Architecture, and e-Government Certificate Programs at the National Defense University’s Information Resources Management College. She participated in the development of A Practical Guide to Federal Enterprise Architecture that was published by the Federal Chief Information Officers Council in 2001. She has presented at numerous forums such as the ArchPlus Seminars in Washington, D.C., a Management Seminar for GAO, an executive seminar for Environmental Protection Agency, EA conferences, the Software Technology Conference, Department of Interior’s Enterprise Architecture Summit, Internal Revenue Service EA Workshop, and was a guest speaker at Syracuse University’s graduate program in Information Management. Additionally Ms. Strano has provided advice on EA efforts for the Department of Defense Financial Management System and the Blue Ribbon Advisory Team for the U.S. State Department. She has over 30 years of experience in information systems and participated in the development and implementation of the National Airspace System architecture while managing the System Engineering Division at the Federal Aviation Administration. Ms. Strano is currently pursuing a Doctorate in Business Administration with a concentration in Information Systems.

Professor Qamar Rehmani teaches in the Information Systems concentration at Argosy University and has chaired a number of doctoral dissertations in Business Administration. He currently serves on the university’s institutional research and technology committees. Dr. Rehmani has over 20 years of experience in information systems through his work in academia, industry, and as an entrepreneur. In the computer industry he has developed and implemented programs for improving product support, managed product development, and has overseen design and quality assurance for several communications products. As an entrepreneur, he founded an internet service provider during the midnineties. He has also worked on research projects for NASA’s Space Shuttle. Dr. Rehmani has a Bachelor of Science in Electrical Engineering from the Indian Institute of Technology, Kanpur, and earned his Master of Business Administration and PhD degrees from the University of Houston.


Association of Enterprise Architects (2005). (aEA) www.aeajournal.org

Akella, J., and Barlow, C. (2004) “Defining the Role of the Chief Architect.” Enterprise Architect.

Allega, P. (2004). “The Drive for a Globally Certified Enterprise Architect.” EA Community. META Trend. Meta Group, Inc.

Bernard, S. (2004). An Introduction to Enterprise Architecture. AuthorHouse, IL.

Bredemeyer, D., Malan, R. (2004). “What It Takes to Be a Great Enterprise Architect.” Enterprise Architecture. Volume 7, Number 8.

Clark, J. (2000). “Regulation.” Architecture Australia. July/August 2000, pgs 22-24.

Cook, M.A. (1994). Building Enterprise Information Architectures. Reengineering Information Systems. Prentice-Hall, Inc.

Cuff, D. (1996). “Celebrate the Gap Between Education and Practice.” Architecture. Aug 96, 85(8}, pgs 94-95.

Davidson, C. (2000). Critique. Architectural Record. Feb 00, 189 (2), pgs 51-53.

Dillon, A. (2001 }(a). “Practice Makes Perfect: IA at the Beginning of the End?” Bulletin of the American Society for Information Science. April/May/2001, 27(4), pgs 28-29.

Dillon, A. (2001 }(b). “Architecture, Butterflies and Common Sense: The ABC’s of a Profession on the Rise.” Bulletin of the American Society for Information Science. Feb-Mar 2001 , 27( 3) pgs 28-29.

Duffy, F. (1996). “Communicate, Don’t Isolate.” Architecture. 85(2}, pgs 55-58.

Enterprise Architecture Interest Group (2005). (EAIG). http://www.eaig.org/

Edwards J.K. (1998). The Education of an Architect: Guide to Architecture Schools (Sixth Edition). Association of Collegiate Schools of Architecture. Washington, D.C.

Fisher, T. (1994). “Can This Profession be Saved?” Progressive Architecture. Feb 94, 75(2}, pgs 44-51.

Global Enterprise Architecture Organization (2005). (GEAO). www.geao.org

Glazier, N. (1990). “The Prince, the People, and the Architects.” American Scholar. Fall 1990, 59(4}, pgs 12-20.

Goldberger, P. (1995). “Back to the Past.” New Republic. 213 (22), pgs 42-48.

Hite, R. (2000). “Enterprise Architectures: An Auditor’s Perspective.” ArchPlus Seminar, September, 2000, Washington, D.C.

Institute for Enterprise Architecture Development (2005). (IFEAD). www.enterprise-architecture.info/

Kubany, E., and Linn, C. (1999). ‘Why Architects Don’t Charge Enough.” Architectural Record. Oct 99, pgs 110-119.

LePatner, B. (1996). “Listen up or Lose the Client.” Architecture. Feb 96 85(2), pgs 153- 156.

Manley, S., and Parnaby R. (2000). “The Return of the Architect-Planner?” Planning Practice and Research. 15(3) pgs 269-277.

Mazumdar, et al (1997). “Intergroup Social Relations and Architecture: Vernacular Architecture and Issues of Status, Power, and Conflict.” Environment and Behavior. May 1997,29(3), pgs 374-422.

McGlynn, S., and Murrain, P. (1994). ”The Politics of Urban Design.” Planning Practice and Research. 9(2) pgs 311-320.

Michael, S. (2004)(a). “Chief Architects Gather.” Federal Computer Week. Apr 6 ’04.

Michael, S. (2004)(b). “EA University.” Federal Computer Week. September 6, 2004.

Miller, J. (2004). “CIO Council Finds IT Workers Lack Necessary Skills.” Government Computer News. June 1, 2004.

Monaghan, P. (2000). “Verbatim.” Chronicle of Higher Education. 46(34) pgs A24-26.

O’Rourke, C., Fishman, N., and Selkow, W. (2003). Enterprise Architecture Using the Zachman Framework. Thompson Course Technology, Massachusetts.

Pavlak, A. (2005). Creating Enterprise Architecture with Special Expert Teams. alEA DC Metro Chapter presentation, July 2005.

Ramstack, T. (2005). “Resigned to Old Designs? Innovative GSA Architect’s Departure Worries Some.” The Washington Times. February 24, 2005.

Reed, K. (2001). “Government Policy on the Practice of Architecture” (editorial comments). Architecture. Aug 01, 90(8), pg 21.

Rogerson, P. (1996). “The Planner’s Dream.” Hospital Development. Apr 96,27(4) pgs 9-11

Ross, S. (1994). “Will Amateur CAD Put Residential Architects Out of Business?” Architectural Record. Apr 94 182(4) pgs 36-37

Rybczynski, W. (1992). “The Art of Building, or the Building or Art?” Wilson Quarterly. Autumn 1992, 16(4) pgs 46-57.

Salvadori, M. (1997). Architects and Engineers. Why Buildings Stand Up: The Strength of Architecture. W.W. Norton & Company, Inc., New York, pg 24.

Smith, P. (1995). “National Vocational Qualifications (Great Britain) Peril for Professions”. Times Higher Education Supplement. 1164, pgs 12-13.

Spewak, S. and Hill S. (1992). Enterprise Architecture Planning. Developing a Blueprint for Data. Applications and Technology. John Wiley and Sons, Inc. New York. pg.25.

Theuerkorn, R. (2005). Lightweight Enterprise Architectures. Auerbach Publications. Washington, D.C.

United States General Accounting Office (2003). Information Technology: A Framework for Assessing and Improving Enterprise Architecture Management (Version 1.1). Executive Guide. GAO-03-584G. April 2003.

Varangu, A. (1998). ”Taking a Holistic Approach to Suburbs.” Journal of Planning Literature. 12(4), pgs 469-548.

Woods, M.N. (1999). From Craft to Profession: The Practice of Architecture in Nineteenth Century America. University of California Berkeley Press. California.

Zachman, J.A. (1987). “A Framework for Information Systems Architecture.” IBM Systems Journal. Vol. 26, No.3, pgs 276-290.

Journal of Enterprise Architecture

Leave a Comment