software architecture - past-present-future
DESCRIPTION
A bit of a rant on the bad way of doing software architecture, packaged in a cute reflection on the 4+1 view.TRANSCRIPT
![Page 1: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/1.jpg)
Software Architecture:Past, Present & Future ?
![Page 2: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/2.jpg)
Software Architecture by the Book
1992
(System) Architecture= physical structure, instruction sets
BrooksMillsParnas1985
1991 “Architecture between and process”Royce & Royce
{ elements, forms, rationale } = software architecturePerry & Wolf
+ constraints
= components & connectors
1994 First book on Software Architecture
![Page 3: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/3.jpg)
The Wheel
![Page 4: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/4.jpg)
Software Architecture by the Book
1995
1998
SEI’s SAAMRational’s 4+1 viewsSiemens 4 views
Large Software Development OrganizationsSiemens, Nokia, Philips, Nortel, IBM,...
Software Product Line Architectures
![Page 5: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/5.jpg)
Industrial Age
![Page 6: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/6.jpg)
4+11995
![Page 7: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/7.jpg)
4+1Logical View Development View
Process View Physical View
Classes, Interfaces,Collaborations
Components,Layering
Mapping onto HardwareConcurrency & Synchronization
Use Case
View
1995
![Page 8: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/8.jpg)
4+11995
• Best Practices Framework
• No Formalisms → Blueprints
• Non-functionals in Process View
• Layering in Development View
• Some (technical) details are so 90’s ;-)
![Page 9: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/9.jpg)
4+11995
• Iterative Process
• Scenario-driven
• DocumentationSoftware Architecture + Software Design
![Page 10: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/10.jpg)
![Page 11: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/11.jpg)
Software Architecture by the Book
1999
2005
First ConferencesNon-academics start to pitch in best practicesFounding of World-Wide groups (IFIP WG 2.10, WW ISA)
Open Group’s ADLSAAM, BAPO and ATAMRM-ODPIEEE 1471
![Page 12: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/12.jpg)
The Bubble
![Page 13: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/13.jpg)
1985 1990 1995 2000 2005
Basic Research
Concept Formulation
Development Extension
Internal Enhancement/Exploration
External Enhancement / Exploration
Popularization
![Page 14: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/14.jpg)
1995
2000
2005
2010
![Page 15: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/15.jpg)
Future ?
![Page 16: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/16.jpg)
2006
Chief ArchitectsSlight Inflation in TitlesRich ADL’s vs UMLDomain Specific Pre-Cooked ArchitecturesXML and SOAP ImpactScripting LanguagesOpen Source
“A Discipline has Emerged”
New Ideas can Still be ExploredOpportunities:
Architectural Design ↔ QualityBetter Language ?Assurance for ConformanceTesting based on Architecture ...
![Page 17: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/17.jpg)
Really ?
![Page 18: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/18.jpg)
Software Architecture & Me
make itbuy it
design itdocument it
do it code it
...1995 2000 2005 2010 2015
![Page 19: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/19.jpg)
Where did we go wrong ?
![Page 20: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/20.jpg)
Recap ...
PROCESS
![Page 21: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/21.jpg)
People
![Page 22: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/22.jpg)
4+1Logical View Development View
Process View Physical View
Classes, Interfaces,Collaborations
Components,Layering
Mapping onto HardwareConcurrency & Synchronization
Use Case
View
20131995
![Page 23: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/23.jpg)
4+120131995
• Person-centric
• No Demanding Formalisms
• But Still Formalized
• Iterative Process
• Scenario-driven
![Page 24: Software Architecture - Past-Present-Future](https://reader034.vdocuments.us/reader034/viewer/2022052601/558b559ad8b42a4a698b4649/html5/thumbnails/24.jpg)