IT 304 Use Case Specification PDF

Preview

Summary

something...

Description

IT-304-J1754 Systems Reqmts/Implement Plan 20EW1 Use Case Specification Salome Odipo 20th September 2020

1

Use Case Specification Components Use Case Number What is the number of this use case? (#1–4) Use Case Name What is the name of this use case? Actor Who is involved in this use case? Summary Description What happens in this use case? Priority and Importance What is the importance of this use case? It’s primary if it’s a major process, secondary if it’s a minor process, optional if it may not always occur. Relationships between Use Cases Which actors does this use case interact with? Trigger What starts the use case? Pre-Condition (Methods/Operations) What happens before the use case starts? Post-Conditions (Methods/Operations) What happens after the use case? Path What is the path of the process? What is the Main Success Scenario that needs to be documented in this use case specification? (The Main Success Scenario is a single set of actions toward the goal of the use case.) If you notice variations from the Main Success Scenario, document them as Extensions or as Included Use Cases. Non-Functional Requirements What are the non-functional requirements of the use case?

Responses MHC_UC_1 Capture patient information/reason for visit Check-in receptionist A patient checks-in at the self-service kiosk and provides their information and reason for visit Primary

Check-in receptionist, Patient, Business Admin Patient arrives at Millennia Health Center Patient should have an appointment Patient information and reason for visit are captured into the system 1. Use Case: Book appointment is done 2. Patient arrives at MHC hospital 3. If the patient opts out of using the selfservice kiosk, they provide their information to the check-in receptionist 4. Check-in receptionist enters the patient details into the system as well as reason for visit 5. Use case ends successfully NF1: Security of patient information enters

Use Case Specification Components Use Case Number What is the number of this use case? (#1–4) Use Case Name What is the name of this use case? Actor Who is involved in this use case? Summary Description What happens in this use case? Priority and Importance What is the importance of this use case? It’s primary if it’s a major process, secondary if it’s a minor process, optional if it may not always occur. Relationships between Use Cases Which actors does this use case interact with? Trigger What starts the use case? Pre-Condition (Methods/Operations) What happens before the use case starts?

Post-Conditions (Methods/Operations) What happens after the use case? Path What is the path of the process? What is the Main Success Scenario that needs to be documented in this use case specification? (The Main Success Scenario is a single set of actions toward the goal of the use case.) If you notice variations from the Main Success Scenario, document them as Extensions or as Included Use Cases. Non-Functional Requirements What are the non-functional requirements of the use case?

Responses MHC_UC_2 Verify patient insurance Business Admin The patient’s medical insurance information is verified and is confirmed as current Primary

Business Admin, Patient, check-in receptionist This use case is triggered after the patient information has been entered into the system 1. The patient must have an appointment 2. The patient’s information should be in the system Have current and up to date patient insurance information which allows billing once 1. Use case: Capture patient information is done 2. Patient provides insurance details by scanning their insurance card at selfservice kiosk 3. Business admin verifies insurance information provided by the patient 4. Use case ends successfully

NF1: Security of patient insurance information

Use Case Specification Components Use Case Number What is the number of this use case? (#1–4) Use Case Name What is the name of this use case? Actor Who is involved in this use case? Summary Description What happens in this use case? Priority and Importance What is the importance of this use case? It’s primary if it’s a major process, secondary if it’s a minor process, optional if it may not always occur. Relationships between Use Cases Which actors does this use case interact with? Trigger What starts the use case? Pre-Condition (Methods/Operations) What happens before the use case starts?

Post-Conditions (Methods/Operations) What happens after the use case? Path What is the path of the process? What is the Main Success Scenario that needs to be documented in this use case specification? (The Main Success Scenario is a single set of actions toward the goal of the use case.) If you notice variations from the Main Success Scenario, document them as Extensions or as Included Use Cases. Non-Functional Requirements What are the non-functional requirements of the use case?

Responses MHC_UC_3 Capture patient copay Business Admin All copayments, if required, need to be collected from the patient when they arrive. Primary

Business Admin, Patient, Check-in receptionist Patient’s insurance information is verified 1. The patient’s insurance details have been verified 2. Patient’s information and reason for visit have been captured 1. The patient’s is able to receive medical care 1. Use case: Verify insurance is done 2. Patient makes copayment 3. Business Admin confirms copayment has been made 4. Use case ends successfully

NF1: Accuracy of the system to capture copayments correctly

Use Case Specification Components Use Case Number What is the number of this use case? (#1–4) Use Case Name What is the name of this use case? Actor Who is involved in this use case? Summary Description What happens in this use case? Priority and Importance What is the importance of this use case? It’s primary if it’s a major process, secondary if it’s a minor process, optional if it may not always occur. Relationships between Use Cases Which actors does this use case interact with? Trigger What starts the use case? Pre-Condition (Methods/Operations) What happens before the use case starts?

Post-Conditions (Methods/Operations) What happens after the use case?

Path What is the path of the process? What is the Main Success Scenario that needs to be documented in this use case specification? (The Main Success Scenario is a single set of actions toward the goal of the use case.) If you notice variations from the Main Success Scenario, document them as Extensions or as Included Use Cases. Non-Functional Requirements What are the non-functional requirements of the use case?

Responses MHC_UC_4 Schedule next appointment Patient The patient books the next appointment on when the they should receive a follow up if necessary Optional

Doctor, Patient Copayment is made by the patient 1. Patient’s insurance or payment details have been captured 2. Doctor has examined the patient and updated their medical history in the system 3. Patient has made full payment of copayment 1. Patient’s next appointment date is entered into the system 2. Patient visits the hospital on said date of appointment 1. Use case: capture patient’s copay is done 2. Patient next appointment date is captured in the system 3. Use case ends successfully

NF1: Usability of the system to allow the patient schedule next appointment

References Lynch, W. (2019, March 22). All you need to know about use case modeling. Retrieved from https://medium.com/@warren2lynch/all-you-need-to-know-about-use-case-modeling828756da3215 Song, I.-Y. (2003). Object oriented analysis and design using UML. Retrieved from http://www.pages.drexel.edu/~ap62/pages/uc_3.html...