I'm currently learning object-oriented programming and we have moved on to UML. We are learning about use cases and actors currently and we need to create a list of actors and use cases initiated by each actor for a given problem.
I understand what each of the individual components are but we haven't been given any examples. I've looked up examples but it only seems to give the final result of the use case diagram. What I am struggling with is using a problem statement ( the requirements of the system) to then create and find the actors and use cases.
Here's the domain to model: https://www.scribd.com/document/401208954/Pms
And this is my example of what I think I have to do (but not sure if I'm on the right track)
2.2 MONITOR:
Each bed has a separate monitor that collects patient data, sends
information to the display, and response to user commands and queries.
My assumptions:
The requirement is going to be: collects patient data.
The goal: sends info to the display and the owner: the patient
Do am I approaching the analysis from the right side? How can I identify the Use Case of a given statement and the actors involved?
Best Answer
You need to step back a bit and look at the system as a whole.
An actor is anyone who interacts with the system. Users are always actors (hint: read the last sentence of "1. Purpose"). Other people can also be actors where they need to interact with the system - for instance if the system asks them to do something. I am not sure that the "patient" is even an actor in this example - they don't seem to do anything but be monitored.
Other computer systems that are outside the system you are modelling can also be actors. For example, if two computers communicate over a network, but you are only responsible for one of them, then the other must be an actor.
A use case represents a series of interactions between the user and the system, to achieve a specific purpose. So you have to think about all the things that the users will do with the system. It sounds like you are only being asked to identify what the use cases are at this stage, not actually write them out in full.