(Please do not copy and paste from another question. Please keep it simple, I am new to this)

(Examples)

Problems and Exercises 1. After reading the following narrative, do the following: i. Develop an activity diagram for each scenario. ii. Complete a fully developed use case descrip- tion for each scenario. Quality Building Supply has two kinds of custo- mers: contractors and the general public. Sales to each are slightly different. A contractor buys materials by taking them to the checkout desk for contractors. The clerk enters the contractor's name into the system. The system displays the contractor's information, including current credit standing. The clerk then opens up a new ticket (sale) for the contractor. Next, the clerk scans in each item to be purchased. The system finds the price of the item and adds the item to the ticket. At the end of the purchase, the clerk indi- cates the end of the sale. The system compares the total amount against the contractor's current credit limit and, if it is acceptable, finalizes the sale. The system creates an electronic ticket for the items, and the contractor's credit limit is reduced by the amount of the sale. Some contractors like to keep a record of their purchases, so they request that ticket details be printed. Others aren't interested in a printout. A sale to the general public is simply entered into the cash register, and a paper ticket is printed as the items are identified. Payment can be by cash, check, or credit card. The clerk must enter the type of payment to ensure that the cash register balances at the end of the shift. For credit card payments, the system prints a credit card voucher that the customer must sign. FIGURE 5-2 Fully developed use case description for Create customer account Use case name: Scenario: Triggering event: Brief description: Actors: Related use cases: Stakeholders: Preconditions: Create customer account. Create online customer account New customer wants to set up account online Online customer creates customer account by entering basic information and then following up with one or more addresses and a credit or debit card. Customer. Might be invoked by the Check out shopping cart use case. Accounting, Marketing, Sales. Customer account subsystem must be available. Credit/debit authorization services must be available. Customer must be created and saved. One or more Addresses must be created and saved. Credit/debit card information must be validated. Account must be created and saved. Address and Account must be associated with Customer. Postconditions: Flow of activities: Actor System 1. Customer indicates desire to create customer account and enters basic customer information. 1.1 System creates a new customer. 1.2 System prompts for customer addresses. 2. Customer enters one or more addresses 2.1 System creates addresses. 2.2 System prompts for credit/debit card. 3. Customer enters credit/debit card 3.1 System creates account. information 3.2 System verifies authorization for credit/debit card. 3.3 System associates customer, address, and account. 3.4 System returns valid customer account details. 1.1 Basic customer data are incomplete. 2.1 The address isn't valid. 3.2 Credit/debit information isn't valid. Exception conditions: FIGURE 5-3 Fully developed use case description for Ship items Use case name: Scenario: Triggering event: Brief description: Actors: Related use cases Stakeholders: Preconditions: Ship items. Ship items for a new sale. Shipping is notified of a new sale to be shipped. Shipping retrieves sale details, finds each item and records it is shipped, records which items are not available, and sends shipment. Shipping clerk. None. Sales, Marketing. Shipping, warehouse manager Customer and address must exist. Sale must exist Sale items must exist. Postconditions: Shipment is created and associated with shipper. Shipped sale items are updated as shipped and associated with the shipment. Unshipped items are marked as on back order. Shipping label is verified and produced. Flow of activities: Actor System 1. Shipping requests sale and sale item information 1.1 System looks up sale and returns customer, address, sale, and sales item information. 2. Shipping assigns shipper. 2.1 System creates shipment and associates it with the shipper. 3. For each available item, shipping records item is shipped. 3.1 System updates sale item as shipped and associates it with shipment. 4. For each unavailable item, shipping records back order. 14.1 System updates sale item as on back order. Exception conditions: 5. Shipping requests shipping label 5.1 System produces shipping label supplying package size and for shipment. weight. 5.2 System records shipment cost. 2.1 Shipper is not available to that location, so select another. 3.1 If order item is damaged, get new item and updated item quantity 3.1 If item bar code isn't scanning, shipping must enter bar code manually. 5.1 If printing label isn't printing correctly, the label must be addressed manually. FIGURE 2-16 Activity diagram showing concurrent paths Salesperson Engineering Purchasing Production Scheduling Accept order Order Make specifications Buy materials Program computer Schedule production FIGURE 5-4 Activity diagram for Create customer account showing alternate way to model the flow of activities Customer System Request account Create customer Enter addresses Create addresses 000 0 0 0-0-0- Enter credit info Create account Verify credit info Return account details FIGURE 5-5 Activity diagram for Fill shopping cart showing richer user experience Customer System Search for product Look at product reviews Select options and quantity Search and view accessories Add to cart Select accessory options and quantity Add to cart Problems and Exercises 1. After reading the following narrative, do the following: i. Develop an activity diagram for each scenario. ii. Complete a fully developed use case descrip- tion for each scenario. Quality Building Supply has two kinds of custo- mers: contractors and the general public. Sales to each are slightly different. A contractor buys materials by taking them to the checkout desk for contractors. The clerk enters the contractor's name into the system. The system displays the contractor's information, including current credit standing. The clerk then opens up a new ticket (sale) for the contractor. Next, the clerk scans in each item to be purchased. The system finds the price of the item and adds the item to the ticket. At the end of the purchase, the clerk indi- cates the end of the sale. The system compares the total amount against the contractor's current credit limit and, if it is acceptable, finalizes the sale. The system creates an electronic ticket for the items, and the contractor's credit limit is reduced by the amount of the sale. Some contractors like to keep a record of their purchases, so they request that ticket details be printed. Others aren't interested in a printout. A sale to the general public is simply entered into the cash register, and a paper ticket is printed as the items are identified. Payment can be by cash, check, or credit card. The clerk must enter the type of payment to ensure that the cash register balances at the end of the shift. For credit card payments, the system prints a credit card voucher that the customer must sign. FIGURE 5-2 Fully developed use case description for Create customer account Use case name: Scenario: Triggering event: Brief description: Actors: Related use cases: Stakeholders: Preconditions: Create customer account. Create online customer account New customer wants to set up account online Online customer creates customer account by entering basic information and then following up with one or more addresses and a credit or debit card. Customer. Might be invoked by the Check out shopping cart use case. Accounting, Marketing, Sales. Customer account subsystem must be available. Credit/debit authorization services must be available. Customer must be created and saved. One or more Addresses must be created and saved. Credit/debit card information must be validated. Account must be created and saved. Address and Account must be associated with Customer. Postconditions: Flow of activities: Actor System 1. Customer indicates desire to create customer account and enters basic customer information. 1.1 System creates a new customer. 1.2 System prompts for customer addresses. 2. Customer enters one or more addresses 2.1 System creates addresses. 2.2 System prompts for credit/debit card. 3. Customer enters credit/debit card 3.1 System creates account. information 3.2 System verifies authorization for credit/debit card. 3.3 System associates customer, address, and account. 3.4 System returns valid customer account details. 1.1 Basic customer data are incomplete. 2.1 The address isn't valid. 3.2 Credit/debit information isn't valid. Exception conditions: FIGURE 5-3 Fully developed use case description for Ship items Use case name: Scenario: Triggering event: Brief description: Actors: Related use cases Stakeholders: Preconditions: Ship items. Ship items for a new sale. Shipping is notified of a new sale to be shipped. Shipping retrieves sale details, finds each item and records it is shipped, records which items are not available, and sends shipment. Shipping clerk. None. Sales, Marketing. Shipping, warehouse manager Customer and address must exist. Sale must exist Sale items must exist. Postconditions: Shipment is created and associated with shipper. Shipped sale items are updated as shipped and associated with the shipment. Unshipped items are marked as on back order. Shipping label is verified and produced. Flow of activities: Actor System 1. Shipping requests sale and sale item information 1.1 System looks up sale and returns customer, address, sale, and sales item information. 2. Shipping assigns shipper. 2.1 System creates shipment and associates it with the shipper. 3. For each available item, shipping records item is shipped. 3.1 System updates sale item as shipped and associates it with shipment. 4. For each unavailable item, shipping records back order. 14.1 System updates sale item as on back order. Exception conditions: 5. Shipping requests shipping label 5.1 System produces shipping label supplying package size and for shipment. weight. 5.2 System records shipment cost. 2.1 Shipper is not available to that location, so select another. 3.1 If order item is damaged, get new item and updated item quantity 3.1 If item bar code isn't scanning, shipping must enter bar code manually. 5.1 If printing label isn't printing correctly, the label must be addressed manually. FIGURE 2-16 Activity diagram showing concurrent paths Salesperson Engineering Purchasing Production Scheduling Accept order Order Make specifications Buy materials Program computer Schedule production FIGURE 5-4 Activity diagram for Create customer account showing alternate way to model the flow of activities Customer System Request account Create customer Enter addresses Create addresses 000 0 0 0-0-0- Enter credit info Create account Verify credit info Return account details FIGURE 5-5 Activity diagram for Fill shopping cart showing richer user experience Customer System Search for product Look at product reviews Select options and quantity Search and view accessories Add to cart Select accessory options and quantity Add to cart