sa past-future

WICSA/ECSA 2012, Helsinki

So#ware Architecture: Past, Present, and Future Direc7ons

Ivica Crnkovic Mälardalen University, Sweden

www.idt.mdh.se/~icc

Past & Present -‐ impression from:

•  Dewayne E. Perry, Alexander L. Wolf . Founda7ons for the study of so#ware architecture, ACM SIGSOFT SoMware Engineering Notes, Volume 17 Issue 4, Oct. 1992, Pages 40 – 52

Google Scholar: 2012-‐08-‐20: Cited by 1893

2.1 Developing an Intui]on about SoMware Architecture

•  Compu]ng hardware architecture •  Network architecture •  Building architecture

2. Intui7on, Context, and Mo7va7on

2.1 Developing an Intui]on about SoMware Architecture

•  Compu]ng hardware architecture •  Network architecture •  Building architecture

2. Intui7on, Context, and Mo7va7on

Mul]ple views; Architectural styles; Style and engineering; Style and materials

2. Model of So#ware Architecture

•  SoMware Architecture = { Elements, Form, Ra]onale} – Elements: •  processing elements; •  data elements; •  connec]ng elements.


•  Example 1:

Croa7a Downs Italy For Men's Water Polo Gold

Processing elements

Data element

Connec]ng element


•  Example 2:

Soccer -‐ Euro 2012 Italy – Germany

Processing elements

Data element

Connec]ng element

5. Some Benefits Derived from So#ware Architecture

•  SA and Analysis –  Consistency and Dependency Analysis

•  Consistency of architectural styles •  Consistency of architectural constraints •  …. •  Establishment of dependencies between SA and design, SA and requirements

•  Implica]on of changes on SA on design and requirements and vice versa

–  SA and reuse •  Reusing SA components (in contracts to executable components)

Present

•  SoMware Architecture = { Elements, Form, Ra]onale}

ADLs UML …..

Research Academia Theory

Prac]ce

Methods, Processes (ATAM,…)

Ra7onale Non-‐func]onal proper]es à Quality aiributes

Present à Future – some ques7ons •  Buschmann, Frank; Ameller, David ; Ayala, Claudia P. ; Cabot, Jordi ; Franch, Xavier: Architecture Quality Revisited, SoMware, IEEE, July-‐Aug. 2012

•  “nonfunc]onal quality is of liile relevance for users and customers, but instead mainly a concern for architects.”

Present à Future – some ques7ons •  Buschmann, Frank; Ameller, David ; Ayala, Claudia P. ; Cabot, Jordi ; Franch, Xavier: Architecture Quality Revisited, SoMware, IEEE, July-‐Aug. 2012

•  “nonfunc]onal quality is of liile relevance for users and customers, but instead mainly a concern for architects.”

Has SoMware Architecture became less interes]ng and less important since there already exists many solu]ons Is it just a ques]on to (re)use them?

Present à Future – some ques7ons •  SA – What does it mean? – SoMware Architecture or System Architecture?

CodeSoftware components

Time: ... EFPsMemory: ...Energy: ...Allocation

mapping

SensorsVisualiza-tion and

actuators

N x CPU

FPG

A3D-sensor

Vision

Sonar actuatorsM x GPUFSonar

...

Example: Underwater robot

Other examples: Systems of Systems SoMware-‐intensive systems, Social systems,….

Present à Future – some ques7ons •  SA – What does it mean? – SoMware Architecture or System Architecture? •  Diversity of Hardware •  Tight integra]on of SoMware and Hardware (SW is controlling HW) •  Changes – system concerns, not soMware concerns

Present à Future, Challenges •  SA – From sta]c SA to dynamic SA – From Design Models to Run-‐]me models

– From upgrading/upda]ng ( S(n)-‐> S(n+1) ) to con]nuous change ( S(x) = f(x)dx )

– From structure to control

Present à Future, Challenges •  SA – From sta]c to adap]ve and resilient systems – From isolated to eco systems

16

dependable (robust&resistent) systems”

states

“Resilient systems”

Well define system boundaries System analysis

Undefined boundaries “Panarchical” system analysis

Present –> Futureà Future, challenges

*) Susan Stepney, Unconven]onal Computer Programming

/architecture

Future of SoMware Architecture

SA ??

Future of SoMware Architecture

sa past-future

Education