Com S 362 --- Object-Oriented Analysis and Design EXERCISE 11: DOMAIN MODELS (2) (File $Date: 2003/10/22 05:15:47 $) The purpose of this exercise is for you to understand attributes in domain modeling. As with all exercises, this is to be done individually, not in teams. 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. [Attributes in domain model] Read chapter 12 of Craig Larman's book Applying UML and Patterns (second edition, Prentice Hall PTR, Upper Saddle River, NJ, 2002). Add appropriate attributes to the domain model of Crossword Puzzle developed in Exercise 10. We suggest that you draw the domain model by hand on paper. 2. [Attribute concepts] Read chapter 12 of Craig Larman's book Applying UML and Patterns (second edition, Prentice Hall PTR, Upper Saddle River, NJ, 2002). a. Are there any connections between the attributes in domain model and the ones in implementation? b. In what situations it is better to represent the type of an attribute as a non-primitive class? c. When it is better to use associations instead of attributes? 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 chapter 4 of Martin Fowler with Kendall Scott's book UML Distilled (Addison-Wesley Longman, Inc., Reading, MA, 2000).