Software architecture courses are generally told with the assumption of everything is perfect, e.g. customers know what they want, team members have all of the necessary skills to complete the product with the expected quality. In this presentation, I have talked about the real world problems that we face while architecting software systems.

1. Software Architecture -
The Untold Story
Turgay ÇELİK, PhD,
Technical Lead @MilSOFT

2. What if we don’t care design?
2

3. 3

4. https://www.bbc.com/news/world-europe-44871788
4

5. So… we design
5

6. Software Architecture - The Why
Software Projects are “big” - budget, team, importance
Software Projects are “complex” - Storage, High Performance Queries, Reliable
Messaging, Fault Tolerance, Reliability, Resilience, Distribution and Parallelism,
User Experience,
It is getting more and more complex...
6

7. Software Complexity and Growth
US DoD - Defence Science Board - Design and Acquisition of Software for Defence Systems (Feb. 2018)
7

8. Software Architecture - What
Wiki Definition:
“Software architecture refers to the high level structures of a software system, the
discipline of creating such structures, and system.
Each structure comprises software elements, relations among them, and properties
of both elements and relations.”
8

9. Software Architecture - The Told
9

10. Software Development - Classical Approach
10

11. The Untolds #1 Requirements Always Change, so the Design
11

12. The Untolds #2: We Generally Don’t Have Enough Time
12

13. The Untolds #3: We Generally Don’t Have Enough People
13

14. The Untolds #4: We Have Legacy Code, A Lot.
14

15. The Untolds #5: Staff Turnover
Reaction of a senior engineer, having
seen it all before
15
http://devopsreactions.tumblr.com/post/150811199010/reaction-of-a-senior-engineer-
having-seen-it-all

16. Software Architecture - Evolutionary
16

17. More Concepts...
Minimum Viable Product
Agile Software Development
Architecture DAR (Decision Analysis and Resolution)
17