software architecture - past-present-future

Software Architecture:Past, Present & Future ?

Christophe.VanGinneken@student.kuleuven.be

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

The Wheel

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

Industrial Age

4+11995

4+1Logical View Development View

Process View Physical View

Classes, Interfaces,Collaborations

Components,Layering

Mapping onto HardwareConcurrency & Synchronization

Use Case

View

1995

4+11995

• Best Practices Framework

• No Formalisms → Blueprints

• Non-functionals in Process View

• Layering in Development View

• Some (technical) details are so 90’s ;-)

4+11995

• Iterative Process

• Scenario-driven

• DocumentationSoftware Architecture + Software Design

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

The Bubble

1985 1990 1995 2000 2005

Basic Research

Concept Formulation

Development Extension

Internal Enhancement/Exploration

External Enhancement / Exploration

Popularization

1995

2000

2005

2010

Future ?

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 ...

Really ?

Software Architecture & Me

make itbuy it

design itdocument it

do it code it

...1995 2000 2005 2010 2015

Where did we go wrong ?

Recap ...

PROCESS

People

4+1Logical View Development View

Process View Physical View

Classes, Interfaces,Collaborations

Components,Layering

Mapping onto HardwareConcurrency & Synchronization

Use Case

View

20131995

4+120131995

• Person-centric

• No Demanding Formalisms

• But Still Formalized

• Iterative Process

• Scenario-driven