Sa past-future

241 views
193 views

Published on

ECSA - WICSA 2012 Conference
Panel
Software Architecture: Past, Present, and Future Directions

Published in: Education, News & Politics
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
241
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Sa past-future

  1. 1. WICSA/ECSA  2012,  Helsinki     So#ware  Architecture:  Past,  Present,  and  Future  Direc7ons   Ivica  Crnkovic   Mälardalen  University,  Sweden   www.idt.mdh.se/~icc      
  2. 2. 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  
  3. 3. 2.  Intui7on,  Context,  and  Mo7va7on  2.1  Developing  an  Intui]on  about  SoMware                Architecture  •  Compu]ng  hardware  architecture  •  Network  architecture  •  Building  architecture    
  4. 4. 2.  Intui7on,  Context,  and  Mo7va7on  2.1  Developing  an  Intui]on  about  SoMware                Architecture  •  Compu]ng  hardware  architecture  •  Network  architecture  •  Building  architecture     Mul]ple  views;   Architectural  styles;   Style  and  engineering;   Style  and  materials  
  5. 5. 2.  Intui7on,  Context,  and  Mo7va7on  2.1  Developing  an  Intui]on  about  SoMware                Architecture  •  Compu]ng  hardware  architecture  •  Network  architecture  •  Building  architecture     Mul]ple  views;   Architectural  styles;   Style  and  engineering;   Style  and  materials  
  6. 6. 2.  Model  of  So#ware  Architecture  •  SoMware  Architecture  =  {  Elements,  Form,   Ra]onale}   –  Elements:   •  processing  elements;   •  data  elements;   •  connec]ng  elements.  
  7. 7. 2.  Model  of  So#ware  Architecture   Data  •  Example  1:   element   Processing   elements   Connec]ng   element   Croa7a  Downs  Italy  For  Mens  Water  Polo  Gold  
  8. 8. 2.  Model  of  So#ware  Architecture   Processing   elements  •  Example  2:   Data   element   Connec]ng   Soccer  -­‐  Euro  2012  Italy  –  Germany     element  
  9. 9. 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)  
  10. 10. Present  •  SoMware  Architecture      =  {  Elements,  Form,  Ra]onale}   Research   Academia   Theory   Prac]ce   ADLs   Methods,  Processes     UML   (ATAM,…)   …..   Ra7onale    Non-­‐func]onal  proper]es    à  Quality  aiributes  
  11. 11. 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.”    
  12. 12. 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?  
  13. 13. Present  à  Future  –  some  ques7ons   •  SA  –  What  does  it  mean?   –  SoMware  Architecture  or  System  Architecture?   Software components CodeExample:  Underwater  robot   Time: ... EFPs Memory: ... Allocation Energy: ... mapping Vision N x CPU Visualiza- FPGA 3D-sensor Sensors tion and Sonar actuators F M x GPU ... Other  examples:    Systems  of  Systems    SoMware-­‐intensive  systems,  Social  systems,….  
  14. 14. 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  
  15. 15. 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    
  16. 16. Present  à  Future,  Challenges  •  SA       –  From  sta]c  to  adap]ve  and  resilient  systems   –  From  isolated  to  eco  systems   dependable  (robust&resistent)  systems”   “Resilient  systems”   Well  define  system  boundaries   Undefined  boundaries   states   System  analysis     “Panarchical”  system  analysis     16  
  17. 17. Present  –>  Futureà  Future,   challenges   /architecture  *)  Susan  Stepney,  Unconven]onal  Computer  Programming  
  18. 18. Present  –>  Futureà  Future,   challenges   /architecture  *)  Susan  Stepney,  Unconven]onal  Computer  Programming  
  19. 19. Future  of  SoMware  Architecture   SA   ??  
  20. 20. Future  of  SoMware  Architecture  

×