1. Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 223 Applied Software Design Techniques Lecture 7 Duplication of course material for any commercial purpose without the explicit written permission of the professor is prohibited.

2. Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 2 Today Expert practices Recap of first design exercise Naming The papers Onward Second design exercise

3. Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 3 Experts keep going Experts design all the time Experts know the design is not done until the code is delivered and running Experts keep learning Experts play

4. Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 4 Recap of first design exercise How did it go? How did the design behaviors play out? Did the design behaviors help or hinder the design process? Did the design behaviors help or hinder the design?

5. Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 5 Naming Tell us about naming itself – what do we see? Tell us about the process of findings naming Tell us about the value of naming

6. Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 6 The papers

7. Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 7 Onward Identify whether and how APIs a role in your system, and bring a printed copy documenting your findings to class next week Be prepared to talk about your findings Be prepared to talk about the process of identifying your findings Be prepared to talk about the value of your findings

8. Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 8 Onward Read all of the papers listed on the web site for June 4 Prepare two questions, observations, or assertions about the papers and their overall content (printed, with name and student id)

9. Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 9 Second design exercise – structure In a team of 4-5, spend two sessions of 1½ to 2½ hours each designing at the whiteboard Individually, prepare a worked out design document that uses as the starting point the design work at the whiteboard Be mindful of the expert practices Videotape your sessions

10. Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 10 Second design exercise – prompt Design PricePredictor, an app that: – allows users to track and predict prices of items of interest in online stores such as Amazon.com or Overstock.com PricePredictor is primarily meant to be used by individuals PricePredictor is meant to be created according to the ‘release early, release often’ methodology, with major upgrades planned each half year

11. Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 11 Second design exercise – deliverables Produce a document detailing your individual design as refined from the design that exists at the end of the second session – what are the design decisions – what are the first three increments after the first release, and how does the design accommodate these increments – continue designing after the two sessions are done Document, with seven short video snippets, when and how you exhibited certain expert practices while you worked at the whiteboard – DVD or memory stick (to be returned) – a document that indexes/explains the snippets

12. Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 12 Second design exercise – due date June 11, at the beginning of class, 08:00am Note: DBH 1200

13. Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 13 Second design exercise – grading Design product – innovativeness of functionality – implementability – understandability – evolvability Design process – expert practices