For this exercise, each student will create a Domain Model for a simple software system.
The Domain Model should only contain class nodes for each Domain entity and possibly entity attributes but no behaviors (aka methods). Make sure to include appropriate relationships with multiplicity indicators, and inheritance relationships (if any) that you can discern from the problem description.
Feel free to work with each other during the remainder of the class session when you start this exercise and before the next class to develop ideas and strategies. However, each individual student is responsible for submitting in the course dropbox a copy of his or her own domain model by the start of the next class. You should spend no more than 30 minutes on this exercise.
The next class session we will work with your models in three phases. In the first phase, small groups (3-4 students each) will quickly create consensus domain models that incorporate the best aspects of the individual student models. Since you will have to discuss your individual design with your team be sure to have a hard copy or a way to display the design in the team session. In the second phase, several teams will present their models to the class as a whole (a few minutes per presentation). In the final phase, we revisit the problem statement and the domain model to look for differences and commonalities across the models.
You must submit your domain model as a PDF, Word, or image file to the Domain Model dropbox by the start of the next class, or if your instructor has changed that, the time the dropbox specifies. If you are drawing your domain by hand, scan your diagram to a PDF file. If you took a snapshot of a diagram on a whiteboard, then submit the image file.