Architectural Thinking @ Domain Driven Design Meetup Vienna Feb 2019

These slides present the motivation and basic concepts of Architectural Thinking and its relation to Domain Driven Design

1. ©iteratec
ArchitecturalThinking
Dr. Wolfgang Goebl
DDD Meetup Vienna, Feb 22
nd
2019
1

2. The Problem
2
Dark Waters of Legacy IT
Agile! Agile!
Agile!
Innovation!
Vision?
Strategic Management?
Architecture?
Reengineering?

3. Prologue:
What obviously does not work*
3
*when used in isolation

4. 4
Hardcore Agility

5. 5
Design Thinking
... and create
yet another
unrealizable
point
solution!
Design Thinking
Let’s create yet
another
unrealizable
point solution!

6. Software/System Architecture only

7. Domain Driven Design
7
Domain Driven Design
IT Biz

8. Enterprise Architecture Management as Connector?
Vision/Strategy
Management
Design
Thinking
Business
Analysis
Business
Process
Management
IT Operations
Project
Management
Programm
Management
EAM
(Agile-)Solution
Development
Business Units
8
Archimate®
Zachmann
TOGAF®
An isolated, bloated, Ivory Tower Discipline as Connector?

9. 9
Separated Disciplines
Design
Thinking!
Use Micro-
services!
Be
Agile!
I am the
Leader!
Let’s
Architect!
Cloud is
the
Solution!

10. Agenda
10
1.2 Lean over bloated Frameworks
1.3 Collaborative & Iterativover autocratic
1.1 Customer centricover technocratic
4. Architectural Thinking and DDD
1. Architectural Thinking

11. 1. Architectural Thinking
11
1.2 Lean over bloated Frameworks
1.3 Collaborative & Iterativover autocratic
1.1 Customer centricover technocratic
4. Architectural Thinking and DDD
1. Architectural Thinking

12. Vision Statement
12
„We bring disciplines together
to build the missing bridges
that enable organizations to adapt and thrive.“

13. Architectural Thinking Association®
›Non Profit Association
›“Förderung des architekturellen Denkens in Unternehmen”
›Truly open Architectural Thinking Framework®
›architectural-thinking.com/participate
13

14. What we do
14
“We form an interdisciplinary leadership team that
creates wisdom how to connect disciplines.”
“We bring in the thought leaders of relevant
disciplines to participate in our vision.”
“We define a compelling, simple AT framework where
everbody wants to connect to.”

15. Clusters of Disciplines to be connected
15

16. 1.1 Customer centric over technocratic
16
1.2 Lean over bloated Frameworks
1.3 Collaborative & Iterativover autocratic
1.1 Customer centricover technocratic
2. Architectural Thinking and DDD
1. Architectural Thinking

17. 22.02.2019
17
C-level Executives
Business Unit Leads
Computing
Center
Who is the primary Customer of Architectural Thinking?
Innovation-
management
CIO / CDO
IT Solution
Architects
Development
teams
Process-
management

18. 22.02.2019
18
What‘s the Biggest Pain of Executives?
Too intransparent!
Too expensive!
Too slow!
Strategy
implementation?

19. 19
How can Architectural Thinking help?
Expensive!
Slow!
Intrans-
parent!
Strategy
implement?
Business Architecture
Strategic Budgeting based on Capabilities
Governance based of Business Architecture
Prio by Strategic Fields of Action

20. Business Architecture
20

21. Business Architecture
Makes Business People Accountable for Architecture and Drives IT
21
App A
App D
App B
App E
App C
App F
App G
Business Architecture

22. Capability Model
22
Capabilities represent the basic
building blocks, or DNA, of a
business.
Business Architecture

23. Strategic Budgeting
Per Capability
23

24. Governance via Strategic Fields of Action
24

25. 1.2 Lean Maps over bloated Frameworks
25
1.2 Lean over bloated Frameworks
1.3 Collaborative & Iterativover autocratic
1.1 Customer centricover technocratic
2. Architectural Thinking and DDD
1. Architectural Thinking

26. 26
Lean Maps –Enterprise Level

27. 27
Lean Maps –Solution Level

