SlideShare a Scribd company logo
Follow me on Twitter @simonbrown
Simon Brown
Software architecture for developers
I help software teams understand
software architecture,
technical leadership and
the balance with agility
(I code too)
Training Book Speaking
Buy the book for $10
YI85bLbAXGks
(expires 30th March 2013)
simon.brown@codingthearchitecture.com
@simonbrown on Twitter
Jersey, Channel Islands
What is software
architecture?
What is architecture?
As a noun...
Structure
The definition of something in terms
of its components and interactions As a verb...
Vision
The process of architecting,
making (significant) design decisions, etc
and
Grady Booch
http://www.handbookofsoftwarearchitecture.com/index.jsp?page=Blog&part=2006
What is design?
Architecture represents the
significant decisions,
where significance is measured
by cost of change.
Can you refactor
it in an afternoon?
Chaos!Does the team understand what they are building and how they are building it?
Chaos!Does the team understand what they are building and how they are building it?
No defined structure,
inconsistent approaches,
big ball of mud,
spaghetti code, ...
STOPSlow, insecure, unstable, unmaintainable,
hard to deploy, hard to change,
over time, over budget, ...
Shared vision of
TL; DR
Software
Architecture
Document
Shared vision of
WTF?!
The software
architecture role
The software architecture role is
different
to the lead developer role
It’s an inward and
outward facing role
It’s about the
bigpicture
Abstract Specific
As software developers, the
codeis usually our main focus
Lines of code
Classes, functions
Design patterns
Unit tests
Refactoring
Abstract Specific
Sometimes you need to
step back
from the IDE
Lines of code
Classes, functions
Design patterns
Unit tests
Refactoring
The low-level detail
is equally important
Don’t code 100% of
the time though!
Would we
code
it that way?
All decisions
involve a
trade-off
Should software architects write
code
on software projects?
Ideally yes, but...
Software architects
must be
master builders
And coding is a great way
to retain this skill
Plus it reduces many of the
problems associated with
ivory tower architecture
Depth
Deep hands-on technology
skills and knowledge
Breadth
Broad knowledge of
patterns, designs,
approaches, technologies,
non-functional requirements,
different ways of working, etc
...
options and trade-offs
Generalising
Specialist
Every software
development team
needs a
master builder
1 or many
Software architecture is about
technical
and
soft skills
Software Architect
Leadership
Communication
Influencing
Negotiation
Collaboration
Coaching and Mentoring
Motivation
Facilitation
Political
The irresponsible architect
Cross-site scripting attacks
possible; weak passwords
allowed; HTTP sessions
didn’t timeout; ...
Basic functionality errors;
little or no quality
assurance; rework required
late in the project because
of assumptions; ...
Even on
“strategic platform”
projects :-o
No non-functional testing
(e.g. penetration testing or
load testing); ...
No documentation; ...
The software architecture role
Architectural
Drivers
Understanding requirements
and constraints
Architecture
Evolution
Ownership of the architecture
throughout the delivery
Coaching and
Mentoring
Guidance and assistance
Quality
Assurance
Introduction and adherence
to standards and principles
Coding
Involvement in the hands-on
elements of software delivery
Technology
Selection
Choosing and evaluating
technology
Architecting
Designing software
Architecture
Evaluation
Understanding that the
architecture works
Software architecture introduces
control?
Chaos!Does the team understand what they are building and how they are building it?
Let’s agree
on some things
Let’s make the implicit,
explicit
Put some boundaries
and guidelines in place
Software Architect
Software Developers
Control
Guidelines, consistency,
discipline, rigour, boundaries,
...
Feedback
“I don’t understand why...”
“How should we...”
“I don’t like the way that...”
Developer Developer Developer Developer Developer
Gap
Architect
Sits in an ivory tower
Focusses on the
low level detail
Collaborating and
sharing
Architecturally
aware
Software Architect
Software Developer
Reduced gap
Avoid ivory towers by
collaborating and
being engaged
Do this well and everybody
becomes an architect :-)
Designing
software
1. Current Situation
We have an existing Internet Banking offering that allows customers to securely view
information about their bank accounts held with us via the web. Although we were one of the
first to market with such a product, the system itself is a number of years old now and a series
of problems has been identified during a consulting exercise that we recently initiated. In
summary:
• The system only provides customers with read-only access to information about their
bank accounts. This includes account balances, recent transactions and recent
statements.
• The information presented to customers is slightly out-of-date, because information from
the core banking system is exported to the website on a nightly basis.
• Transactional requests are not possible through the site, with customers instead sending
a secure message to the call centre with their request instead. This process is open to
abuse and fraud.
• The number of features supported by the offering is limited.
• The technology is no longer seen as “leading edge”, is hard to enhance and costly to
maintain. In addition, the technology has reached “end of life” and is no longer
proactively supported by the vendor.
• The system doesn’t meet current website accessibility standards.
In a recent survey, our Internet Banking system was perceived as poor in terms of the user
experience and the level of information available through the website. With our competitors
now offering fully transactional systems, there is a risk that we will lose business.
2. Vision
The board have given us the go-ahead to initiate a project to replace the current Internet
Banking system, which will need to coincide with the corporate rebranding that will be taking
place in 12 weeks. The replacement system should:
• Provide customers with real-time access to information about their bank accounts.
• Provide customers with the ability to perform common transactions through the website.
This includes making payments, setting up standing orders, transferring money and so on.
• Provide customers with a rich user experience.
• Meet current website accessibility standards.
• Be developed using the new corporate website design guidelines.
Big Bank plc
Internet Banking System
Options
Functional&non-
functionalrequirements
Principles
Constraints
(003) As a business customer, I
want to login so that I can manage
my bank accounts online.
Priority: Must
(009) As a personal customer Iwant to download statements forthe last three months.
Priority: Must
Understanding the functional requirements is
obvious but forgotten
(003) As a business customer, I
want to login so that I can manage
my bank accounts online.
Priority: Must
(009) As a personal customer Iwant to download statements forthe last three months.
Priority: Must
Performance
Scalability
Availability
Security
Disaster Recovery
Accessibility
Monitoring
Management
Audit
...
Flexibility
Extensibility
Maintainability
Interoperability
Legal
Regulatory
Compliance
i18n
L10n
...
✓
✓
✓
✓
✓
✓
✓
✓
Know which are
important to you
Quality Attributes
Learn about and understand the
(often complex) quality attributes
in order to build
sufficient
foundations
Software lives in the real world,
and the real world has
constraints
Constraints are usually
forced upon you
Understand what the constraints are,
who imposed them,
why they are being imposed and
how they affect the
architecture
Given total freedom the
work is likely to sprawl.
T.S.Eliot
Principles
are the things
you want to adopt
They help to introduce
consistency and clarity
Principles are good, but make sure
they’re realistic
and don’t have a
negative impact
1. Current Situation
We have an existing Internet Banking offering that allows customers to securely view
information about their bank accounts held with us via the web. Although we were one of the
first to market with such a product, the system itself is a number of years old now and a series
of problems has been identified during a consulting exercise that we recently initiated. In
summary:
• The system only provides customers with read-only access to information about their
bank accounts. This includes account balances, recent transactions and recent
statements.
• The information presented to customers is slightly out-of-date, because information from
the core banking system is exported to the website on a nightly basis.
• Transactional requests are not possible through the site, with customers instead sending
a secure message to the call centre with their request instead. This process is open to
abuse and fraud.
• The number of features supported by the offering is limited.
• The technology is no longer seen as “leading edge”, is hard to enhance and costly to
maintain. In addition, the technology has reached “end of life” and is no longer
proactively supported by the vendor.
• The system doesn’t meet current website accessibility standards.
In a recent survey, our Internet Banking system was perceived as poor in terms of the user
experience and the level of information available through the website. With our competitors
now offering fully transactional systems, there is a risk that we will lose business.
2. Vision
The board have given us the go-ahead to initiate a project to replace the current Internet
Banking system, which will need to coincide with the corporate rebranding that will be taking
place in 12 weeks. The replacement system should:
• Provide customers with real-time access to information about their bank accounts.
• Provide customers with the ability to perform common transactions through the website.
This includes making payments, setting up standing orders, transferring money and so on.
• Provide customers with a rich user experience.
• Meet current website accessibility standards.
• Be developed using the new corporate website design guidelines.
Big Bank plc
Internet Banking System
Options
Functional&non-
functionalrequirements
Principles
Constraints
Start analysing
or start coding?
“Analysis paralysis” &
“refactor distractor”
are both bad
Boxes & lines
Thing
Other Thing
Important line
Visualising
software
UML tool?
Whiteboard or
flip chart?
You don’t need a UML
tool to do architecture
but agree on notation
Collaborative design
(e.g. pair architecting)
NoUML
diagrams?
We can visualise our process...
...but not our
software!
Moving fast (agility) requires
good
communication
System
Container
Container
Container
Component
Component
Component
Class
Class Class
Class
1. Context 2. Containers 3. Components
Thinking inside the box
... and, optionally,
4. Classes
C4Context
Containers
Components
Classes
This only covers
the static structure
(runtime, infrastructure,
deployment, etc are also important)
This isn’t about
creating a standard
It’s about providing you
some organisational ideas
Context
• What are we building?
• Who is using it? (users, actors, roles, personas, etc)
• How does it fit into the existing IT environment?
• What are the high-level technology decisions?
• How do containers communicate with one another?
• As a developer, where do I need to write code?
Containers
Components
• What components/services is the system made up of?
• Is it clear how the system works at a high-level?
• Do all components have a home (a container)?
Some tips for
effective sketches
Titles
Short and meaningful, numbered if
diagram order is important
Lines
Make line style and arrows explicit,
add annotations to lines to provide
additional information
Layout
Sticky notes and index cards make a
great substitute for drawn boxes,
especially early on
Labels
Be wary of using acronyms
Colour
Ensure that colour coding
is made explicit
Orientation
Users at the top and database at the
bottom? Or perhaps “upside-down”?
Shapes
Don’t assume that people will
understand what different shapes
are being used for
Borders
Use borders to provide emphasis
or group related items,
but ensure people know why
Keys
Explain shapes, lines, colours,
borders, acronyms, etc
Responsibilities
Adding responsibilities to boxes can
provide a nice “at a glance” view
(Miller’s Law; 7±2)
Effective sketches
are an excellent way to
communicate
software architecture
During the design process
and retrospectively
Documenting
software
“
Working software
over
comprehensive
documentation
This doesn’t mean
“don’t do any
documentation”!
Manifesto for Agile Software Development, 2001
The code doesn’t tell
the *whole* story,
but it does *a* story
Tribal
knowledge
“just talk!”
“diagrams and documents
are just props
for conversations”
The bus factor(it’s not just about buses though!)
Any idea how X
works?
No idea what
you’re on about...
#fail
Your system
Current Development Team
Database Administrators
Business Sponsors
Operations/Support Staff
Compliance and AuditSecurity TeamOther Teams
Future Development Team
Software architecture
is a platform for
conversation ... be social!
Software
Architecture
Document
Guidebook
Maps
Sights and
itineraries
History and
culture
Practical
Information
Functional
Overview
What does the system do?
Quality
Attributes
Are there any significant
non-functional
requirements?
Constraints
Are there any significant
constraints?
Principles
What design and
development principles
have been adopted?
Software
Architecture
What does the big picture
look like and how is the
system structured?
Infrastructure
Architecture
What does the target
deployment
environment look like?
Deployment
What is the mapping
between software and
infrastructure?
Operation
& Support
How will people operate
and support the system?
Context
What is this all about?
External
Interfaces
What are the external
system interfaces?
Code
Are there any
implementation details
you need to explain?
Data
What does the data model
look like and where is it
being stored?
Documentation should
describe what
the code doesn’t
Reduce waste,
add value
Use it to explain intent and
act as a guide to navigate
the source code
How much of the document is
up to date and relevant?
Software architecture in the
development
lifecycle
AaaS ... architecture as a service
Software development is not a
relay sport
Software
Architecture
Document
The software architecture
role should be engaged
throughout
(not just analysis and design)
How much up front design should you do?
Big design up front?
Emergent design?
(or none, depending on
your viewpoint!)
Something in between?
Waterfall
You should do
“just enough”
Base your architecture on
requirements, travel light
and prove your architecture
with concrete experiments.
Base your architecture on
requirements, travel light
and prove your architecture
with concrete experiments.
Base your architecture on
requirements, travel light
and prove your architecture
with concrete experiments.
Scott Ambler
http://www.agilemodeling.com/essays/agileArchitecture.htm
What is architecturally
significant?
Costly to change
(can you refactor it
in an afternoon?)
Complex
New
You need to
identify and mitigate
your highest priority
risks
Things that will cause
your project to fail
or you to be fired!
Probability
Impact Low (1) Medium (2) High (3)
Low(1)Medium(2)High(3)
1 2
2 4
3
3 6
6
9
Who looks after the risks
on most software projects?
A (usually) non-technical project manager!
Risk-storming
A collaborative and visual technique for identifying risk
You still need to
deal with the risks
(mitigation strategies include hiring people,
undertaking proof of concept
and changing your architecture)
How much up front design should you do?
“Just enough”
Understand how the
significant elements
fit together
Identify and mitigate
the key risks
Provide firm foundations
and a vision
to move forward
The software architecture role and
the process of software architecting are
different
From chaos to self-organising
Dedicated
software architect
Single point of responsibility for
the technical aspects of the
software project
Everybody is a
software architect
Joint responsibility for the
technical aspects of the
software project
The software architecture role
Elastic Leadership (Roy Osherove)
Survival (command and control),
learning (coaching),
self-organising (facilitation)
Software
Architecture
Document
From big design up front to evolutionary
The process of software architecting
Big up front design
Requirements capture, analysis
and design complete before
coding starts
Evolutionary
architecture
The architecture evolves
secondary to the value created
by early regular releases of
working software
/// <summary>
/// Represents the behaviour behind the ...
/// </summary>
public class SomeWizard : AbstractWizard
{
private DomainObject _object;
private WizardPage _page;
private WizardController _controller;
public SomeWizard()
{
}
...
}
/// <summary>
/// Represents the behaviour behind the ...
/// </summary>
public class SomeWizard : AbstractWizard
{
private DomainObject _object;
private WizardPage _page;
private WizardController _controller;
public SomeWizard()
{
}
...
}
21st century software architecture
“just enough”
The role
The process
Understand how the
significant elements
fit together
Identify and mitigate
the key risks
Provide firm foundations
and a vision
to move forward
Software
Architecture
Document
you
Do whatever works for
Buy the book for $10
YI85bLbAXGks
(expires 30th March 2013)

