van't Wout / Waage / Hartman The Integrated Architecture Framework Explained

Why, What, How
1. Auflage 2010
ISBN: 978-3-642-11518-9
Verlag: Springer
Format: PDF
Kopierschutz: 1 - PDF Watermark

E-Book, Englisch, 246 Seiten

When I joined Capgemini back in 1996 I was amazed by investment that had been made in developing Enterprise Architecture, and at the root of this, the IAF methodology. Back in the mid 1990s the importance of architecture was dimly recognised but certainly it was not widely understood as a crucial element of successful enterprise wide IT implementation. A decade later with the huge growth in the role, the sophistication, and importance of Information Technology it has become recognized, and established for the value it brings. With this recognition has come various forms of 'standardization' ranging from the work of the Open Group and its moves to establish TOGAF as a common framework, together with ITAC to certify architects, through to a wide variety of product vendor architects, even to some industry sectors establishing their own architectures. Has this diminished, or even may be removed the need for IAF? Well it might have done if the world had stood still, but it hasn't. Simul- neously the range and complexity of technology has increased, the functionality has been extended to embrace new front office capabilities and most of all the externalization and globalization of business has added a whole new extra dimension. Standardization might have improved connections and interfaces, and in so doing produced 'systems' of apparently limitless extendibility, but it has done little to improve the necessary 'understanding'.

Jack van 't Wout started in IT in 1978 and joined Capgemini in 1990. He got involved with architecture in 1993, and is generally acknowledged as one of the founding fathers of IAF. Jack has executed over 20 enterprise architecture and governance engagements and has trained more than 500 people in IAF. Jack's focus is on the financial services sector.Maarten Waage has worked in the IT industry since 1984 and joined Capgemini's precursor Volmac one year later in the Systems and Networks division. He has been practicing architecture since 1995 and got involved in IAF development and deployment in 1997. Maarten has extensive experience in enterprise architecture and large scale transformations. He focuses on the public sector.Herman Hartman has worked with Capgemini and its predecessor Volmac since 1976. He became involved in the development of IAF in 1994 when he laid the basis to encapsulate existing architecture best practices in new ways of working. He has conducted architecture work in dozens of projects. Herman focuses on enterprise architecture engagements in the industry sector.Max Stahlecker is the youngest member of the team of authors. He is in the IT industry since 2001. Max did his thesis on enterprise architecture, architectural conformance and business transformation. He has been practicing architecture with IAF since he joined Capgemini 2006 and has been involved with its development since then.Aaldert Hofman started to work with Capgemini in 1990 and worked in the IT industry since 1988. He has developed architectures since 1996 and got involved in IAF development and lecturing in 1998. Aaldert is specialized in security architecture and the broader risk management theme.

Autoren/Hrsg.

van't Wout, Jack

Waage, Maarten

Hartman, Herman

Stahlecker, Max

Hofman, Aaldert

Inhaltsverzeichnis

1;Foreword;5
2;Preface;7
2.1;IAF Is Here to Stay!;7
2.2;Preface;8
2.3;Objectives of the Book;9
2.4;Intended Readers;9
2.5;Structure of the Book;10
2.6;Acknowledgements;10
3;Contents;12
4;IAF Background, Value and Strategy;18
4.1;1.1 What Is IAF? A Short Summary;18
4.2;1.2 Reasons for Having IAF;18
4.3;1.3 The Value of IAF;19
4.4;1.4 IAF Strategy;20
4.5;1.5 A Short Recap of IAF Versions;21
5;IAF’s Architecture;22
5.1;2.1 Introduction;22
5.2;2.2 The Context: The ‘‘Why’’ of IAF;24
5.3;2.3 Requirements: The ‘What’ of IAF;27
5.4;2.4 Logical Structure: The ‘How’ of IAF;35
5.5;2.5 Physical Elements: The ‘With What’ of IAF;45
5.6;2.6 Recap: IAF’s Meta-meta Model;49
6;IAF’s Aspect Areas Explained;52
6.1;3.1 Introduction;52
6.2;3.2 Contextual Artifacts and Views;52
6.3;3.3 Business Architecture;70
6.4;3.4 Information Architecture;98
6.5;3.5 Information System Architecture;115
6.6;3.6 Technology Infrastructure Architecture;138
6.7;3.7 The Quality Aspect of Architecture;155
7;IAF in Perspective with Other Frameworks and Methods;168
7.1;4.1 Introduction;168
7.2;4.2 IAF and Other Architecture Frameworks;169
7.3;4.3 IAF and Business Transformation;184
7.4;4.4 IAF and Analysis/Design/Development ;186
7.5;4.5 IAF and Industry Process Frameworks;196
7.6;4.6 IAF and Project Management Methods;202
7.7;4.7 Combining TOGAF, Prince2 and IAF;205
7.8;4.8 IAF and Architecture Tooling;206
7.9;4.9 IAF and Modelling Techniques;209
7.10;4.10 IAF and TechnoVision;212
8;Applying IAF and Using Its Outcomes;218
8.1;5.1 Understanding the Context in Which IAF Is to Be Implemented;218
8.2;5.2 IAF for Enterprise Transformation;219
8.3;5.3 IAF for Solutions Architecture;220
8.4;5.4 Architecture Function and Design Authority;222
8.5;5.5 IAF Roadmaps;227
8.6;5.6 Using IAF Outcomes by Non-architects;235
9;Real Life Case Studies;241
9.1;6.1 Insurer - Enterprise Transformation;241
9.2;6.2 Bank - Design Authority;243
9.3;6.3 Public Transporter - Solution Architecture;245
10;The Making of IAF;248
10.1;7.1 IAF’s Birth;248
10.2;7.2 IAF’s Evolution;249
10.3;7.3 IAF’s Future;253
11;About the Authors;254
12;Index;255