Medical Booking System - 2.0
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More โ
TO-BE Scenario vs 2.0 (Covid-19)
In this scenario, the Medical Booking System (MBS) is autonomous and available 24/7. Patient uses MBS to book the appointment without the need of the receptionist.
Doctors are now required to keep their online calendar up to date. We will use an existing popular Calendar enterprise web solution
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More โ
To Be workflow model
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More โ
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More โ
Use Case Model from To-Be Workflow
- Do not convert Manual activities into use cases
- For interactive activities (user task) the use cases are in relationship with the human actor. If multiple systems are involved, then they are also related with the other system
- For automated activities (system task) the use cases are in relationship with the system actor
- For integration activities (automated activities involving 2 systems) we depict two use cases for integration.
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More โ
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More โ
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More โ
Modeling use cases
Step 1: Identify Actors
We identify one actor in the lecture. Mac as a patient. Recall that an actor portrays any entity (or entities) that performs certain roles in a given system. The different roles the actor represents are the actual business roles of users in a given system.
An actor in a use case diagram interacts with a use case. For example, for modeling a banking application, a customer entity represents an actor in the application. Similarly, the person who provides service at the counter is also an actor. But it is up to you to consider what actors make an impact on the functionality that you want to model.
If an entity does not affect a certain piece of functionality that you are modeling, it makes no sense to represent it as an actor. An actor is shown as a stick figure in a use case diagram depicted "outside" the system boundary, as shown in Make Appointment figure.
To facilitate collaboration and quick use case modeling do check the plantuml use case reference
Step 2: Identify use cases
- The tasks that each Actor requires the system to perform. This may influence both the description of the Actor and the Use Case.
- Whether each Actor needs to create, read, update, and/or delete any data to/from the system which is commonly referred to as โCRUDโ: Create, Read, Update, and Delete.
- If any of the Actors informs the system of any changes.
- If any Actor requires notification of any system occurrences.
Step 3: Depict cases in graphical mode
We use the relationship to represent the communication between the actor and the use case
- Depicted by line or double-headed arrow line
- Also called association relationship
Use case Solution
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More โ
Use Package
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More โ
Function Model
Function |
Use Cases |
New/Existing/To be modified |
System/Comments |
MBS-CORE |
Search for Doctor Availability |
* |
MBS/Patient searchs for his doctor availability |
MBS-CORE |
Confirm Appointment Selection |
* |
MBS/System acknowledges confirmation of appointment |
MBS-CORE |
Logins into MBS |
* |
MBS/ Patient is authenticated in the system |
MBS-CORE |
Email Appointment Confirmation to Patient |
* |
MBS/System acknowledges confirmation via email |
MBS-Integration |
Checks Doctor Availability in Calendar |
* |
MBS/System integration with Calendar |
MBS-Integration |
Reserve Appointment in Calendar |
* |
MBS/System integration with Calendar |
Calendar-Integration |
Reply Doctor Availability |
* |
Calendar/System API Response |
Calendar-Integration |
Confirm Appointment Reservation |
* |
Calendar/System API Response |
Calendar-CORE |
CRUD Calendar |
* |
Calendar/Existing Cloud Solution |
Work individually, in pairs or trios to complete the Function Model
Process inovation extension
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More โ
Work individualy or in teams to brainstorm the different tasks in the process and how they can be augmented using innovative technologies.
See below for a possible solution
Image Not Showing
Possible Reasons
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More โ