A Reference Architecture for Enterprise Architecture: According to EA3, Documented in EA3
This book endeavors to help further lift the discipline of EA by providing a reference architecture for an EA function and taking an EA approach to its analysis and documentation. By doing so it aims to demonstrate, explain and rationalize why and how to do and manage good, proper and successful EA. **** The book outlines the key drivers and components of an EA function, including the influences on and objectives of EA and the business and technology processes and resources required and used to address and achieve these. **** At the end of each architectural layer section of the book, tips and suggestions are provided on how to identify and assess what is important when one architects both the enterprise and EA function from that layer's perspective. **** For example, keeping on point and avoiding being pushed into related, but non-EA activities; buying time to do things properly while still being responsive and agile to changes in enterprise drivers; fitting into the organization's governance structure; building a capability not just delivering a series of non-repeatable, point-sensitive EA services are just some of the many challenges facing Enterprise Architects that the book deals with. **** As a reference architecture typically describes a complete target architecture, and a complete architecture can take a long time to develop and fine tune, more than can be expected within a single release or project or within the time frame that initial outcomes are required by EA stakeholders and customers, the book takes a look at the different capability increments or themes that might be pursued to meet the differing EA needs and expectations of different enterprises. **** To ensure the reference architecture incorporates best practices in EA, it is built on the concepts and principles of EA outlined in Dr Scott Bernard's book, 'An Introduction to Enterprise Architecture, EA3', and his EA training program and certification courses. Both of which in turn build on the EA experiences and practices of EA practitioners over near to three decades. **** While there are a number of useful and informative EA frameworks and books available guiding organizations on what EA should deliver, organizations and individuals are still left without the one thing that they themselves espouse for the enterprise at large, a target architecture. One that can be used to guide the alignment of EA to the enterprise and that can maximize the effectiveness of the planning and oversight and the formation and execution of EA. This leaves many decisions to be made in the absence of sound, communicable, measurable and transparent views as to why and what to strive for when doing EA.