Scribd
Upload
21 views

Sec 03

Uploaded by

Mahmoud Nasser
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
21 views

Sec 03

Uploaded by

Mahmoud Nasser
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 22

Software Engineering

Use Case Diagram


by: Mahmoud Khalaf Saeed

SECTION 03
Use Case Diagram objects
Use case diagrams consist of Four objects.

Actor Use case System

Relationships
Relationship in use case diagram.
Relationship in use case diagram.
Actors and goals list
Actors and goals list
Actors and goals list
Actors and goals list
Actors and goals list
Sample Use case diagram
Use Case formats

Brief main success scenario

Casual Main success &alternative scenario

Fully dressed All steps and variations in details


Brief use case
- Create patient record (primary actor : medical
receptionist).
When the user needs to use MHC-PMS the medical
receptionist asks the patient to enter his/her data which
contain name , age , address , and next of kin after completing
the patient data , patient record is created to hold all
information about the patient including treatments and
consultations.
Casual use case
Describe medication dose (primary actor : Doctor )
Main success scenario: with the help of patient record
information the doctor check and diagnose the patient
after diagnosis he describe the appropriate dose to him ,
the system checks if the prescribed dose within the range
or not after ensuring that the dose within range the does
information will be added to patient record and the
system later will remind the patient with the dose and its
quantity.
Casual use case cont.
Alternative scenario: if the dose wasn’t accurate
(out of range) the system asks the doctor to revise
the dose and write the appropriate dose to the
patient , the system ensure that the new dose is
within the range and then it will be added to
patient record and later the system will remind the
patient with dose informations
The fully dressed use case :
Use case name: Provide impression.
Scope: MHC-PMS
Level: user goal
Primary actor
• Patient / patient's next of kin
The fully dressed use case :
Use case name: Provide impression.
Scope: MHC-PMS
Level: user goal
Primary actor
• Patient / patient's next of kin
The fully dressed use case : Stakeholders and interests
• Patient : want to provide his/her impression to help him in avoid next
consultation errors also inform medical errors
• Doctor : want to enhance his/her dealing with patient and help the
management in accurately assess him
• System manger : wants to collect impressions about doctors and the
consultation itself to help in assessing and improving the quality of
service in system.
• Nurse : wants to ensure that the coordination between the patient and
the doctor is done successfully.
• Patient’s next of kin :wants to avoid the bad impression and bad
implication of non-successful consultations .
The fully dressed use case
Preconditions
• Patient and must be authenticated
• Consultation must be done , …
Success guarantee (post-condition)
• Impression is saved to impression log
• Doctor’s rate must be updated , …
Main success scenario
• The patient writes the impression
• The impression is saved
• Doctor’s rate updated
The fully dressed use case : Extensions
a)At any time, system fails
- the recoverability allows us to come back to the current state
- the survivability allows us to deliver the main sensitive function
b)the patient not capable of writing
- the system authenticates the next of kin
- the patient can inform orally the next of kin with his impression
c)the patient needs to write his impression on a paper
- the medical record staff can use system scanner to save the paper
on impression log
, ………
The fully dressed use case :
• Special requirements
• Touch screen , scanner , papers ,pen, keyboard, …….
• Frequency of occurrence
• It’s a main function that can continuously implemented.
• Miscellaneous:
▪ How to ensure the valid impression ?
▪ How to use the patient impression to improve the rate of
the doctor
▪ How to avoid fooling of patient’s next of kin
Assignment
• Actors and goals list for all system
• Use case diagram
• Write format for the appropriate use cases in your system
• Brief ( at least 3 use cases)
• Casual ( at least 3 use cases)
• Fully dressed (( at least 3 use cases)
Don’t write format for login/sign up use cases
Don’t miss any section of fully dressed use case
Attach the assignment before next section for any review
On [email protected]
Thank You 😍

You might also like