1 / 23

Design Recovery II

Design Recovery II. Informatics 122 Alex Baker. Cake Recovery – Opinions?. How difficult was this? Why?. 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.

jsokolowski
Télécharger la présentation

Design Recovery II

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

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. Domain of Use Knowledge Design Recovery in Diamond • Ideas from your documents • Connection to the designers’ ideas Dom Materials Representation Ideas Activity concern manipulates informs captures enhances Goal

  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 3rd 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

More Related