architecture, architects and other mythological creatures

1http://www.ancient-origins.net/ancient-places-europe/colossus-rhodes-ancient-greek-mega-

statue-003249

2https://www.linkedin.com/pulse/keeping-architecture-out-ivory-tower-gregor-hohpe

3

http://www.metalsucks.net/wp-content/uploads/2014/06/In-Search-of-Sun-Band-Pic-Hair-

Pulling.jpg

ARCHITECTURES, ARCHITECTS AND OTHER

MYTHOLOGICAL CREATURES

Vicenç García Altés

@vgaltes

vgaltes.com

Architecture is the decisions that

you wish you could get right

early in a project, but that you

are not necessarily more likely

to get them right than any other.

5

Ralph Johnson

Architecture represents the

significant design decisions that

shape a system, where

significance is measured by cost

of change.

6

Grady Boock

BUSINESS VS IT

7https://www.askideas.com/27-most-funny-fights-pictures/

8

https://twitter.com/artolamola/status/804341117231697920

ACTIVITIES AND ARTIFACTS

■ Domain vision statement creation -> Domain vision statement, List of

business capabilities, Glossary

■ Study business roadmap -> List of business capabilities, Glossary

■ Reference scenario mapping -> List of reference scenarios, Glossary

■ Business process flow mapping -> Business process flow map, List of

business capabilities, List of domain events, Glossary

■ Exception scenario mapping -> Business process flow map, List of domain

events, Glossary

■ System mapping -> High level system diagram, Glossary

■ Context mapping -> Context map, Glossary

■ Domain refactoring -> Subdomain map

■ Domain modeling -> Domain models for each subdomain

10

ACTIVITIES

■ Mission Statement

■ Impact Mapping

■Business Model Canvas

■ Domain Use Case Diagrams

■ Event Storming

■ Core Domains Diagram

■ Bounded Context and Autonomy Contexts

■ Context Maps

■ Value Stream Maps

■ Lean Canvas

■ Value Proposition Canvas

12

BUSINESS MODEL CANVAS

13

BMC – DOMAIN DISCOVERY

14

BMC – KEEP BUSINESS IN THE LOOP

15

BMC – KEEP DEVELOPERS IN THE LOOP

16

BUSINESS AS ARCHITECTS

17https://cdn.shutterstock.com/shutterstock/videos/4298990/thumb/1.jpg

DEPLOYING TO PRODUCTION

18

CONWAY’S LAW

19

“organizations which

design systems ... are

constrained to produce

designs which are copies

of the communication

structures of these

organizations”

Mel Conway, 1968

We find strong evidence to

support the hypothesis that a

product’s architecture tends to

mirror the structure of the

organization in which it is

developed.

20

MacCormack et al

21http://www.orgcharting.com/wp-content/uploads/hotel-organizational-chart.png

If the architecture of the system

and the architecture of the

organization are at odds, the

architecture of the organization

wins.

23

Ruth Malan

COLLABORATION VS X AS A SERVICE

24

COLLABORATION X AS A SERVICE

http://web.devopstopologies.com

TEAM TYPES

25http://web.devopstopologies.com

TYPES OF SOFTWARE MONOLITHS

■ Application monolith

■ Joined at the DB

■ Monolithic build (rebuild everything)

■ Monolithic releases (release everything)

■ Monolithic model and implementation (attempted consistency across many

different contexts)

■ Monolithic thinking (apply same solutions for everything)

26

FRACTURE PLANES

■ Business domain bounded context

■ Regulatory compliance

■ Change cadence

■ Technology

■ Risk

■ Performance isolation

■ User personas

■ Team location

■Customer responsiveness

27

SACRIFICIAL ARCHITECTURE

28http://www.mexicolore.co.uk/images-4/413_01_2.jpg

WRAP UP

29https://giftwraphq.files.wordpress.com/2013/01/photo-4.jpg

IT DEPENDS

30http://bastondeoro.com/wp-content/uploads/2016/05/5.jpg

TRADEOFFS

31

http://1.bp.blogspot.com/-wLG-

FJxIsg8/UMdOCHiyQRI/AAAAAAAAAaM/oIX-EiSCQFE/s1600/food-

tradeoff.jpeg

THANK YOU

Vicenç García Altés

@vgaltes

[email protected]

vgaltes.com