Lab 4-2 Create an Activity Diagram

Transcription

1 Create an Activity Diagram Lab 4-2 Create an Activity Diagram Before You Begin In this lab, you ll practice creating an activity diagram that shows the workflow for a use case s basic flow. We will model an activity diagram as it relates to our use-case model, specifically to illustrate the Maintain Personal Planner use case s basic flow. Make sure you ve successfully completed Lab 4-1. Do not begin this lab until you ve discussed the appropriate information in Module 4: The Use-Case Model in the Student Manual. Objective In Lab 4-2, select one of the following options to create an activity diagram. Option 1 Look at the Maintain Personal Planner Use-Case Specification on page 4-11 to determine the activities in the basic flow. Option 2 Use the Activity Diagram on page 4-12 and follow the existing diagram to create the activity diagram in your model. Lab Outcome Completed activity diagram showing the Maintain Personal Planner use case s basic flow 4-9

2 Lab Artifacts Maintain Personal Planner Use-Case Specification Activity Diagram Lab4_1.mdl file Lab4_2.mdl file 4-10

3 Maintain Personal Planner Use-Case Specification 1. Maintain Personal Planner 1.1 Brief Description This use case allows the Prospective Buyer to set up an account that will store home search preferences, contact information, and other financial or personal information that will aid the Prospective Buyer in finding a home on the web site. 2. Flow of Events 2.1 Basic Flow This use case begins when the Prospective Buyer chooses to create a Personal Planner profile. 1. The system requests the Prospective Buyer to create a new profile if one does not already exist. If a profile does exist, the customer is given the option to log on to the system. 2. The system prompts the customer to create a new profile. Profile information includes: name, address, password, and a preference on receiving marketing news by The system creates the customer profile using the customer s address as his logon ID. When the new profile has been created, an message will be sent to the customer welcoming him to the system and providing access information and other details that can be changed on an as-needed basis. 4. The customer enters a default set of home search criteria and saves the information. 2.2 Alternative Flows Duplicate Logon ID Exists If, in the Basic Flow, the Prospective Buyer enters an address that already exists, then the system will assume that the user has already created a profile. The system will prompt the customer with a message that a profile already exists for the given address and asks if the user would like to create a new account using the existing account Prospective Buyer Forgets Password If, in the Basic Flow, the Prospective Buyer forgets his password, the system will allow him to create a new one. The system will prompt the user for his logon ID ( address), and the system will then generate a new password and send it to the Prospective Buyer s address that is used as the logon ID Invalid Format or Insufficient Information If, in the Basic Flow, the Prospective Buyer has not specified sufficient information to create the customer profile, the system will prompt the actor for the missing information. The Prospective Buyer can either enter the missing information or choose to cancel the operation, at which point the use case ends. 3. Special Requirements 4. Pre-Conditions 5. Post-Conditions 6. Extension Points 4-11

4 Activity Diagram Choose Maintain Profile Find Buyer Profile [ Profile exists ] Logon To System [ Profile does not exist ] Create New Profile 4-12

5 Task 1: Add Activity Diagram to the Browser Add the Maintain Personal Planner activity diagram under its use case in the browser. Steps 1. Make sure Lab4_1.mdl is open. Rightclick the Maintain Personal Planner use case, and then click New. 2. Click Activity Diagram and name it Basic Flow. 3. Open the new activity diagram. Comments Make sure to right-click the use case, NOT the package. After naming the diagram, click outside the name box. Task 2: Add Activities Using either the use-case specification on page 4-11 or the Activity Diagram on page 4-12, determine the activities for the use case s basic flow and add them to the diagram. Task 3: Add Start and End States Now, add your start state and end state(s) to the diagram. Hint: You can have more than one end state, but only one start state. Task 4: Add State Transitions, Decisions and Guard Conditions Try This Activity Finally, add your transitions, any decisions, and guard conditions needed for the alternate flows. Hints: For decisions, add the decision icon first, and then add the state transition. For guard condition text (text in square brackets in diagram), open the transition s Specification window, and then go to the Detail tab. To check your completed use-case model, open Lab4_2.mdl. Leave Lab4_2.mdl open. You ll use it for the next lab. If there is time, run the Show Usage report on any element in a use-case or activity diagram. Hint: Open the diagram and select a model element, and then go to the Report menu. 4-13

6 4-14