Com S 362 --- Object-Oriented Analysis and Design

		   EXERCISE 13: BASIC OO DESIGN (2)
                 (File $Date: 2004/09/03 14:07:23 $)

The purpose of this exercise is for you to get some experience with
basic OO design.

As with all exercises, this is to be done individually, not in teams.
However, if your team has already done this, you can hand in one
diagram for the entire team; just be sure to indicate everyone's name.
And it is due the day this topic is planned to be discussed in class, unless
specified otherwise (see the syllabus at:
http://www.cs.iastate.edu/~cs362/syllabus.shtml). 

As with all exercises, you have two choices for doing the work. You
can either:

  - complete it as specified or
  - write down questions or problems that you had in trying to
    complete it.

If you write down questions or problems you have, these should be
detailed enough so that we can tell that you have read the materials
and thought about them.  (Don't just write: "I couldn't get it to
work; say what you tried and what you didn't understand.)  During the
class where this exercise is discussed, you should try to get help
with these by explaining what you did and what your problems or
confusions are.  Don't be shy; there will be other people with the
same problem, and everyone can learn by discussing these issues.

1. [Design Class Diagram for Team Project]

Read chapter 19 of Craig Larman's book Applying UML and Patterns
(second edition, Prentice Hall PTR, Upper Saddle River, NJ, 2002).
Also, for more examples look at the web page for the StickSync project:

  http://www.cs.iastate.edu/~cs362/sticksync/design-model.shtml

Draw a design class diagram for your project that encompasses the
scenarios that you plan to implement in the first elaboration iteration
of your project. 

We suggest that you draw the diagram by hand on paper.

WHAT TO HAND IN

You should have at the beginning of class, written answers to the
above questions (or written out questions and problems you encountered
for each part).  Make sure your name is on these. Attach the
printouts, if any, requested above.

ADDITIONAL READINGS

If you have time, read chapters 4 and 6 of Martin Fowler with Kendall
Scott's book UML Distilled (Addison-Wesley Longman, Inc., Reading, MA, 2000).