BIS 261 DeVry All Week iLab

example, the noun, zip code might appear in your use case description, but the zip code is an attribute of the
Customer class and does not need a class of its own.
4. For each noun on the list, ask whether it is a synonym of another noun that also appears on the list. Only one
class should be used to represent a person, place, thing, or event, even if it is sometimes referred to by
different words. For example, you might have used the words customer and client in your use case description.
If these both refer to the same person, then only one class named Customer should be used to represent both
items.
STEP 5: Draw class diagram
.equella.ecollege.com/file/5e651ec8-89f7-44f0-95d4-d1b272ff2a8b/1/BIS261_W6_iLab.html#top">Back to Top
Based on your final list of classes from Step 4, draw a domain model class diagram showing the classes involved in
the Rent a Game use case. Your diagram should include at least five classes, at least two attributes for each class,
and class relationships with multiplicities. To create this diagram:
1. If necessary, log in to the Citrix iLab, open the Microsoft Applications folder, launch Microsoft Visio, and open
the LastName_W6_iLab.vsd file that you created in Step 2;
2. Right-click on the sheet tab labeled Use Case-1 at the bottom of the window, and select Insert Page, as
shown:
.equella.ecollege.com/file/5e651ec8-89f7-44f0-95d4-d1b272ff2a8b/1/images--w6_ilab_08.gif">
1. In the Page Setup dialog, enter Class Diagram-2 in the Name box as shown:
.equella.ecollege.com/file/5e651ec8-89f7-44f0-95d4-d1b272ff2a8b/1/images--w6_ilab_09.gif">
Click OK to close the dialog.
1. Using the drop-down list in the toolbar, set the zoom level to 100%.
2. In the Shapes toolbox, click the UML Static Structure heading to expand it.
3. For each class that you identified in Step 4, drag a class symbol from the Shapes toolbox onto the diagram.
After dropping each class onto the diagram, while the class is still selected, type the name of the class. The
class name should appear in the top third of the class symbol. Click outside of the class shape to deselect it.
4. Right-click on each class and select Properties. In the UML Class Properties dialog, under Categories on the
left, select Attributes. In the Attributes grid on the right, click in the first blank cell in the Attribute column, enter
the name of an attribute, and press Enter. You should enter at least two attributes for each
class..equella.ecollege.com/file/5e651ec8-89f7-44f0-95d4-d1b272ff2a8b/1/images--w6_ilab_10.gif">
Click OK to close the dialog after entering your attributes. You should see the attributes displayed in the middle third of
the class symbol, as shown: .equella.ecollege.com/file/5e651ec8-89f7-44f0-95d4-d1b272ff2a8b/1/images--
w6_ilab_11.gif">
1. For each relationship between two classes, drag a binary association line from the Shapes toolbox onto the
diagram. Connect the endpoints of the binary association line to the related classes in the same way that you
connected the endpoints of the Communicates lines to actors and use cases in Step 2.
2. To remove the end labels from the binary association lines, right-click on the binary association line and select
Shape Display Options. In the UML Shape Display Options dialog, under End options, uncheck the boxes for
First end name and Second end name. Ensure that the box for End multiplicities is checked. Near the bottom
of the dialog, check the box for Apply to subsequently dropped UML shapes . . . Click OK.
.equella.ecollege.com/file/5e651ec8-89f7-44f0-95d4-d1b272ff2a8b/1/images--w6_ilab_12.gif">
1. To designate multiplicities for each relationship, right-click on the binary association line and select Properties.
In the UML Association Properties dialog, select Association under Categories on the left. In the Association
Ends grid on the right, click on each cell in the Multiplicity column and use the drop-down list to select the
desired multiplicity, as shown: .equella.ecollege.com/file/5e651ec8-89f7-44f0-95d4-d1b272ff2a8b/1/images--
w6_ilab_13.gif">