ICT.IDS.DM1.

[VD]
Design Methods 1

Introduction (check elo for latest version!)

Windesheim zet kennis in werking
 Information

• Study load
• Course: 4 EC’s (=~ 11 a 12 hours per week)
• 3 hours lecture per week (2 hours for DT)
• Examination
• Written examination
• 18 essay questions
• Practicum labs (Pretscan)

Windesheim zet kennis in werking

Sources

• Sheets with notes

• Documentation on ELO
• Archimate 2.1 Specification (via opengroup.org)
• Labs on ELO
• TOGAF reference

Windesheim zet kennis in werking

 Global overview
• Introduction
– Infrastructure life-cycle
– IT Architecture
• Enterprise Architecture
• Modelling Enterprises with Archimate
– Language and concepts
– Layer model
– Relations
• Problem and risk analysis
• Infrastructure Requirements Analysis
– Requirements Traceability Matrix

Windesheim zet kennis in werking

 Goal
• To create an adequate, appropriate IT infrastructure design in a
structured way.

Windesheim zet kennis in werking

 Content

• IT infrastructure life-cycle
• Definitions:
– IT Design
• Stakeholders of infrastructure design
– IT architecture
– Infrastructure
– Infrastructure architecture
• The why and how of IT architecture
• The role of the infrastructure architect

Windesheim zet kennis in werking

 IT Infrastructure life-cycle model
Project Initiation Retirement
Verification and validation

Problem Risk Production

Analysis Exploitation

Defi
nitio

on
n

grati
Requirement Acceptance

and
Analysis Test

inte
s
peci

and
ficati

Test
Functional Functional

on
Design Test

Technical Unit
Design Test

Realization

Windesheim zet kennis in werking

 IT Infrastructure life-cycle model
PRINCE2
Project Initiation Retirement
Verification and validation
TOGAF 5 WHY
Archimate
Problem Risk Production
Fishbone ISO20000
Analysis Exploitation

Defi
nitio

on
n

grati
Requirement Acceptance

and
Analysis Test

inte
s
peci

and
ficati

Test
OIAm Functional Functional TMAP

on
Design Test

Technical Unit
Design Test

Realization

Windesheim zet kennis in werking

 IT Infrastructure life-cycle model
PRINCE2
PVA Project Initiation Retirement
Verification and validation
TOGAF 5 WHY
Archimate
Problem Risk Production
Fishbone ISO20000
Analysis Exploitation

Defi
EA models PRA

nitio

on
n

grati
Requirement Acceptance

and
RTM
Analysis Test

inte
s
peci

and
ficati

Test
OIAm Functional Functional TMAP

on
FD Testplan
Design Test

Technical Unit
TD
Design Test

ICE Realization

Windesheim zet kennis in werking

 Alternatives for V-model for Systems Engineering
Why alternatives: Waterfall is sequential development
– risk of changing requirements
• Alternatives: Agile, Scrum
– Backlog
– Iteration
• Sprintlog
– Release
– Production

Windesheim zet kennis in werking

 Introduction to IT Architecture

Windesheim zet kennis in werking

 Why IT architecture?

Windesheim zet kennis in werking

 Why me?
Historically, IT staff have been organized vertically based on the
technology stack they managed. The organization still needs depth of
technical expertise, but also now demands better collaboration from
people who can work horizontally across teams.

Because getting people to think beyond their stack is a challenge

when the traditional model paid them to be expert in it, IT leaders
must hack their culture and get those people out of their bubble.

Gartner, 2019

Windesheim zet kennis in werking

 Architecture and design
• Architecture is related to design, but it is not the same!

Windesheim zet kennis in werking

 About Design

Windesheim zet kennis in werking

 Designing buildings
What do these different buildings have in common?

Windesheim zet kennis in werking

 Design is about
• Functionality, like:
• Parking
• Living
• Office
• Messaging

• Qualities, like:
• Nice
• Secure
• Efficient
• Solid
• Availability

Windesheim zet kennis in werking

 Stakeholders of a design

• The stakeholders of a design

– Support
– Builder
– Tester
– Management

• Indirectly:
– End user

Windesheim zet kennis in werking

 IT Design Definition
• Designing is the process of taking decisions / making
choices, from global scope to detail scope, to define
the elements of a system to be build.

Windesheim zet kennis in werking

 IT Design and IT Architecture

• Designing is the process of taking decisions / making

choices, from global scope to detail scope, to define
the elements of a system to be build.

• IT Architecture guides design: frames design space

(just like the generic architecture of buildings guides the
design of new buildings!)

• IT Architectural decisions are distinguished by:

– Have IT environment-wide impact
– Influence quality attributes that are important for
the entire IT environment

Windesheim zet kennis in werking

 IT Design and IT architecture
Architecture and design are closely related; the main difference between them is really
about which way we face.
• Architecture faces towards strategy, structure and purpose, towards the abstract.
• Design faces towards implementation and practice, towards the concrete.

Strategy

Architecture

Design

Concrete (realisation)

Windesheim zet kennis in werking

 IT architecture and IT infrastructure architecture

• The difference between IT architecture and IT infrastructure architecture is the scope:

– IT architecture is about information, application and technical infrastructure

