Timeline for Does the current Use Case Diagram clearly represent how users interact with the system?
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 2, 2024 at 20:07 | vote | accept | Shahad At | ||
| Nov 26, 2024 at 8:08 | comment | added | Christophe | @FilipMilovanović no need to be sorry ;-) It's a constructive remark on an important point that I did not develop too much because of my own assumptions. I added a link to highlight the "autonomous" with an other answer where I explain more in detail the principle. | |
| Nov 26, 2024 at 8:05 | history | edited | Christophe | CC BY-SA 4.0 |
added 75 characters in body
|
| Nov 26, 2024 at 7:13 | comment | added | Filip Milovanović | @Christophe - ah, sorry - I didn't read all the way through. I was focused on trying to parse OPs description in the question, and couldn't shake the feeling that the OP represented the AI as an actor almost by default because it's "an intelligence". | |
| Nov 26, 2024 at 7:02 | comment | added | Christophe | @FilipMilovanović This is completely exact. This is why in the last bullet I referred to an "autonomous AI actor", suggesting therewith an external model that exists on its own. considering it is a supporting role that a human could in theory also play, the actor would be suitable. | |
| Nov 26, 2024 at 6:24 | comment | added | Filip Milovanović | P.S. Depending on the description of the associated use case, as depicted, the role of the AI actor could either be interpreted as that of an external agent that either just orchestrates the process, without having diagnostic capabilities itself (your system does), or as a supporting external system with diagnostic capabilities that your system does not itself possess. | |
| Nov 26, 2024 at 6:19 | comment | added | Filip Milovanović | @ShahadAt - Also, actors are meant to represent users (or rather, their roles), or supporting services external to the system. If the AI model isn't considered a separate, external (possibly 3rd party) service that your system makes use of, then it shouldn't be an actor, as it is just another part of the system itself. So it'd be covered by a UC named something like "Submit image for initial diagnosis." | |
| Nov 25, 2024 at 18:29 | comment | added | Shahad At | @Christophe I haven’t decided on that yet, but for now, the medications that will be displayed don’t require a doctor’s prescription and can be purchased directly from the pharmacy. | |
| Nov 25, 2024 at 17:21 | history | edited | candied_orange | CC BY-SA 4.0 |
edited body
|
| Nov 25, 2024 at 10:50 | comment | added | Bart van Ingen Schenau | @ShahadAt, a use-case diagram is basically a graphical table-of-contents for why actors would want to use the system. Anything that hints at a how or what does not have a place in a use-case diagram. | |
| Nov 24, 2024 at 23:21 | comment | added | Christophe | Although I'm not a fan of it, you could alternatively use «include» not to show the sequence but the subgoals with involvement of different actors. Capture image would be included in it, diagnosis (but without going into its steps) and get medication presciption. | |
| Nov 24, 2024 at 23:20 | comment | added | Christophe | Regarding potential merge, the two possibilities are open: you could have a UC "diagnosis and prescription" and AI actor would be involved even if it doesn't do it all. You could even merge in it the capture, and associate user to "diagnosis and prescription. An activity diagram would describe the different steps. | |
| Nov 24, 2024 at 23:10 | comment | added | Christophe | Interesting. So "Manage database" is meant to manage the medications for possible diseases? In this case keep that UC but make it more specific. Out of curiosity, does your database also deal with allergies to the medication or incompatibilities with other medications that the patient already takes for other purposes? | |
| Nov 24, 2024 at 16:52 | comment | added | Shahad At | Thank you for your feedback and suggestions. I have a question regarding your suggestion to merge the diagnosis-related steps These steps are currently separate but sequential, with interactions between the system and the user in each. Do you think it’s better to combine them into one use case (Identify Disease) or keep them separate since they involve distinct interactions? the role of the AI Model, it only identifies the disease and sends the result to the system. The medications are retrieved from the database and are not directly part of the AI’s output. | |
| Nov 24, 2024 at 15:22 | history | edited | Christophe | CC BY-SA 4.0 |
added 1701 characters in body
|
| Nov 24, 2024 at 15:04 | history | answered | Christophe | CC BY-SA 4.0 |