Software architecture evaluation – methods, experiences, issues

More documents

Recommendations

Info

Problem: Feeding the beast 14 <strong>Software</strong> Architecture Course, Turku , November 2013 Department of Pervasive Computing
Problem: Information bloat 15 Falessi et al. (TOSEM, to appear): only half of design rationale information in full documentation is probably needed <strong>Software</strong> Architecture Course, Turku , November 2013 Department of Pervasive Computing
Page 1 and 2: 1 Software architecture evaluation
Page 3 and 4: Background 3 Two nationally funded
Page 5 and 6: Scenario-based approach: use scenar
Page 7 and 8: Evaluation reports: second format 7
Page 9 and 10: Exploiting SA evaluation for inform
Page 11 and 12: Pattern language for machine contro
Page 13: Frustrating experience … 13 • I
Page 17 and 18: Lean AKM Manifesto 17 1. The produc
Page 19 and 20: Towards invisible AKM 19 Activities
Page 21 and 22: Example 21 Architectural decisions
Page 23 and 24: Shortcomings in ATAM based AK 23
Page 25 and 26: Possible approach for SA informatic
Page 27 and 28: 27 Example: Process-based slicing A
Page 29 and 30: 29 Example: Role-based slicing A ma
Page 31 and 32: Example: maintenance scenario docum
Page 33 and 34: Trustworthiness problem 33 • Scen
Page 35 and 36: DCAR: decision-based architecture e
Page 37 and 38: DCAR process 37 Identify forces tha
Page 39 and 40: DCAR is … 39 • Lightweight: doe
Page 41 and 42: Thanks! 41 Software Architecture Co

Software architecture evaluation – methods, experiences, issues

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?