More Related Content

PPTX
Chapter 2
PDF
Fundamentals of LinkedIn Sales Navigator for Business Development
PDF
Marketing Performance Report Card: 6 Metrics You Should Measure
PDF
Style Guide Best Practices
PPTX
Data warehousing implementation issues
PPTX
Data visualization
PDF
Alibaba case study
PPT
Semantic web an overview and projects
Chapter 2
Fundamentals of LinkedIn Sales Navigator for Business Development
Marketing Performance Report Card: 6 Metrics You Should Measure
Style Guide Best Practices
Data warehousing implementation issues
Data visualization
Alibaba case study
Semantic web an overview and projects

What's hot (15)

PDF
The 3 Secrets of Highly Successful Graduates
PDF
Sales Bible course
PDF
Demand Generation Marketing Strategy PowerPoint Presentation Slides
PDF
The theory-and-practice-of-space-and-assortment-optimization-final
PPTX
Data Analytics
PDF
DI&A Slides: Descriptive, Prescriptive, and Predictive Analytics
PDF
Types of business intelligence tools
PPTX
Alibaba market strategy
PDF
Work Hacks : Body Language
KEY
Value co creation canvas by wim rampen
PPTX
Hair_EOMA_1e_Chap001_PPT.pptx
PPT
customer oriented selling
PPTX
7 Ways Soft-Skills Power Organizational Performance
PPTX
Data Visualization
PPTX
Alibaba Group Overview
The 3 Secrets of Highly Successful Graduates
Sales Bible course
Demand Generation Marketing Strategy PowerPoint Presentation Slides
The theory-and-practice-of-space-and-assortment-optimization-final
Data Analytics
DI&A Slides: Descriptive, Prescriptive, and Predictive Analytics
Types of business intelligence tools
Alibaba market strategy
Work Hacks : Body Language
Value co creation canvas by wim rampen
Hair_EOMA_1e_Chap001_PPT.pptx
customer oriented selling
7 Ways Soft-Skills Power Organizational Performance
Data Visualization
Alibaba Group Overview
Ad

