Lab 03 - Use Case Diagrams & Use Case Narratives - Student Answers

CNIT 180 Lab 3: Use Cases Diagrams & Use Case Narratives EXERCISES Complete the exercises assigned by your instructor by drawing the assigned models. Save each diagram. Copy and paste each diagram into Lab 03 – Use Case Diagrams & Use Case Narratives – Student Answers. Save that document to your home directory. Close that document. Attach Lab 03 – Use Case Diagrams & Use Case Narratives – Student Answers to the Lab 03 Assignment in Brightspace and submit. 1. Using the context model diagram KEY from Lab 2 for the Northwind Information System (#1), create a use case diagram. Answer: 2. Using the context model diagram KEY from Lab 2 for the student scheduling system (#2), create a use case diagram. Answer:

CNIT 180 Lab 3: Use Cases Diagrams & Use Case Narratives 3. Using the context model diagram KEY from Lab 2 for the Automated Teller Machine (#3), create a use case diagram. Answer: 4. Using the context model diagram KEY from Lab 2 for the RipUOFF (RUF) Banking Center Information System (#5), create a use case diagram. Answer: 5. Using the context model diagram for the Pixton Library Resource Inventory and Patron Check-Out System shown below, create a use case diagram. Using the

CNIT 180 Lab 3: Use Cases Diagrams & Use Case Narratives Use-Case Name: Access System Use Case Type Business Requirements:  System Analysis:  System Design:  Use-Case ID: Priority: High Source: Security Protocol Primary Business Actor: User Primary System Actor: User Other Participating Actors: None Other Interested Stockholders: None Description: This use case describes the security process in the event that a registered user wants to access the system. Precondition: Must be a registered user Trigger: User requests to gain access to the system Typical Course Of Events: Actor Action System Response Step 1 : User requests to login to the system Step 2 : System responds by prompting the user to supply their login credentials (user ID, password) Step 3 : User inputs ID and password Step 4 : System verifies user’s credentials with those stored in the system Step 5 : System prompts the user with one of the five security questions they have answered during the registration process Step 6 : User answers the security question Step 7 : System verifies the answer to the security question Step 9 : User receives a confirmation that they have been granted access to the system Step 8 : System grants user access to the system

CNIT 180 Lab 3: Use Cases Diagrams & Use Case Narratives Alternate Courses: Alt Step 4a : The ID and/or password are incorrect. System prompts user again for their ID and password. GO TO Step 3. Alt Step 4b : The ID and password are correct, but the password is 60 days or older. System requires user to change their password. The system would then provide a confirmation once the user’s password is reset. GO TO Step 3. Alt Step 7a : The user fails to provide the correct answer to the security question. System will prompt the user again with the same security question. GO TO Step 6. Conclusion: The user gains access to the system Postcondition: No change Business Rules: None Implementation Constraints and Specifications: The user has up to three attempts to input their ID and password before the system locks their account. This also applies to the security question. Assumptions: The person using the credentials is indeed the registered user Open Issues: None 7. Given the narrative below, prepare a use case narrative. When a patron requests the checkout of a library asset or more, they are asked by the librarian to provide account identification (membership card). If they cannot provide their membership card or some other approved identification, the transaction is terminated and the patron is notified. The librarian logs on the system and selects the option for a patron to checkout an asset. The system prompts for account identification and the librarian enters the patron’s membership number or other identifying information such as last name and first name. The system verifies the account exist (if not the user is prompted to enter a valid account number or other identification) making sure it is active, there are no outstanding fines, and their borrowing limit has not been already met (already have the maximum number of assets out on loan). If the patron could not provide their account card but provided some other form of identification, the system sets the patron’s borrowing limit to three assets instead of six. If the patron’s account is found not to be active, or they have outstanding fines, or they already the maximum numbers of assets borrowed, the system communicates this status to the user and the patron is notified of the situation and the transaction is terminated. If the account is found to be valid, the system prompts for the identification number of the first asset to be checked out. The librarian provides identification of the asset. The system verifies the asset exists (if not the user is prompted to enter a valid asset number). The system verifies the asset is one that can be checked out (if not the user is notified). The system records the checkout event, verifies that the user has not reached the maximum number of borrowed assets, and then prompts for the next asset to be checked out. The previous activity will be repeated for each asset to be checked out. When the maximum number of borrowed assets has been reached, the system notifies the user and in turn the librarian notifies the patron. Once all assets have been presented for checkout, the librarian informs the system that the checkout event is complete. The system records the remaining checkout information and a receipt is generated showing the transaction activity. The process ends once the receipt is given to the patron along with the assets being checked out. Answer: System Name

CNIT 180 Lab 3: Use Cases Diagrams & Use Case Narratives Use-Case Name: Checkout Equipment Use Case Type Business Requirements:  System Analysis:  System Design:  Use-Case ID: Priority: High Source: Requirement Primary Business Actor: Employee Primary System Actor: Employee Other Participating Actors: None Other Interested Stockholders: None Description: This use case describes the event in which an employee requests to checkout a piece of equipment. Precondition: The person checking out the equipment is an actual employee. Trigger: Employee requests to checkout a piece of equipment. Typical Course Of Events: Actor Action System Response Step 1 : Employee initiates a request to checkout a piece of equipment. Step 2 : System responds by prompting the Employee for his ID. Step 3 : Employee provides his ID. Step 4 : System confirms that the employee is authorized to check equipment. Step 5 : System checks equipment restrictions to confirm that the employee has the skill qualification. Step 6 : System checks for equipment availability Step 8 : User receives the checkout receipt and the location of equipment Step 7 : System provides the receipt for the checkout details and the location of the equipment. Alternate Courses: Alt Step 4a : System finds that employee is not authorized to handle the equipment. System terminates with an error message. Alt Step 5a : System finds that employee does not have the skillset to handle the equipment. System terminates with an error message. Alt Step 6a : System finds that the equipment the employee wants to check out is unavailable. System terminates with an out of stock message. Conclusion: Employee successfully checks out equipment. Postcondition: No change Business Rules: Employee must return equipment after they are finished using it. Implementation Constraints and Specifications: Employee must have the skill qualifications to operate their requested equipment. Assumptions: None Open Issues: None