introduction to software architecture
DESCRIPTION
TRANSCRIPT
© Yuriy Guts, 2013
Software Architecture
Introduction to
What is
Software
Architecture?
Modules, connections, dependencies and interfaces?
Modules, connections, dependencies and interfaces?
The relationship between the elements that make up the product?
Modules, connections, dependencies and interfaces?
The relationship between the elements that make up the product?
The decomposition of the problem into smaller implementable elements?
Modules, connections, dependencies and interfaces?
The relationship between the elements that make up the product?
The decomposition of the problem into smaller implementable elements?
The skeleton/backbone of the product?
An abstract view?
An approach to achieve a goal?
A blueprint?
The big picture?
Modules, connections, dependencies and interfaces?
The relationship between the elements that make up the product?
The decomposition of the problem into smaller implementable elements?
The skeleton/backbone of the product?
An abstract view?
An approach to achieve a goal?
A blueprint?
The big picture?
There are literally hundreds of
definitions of Software Architecture
http://tinyurl.com/sei-definitions
Is there anything in common?
“
”
The structure or structures of the system,
which comprise software elements, the
externally visible properties of those
elements, and the relationships among them.
“Software Architecture in Practice” book
Software Engineering Institute
“
”
The structure or structures of the system,
which comprise software elements, the
externally visible properties of those
elements, and the relationships among them.
“Software Architecture in Practice” book
Software Engineering Institute
”“ Those aspects that are the hardest to change.
Chris Verhoef; Martin Fowler
“
”
The structure or structures of the system,
which comprise software elements, the
externally visible properties of those
elements, and the relationships among them.
“Software Architecture in Practice” book
Software Engineering Institute
”“ Those aspects that are the hardest to change.
Chris Verhoef; Martin Fowler
STRUCTURE
VISION
Structure + Vision
Regardless of the domain,
architectural work is about
Developing
Organization
Stakeholders
Marketing
Stakeholders
Maintenance
StakeholdersCustomer
Stakeholders
End-User
Stakeholders
There are no “good” and “bad” architectures
There are ones that are more suitable
given current constraints,
and the ones that are less suitable.
Levels of Architecture
Component Designer
Levels of Architecture
Component Designer
Application Architect
Levels of Architecture
Component Designer
Application Architect
Solutions Architect
Levels of Architecture
Component Designer
Application Architect
Solutions Architect
Business (Enterprise) Architect
The Software Architect Role
Anti-pattern:
“The Ivory Tower Architect”
Development team
Do Agile teams need architects?
Architectural
Drivers
Understanding requirements
and constraints
Technology
Selection
Choosing and evaluating
technologies
Architecting
Designing software
Architecture
Evaluation
Verifying that the architecture
actually works
Architecture
Evolution
Ownership of the architecture
throughout the delivery
Coaching &
Mentoring
Providing guidance and
assistance to teams
Coding
Involvement in hands-on
software delivery
Quality
Assurance
Introduction and adherence to
standards and principles
Even in the agilest of teams
you need someone
to take care of all this!
Otherwise it would get messy.
“Agile” Architect
It may not be a dedicated person.
Responsibilities can be split among multiple people.
Involvement varies depending on team maturity:
1. Chaos (survival mode): requires direct authoritative leadership.
2. Learning: requires a coaching leadership style.
3. Self-organizing (mature): requires facilitation to keep balance.
Choosing a reference architecture
Architecture Visualization:
The 4+1 Model
SA involvement within the company
• Support for Sales and Marketing
• Bootstrapping new projects
• Technology consulting for existing projects
• Investigating new technologies, developing PoC
• Internal training, competence development
Q & A
Acknowledgements
• Len Bass, Paul Clements, Rick Kazman. Software Architecture in Practice, 2nd edition [2003].
• Paul Clements et al. Documenting Software Architectures: Views and Beyond, 2nd edition [2010].
• Simon Brown. Software Architecture for Developers [2013].