28. Connect Solution Requirements with Enterprise Level
Assign Requirements to Capabilities
28

29. 1.3 Collaborative & Iterative over autocratic
29
1.2 Lean over bloated Frameworks
1.3 Collaborative & Iterativeover autocratic
1.1 Customer centricover technocratic
2. Architectural Thinking and DDD
1. Architectural Thinking

30. 30
Grassroots Democracy?

31. 31
Autocratic Leadership?

32. …its Always a Sound Combination!
32
What’s the Best Way to Make Strategic Decisions?
Democratic, Bottom-up Management, Top-down

33. Connect “Managing Disciplines to Enterprise Maps
33
Ear
Leg
Tooth
Trunk
Eye
Require
ment
Budget Solution
Vision
Strategy
Project
Code
Gover
nance

34. “Architecture Coordinator” im Entwicklungsteam
›80% of architectural Work happens in Solution Team
›Everybody is architect on micro level
›“Architecture Coordinator” accountable for
›Solution Architecture as a whole
›Integration with Enterprise Architecture
TT.MM.JJJJ | ggf. Text
34
Autonomous Team

35. ©iteratec
Digital
Governance
Board
Capability 1 Capability 2
‘Cross
Product’
Capability
3…
‘Technol.
Platform’
Autonomes
Team
Autonomous
Team
Autonomous
Team
Autonomous
Team
Autonomous
Team
Autonomous
Team
Autonomous
Team
Autonomous
Team
Autonomous
Team
“Architecture Coordinator” Enterprise Level
›20% of Architecture Work
›Optimizes across Solutions
›Enge Abstimmung mit AC Solution

36. ©iteratec
Digital
Governance
Board
Capability 1
Board
Capability 2
Board
‘Cross
Product’
Board
Capability 3
Board
‘Technol.
Platform’
Board
Autonomes
Team
Autonomous
Team
Autonomous
Team
Autonomous
Team
Autonomous
Team
Autonomous
Team
Autonomous
Team
Autonomous
Team
Autonomous
Team
Autonomous
Team
Ideas
Concepts
Strategic
Fields of
Action
(SFA)
Aggregated
SFAs
Architectural Map as Core of Company wide Governance
Vorstand
Bereichsleiter

37. 1.3 Collaborative & Iterative over autocratic
37
1.2 Lean over bloated Frameworks
1.3 Collaborative & Iterativeover autocratic
1.1 Customer centricover technocratic
2. Architectural Thinking and DDD
1. Architectural Thinking

38. Domain Driven Design
38

39. “Model” Domain Driven Design vs Business Architecture
39
Domain
A sphere of knowledge (ontology), influence, or activity. The subject area to which the
user applies a program is the domain of the software;
Model
A system of abstractions that describes selected aspects of a domain and can be used to
solve problems related to that domain;
Ubiquitous Language
A language structured around the domain modeland used by all team members to
connect all the activities of the team with the software.
=Enterprise
=Capabilities, Value Streams, Information Objects
=Nope…Focus on strategic Level

40. Positioning Domain Driven Design in Discipline’s Cluster
40
DDD

41. 41
Dr. Wolfgang Goebl
[email protected]
architectural-thinking.com

42. Recommended Reading
[Ambler10]: S. Ambler: ‘Disciplined Agile Delivery’
[BAGuild16]: Business Architecture Guild, “A Guide to the Business Architecture Body of
Knowledge®” (BIZBOK® Guide, v6.5), http://www.businessarchitectureguild.org/
[Brooks10]: F. Brooks: ‘The Design of Design: Essays from a Computer Scientist’
[Carr18]: D. Carr 'State of Enterprise Architecture Survey: Results and Findings'
https://eapj.org/wp-content/uploads/2018/05/EAPJ-Special-Edition-State-of-EA-Survey.pdf
[Eckstein18]: J. Eckstein: ‘Company-wide Agility’
[Kostic16]: N. Kostic: ‘Demystifying Enterprise Architecture‘
http://www.entarchs.com/blog/demystifying-enterprise-architecture.html
[Westerman15]: ‘Leading Digital Turning Technology into Business Transformation’
42