Pragmatic Architecture, Today: Bart Blommaerts

Download as pdf or txt
Download as pdf or txt
You are on page 1of 56

PRAGMATIC ARCHITECTURE, 


TODAY
BART BLOMMAERTS

@DAGGIEBE
SATURN, 2017-05-02
PRAGMATIC ARCHITECTURE, TODAY

BART BLOMMAERTS

▸ Application Architect
▸ Ordina Belgium
▸ JWorks
▸ @DaggieBe
Architecture

WHAT?
PRAGMATIC ARCHITECTURE, TODAY

VIEWPOINTS

▸ Context
▸ Functional
▸ Information
▸ Concurrency
▸ Development
▸ Deployment
▸ Operational
PRAGMATIC ARCHITECTURE, TODAY

PERSPECTIVES

▸ Accessibility ▸ Location
▸ Availability and Resilience ▸ Performance and
Scalability
▸ Development Resource
▸ Regulation
▸ Evolution
▸ Security
▸ Internationalization
▸ Usability
Architecture

REALLY?
ABILITY TO
CHANGE
PRAGMATIC ARCHITECTURE, TODAY

ARCHITECTURE REPRESENTS THE


SIGNIFICANT DESIGN DECISIONS THAT
SHAPE A SYSTEM, WHERE SIGNIFICANT
IS MEASURED BY COST OF CHANGE.

Grady Booch
PRAGMATIC ARCHITECTURE, TODAY

A SYSTEM IS MORE THAN THE SUM OF


ITS PARTS; IT IS AN INDIVISIBLE WHOLE.
IT LOSES ITS ESSENTIAL PROPERTIES
WHEN IT IS TAKEN APART.

Russell L. Ackoff
BE PART OF THE
TEAM

ACTIVITY OVER ROLE
PRAGMATIC ARCHITECTURE, TODAY

AS A TEAM

▸ Facilitating
▸ Collaborating
▸ Modelling
▸ Sharing
▸ Resolving
▸ Improving
▸…
INVOLVED IN
CODE?
YES
EXPERIENCE THE SAME PAIN AS
EVERYBODY ELSE ON THE TEAM
PRAGMATIC ARCHITECTURE, TODAY

CODE

▸ Support and coaching


▸ Best practices
▸ Code reviews
▸ Proof of Concepts
▸ Reusable building blocks
▸ Etc.
SYSTEM
STAKEHOLDERS
EVOLUTIONARY
TEAM MEMBER
INVOLVED IN
CODE
Architecture

VISUAL
PRAGMATIC ARCHITECTURE, TODAY

ONE CANNOT SEE THE OCEAN'S


CURRENTS BY STUDYING DROPS OF
WATER.

Grady Booch
PRAGMATIC ARCHITECTURE, TODAY

VISUALISATION - GOAL

▸ Consistency
▸ Reporting
▸ Checking and validation
▸ Sharing information
PRAGMATIC ARCHITECTURE, TODAY

VISUALISATION - GROUND RULES

▸ UML is usually not necessary


▸ Can be used for model-driven development
▸ Boxes and lines
▸ Be consistent
▸ Provide a legend
▸ Make sure stakeholders understand
PRAGMATIC ARCHITECTURE, TODAY

VISUALISATION - GROUND RULES

▸ Decision log
▸ Document your decisions and alternatives
▸ Avoid fluffy diagrams
▸ Avoid mixed abstractions
▸ Only document what’s useful
Architecture

WHY?
PRAGMATIC ARCHITECTURE, TODAY

WHY? UP-FRONT DESIGN

01
PRAGMATIC ARCHITECTURE, TODAY

UP-FRONT DESIGN

▸ Think about the big picture


▸ eg. used technology
▸ automation
▸ patterns (monolith, distributed, …)
▸ layering
▸ And it’s evolution
▸ But … be pragmatic
PRAGMATIC ARCHITECTURE, TODAY

JUST ENOUGH UP FRONT DESIGN TO


CREATE FIRM FOUNDATIONS FOR THE
SOFTWARE PRODUCT AND ITS
DELIVERY.

Simon Brown
JUST ENOUGH?
PRAGMATIC ARCHITECTURE, TODAY

JUST ENOUGH?

▸ Greenfield
▸ All the components of the system
▸ High-level
▸ Show the whole system
▸ Add details later
▸ White board diagram
PRAGMATIC ARCHITECTURE, TODAY

JUST ENOUGH? GREENFIELD


PRAGMATIC ARCHITECTURE, TODAY

JUST ENOUGH?

▸ Existing system
▸ As-is situation
▸ Domain of change
▸ Extension points
PRAGMATIC ARCHITECTURE, TODAY

WHY? COMMUNICATION

02

01
PRAGMATIC ARCHITECTURE, TODAY

COMMUNICATION

▸ During inception
▸ Many stakeholders
▸ Many desires
▸ Many questions …
PRAGMATIC ARCHITECTURE, TODAY

COMMUNICATION

▸ During development process


▸ Sharing a technical vision
▸ Everybody collaborates to the same end-goal
▸ Leave your ego at the door
PRAGMATIC ARCHITECTURE, TODAY

WHY? POLITICS

03

02

01
PRAGMATIC ARCHITECTURE, TODAY

POLITICS

▸ Decisions
▸ Stakeholders will question many decisions
▸ Focus on system integrity
▸ Fear of change at corporate IT
▸ Creating systems “nobody wants to touch”
▸ Play the game …
PRAGMATIC ARCHITECTURE, TODAY

WHY? MAKE DECISIONS EXPLICIT

04

03

02

01
Architecture

HOW?
OODA
OBSERVE
ORIENT
DECIDE
ACT
PRAGMATIC ARCHITECTURE, TODAY

OODA - EXAMPLE

▸ Context view
PRAGMATIC ARCHITECTURE, TODAY

OODA - EXAMPLE

▸ Context view
PRAGMATIC ARCHITECTURE, TODAY

OODA - EXAMPLE

▸ Context view
PRAGMATIC ARCHITECTURE, TODAY

OODA - EXAMPLE

▸ Context view
PRAGMATIC ARCHITECTURE, TODAY

RUNTIME OBSERVATIONS

▸ System composition
▸ Measuring value
▸ Application-driven
▸ Capturing data
PRAGMATIC ARCHITECTURE, TODAY

READING MATERIAL

▸ Software Systems Architecture by Rozanski and Woods


▸ 37 Things One Architect Knows About IT Transformation by Gregor
Hohpe
▸ Continuous architecture by Pureur and Erder
▸ Bredemeyer consulting - http://www.bredemeyer.com/
▸ Form follows function - https://genehughson.wordpress.com/
▸ A trace in the sand - http://www.ruthmalan.com/Journal/
JournalCurrent.htm
▸ Coding the architecture - http://www.codingthearchitecture.com/
▸ Continuous architecture in practice - https://pgppgp.wordpress.com/
▸ Who needs an architect? - http://martinfowler.com/ieeeSoftware/
whoNeedsArchitect.pdf
THANK YOU
@DAGGIEBE

You might also like