IT 304 Use Case Specification

docx

School

Southern New Hampshire University *

*We aren’t endorsed by this school

Course

304

Subject

Mechanical Engineering

Date

Dec 6, 2023

Type

docx

Pages

Uploaded by msheba08

IT 304 Use Case Specification Bathsheba Harris 16 September 2023 Use Case Specification Components Responses Use Case Number What is the number of this use case? (#1–4) 1 Use Case Name What is the name of this use case? Capture patient information/reason for visit. Actor Who is involved in this use case? Front office receptionist, Patient Summary Description What happens in this use case? All the patient's information is communicated across all the authorized platforms. 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. To mitigate the occurrence of significant errors, it is imperative to ensure the regular updating of all systems and maintain comprehensive records of each patient's visit. Relationships between Use Cases Which actors does this use case interact with? Front office receptionist, Provider of Insurance, Patient Trigger What starts the use case? The Patient checks in for an appointment at Millennia Health Center. Pre-Condition (Methods/Operations) What happens before the use case starts? The patient schedules an appointment. Post-Conditions (Methods/Operations) What happens after the use case? The patient information and reason for the visit have been documented, closed, and filed in the patient's medical chart. 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. Each patient's medical record and visit will be verified and updated across all systems as soon as the patient checks in and out of their appointment. Non-Functional Requirements What are the non-functional requirements of the use case? The protection and confidentiality of patient information entered. 1

Use Case Specification Components Responses Use Case Number What is the number of this use case? (#1–4) 2 Use Case Name What is the name of this use case? Verify patient insurance Actor Who is involved in this use case? Front office receptionist, Provider of Insurance Summary Description What happens in this use case? The patient’s information is gathered by the front office receptionist and the patient’s insurance is verified with the Insurance provider. 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. Ensuring patients receive necessary healthcare and physicians receive appropriate compensation is of utmost importance. Relationships between Use Cases Which actors does this use case interact with? The receptionist and insurance providers exchange information Trigger What starts the use case? All patient data have been entered into the system.

Use Case Specification Components Responses Pre-Condition (Methods/Operations) What happens before the use case starts? The patient should have an appointment scheduled in the Millennia Health Center system. Post-Conditions (Methods/Operations) What happens after the use case? The system records should have the patient's up to date information and the purpose of their visit. 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. [Insert response here] Non-Functional Requirements What are the non-functional requirements of the use case? The protection and confidentiality of patient information entered.

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

Use Case Specification Components Responses Use Case Number What is the number of this use case? (#1–4) 3 Use Case Name What is the name of this use case? Capture patient copay Actor Who is involved in this use case? Front office receptionist, Patient Summary Description What happens in this use case? The patient's copayment (if any) must be collected at the time of service. 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. The receptionist is required to fulfill their responsibilities. The determination of the patient's co-payment is contingent upon the provisions outlined in the patient's insurance policy. Also, it is important to figure out whether a copayment is a requirement for each scheduled visit. Relationships between Use Cases Which actors does this use case interact with? The receptionist and patient. Trigger What starts the use case? The verification of the patient's coverage is completed. Pre-Condition (Methods/Operations) What happens before the use case starts? The patient has an appointment and needs to pay a copayment at the time of check-in. Post-Conditions (Methods/Operations) What happens after the use case? Patient insurance is in the network allowing the patient the ability to obtain medical care. 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. The verification and collection of any required copayments. Non-Functional Requirements What are the non-functional requirements of the use case? The system's reliability in accurately recording copayment amounts.

Use Case Specification Components Responses Use Case Number What is the number of this use case? (#1–4) 4 Use Case Name What is the name of this use case? Schedule next appointment Actor Who is involved in this use case? Front office receptionist, Patient Summary Description What happens in this use case? At check-out, over the phone, or via a website, appointments can be scheduled. 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. The patient schedules any new or follow-up appointments. Relationships between Use Cases Which actors does this use case interact with? The patient and possibly the receptionist Trigger What starts the use case? If the patient requires a follow-up appointment or other issues the patient may need to be seen. Scheduling that next appointment.

Use Case Specification Components Responses Pre-Condition (Methods/Operations) What happens before the use case starts? Patient schedules an appointment with their provider. Post-Conditions (Methods/Operations) What happens after the use case? The patient confirms their appointment and receives a reminder. 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. It's important to make sure that the appointment fits into the doctor's schedule and that insurance will cover it. Non-Functional Requirements What are the non-functional requirements of the use case? The patient's ability to use the different methods to set up their next appointment. This template is adapted from the work of Warren Lynch (2019) and II-Yeol Song (2003). References

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

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-modeling- 828756da3215 Song, I.-Y. (2003). Object oriented analysis and design using UML. Retrieved from http://www.pages.drexel.edu/~ap62/pages/uc_3.html