© 2014 AMOS SE

The Age of

Architecture?!

Gregor Hohpe

AMOS Chief IT Architect

ECSA 2014, Vienna

2

About

3

Me

© 2014 AMOS SE 4

Comp Sci

Comp Sci

Eng. Mgmt.

Diplom

MS

ME

Startup

Consulting

Software

Corporate IT

© 2014 AMOS SE 5

© 2014 AMOS SE 6

© 2014 AMOS SE 7

© 2014 AMOS SE

Output oriented

over process oriented

is free

A players hire

A players. B players

hire C players.

Demo

or

Die

Abstraction

!=

Dumbing

down

Control

is an

illusion

Content is

King

Hic Rhodos

hic salta

Lead

by

Example The

Age of

Architecture

The proof

is in the

pudding

Do what

you say

and say

what you

do

Theory

Never

stop

learning

© 2014 AMOS SE

9

Architecture

© 2014 AMOS SE

“Software Architecture”

“The structure of the components, their interrelationships, and principles

and guidelines governing their design and evolution over time”

Structure and relationships, seeing the big picture end-to-end

Thinking ahead

Decisions, choices or constraints put into place

Reasons and rationale why things are the way they are

“What you cannot change from one day to the next”

“Design decisions about any system that keep implementors and

maintainers from exercising needless creativity”

10

© 2014 AMOS SE

Architecture?

11

© 2014 AMOS SE

Architecture!

12

© 2014 AMOS SE

Architecture!

13

© 2014 AMOS SE

Design (Solution Architecture)

14

© 2014 AMOS SE

15

Architects

© 2014 AMOS SE

Master Planner?

16

© 2014 AMOS SE

Gardener?

17

© 2014 AMOS SE

Tour Guide?

18

© 2014 AMOS SE

19

Theses

© 2014 AMOS SE

There always is an architecture

20

Source: Foote Yoder. Big Ball of Mud, 1999, http://www.laputan.org/mud/

© 2014 AMOS SE

And there is always a reason for it

21

Source: Foote Yoder. Big Ball of Mud, 1999, http://www.laputan.org/mud/

© 2014 AMOS SE

An architecture isn’t simply “good” or “bad”

22

Berlin Gropius-Stadt

© 2014 AMOS SE

Rather, architecture is fit or unfit for purpose

23

© 2014 AMOS SE

You cannot judge a decision by the outcome

24

Baron & Hershey, Outcome bias in decision evaluation, 1988.

Architects

in the

Enterprise

25

© 2014 AMOS SE

IT

Architecture:

The

gap

between

buzzword

and

product

26

© 2014 AMOS SE

“From board room to engine room”

27

© 2014 AMOS SE

The „Architect Elevator“

The ability to move quickly between

levels of abstraction and audiences while

adjusting communication style

accordingly.

Some buildings (companies) have more

floors than others.

28

© 2014 AMOS SE

Layered Abstraction

29

Works well in a

relatively static environment

© 2014 AMOS SE

The current IT Environment

30

“Yes it blends!”

Will it blend?, Youtube, 2014

© 2014 AMOS SE

Architect Skill Profile

31

Skill

Impact Leadership

• Training & Practice

• Mentee

• Certification

• Mentoring & Teaching

• Communication

• Arch. Board Member

• External visibility

• Cost & Complexity Reduction

• Reduced time to market

• Clear Roadmap

The Role of an Architect

• Business / IT alignment

• End-to-end view

Analytical

• Systems thinking

• Architectural Thinking

Communication

• Presentation skills

• Conflict resolution

• Stakeholder Mgmt.

• Technical Writing

Management

• Behavioral patterns

Technical

• Cloud computing

• Big Data

• Disaster Recovery

Company Specific

• Strategic initiatives

• Core platforms

• IT Transformation

1

2 3

© 2014 AMOS SE

Procedural vs. Declarative Knowledge

32

“How” “That”

“Why”

Hans’

Brother

Ivory

Tower

Resident

Practitioner Academic Successful

Architect

Procedural Declarative

© 2014 AMOS SE 33

Procedural

Declarative

Procedural vs. Declarative Knowledge

Hans’

Brother

Theorist

Software

Engineer

Architect

© 2014 AMOS SE

Systems Thinking

34

Complexity

Ra

nd

om

ne

ss

Unorganized Complexity

(aggregates)

Organized Complexity

(systems)

Organized

simplicity

(mechanisms)

Source: Gerald Weinberg. An Introduction to General Systems Thinking, Wiley, 1975

Types of systems and modes of thought

Statistical treatment

Analytical treatment

35

Enterprise

Architects

© 2014 AMOS SE

Enterprise Architecture?

36

© 2014 AMOS SE

Enterprise Architecture

Enterprise Architecture

37

Architecting the Enterprise

or

(IT) Architecture for the Enterprise?

IT Architecture Business

Architecture

© 2014 AMOS SE

Architecting the Enterprise

38

© 2014 AMOS SE

Enterprise Architecture & Standardization

City Planning

Building Codes

• Strategic direction

• Identify trends

• Opportunities & threats

• Tactic enforcement

• Safety / Security

• Uniformity

Zoning

Materials List

• Patterns

• Hot spot identification

• Complexity reduction

• Repeatability

• Compliance

• Cost reduction

39

30-50

years

20-30

years

10-15

years

5-10

years

40

What next?

© 2014 AMOS SE

Conclusion

41

Complexity Speed

Architects

done by

Current Technology Landscape

Architecture

It’s a great time to be an architect!

import

ant! im

porta

nt!

42

fin

www.enterpriseintegrationpatterns.com www.allianz.com/careers