Journal of Enterprise Architecture - May 2007


Journal of Enterprise Architecture May 2007 \| Volume 3, Number 2


To order a back issue of the Journal of Enterprise Architecture, please email Scott Bernard (email) at Scott.Bernard@aeajournal.org and note the Volume and Number of the Journal. All back issues cost $5.00 per issue plus $2.00 U.S. domestic shipping or $3.50 international shipping (per copy).

Feature
	Architect's Spotlight: Tanaia Parker

Articles
	Essential Layers, Artifacts, and Dependencies of Enterprise Architecture by Robert Winter and Ronny Fischer
		After a period where implementation speed was more important than integration, consistency and reduction of complexity, architectural considerations have become a key issue of information management in recent years again. Enterprise architecture is widely accepted as an essential mechanism for ensuring agility and consistency, compliance and efficiency. Although standards like TOGAF and FEAF have developed, however, there is no common agreement on which architecture layers, which artifact types and which dependencies constitute the essence of enterprise architecture. This paper contributes to the identification of essential elements of enterprise architecture by (1) specifying enterprise architecture as a hierarchical, multilevel system comprising aggregation hierarchies, architecture layers and views, (2) discussing enterprise architecture frameworks with regard to essential elements, (3) proposing interfacing requirements of enterprise architecture with other architecture models and (4) matching these findings with current enterprise architecture practice in several large companies.
	Presenting a Theory-Based Model for IT Management Responsibilities by Magnus Gammelgard, Marten Simonsson, and Asa Lindstrom
		Enterprise architecture is all about the IT systems, the IT organization, and how they provide value to the business. Nonetheless, the complex relations within this trinity have previously been overlooked in literature. The herein proposed reference model for IT management responsibilities therefore aims at explaining how IT organizations and IT systems serve as value enablers to the business, thus clarifying the boundaries of IT management's responsibilities. The model is based on extensive literature studies and has been tested in a series of empirical studies.
	Enterprise Architecture and Change Management by Fatima Espinoza
		This article provides an analysis of how enterprise architecture (EA) promotes change and provides a framework for change management. he article first explores the reasons for organizations to change and points out elements such as technological trends and market pressures as determinant forces that foster these changes. As a preamble to the analysis of EA as a framework for change management, an introduction to the concept of change management is made by presenting several perspectives. The article concludes by recognizing EA as a force that encourages change, and the contributions that EA makes to reducing stakeholders resistance to change.
	The Future of Information Technology - Part 4: Self-Adapting System Architecture 2018-2026 by Robert Ellinger
		Though it is largely an abstract concept, enterprise architecture (EA) has shaped, is shaping, and will continue to shape information technology. This four-part article traces the author's observations and predictions about the current and future state of information technology, and the role that EA will play in that evolution. Part 4 looks ver far forward to the next architectural step beyond MEDA that may be called the Self Adapting System Architecture (SASA). Given that SASA is 15 to 20 years out, it is more of an IT architectural vision than a true architecture like SOA or MEDA. Yet, the technology on which it is based has been in university computer science laboratories for 10 to 20 years. This technology has been used in many visionary IT experiments, but has not moved from basic research to research and development yet, in part because it is multifaceted intricate, convoluted, and complex. More importantly, the migration to SASA will require significant changes in business processes and organizational culture.

Case Study
	The Methodology for Business Transformation v1.5: A Practical Approach to Segment Architecture by Colleen Coggins and Jerad Speigel
		This article describes the Methodology for Business Transformation v1.5 and how it can be used as a step-by-step approach for developing architecture. The recent publication of OMB's Federal Enterprise Architecture (FEA) Practice Guidance clearly articulates the inter-relationships between the three architecture levels: enterprise, segment, and solution. This article introduces the MBT v1.5 as a practical approach to developing these architecture levels with executive and mission area leadership, participation, and buy-in. This article is written to encourage federal and private sector architecture practitioners to use the MBT in their own organizations. The MBT is feely available as an open-source methodology . It is available at www.doi.gov/ocio/architecture/mbt.

© 2007 JEA - a\|EA. All rights reserved.