Handbook on Enterprise Architecture (International Handbooks on...

Features

• Cover Type: Hard Cover with 787 pages
• Published by: Springer
• Edition: 1st Edition November 5, 2003
• Written in: English
• ISBN 10 Number: 3540003436
• ISBN 13 Number: 978-3540003434
• Book Dimensions: 9.5 x 6.5 x 2 inches
• Weighs: 2.8 pounds

Book Description


 This Handbook is about methods, tools and examples of how to architect an enterprise through considering all life cycle aspects of Enterprise Entities (such as individual enterprises, enterprise networks, virtual enterprises, projects and other complex systems including a mixture of automated and human processes). The book is based on ISO15704:2000, or the GERAM Framework (Generalised Enterprise Reference Architecture and Methodology) that generalises the requirements of Enterprise Reference Architectures. Various Architecture Frameworks (PERA, CIMOSA, Grai-GIM, Zachman, C4ISR/DoDAF) are shown in light of GERAM to allow a deeper understanding of their contributions and therefore their correct and knowledgeable use. The handbook addresses a wide variety of audience, and covers methods and tools necessary to design or redesign enterprises, as well as to structure the implementation into manageable projects. 

Book Info
Handbook presents methods, tools, and examples of how to architect an enterprise through considering all life cycle aspects of Enterprise Entities. Based on ISO 15704:2000, or the GERAM Framework. For enterprise engineers.

Reader Reviews
This book is a collection of articles that describe the key elements of the Generalized Enterprise Reference Architecture and Methodology {GERAM}, with each article written by an expert in a particular topic area, and the whole skillfully glued together by the editors. My take on GERAM - having suffered through more approaches to architecture than I care to relate, some good and some bad, the GERAM approach is a beacon of sanity. First, it logically and clearly divides architecture into domains, which are interconnected as follow: (1) Generalized enterprise reference architecture (high-level model for integration) employs an enterprise modeling methodology that uses enterprise modeling language(s). The language(s) are implemented as enterprise engineering tools, which are used to develop enterprise models, which are, in turn, used to design operational systems. (2) Also feeding into the enterprise modeling tools are: partial enterprise models, which are supported by general enterprise modeling concepts, and directly support enterprise modeling tools. (3) Finally, there are 'Enterprise Modules', comprised of processes, staff resources, and technology, which are the basis for implementing the operational system. From the above, which is hard to visualize in a text description, one can see that GERAM is a pick and choose model that has a great deal of flexibility. It's not a perfect model, but it's also not rigid, which is the reason I like it so. With the context provided above, the book addresses GERAM in five parts, each of which contains relevant articles: Part I Architecture Frameworks, is a well stated and illustrated of GERAM and how it maps to other architecture frameworks. Part II Strategy Making and Business Planning, covers business aspects ranging from corporate strategy to developing the business model, to developing the enterprise concept and associated business plan. Part III Defining the Requirements for Enterprise Change, provides a focus on modeling. Part IV Developing the Master Plan, steps you through the design phase. Part V consists of four case studies that reinforce the preceding parts of this book. Do you need yet another architecture approach? The answer is, it depends. I do not view GERAM as much a distinct architecture approach as much as it's an approach to architecture. I believe that it can be applied - in part or in its entirety - to any architecture model because of the inherent flexibility. I certainly believe that this book is an essential resource for any enterprise architect because of the way it separates key elements of an architecture. Comment | | (Report this)