Table of Contents
About the book
Why did I write the book?
A new approach to software development?
About the author
Acknowledgements
I Architecture
What is software architecture''?
Architecture as a noun - structure
Architecture as a verb - vision
Types of architecture
Towards a definition ofsoftware architecture''
Enterprise architecture - strategy rather than code
Architecture vs design
Is software architecture important?
Does every software project need software architecture?
Architectural drivers
1. Functional requirements
2. Quality Attributes (non-functional requirements)
3. Constraints
4. Principles
Understand their influence
II Architects
The software architecture role
1. Architectural drivers
2. Designing software
3. Technical risks
4. Technical leadership
5. Quality assurance
Software architecture is a role, not a rank
Create your own definition of the role
Technical leadership
Controlling chaos
Collaborative technical leadership is not easy
Do agile teams need software architects?
Software development is not a relay sport
Mind the gap
Software architects and coding
A step back in time
Should software architects write code?
The tension between coding and being senior
Software as an engineering discipline
The skills and knowledge of a software architect
Technology skills
Soft skills
Domain knowledge
From developer to architect
Tips for new software architects
III Architecting
Managing technical risks
Quantifying and prioritising risks
Identifying risks
Mitigating risks
Risk ownership
Software architecture in the delivery process
The conflict between agile and architecture
Technical vs functional design
Software architecture provides boundaries
How much up front design should you do?
Firm foundations
Contextualising just enough up front design
Introducing software architecture
The essence of software architecture
IV Appendices
Appendix A: Financial Risk System
Background
Functional Requirements
Non-functional Requirements