Viewers also liked (20)

PPT
Architectural Design in Software Engineering SE10
PPT
Architecture design in software engineering
PDF
Architecture: where do you start?
PDF
ASAS 2013 - Agility and the essence of software architecture
PDF
Simon Brown: Software Architecture as Code at I T.A.K.E. Unconference 2015
PDF
Making things that work with us - Distill
PDF
Making your washing machine talk with a power plant
PPTX
Game Architecture and Programming
PPTX
Software architecture
PDF
An Introduction to Software Architecture - Summary
PPTX
Software Architecture Fundamentals Part-1 Architecture soft skill
PDF
Software Engineering - chp0- introduction
PPT
User Driven Software Architecture
PPTX
A summary of software architecture guide
PPTX
Software Architecture Introduction
PDF
Agile Software Architecture
PDF
Software Architecture for DevOps and Continuous Delivery
PPT
Software architecture 2
PPTX
Business Architecture - Paul Turner
Architectural Design in Software Engineering SE10
Architecture design in software engineering
Architecture: where do you start?
ASAS 2013 - Agility and the essence of software architecture
Simon Brown: Software Architecture as Code at I T.A.K.E. Unconference 2015
Making things that work with us - Distill
Making your washing machine talk with a power plant
Game Architecture and Programming
Software architecture
An Introduction to Software Architecture - Summary
Software Architecture Fundamentals Part-1 Architecture soft skill
Software Engineering - chp0- introduction
User Driven Software Architecture
A summary of software architecture guide
Software Architecture Introduction
Agile Software Architecture
Software Architecture for DevOps and Continuous Delivery
Software architecture 2
Business Architecture - Paul Turner
Ad

