The increasing importance of Enterprise Architecture is driven by requirements for seamless inter-operation between business, rapidly changing market, and ever-changing information and systems technologies. Enterprise architecture defines the overall design structure of the business and the information and technical infrastructure that supports the business, based on defined principles and models that guide the planning and designing, building and operating the enterprise and its strategic choices. This article highlights the importance of a principles-based enterprise architecture framework as a design imperative for business service groups, information management teams, and application and technology solution groups; as as a foundation for achieving interoperability, integration, and alignment of an organization’s systems (business, information, technology) across an enterprise.
enterprise architecture, principles, framework, business, information, applications, technology
About the author
Richard Bryson is currently on executive interchange as a Senior Director supporting the Chief Architect for the Government of Canada (Treasury Board Secretariat, Chief Information Officer Branch). Mr. Bryson leads the collaborative development of enterprise-wide architecture domain work products aimed at guiding and supporting the policies, strategies, designs, and stewardship for service transformation, shared services and 1M/IT initiatives – within an enterprise-wide context. He holds a Bachelors degree (management, computer science) from the University of Waterloo. Mr Bryson’s background covers a broad range of strategic management and information technology consulting engagements, primarily for public sector organizations, in the areas of: strategy maps, balanced scorecards; enterprise architecture; 1M/IT strategy, policy, plans; shared services and systems; and applying associated industry best practices. He has been an associate consultant for Gartner Consulting Inc. and MetaGroup Consulting Inc. (now Gartner), completing executive level client assignments in the areas of enterprise architecture, common shared services, CIO best practices and strategic 1M/IT plans.
Commonwealth of Virginia (2001). Conceptual Architecture
Gartner Group, Inc. (2005). Enterprise Architecture: How to Achieve Results -Advice, Strategies and Proven Practices, Gartner Consulting, November 2005.
Government of Canada (2000). Federated Architecture, Iteration One, June 2000.
MetaGroup (2005). Creating an Effective Conceptual Architecture, Meta Practice, January 2005.
MetaGroup (2004). Common Strategic Requirements, Meta Practice, July 2004.
NASCIO (2004). Enterprise Architecture ToolKit, National Association of State Chief Information Officers (NASCIO), October 2004 .. Princeton University (2006). Cognitive Sciences Library. Word Net; definition of “architecture.” http://www.wordnet.princeton.edulperllwebwn.
State of Louisiana (2003). Information Technology Enterprise Architecture Conceptual Architecture, Version 1.0.
State Government of Connecticut (2000). Conceptual Architecture. State Government of Minnesota (2004). Minnesota Enterprise Technical Architecture.
TOGAF v8.1 (2005). The Open Group Architectural Framework (TOGAF) “Enterprise Edition” Version 8.1, The Open Group. http://www.opengroup.org.
United States Department of the Interior (2005). DOl Enterprise Architecture. http://www.doLgov. Wikipedia. Definition of the word “architecture.” http://www.en.wikipedia.org/wiki/Architecture.
Zachman, John (2004). The Framework for Enterprise Architecture. Zachman International. www.zifa.com
Journal of Enterprise Architecture