Scribd
Upload
721 views12 pages

Introduction To IAF - Cap Gemini

The Integrated Architecture Framework (IAF) was developed by Capgemini architects in the 1990s as a structured way for architects to share their experiences and work with architecture across all levels of a business. The IAF uses aspects, layers, artifacts, views, and an iterative process to align business strategy with information systems and technology infrastructure. Key artifacts include services, contracts, and components used at different levels from conceptual to physical. Views combine artifacts to analyze solutions from different perspectives like products, integration, or security. The IAF ensures each solution is holistically aligned with the overall architecture.

Uploaded by

Rhammania Adra
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
721 views12 pages

Introduction To IAF - Cap Gemini

The Integrated Architecture Framework (IAF) was developed by Capgemini architects in the 1990s as a structured way for architects to share their experiences and work with architecture across all levels of a business. The IAF uses aspects, layers, artifacts, views, and an iterative process to align business strategy with information systems and technology infrastructure. Key artifacts include services, contracts, and components used at different levels from conceptual to physical. Views combine artifacts to analyze solutions from different perspectives like products, integration, or security. The IAF ensures each solution is holistically aligned with the overall architecture.

Uploaded by

Rhammania Adra
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

Integrated Architecture Framework

An introduction to IAF and its implementation in QualiWare Mats Gejnevall, Certified Global Architect Capgemini

Once upon a time...


there were some architects at Capgemini that thought that:
Zachman [IBM 1980] was a great starting point for an architect, but there were something missing and; Our architects should be able to share their experiences in a structured way and; We should have a structured and concise way of working with architecture everywhere

Said and done! During 1992 1995 the groundwork was laid to the framework today called the Integrated Architecture Framework

Aspects and Layers in IAF

BUSINESS

CONTEXTUAL

INFORMATION SYSTEMS

TECHNOLOGY INFRASTRUCTURE

CONCEPTUAL

INFORMATION
LOGICAL

PHYSICAL

Basic artifacts
Services describe the behavior of a specific aspect area
Used at the conceptual level Describe requirements, not solutions Service F Service A

Interaction Model
Service G
Contract Contract

Contracts describe interrelations between artifacts


Used at the conceptual, logical and physical levels Describe how services work together and how components work together

Service B

Components describe the solution for an aspect area


Used at the logical and the physical levels Describe solution elements Component X
Service F Service G

Component Y
Contract
Service B

Cross references describes traceability between artifacts


Used at all levels Shows the traceability path between artifacts Cross Ref

Service A

Interaction Model

Views
A view is the result of an analysis of base architecture content with a specific objective A view usually combines (multiple) base artefacts, (also) from multiple aspect areas Examples are e.g. looking at the solution from:
A product point of view to see the impact of a package selection An integration point of view to see how components will be integrated and what integration mechanism theyll use A migration point of view to visualise the migration from the current state to a future state highlighting the key stages in that journey. A cost point of view to analyse the associated costs A security point of view to analyse how security requirements affect the architecture

Product view

Integration view

Migration view

Security view

IAF is an iterative, cyclical, holistic approach which ensures each solution is aligned with the overall architecture

Contextual

In what context will the architecture be created

Conceptual

What is the business & its interaction

Align

What are the info processing requirements & interaction


Principles For clustering

Align

What IS services are required & what is their interaction


Principles for clustering

Align

What TI services are required & what is their interaction


Principles for clustering

Principles for clustering

Logical

How is the business (ideally) structured

Views for analysis

How is information (ideally) structured

Views for analysis

How are the IS systems (ideally) structured

Views for analysis

How are the boxes & wires (ideally) structured


Principles & Strategy

Physical

Which parts of the business will change

Business

Principles & Strategy Views for analysis

Which manual and automated processes need to be linked

Information

Principles & Strategy Views for analysis

Which packages & bespoke software

Information System

Principles & Strategy Views for analysis

Which Hardware, systems software & network components

Technology Infrastructure

A simplified but common way through the framework


Contextual
Scope Objectives Principles As-Is Context...

Conceptual

Services

Contracts

Criteria

Logical

Solution Alternative 1 Components Contracts

Solution Alternative n Components Contracts

Criteria

Physical

Solution Alternative 1
Components Guidelines

Solution Alternative n
Components Guidelines

What is the difference between Enterprise, Domain and Solution Architecture?


Enterprise Level Strategy
Business & IT Mission, Strategy, Principles

Domain Level Targets


Domain Targets

Enterprise Architecture

Solution Level Objectives

Domain Architectures

Project Objectives

Solution Architectures

Projects Projects Projects

Managing the Architecture is an ongoing Process based on a dialogue with the business

Apply To
Business
Vision / Strategy / Scope Why? [Contextual] Requirements Model What? [Conceptual]

Information

Information Systems

Technology Infrastructure

Projects Projects Projects Future Architecture

Logical Model How? [Logical]

Realisation Model With what? [Physical]

Business
Vision / Strategy / Scope Why? [Contextual] Requirements Model

Information

Information Systems

Technology Infrastructure

Business / Technology Scenarios

Dialog Business/IT

What?

[Conceptual]

Logical Model How? [Logical]

Realisation Model With what? [Physical]

Current Architecture Current Business & IT Environment

Technology & Business Trends

Business & IT Strategy

Available books

http://www.springer.com/business+%26+management/business+information+systems/boo k/978-3-642-11517-2

http://www.lithandbook.com/

More information to read: http://www.capgemini.com/services/soa/ent_architecture/iaf/

More information to read: http://www.capgemini.com/services/soa/ent_architecture/iaf/

You might also like