Similar to Software architecture for developers by Simon Brown (20)

PDF
Software architecture for developers
PPT
It Consulting Slides
PDF
ASAS 2014 - Simon Brown
PPTX
Chapter 7 Development Strategies
PDF
Managing and Using Information Systems A Strategic Approach 6th Edition Pearl...
PDF
chapter07-120827115403-phpapp01.pdf
PDF
By the Book: How Great User Experiences in Software Can Impact Government and...
PPTX
Chapter 7 Development StrategiesInformation Technology Project Management .pptx
PPT
Final wireframes from screen concept to user interaction v0.4
PPTX
PPTX
L08 architecture considerations
PDF
L10 Architecture Considerations
PPTX
The Role of a Principal Engineer - Michael Gray- Leeds Sharp
KEY
Auditing Roundtable Conference 2012 - Choosing the best software
PDF
That soft, messy people factor in technology projects
PPT
Sa002 abc
PDF
Hawaii OIMT presentation
PPT
User Experience Strategy
PPTX
Indranil Guha - It transformation challenges & choices...
PPT
He mian agile project-inception
Software architecture for developers
It Consulting Slides
ASAS 2014 - Simon Brown
Chapter 7 Development Strategies
Managing and Using Information Systems A Strategic Approach 6th Edition Pearl...
chapter07-120827115403-phpapp01.pdf
By the Book: How Great User Experiences in Software Can Impact Government and...
Chapter 7 Development StrategiesInformation Technology Project Management .pptx
Final wireframes from screen concept to user interaction v0.4
L08 architecture considerations
L10 Architecture Considerations
The Role of a Principal Engineer - Michael Gray- Leeds Sharp
Auditing Roundtable Conference 2012 - Choosing the best software
That soft, messy people factor in technology projects
Sa002 abc
Hawaii OIMT presentation
User Experience Strategy
Indranil Guha - It transformation challenges & choices...
He mian agile project-inception

