Southern New Hampshire University
IT-304-J1754 Systems Reqmts/Implement Plan 20EW1
Use Case Specification
Salome Odipo
20th September 2020
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.)
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 self- service 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
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?
NF1: Security of patient information enters
Capture patient information or eason for visit
Check-in receptioni