Presentation is loading. Please wait.

Presentation is loading. Please wait.

Design Recovery II Informatics 122 Alex Baker. Cake Recovery – Opinions? How difficult was this? Why?

Similar presentations


Presentation on theme: "Design Recovery II Informatics 122 Alex Baker. Cake Recovery – Opinions? How difficult was this? Why?"— Presentation transcript:

1 Design Recovery II Informatics 122 Alex Baker

2 Cake Recovery – Opinions? How difficult was this? Why?

3 Cake Recovery – Opinions? How difficult was this? Why? What would have helped more:  Access to BnA/Archstudio design docs  Access to running code  Another 5 days of time

4 Cake Recovery – Opinions? How difficult was this? Why? What would have helped more:  Access to BnA/Archstudio design docs  Access to running code  Another 5 days of time Rather have done something Jetris-like?

5 As bad as it looked? Better or worse?

6 Our Perspective: Cons:  Can’t use the strategies I mentioned  Don’t learn to use reverse engineering tools  Hard work, might obscure obvious lessons  Distracting

7 Our Perspective: Cons:  Can’t use the strategies I mentioned  Don’t learn to use reverse engineering tools  Hard work, might obscure obvious lessons  Distracting Pros:  Forces focus on code  More interesting comparisons  More involved experience  Realistic?

8 Design Recovery in Diamond Goal Dom Materials Representation Domain of Use Knowledge ActivityIdeas concern manipulates informs captures enhances Ideas from your documents Connection to the designers’ ideas

9 Your Designs How well do you understand Cake? What was your process? Ideas  How did you find out?  Was this a good idea for the designers?

10 Representations Best approach?  Precision versus elegance  Multiple diagrams

11 Success? How well do you understand it now? How prepared would you be to implement changes?  Add a new kind of thing?  Make the boxes semi-transparent?  Add double-click behavior?

12 Cake Screenshots

13 The Nature of Software Invisibility  Understanding 3 rd party’s towers Complexity  If users want a program to do 30 different things, then the program must do those 30 different things  Elegance? Conformity Changeability [Brooks: No Silver Bullet]

14 Is this a good design? Was it easy to understand? Would it have been easy to implement? Can it be expanded?

15 Is this a good design? Was it easy to understand? Would it have been easy to implement? Can it be expanded? What would you change?

16 What was the effect of using BnA? Positive

17 What was the effect of using BnA? Positive Negative

18 What was the effect of using BnA? Positive Negative The weight of (re)use

19 Cake Recovery – Useful?

20 Midterm Review Good design / bad design  Theseus and the Minotaur Design patterns Design recovery

21 Possible Midterm Contents Design improvement exercise  Design principles  Patterns Recovery principles  Specific question about Cake (?)

22 Mid-Course Checkup Lost?  Critique?  Create? How do you design software? Implementation?

23 Returning Assignment 2


Download ppt "Design Recovery II Informatics 122 Alex Baker. Cake Recovery – Opinions? How difficult was this? Why?"

Similar presentations


Ads by Google