introduction to iaf - cap gemini
TRANSCRIPT
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
PHYSICAL
CONCEPTUAL
LOGICALIN
FOR
MA
TIO
N
INFO
RM
ATI
ON
SY
STEM
S
TEC
HN
OLO
GY
IN
FRA
STR
UC
TUR
E
Aspects and Layers in IAF
CONTEXTUAL
BU
SIN
ESS
Interaction Model
Interaction Model
Basic artifacts
• Services describe the behavior of a specific aspect area
– Used at the conceptual level
– Describe requirements, not solutions
• Contracts describe interrelations between artifacts
– Used at the conceptual, logical and physical levels
– Describe how services work together and how components work together
• Components describe the solution for an aspect area
– Used at the logical and the physical levels
– Describe solution elements
• Cross references describes traceability between artifacts
– Used at all levels
– Shows the traceability path between artifacts
Service
A
Service
F
Service
G
Component X
Service
B
Component Y
Service
A
Service
F
Service
G
Service
BContract
Contract
Contract
Cross Ref
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 they’ll 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
Productview
Integrationview
Migration view
Security view
IAF is an iterative, cyclical, holistic approach which ensures
each solution is aligned with the overall architecture
Information Information System
Technology
InfrastructureBusiness
What is the business & its interaction
What are the info processing
requirements & interaction
What IS services are required & what is their
interaction
What TI services are required & what is their
interaction
How is the business (ideally) structured
How is information (ideally) structured
How are the IS systems (ideally) structured
How are the boxes & wires (ideally)
structured
Which parts of the business will change
Which manual and automated processes
need to be linked
Which packages & bespoke software
Which Hardware, systems software &
network components
Co
nce
ptu
alL
og
ical
Ph
ysic
al
Align Align Align
Views for analysis
Views for analysis
Views for analysis
Views for analysis
Views for analysis
Views for analysis
Prin
ciples
for
clusterin
g
Prin
ciples
& S
trategy
Prin
ciples
Fo
r clu
stering
Prin
ciples
& S
trategy
Prin
ciples
for
clusterin
g
Prin
ciples
& S
trategy
Prin
ciples
for
clusterin
g
Prin
ciples
& S
trategy
Co
nte
xtu
al
In what context will the architecture be created
Co
nte
xtu
alC
on
cep
tual
Lo
gic
alP
hys
ical
Principles
A simplified but common way through the framework
Criteria
As-Is Context...ObjectivesScope
ContractsServices
Solution Alternative 1
ContractsComponents
Solution Alternative n
ContractsComponents
Criteria
Solution Alternative 1
GuidelinesComponents
Solution Alternative n
GuidelinesComponents
What is the difference between Enterprise, Domain and Solution
Architecture?
Solution Architectures
Enterprise
Architecture
Domain
Architectures
ProjectsProjects
Projects
Business & IT
Mission, Strategy,
PrinciplesDomain
Level Targets
Solution Level Objectives
Enterprise Level
Strategy
Domain
Targets
Project
Objectives
Managing the Architecture is an ongoing Process based on a
dialogue with the business
Business InformationInformation
Systems
Technology
Infrastructure
Vision / Strategy / Scope
Requirements Model
Logical Model
Realisation Model
Why?
What?
How?
With what?
[Contextual]
[Conceptual]
[Logical]
[Physical]
Business InformationInformation
Systems
Technology
InfrastructureBusiness Information
Information
Systems
Technology
Infrastructure
Vision / Strategy / Scope
Requirements Model
Logical Model
Realisation Model
Why?
What?
How?
With what?
[Contextual]
[Conceptual]
[Logical]
[Physical]
Vision / Strategy / Scope
Requirements Model
Logical Model
Realisation Model
Why?
What?
How?
With what?
[Contextual]
[Conceptual]
[Logical]
[Physical]
Business InformationInformation
Systems
Technology
Infrastructure
Vision / Strategy / Scope
Requirements Model
Logical Model
Realisation Model
Why?
What?
How?
With what?
[Contextual]
[Conceptual]
[Logical]
[Physical]
Business InformationInformation
Systems
Technology
InfrastructureBusiness Information
Information
Systems
Technology
Infrastructure
Vision / Strategy / Scope
Requirements Model
Logical Model
Realisation Model
Why?
What?
How?
With what?
[Contextual]
[Conceptual]
[Logical]
[Physical]
Vision / Strategy / Scope
Requirements Model
Logical Model
Realisation Model
Why?
What?
How?
With what?
[Contextual]
[Conceptual]
[Logical]
[Physical]
ProjectsProjects
DialogBusiness/IT
Projects
Future
Architecture
Current
Architecture
CurrentBusiness &IT Environment
Technology
& Business
Trends
Business
& IT
Strategy
Apply To
Business /
Technology
Scenarios
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/