– IT infrastructure architecture is about technical infrastructure

Windesheim zet kennis in werking

 IT Architecture definitions

• Various definitions can be found

• We use the OIAm definition

IT Architecture is a consistent set of principles and models that

gives direction to design and realization of information,
applications and technical infrastructure of an organization.

Windesheim zet kennis in werking

 About Infrastructure

Windesheim zet kennis in werking

 The characteristics of Infrastructure
• What stands out?

Windesheim zet kennis in werking

 Infrastructure is about
• Infrastructure is
– Utility
– Facilitating
• You do not notice it
• ... Until broken
• An unaware dependency

Windesheim zet kennis in werking

 IT Infrastructure definition:

• Several definitions can be found

• We go for this definition:

The set of generic facilities that provide the technical

support function to the whole of IT applications of an
organization (also generic applications like email and
calendaring, call management, file & print ...)

Windesheim zet kennis in werking

 Depending on infrastructure
• A successful organization must have:
– Adequate business processes with stakeholders
– Efficient Information management
– Customized applications
– Proper infrastructure foundations

Windesheim zet kennis in werking

 The changing role of IT infrastructure
• The early days:
– Defined by the supplier
– Each application its own infrastructure -> complex management
• Nowadays and evolving:
– Many users, processes, legislation, IT services, building blocks,
security concerns, maintenance procedures
– Consolidation -> complex infrastructure (hairball)
– Infrastructure as a Service / Platform as a Service (Cloud)
but: Law of conservation of misery (complexity)

Windesheim zet kennis in werking

 IT Infrastructure Architecture definition
• Combining it all together:

Infrastructure architecture is the complete, consistent

and coherent set of methods, rules, models and tools
which guides the (re)design, migration and
implementation of the technical infrastructure of an
organization according to a vision

Windesheim zet kennis in werking

 What if there is no infrastructure architecture?
• No alignment of infrastructure to information systems to business
– Failing projects
– No insight in impact of changes
– No guidance for design
– Expensive and/or overlapping information systems

Windesheim zet kennis in werking

 IT Infrastructure Architecture, what is it? (tangible)

• A set of documents about the IT infrastructure landscape containing:

– Models
– Principles
– Rules
– Overviews
– Viewpoints
– Tools
• Written in a standardized language

Windesheim zet kennis in werking

 What does IT infrastructure architecture do?
• Make complexity manageable by models

• Structure
– “Land use planning in the digital world”
– Decomposition in components (functional and technical)
– Relations between components
– Principles
• Abstraction
– Omit all irrelevant information
– Just the essence

Windesheim zet kennis in werking

 Architecture and design standardization
• For effective modelling and communication
standardization is needed:
– Architecture methods
– Language and
– Tools
• Enterprise Architecture methods
– TOGAF
– Archimate

– Note: enterprise architecture is just a bigger

scope: business architecture + IT
architecture

Windesheim zet kennis in werking

 Advantages of IT Infrastructure Architecture

• Clear and complete input for the design, construction and testing
• Alignment of infrastructure, application, information and business
• Standardization, consolidation, structuring of the landscape of systems
• Understanding and communicating complex existing infrastructures
• Balanced assessment of new technologies
• Measurable impact of changes
• Joining management & operation (SLA and product)

Windesheim zet kennis in werking

 The Infrastructure Architect role
• Concept Thinker
• Bridge builder
• Generalist
• Craftsman
"The role of the IT architect is to be able to
understand the business problem and the
business domain and explain it to the
technical people, and to be able to
understand the technology domains and
explain the technical possibilities to
business people” (IBM)
Architects do not interfere with the details of
the solution but with the main line, and
more particularly with the way the solution
components jointly have an added value for
the customer.
Windesheim zet kennis in werking
Also
overseeing
construction
An IT architect analyzes business needs
while designing appropriate ICT
solutions.
Infrastructure Architect. An architect who
designs infrastructures to solve business
problems and achieve business goals.
The infrastructures are ready-to-use
systems that are purchased from third
parties.
 The infrastructure architect/designer
in an organization

PRINCE2 roles in Program and Project

• Program role:
• Guide strategy (long term): why
• Guide tactics (medium term): how
• Advises operations: (short term): what

• Project role:
• Preparation (Startup)
• Guidance at execution (Initiating,
Execution)

Windesheim zet kennis in werking

 Colleagues of an Infrastructure architect
Auxiliary Boardroom Demand
director
Finance User Business
manager representative line manager
Account
Customer EA/domain
manager
architect
Service
IT manager Program
manager
manager
Project
Delivery manager
manager
Project
Service Operations architect
partner manager
Project
Security designer
Vendor IT specialist
officer
Windesheim zet kennis in werking
Supply
 Summary
• You’re familiar with
– V-model of life-cycle development
– Design, architecture, what is the relation?
– IT architecture, infrastructure, infrastructure architecture
– The necessity of Infrastructure architecture
– What is Infrastructure Architecture?
– What does Infrastructure Architecture do?
– Two methods for creating Enterprise Architecture
– Advantages of IT Infrastructure Architecture?
– The roles of an architect/designer in an organization

Windesheim zet kennis in werking

 Next week
• Enterprise Architecture

Windesheim zet kennis in werking