More from Codemotion (20)

PDF
Fuzz-testing: A hacker's approach to making your code more secure | Pascal Ze...
PDF
Pompili - From hero to_zero: The FatalNoise neverending story
PPTX
Pastore - Commodore 65 - La storia
PPTX
Pennisi - Essere Richard Altwasser
PPTX
Michel Schudel - Let's build a blockchain... in 40 minutes! - Codemotion Amst...
PPTX
Richard Süselbeck - Building your own ride share app - Codemotion Amsterdam 2019
PPTX
Eward Driehuis - What we learned from 20.000 attacks - Codemotion Amsterdam 2019
PPTX
Francesco Baldassarri - Deliver Data at Scale - Codemotion Amsterdam 2019 -
PDF
Martin Förtsch, Thomas Endres - Stereoscopic Style Transfer AI - Codemotion A...
PDF
Melanie Rieback, Klaus Kursawe - Blockchain Security: Melting the "Silver Bul...
PDF
Angelo van der Sijpt - How well do you know your network stack? - Codemotion ...
PDF
Lars Wolff - Performance Testing for DevOps in the Cloud - Codemotion Amsterd...
PDF
Sascha Wolter - Conversational AI Demystified - Codemotion Amsterdam 2019
PDF
Michele Tonutti - Scaling is caring - Codemotion Amsterdam 2019
PPTX
Pat Hermens - From 100 to 1,000+ deployments a day - Codemotion Amsterdam 2019
PPTX
James Birnie - Using Many Worlds of Compute Power with Quantum - Codemotion A...
PDF
Don Goodman-Wilson - Chinese food, motor scooters, and open source developmen...
PDF
Pieter Omvlee - The story behind Sketch - Codemotion Amsterdam 2019
PDF
Dave Farley - Taking Back “Software Engineering” - Codemotion Amsterdam 2019
PDF
Joshua Hoffman - Should the CTO be Coding? - Codemotion Amsterdam 2019
Fuzz-testing: A hacker's approach to making your code more secure | Pascal Ze...
Pompili - From hero to_zero: The FatalNoise neverending story
Pastore - Commodore 65 - La storia
Pennisi - Essere Richard Altwasser
Michel Schudel - Let's build a blockchain... in 40 minutes! - Codemotion Amst...
Richard Süselbeck - Building your own ride share app - Codemotion Amsterdam 2019
Eward Driehuis - What we learned from 20.000 attacks - Codemotion Amsterdam 2019
Francesco Baldassarri - Deliver Data at Scale - Codemotion Amsterdam 2019 -
Martin Förtsch, Thomas Endres - Stereoscopic Style Transfer AI - Codemotion A...
Melanie Rieback, Klaus Kursawe - Blockchain Security: Melting the "Silver Bul...
Angelo van der Sijpt - How well do you know your network stack? - Codemotion ...
Lars Wolff - Performance Testing for DevOps in the Cloud - Codemotion Amsterd...
Sascha Wolter - Conversational AI Demystified - Codemotion Amsterdam 2019
Michele Tonutti - Scaling is caring - Codemotion Amsterdam 2019
Pat Hermens - From 100 to 1,000+ deployments a day - Codemotion Amsterdam 2019
James Birnie - Using Many Worlds of Compute Power with Quantum - Codemotion A...
Don Goodman-Wilson - Chinese food, motor scooters, and open source developmen...
Pieter Omvlee - The story behind Sketch - Codemotion Amsterdam 2019
Dave Farley - Taking Back “Software Engineering” - Codemotion Amsterdam 2019
Joshua Hoffman - Should the CTO be Coding? - Codemotion Amsterdam 2019

Recently uploaded (20)

