BIS 261 DeVry Week 6 iLab Latest

More documents

Recommendations

Info

TIP: Review the video tutorial Creating a Use Case Diagram in Microsoft Visio in the Week 6 Lecture for additional help with creating your use case diagram. STEP 3: Write a use case description .equella.ecollege.com/file/5e651ec8-89f7-44f0-95d4-d1b272ff2a8b/1/BIS261_W6_iLab.html#top">Back to Top Write a fully developed use case description for the Rent a Game use case, as follows: 1. Download and open the BIS261_W6_iLab_Template.docx file from the iLab Files folder in Doc Sharing; 2. Enter your name after Created by. Enter the current date after Date; 3. Note that the use case name, Rent a Game, has been filled in for you in the template; 4. In the Scenario section, enter a one-sentence overview of what happens in this use case. This should be slightly more detailed and specific than the use case name; 5. In the Triggering Event section, briefly describe what happens to initiate this use case; 6. In the Brief Description section, summarize the steps that take place when this use case is performed. This should be more detailed than your one-sentence overview in the Scenario section, but not as detailed as the Flow of Events; 7. In the Actors section, list the actors that take part in this use case. These are the actors that are connected to this use case by the Communicates lines in your use case diagram; 8. In the Related Use Cases section, list other use cases, if any, that are connected to this one in the use case diagram. These include use cases that use this one, and use cases that are used by this one. If there are none, enter none; 9. In the Stakeholders section, identify any parties with an interest in the outcome of this use case, other than the actors who directly participate in the use case. These might be, for example, other departments within the company that utilize data generated by this use case. If there are none, enter none; 10. In the Preconditions section, describe the state of the system before the use case is performed; 11. In the Post conditions section, describe the state of the system after the use case has been performed; 12. In the Flow of Events section, list the specific steps involved in performing the normal or usual flow of events in the use case. Assign a sequential number (1, 2, 3, and so on) to each step. List steps performed by an actor in the Actor column, and steps performed by the system in the System column; 13. In the Exception Conditions section, identify any errors or other unusual conditions that might occur while performing the use case, and describe what should happen if each one occurs. For each exception condition, identify the step number in the Flow of Events at which the exception condition might occur; and 14. Save the completed use case description with the file name LastName_W6_iLab.docx. STEP 4: Identify classes .equella.ecollege.com/file/5e651ec8-89f7-44f0-95d4-d1b272ff2a8b/1/BIS261_W6_iLab.html#top">Back to Top Analyze your use case description to identify the major classes that would be involved in implementing the Rent a Game use case. Remember that classes are indicated by important nouns in the use case description that represent persons, places, things, or events that the system must track or manipulate when performing the use case. To identify classes, do the following: 1. Carefully read the Rent a Game use case description that you created in Step 3, and as you do so, make a list of the important nouns representing persons, places, things, or events that appear in the description. 2. For each noun on your list, ask yourself whether the system needs to store information about or manipulate that person, place, thing, or event in order to perform the use case. For example, the noun button might appear in your use case description, but the system does not need to store information about the button, so you would not need to include a Button class in your list. 3. For each noun on the list, ask yourself whether the noun represents an independent person, place, thing, or event needing its own class, or whether it may be an attribute of another person, place, thing, or event. For 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"> After setting the multiplicity for each end, click OK to close the dialog. The following shows a partially completed class diagram with two classes, two attributes for each class, and a binary association between the classes with appropriate multiplicities. Your completed class diagram should include at least five classes, with at least two attributes per class and all necessary association lines and multiplicities. .equella.ecollege.com/file/5e651ec8-89f7-44f0-95d4-d1b272ff2a8b/1/images--w6_ilab_14.gif">
Page 1 and 2: BIS 261 DeVry Week 6 I Lab Latest D
Page 3: 5. In the Shapes toolbox, click the

BIS 261 DeVry Week 6 iLab Latest

Create successful ePaper yourself

Delete template?

Save as template?