Software architecture evaluation – methods, experiences, issues

More documents

Recommendations

Info

Heavy-weightness problem 34 • Medium-sized ATAM can take up to 70 person days • ATAM assumes the presence of many stakeholders that are difficult to get available at the same time • A lot of time is used to refine requirements • Incompatible with agile approaches (e.g. Scrum) Software Architecture Course, Turku , November 2013 Department of Pervasive Computing
DCAR: decision-based architecture evaluation method 35 Design = balancing the forces associated with a design problem Forces pull the solution of the problem towards a certain direction possible decision possible decision problem possible decision forces possible decision Software 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 and 14: Frustrating experience … 13 • I
Page 15 and 16: Problem: Information bloat 15 Fales
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: Trustworthiness problem 33 • Scen
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

Create successful ePaper yourself

Delete template?

Save as template?