PDF
Chapter 3 Spatial Domain Image Processing.pdf
PDF
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
PDF
TokAI - TikTok AI Agent : The First AI Application That Analyzes 10,000+ Vira...
PDF
Empathic Computing: Creating Shared Understanding
PPTX
PA Analog/Digital System: The Backbone of Modern Surveillance and Communication
PDF
GamePlan Trading System Review: Professional Trader's Honest Take
PPTX
VMware vSphere Foundation How to Sell Presentation-Ver1.4-2-14-2024.pptx
PDF
Dropbox Q2 2025 Financial Results & Investor Presentation
PDF
Unlocking AI with Model Context Protocol (MCP)
PDF
solutions_manual_-_materials___processing_in_manufacturing__demargo_.pdf
PPTX
20250228 LYD VKU AI Blended-Learning.pptx
PDF
cuic standard and advanced reporting.pdf
PDF
GDG Cloud Iasi [PUBLIC] Florian Blaga - Unveiling the Evolution of Cybersecur...
PDF
Electronic commerce courselecture one. Pdf
PPTX
Big Data Technologies - Introduction.pptx
PDF
Shreyas Phanse Resume: Experienced Backend Engineer | Java • Spring Boot • Ka...
PDF
Spectral efficient network and resource selection model in 5G networks
PDF
Advanced IT Governance
PDF
Advanced methodologies resolving dimensionality complications for autism neur...
PPTX
MYSQL Presentation for SQL database connectivity
Chapter 3 Spatial Domain Image Processing.pdf
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
TokAI - TikTok AI Agent : The First AI Application That Analyzes 10,000+ Vira...
Empathic Computing: Creating Shared Understanding
PA Analog/Digital System: The Backbone of Modern Surveillance and Communication
GamePlan Trading System Review: Professional Trader's Honest Take
VMware vSphere Foundation How to Sell Presentation-Ver1.4-2-14-2024.pptx
Dropbox Q2 2025 Financial Results & Investor Presentation
Unlocking AI with Model Context Protocol (MCP)
solutions_manual_-_materials___processing_in_manufacturing__demargo_.pdf
20250228 LYD VKU AI Blended-Learning.pptx
cuic standard and advanced reporting.pdf
GDG Cloud Iasi [PUBLIC] Florian Blaga - Unveiling the Evolution of Cybersecur...
Electronic commerce courselecture one. Pdf
Big Data Technologies - Introduction.pptx
Shreyas Phanse Resume: Experienced Backend Engineer | Java • Spring Boot • Ka...
Spectral efficient network and resource selection model in 5G networks
Advanced IT Governance
Advanced methodologies resolving dimensionality complications for autism neur...
MYSQL Presentation for SQL database connectivity

