Integrated Architecture Framework: Difference between revisions

Revision as of 17:24, 7 November 2015

Latest revision as of 16:46, 19 December 2024

(14 intermediate revisions by 15 users not shown)

Line 1:

{{notablity|date=May 2019}}

The '''Integrated Architecture Framework''' (IAF) is an [[enterprise architecture framework]] that covers [[business]], [[information]], [[information system]] and technology infrastructure.<ref>[http://www.capgemini.com/resources/the-integrated-architecture-framework-explained Enterprise, Business and IT Architecture and the Integrated Architecture Framework] at capgemini.com</ref><ref>van't Wout, J., Waage, M., Hartman, H., Stahlecker, M., Hofman, A. (2010). "The Integrated Architecture Framework Explained" - ([httphttps://www.springer.com/business+&+management/business+information+systems/book/978-3-642-11517-2 link])</ref> This [[Software framework|framework]] has been developed by [[Capgemini]] since the 1990s, from the experience of practicing architects on projects for clients across the group. The first version was released in 1996 and was based on the [[Zachman Framework]] and [[Steven Spewak|Spewak's]] ideas about [[Enterprise Architecture Planning]].<ref>Jaap Schekkerman (2003). ''How to Survive in the Jungle of Enterprise Architecture Frameworks''. page 139-144.</ref><ref>[https://www.capgemini.com/resources/architecture-for-the-information-age/ Capgemini - Architecture for the Information Age]</ref> Since Version 1.0 released in 1996 IAF has been developed by Capgemini's internal global architecture community drawing from the experience of practising architects. Now in its 6th edition, IAF provides alignment considering all relevant artefacts.

It's domains are:

This [[Software framework|framework]] has been developed by [[Capgemini]] since the 1990s, from the experience of practicing architects on projects for clients across the group. The first version was released in 1996 and was based on the [[Zachman Framework]] and [[Steven Spewak|Spewaks]] ideas about [[Enterprise Architecture Planning]].<ref>Jaap Schekkerman (2003). ''How to Survive in the Jungle of Enterprise Architecture Frameworks''. page 139-144.</ref>

*[[Business architecture|Business Architecture]] - people, process and organisation

*[[Information architecture|Information Architecture]]

*[[Information system|Information Systems]] - applications

*[[Infrastructure|Technology Infrastructure]] - infrastructure

*[[Governance]]

*[[Security]]

*[[Sustainability]]

It has four levels of abstraction:

The Integrated Architecture Framework is:

*Why - [[Contextual design|Contextual]]

* A comprehensive framework to deliver market-leading solutions

*What - [[Conceptual model|Conceptual]]

* Adaptable to the specific needs of an organization

*How - Logical

* Scalable from individual projects to enterprise-wide transformation

*With What - Physical

* A recognized architecture framework in [[The Open Group]]’s IT Architecture Certification program (ITAC).<ref>ITAC [http://www.opengroup.org/itac/cert/methods.tpl List of Recognized Methods] at opengroup.org</ref>

The Integrated Architecture Framework has evolved based on real-world experience, and continues to provide strong focus on the need to understand business requirements and drivers, and the need for all aspects of the architecture and all architectural decisions to be traceable back to these business priorities.

==References==