Verify Documents: A Step-by-Step Guide for Client Registration

School: Seneca College - Course: PMC 140 - Subject: Accounting

Use Case: Verify Documents Use Case Name:Verify Documents Scenario:Verify the Documents provided by the Client. Triggering Event:Client starts the registration process Brief Description:When the Client starts the registration process. They have to submit their documents for the verification process. Actors:Admin, Client. Related Use Case:Includes: Verify Phone Number and Verify Email. Stakeholders:Client: to provide the documents. Admin: to verify the documents. PreconditionsClient should have the Required Documents. Client should have a valid phone number and Email. Postconditions:Client must create a Username and Password. Username must be unique. Flow of Events:1.Client starts the Registration process. 2.Client provides all the required information. 3.Client provides the required documents. 4.The provided documents are sent to Admin for Verification. 5.After the verification of documents the Client has to create a username and a password. Exception Conditions:1.Client shouldn't pre-exist in the system. If the client already exists the page is redirected to the login page. 2.Phone Number verification is not completed. The application will be saved, but it will be marked incomplete to be completed at a later time. 3.Email verification is not completed. The registration process can move ahead. Client can verify Email at a later time. Use Case: Update Booking Status Use Case Name:Update Booking Status

Scenario:Update Booked and Available Slots for Vaccination. Triggering Event:Client wants to book a vaccination slot. Brief Description:The availability of vaccination slots should be updated regularly for the clients. Actors:Healthcare provider. Related Use Case:Includes: Accept Booking request and Decline Booking request. Stakeholders:Client: to book available slots. Healthcare Provider: to update slot availability. PreconditionsClient should be registered. Healthcare Provider should be accepting bookings. Postconditions:Updated slot results will be accurate. Cancelled slots should be switched to available. Flow of Events:1.Healthcare Provider logs in to the system. 2.Healthcare Provider updates all the booked slots. 3.Healthcare Provider updates all the cancelled slots. 4.All the verified booking requests are accepted. 5.All the invalid booking requests are declined. Exception Conditions:1.The client request is invalid. The client will be redirected to the verify documents page. 2.The client is not registered. The client will be redirected to the registration page. 3.No booking slots are available. Next available slots will be displayed for booking. 4.Vaccinations are not available. Booking page will not be available.