The Integrated Architecture Framework Explained (eBook)

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.

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