Software architecture for developers by Simon Brown

  • 1. Follow me on Twitter @simonbrown Simon Brown Software architecture for developers
  • 2. I help software teams understand software architecture, technical leadership and the balance with agility (I code too) Training Book Speaking Buy the book for $10 YI85bLbAXGks (expires 30th March 2013)
  • 5. What is architecture? As a noun... Structure The definition of something in terms of its components and interactions As a verb... Vision The process of architecting, making (significant) design decisions, etc and
  • 6. Grady Booch http://www.handbookofsoftwarearchitecture.com/index.jsp?page=Blog&part=2006 What is design? Architecture represents the significant decisions, where significance is measured by cost of change. Can you refactor it in an afternoon?
  • 7. Chaos!Does the team understand what they are building and how they are building it?
  • 8. Chaos!Does the team understand what they are building and how they are building it? No defined structure, inconsistent approaches, big ball of mud, spaghetti code, ... STOPSlow, insecure, unstable, unmaintainable, hard to deploy, hard to change, over time, over budget, ...
  • 9. Shared vision of TL; DR Software Architecture Document
  • 12. The software architecture role is different to the lead developer role It’s an inward and outward facing role
  • 14. Abstract Specific As software developers, the codeis usually our main focus Lines of code Classes, functions Design patterns Unit tests Refactoring
  • 15. Abstract Specific Sometimes you need to step back from the IDE Lines of code Classes, functions Design patterns Unit tests Refactoring
  • 16. The low-level detail is equally important Don’t code 100% of the time though!
  • 19. Should software architects write code on software projects? Ideally yes, but...
  • 20. Software architects must be master builders And coding is a great way to retain this skill Plus it reduces many of the problems associated with ivory tower architecture
  • 21. Depth Deep hands-on technology skills and knowledge Breadth Broad knowledge of patterns, designs, approaches, technologies, non-functional requirements, different ways of working, etc ... options and trade-offs Generalising Specialist
  • 22. Every software development team needs a master builder 1 or many
  • 23. Software architecture is about technical and soft skills
  • 25. The irresponsible architect Cross-site scripting attacks possible; weak passwords allowed; HTTP sessions didn’t timeout; ... Basic functionality errors; little or no quality assurance; rework required late in the project because of assumptions; ... Even on “strategic platform” projects :-o No non-functional testing (e.g. penetration testing or load testing); ... No documentation; ...
  • 26. The software architecture role Architectural Drivers Understanding requirements and constraints Architecture Evolution Ownership of the architecture throughout the delivery Coaching and Mentoring Guidance and assistance Quality Assurance Introduction and adherence to standards and principles Coding Involvement in the hands-on elements of software delivery Technology Selection Choosing and evaluating technology Architecting Designing software Architecture Evaluation Understanding that the architecture works
  • 28. Chaos!Does the team understand what they are building and how they are building it? Let’s agree on some things Let’s make the implicit, explicit Put some boundaries and guidelines in place
  • 29. Software Architect Software Developers Control Guidelines, consistency, discipline, rigour, boundaries, ... Feedback “I don’t understand why...” “How should we...” “I don’t like the way that...”
  • 30. Developer Developer Developer Developer Developer Gap Architect Sits in an ivory tower Focusses on the low level detail
  • 31. Collaborating and sharing Architecturally aware Software Architect Software Developer Reduced gap Avoid ivory towers by collaborating and being engaged Do this well and everybody becomes an architect :-)
  • 33. 1. Current Situation We have an existing Internet Banking offering that allows customers to securely view information about their bank accounts held with us via the web. Although we were one of the first to market with such a product, the system itself is a number of years old now and a series of problems has been identified during a consulting exercise that we recently initiated. In summary: • The system only provides customers with read-only access to information about their bank accounts. This includes account balances, recent transactions and recent statements. • The information presented to customers is slightly out-of-date, because information from the core banking system is exported to the website on a nightly basis. • Transactional requests are not possible through the site, with customers instead sending a secure message to the call centre with their request instead. This process is open to abuse and fraud. • The number of features supported by the offering is limited. • The technology is no longer seen as “leading edge”, is hard to enhance and costly to maintain. In addition, the technology has reached “end of life” and is no longer proactively supported by the vendor. • The system doesn’t meet current website accessibility standards. In a recent survey, our Internet Banking system was perceived as poor in terms of the user experience and the level of information available through the website. With our competitors now offering fully transactional systems, there is a risk that we will lose business. 2. Vision The board have given us the go-ahead to initiate a project to replace the current Internet Banking system, which will need to coincide with the corporate rebranding that will be taking place in 12 weeks. The replacement system should: • Provide customers with real-time access to information about their bank accounts. • Provide customers with the ability to perform common transactions through the website. This includes making payments, setting up standing orders, transferring money and so on. • Provide customers with a rich user experience. • Meet current website accessibility standards. • Be developed using the new corporate website design guidelines. Big Bank plc Internet Banking System Options Functional&non- functionalrequirements Principles Constraints
  • 34. (003) As a business customer, I want to login so that I can manage my bank accounts online. Priority: Must (009) As a personal customer Iwant to download statements forthe last three months. Priority: Must Understanding the functional requirements is obvious but forgotten (003) As a business customer, I want to login so that I can manage my bank accounts online. Priority: Must (009) As a personal customer Iwant to download statements forthe last three months. Priority: Must
  • 36. Learn about and understand the (often complex) quality attributes in order to build sufficient foundations
  • 37. Software lives in the real world, and the real world has constraints Constraints are usually forced upon you
  • 38. Understand what the constraints are, who imposed them, why they are being imposed and how they affect the architecture Given total freedom the work is likely to sprawl. T.S.Eliot
  • 39. Principles are the things you want to adopt They help to introduce consistency and clarity
  • 40. Principles are good, but make sure they’re realistic and don’t have a negative impact
  • 41. 1. Current Situation We have an existing Internet Banking offering that allows customers to securely view information about their bank accounts held with us via the web. Although we were one of the first to market with such a product, the system itself is a number of years old now and a series of problems has been identified during a consulting exercise that we recently initiated. In summary: • The system only provides customers with read-only access to information about their bank accounts. This includes account balances, recent transactions and recent statements. • The information presented to customers is slightly out-of-date, because information from the core banking system is exported to the website on a nightly basis. • Transactional requests are not possible through the site, with customers instead sending a secure message to the call centre with their request instead. This process is open to abuse and fraud. • The number of features supported by the offering is limited. • The technology is no longer seen as “leading edge”, is hard to enhance and costly to maintain. In addition, the technology has reached “end of life” and is no longer proactively supported by the vendor. • The system doesn’t meet current website accessibility standards. In a recent survey, our Internet Banking system was perceived as poor in terms of the user experience and the level of information available through the website. With our competitors now offering fully transactional systems, there is a risk that we will lose business. 2. Vision The board have given us the go-ahead to initiate a project to replace the current Internet Banking system, which will need to coincide with the corporate rebranding that will be taking place in 12 weeks. The replacement system should: • Provide customers with real-time access to information about their bank accounts. • Provide customers with the ability to perform common transactions through the website. This includes making payments, setting up standing orders, transferring money and so on. • Provide customers with a rich user experience. • Meet current website accessibility standards. • Be developed using the new corporate website design guidelines. Big Bank plc Internet Banking System Options Functional&non- functionalrequirements Principles Constraints
  • 42. Start analysing or start coding? “Analysis paralysis” & “refactor distractor” are both bad
  • 43. Boxes & lines Thing Other Thing Important line
  • 45. UML tool? Whiteboard or flip chart? You don’t need a UML tool to do architecture but agree on notation
  • 48. We can visualise our process... ...but not our software!
  • 49. Moving fast (agility) requires good communication
  • 51. 1. Context 2. Containers 3. Components Thinking inside the box ... and, optionally, 4. Classes C4Context Containers Components Classes This only covers the static structure (runtime, infrastructure, deployment, etc are also important)
  • 52. This isn’t about creating a standard It’s about providing you some organisational ideas
  • 53. Context • What are we building? • Who is using it? (users, actors, roles, personas, etc) • How does it fit into the existing IT environment?
  • 54. • What are the high-level technology decisions? • How do containers communicate with one another? • As a developer, where do I need to write code? Containers
  • 55. Components • What components/services is the system made up of? • Is it clear how the system works at a high-level? • Do all components have a home (a container)?
  • 56. Some tips for effective sketches Titles Short and meaningful, numbered if diagram order is important Lines Make line style and arrows explicit, add annotations to lines to provide additional information Layout Sticky notes and index cards make a great substitute for drawn boxes, especially early on Labels Be wary of using acronyms Colour Ensure that colour coding is made explicit Orientation Users at the top and database at the bottom? Or perhaps “upside-down”? Shapes Don’t assume that people will understand what different shapes are being used for Borders Use borders to provide emphasis or group related items, but ensure people know why Keys Explain shapes, lines, colours, borders, acronyms, etc Responsibilities Adding responsibilities to boxes can provide a nice “at a glance” view (Miller’s Law; 7±2)
  • 57. Effective sketches are an excellent way to communicate software architecture During the design process and retrospectively
  • 59. “ Working software over comprehensive documentation This doesn’t mean “don’t do any documentation”! Manifesto for Agile Software Development, 2001
  • 60. The code doesn’t tell the *whole* story, but it does *a* story
  • 61. Tribal knowledge “just talk!” “diagrams and documents are just props for conversations”
  • 62. The bus factor(it’s not just about buses though!) Any idea how X works? No idea what you’re on about... #fail
  • 63. Your system Current Development Team Database Administrators Business Sponsors Operations/Support Staff Compliance and AuditSecurity TeamOther Teams Future Development Team Software architecture is a platform for conversation ... be social!
  • 65. Functional Overview What does the system do? Quality Attributes Are there any significant non-functional requirements? Constraints Are there any significant constraints? Principles What design and development principles have been adopted? Software Architecture What does the big picture look like and how is the system structured? Infrastructure Architecture What does the target deployment environment look like? Deployment What is the mapping between software and infrastructure? Operation & Support How will people operate and support the system? Context What is this all about? External Interfaces What are the external system interfaces? Code Are there any implementation details you need to explain? Data What does the data model look like and where is it being stored?
  • 66. Documentation should describe what the code doesn’t Reduce waste, add value Use it to explain intent and act as a guide to navigate the source code
  • 67. How much of the document is up to date and relevant?
  • 68. Software architecture in the development lifecycle
  • 69. AaaS ... architecture as a service Software development is not a relay sport Software Architecture Document
  • 70. The software architecture role should be engaged throughout (not just analysis and design)
  • 71. How much up front design should you do? Big design up front? Emergent design? (or none, depending on your viewpoint!) Something in between? Waterfall
  • 73. Base your architecture on requirements, travel light and prove your architecture with concrete experiments. Base your architecture on requirements, travel light and prove your architecture with concrete experiments. Base your architecture on requirements, travel light and prove your architecture with concrete experiments. Scott Ambler http://www.agilemodeling.com/essays/agileArchitecture.htm
  • 74. What is architecturally significant? Costly to change (can you refactor it in an afternoon?) Complex New
  • 75. You need to identify and mitigate your highest priority risks Things that will cause your project to fail or you to be fired!
  • 76. Probability Impact Low (1) Medium (2) High (3) Low(1)Medium(2)High(3) 1 2 2 4 3 3 6 6 9
  • 77. Who looks after the risks on most software projects? A (usually) non-technical project manager!
  • 78. Risk-storming A collaborative and visual technique for identifying risk
  • 79. You still need to deal with the risks (mitigation strategies include hiring people, undertaking proof of concept and changing your architecture)
  • 80. How much up front design should you do? “Just enough” Understand how the significant elements fit together Identify and mitigate the key risks Provide firm foundations and a vision to move forward
  • 81. The software architecture role and the process of software architecting are different
  • 82. From chaos to self-organising Dedicated software architect Single point of responsibility for the technical aspects of the software project Everybody is a software architect Joint responsibility for the technical aspects of the software project The software architecture role Elastic Leadership (Roy Osherove) Survival (command and control), learning (coaching), self-organising (facilitation)
  • 83. Software Architecture Document From big design up front to evolutionary The process of software architecting Big up front design Requirements capture, analysis and design complete before coding starts Evolutionary architecture The architecture evolves secondary to the value created by early regular releases of working software /// <summary> /// Represents the behaviour behind the ... /// </summary> public class SomeWizard : AbstractWizard { private DomainObject _object; private WizardPage _page; private WizardController _controller; public SomeWizard() { } ... }
  • 84. /// <summary> /// Represents the behaviour behind the ... /// </summary> public class SomeWizard : AbstractWizard { private DomainObject _object; private WizardPage _page; private WizardController _controller; public SomeWizard() { } ... } 21st century software architecture “just enough” The role The process Understand how the significant elements fit together Identify and mitigate the key risks Provide firm foundations and a vision to move forward Software Architecture Document
  • 86. Buy the book for $10 YI85bLbAXGks (expires 30th March 2013)