1. Project Catalogue

2. DAIMIHenrik Bærbak Christensen2 building stuff Problem: –task X is slow/cumbersome/prone to errors in your organization Hypothesis: –using tool T users will experience a [50% speedup / 50% lower effort / 30% less errors] in doing task X Process: –build (parts of) tool X document tool X record open issues Experiment –group of users try tool T, recording time spent/errors...

3. DAIMIHenrik Bærbak Christensen3 building stuff Problem: –product X is slow/faulty/insecure/unmodifiable/... Hypothesis: –having architecture A/applying tactics T1, T2, T3 instead would increase speed/failure rate/security/modifiability by [some measure] Process: –build architectural prototype of product X –refactor X Experiment –Measure QAs before and after...

4. DAIMIHenrik Bærbak Christensen4 building stuff Problem: –product X can be abstracted into framework covering product X, Y, Z Hypothesis: –hotspots A B C using product line techniques will provide sufficient flexiblity for 80% code reuse Process: –refactor X Experiment –Measure code reuse

5. DAIMIHenrik Bærbak Christensen5 building stuff Problem: –we have identified an architectural mismatch problem in product X Hypothesis –mismatch can be solved using technique T Process: –list and evaluate a number of techniques for resolving the mismatch –apply T or apply T1, T2, T3 Experiment –record open issues, document experiment

6. DAIMIHenrik Bærbak Christensen6 applying technique Problem: –our organization may benefit from technique X –we question validity of technique X Hypothesis –by applying X a lower defect ratio / lower cost / better understanding will be achieved Process/experiment –apply X, record experience and open issues Potential Xs: –ATAM, QAWs, Doc through views, QA scenarios, architectural prototyping

7. DAIMIHenrik Bærbak Christensen7 using tools Problem –product X has unknown architecture Hypothesis –using tools Y / technique Z an architecture can be extracted Process : –use Y/Z on X. Document architecture; record open issues Experiment: –report findings of process

8. DAIMIHenrik Bærbak Christensen8 Summary Diploma in software construction: Thus software construction objects important: –construct software, relating to theory, techniques insight in applicability of the theory and techniques –analyze software using known techniques / tools evaluation applicability of the theory and techniques

9. Software Architecture Area Overview

10. DAIMIHenrik Bærbak Christensen10 The course topic framework Architecture Documentation Architecture Construction Techniques Architecture Evaluation Product Lines Architectural Mismatch / COTS / Reuse Architecture Reconstruction

11. DAIMIHenrik Bærbak Christensen11 Project Brainstorming 1. Brainstorming –brainstorm a lot of potential projects 2. Prioritization –Potential: Not too big nor small –Interest: Can you work on it for 5 month? 3. Elaboration [on 3-5 likely candidates] –Idea  Topic  Problem  Hypothesis –Expected results: Hypothesis, open issues... –Expected process: How to tackle, project plan