1. © 2010 University of California, Irvine – André van der Hoek1July 14, 2015 – 14:37:42 Informatics 122 Software Design II Lecture 4 Nick Lopez Duplication of course material for any commercial purpose without the explicit written permission of the professor is prohibited.

2. © 2010 University of California, Irvine – André van der Hoek2July 14, 2015 – 14:37:42 Today’s Lecture Reflection Assignment 2

3. © 2010 University of California, Irvine – André van der Hoek3July 14, 2015 – 14:37:42 Some Caveats We are going to be showing, praising, and critiquing your designs –not to ridicule, rather to provide constructive feedback This is a normal part of any design studio class Rules of the game –do not identify someone, even if you know whose design it is –someone may choose to volunteer and explain their design, but they may also choose not to do so We only highlight parts of certain designs, so please do not correlate our comments here with your final grade for this assignment We only do this based on the UML diagram, not the text

4. Some example Designs © 2007 University of California, Irvine – André van der Hoek4July 14, 2015 – 14:37:42

5. © 2010 University of California, Irvine – André van der Hoek5July 14, 2015 – 14:37:42 Assignment 2 – Implementation You are to implement someone else’s design, namely the design that you ranked first In making this implementation, you have two goals –you must hand in a fully working NumberTrains game adhering to all of the rules of NumberTrains –adhere to the chosen design as much as possible Make sure you still have the designs you evaluated, otherwise ask for them now Due: Wednesday, January 26 th, beginning of class

6. © 2010 University of California, Irvine – André van der Hoek6July 14, 2015 – 14:37:42 Assignment 2 – Deliverables Working code (both source and a JAR file) Brief instructions on how to run the JAR file Brief instructions on how to provide input to the game A revised UML document describing the design underlying the code –i.e., the design you eventually implemented A document describing any and all changes you had to make to the original design with a motivation as to why –why you made these changes –why these changes could not be avoided

7. © 2010 University of California, Irvine – André van der Hoek7July 14, 2015 – 14:37:42 Assignment 2 – Grading Completeness –working code covering all of the rules of BeNumbered Adherence to the original design Motivation for modifications to the original design