Timeline for Two actors have same use case but can access different extends (Use Case Diagram)
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 10, 2023 at 13:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 12, 2023 at 13:05 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 12, 2022 at 12:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 15, 2022 at 11:08 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 17, 2022 at 13:19 | audit | Suggested edits | |||
| Jun 17, 2022 at 13:19 | |||||
| Jun 15, 2022 at 10:56 | answer | added | Thomas Owens♦ | timeline score: 1 | |
| Jun 15, 2022 at 5:41 | comment | added | EagleRex | @ThomasOwens As for connecting the actors directly to the specific use cases, I'm not sure about that. If I connect the actors to the specific use cases under the extend relationship, would they also get access to the "View Properties" use case? | |
| Jun 15, 2022 at 5:36 | comment | added | EagleRex | @ThomasOwens Yes, it is a true use case. I have just removed all of the other use cases form the diagram to make it simpler. From what I have read, I believe this is indeed an extend relationship. The actors can use the use cases mentioned in extend if they want to. but it isn't compulsory to use them. They can just view the properties if they want. Status includes "Unsold, Sold". This is for a school project so I'm going to have to add the extend relationship and I also have to create the use case diagram because the project requires it. | |
| Jun 15, 2022 at 1:05 | comment | added | Thomas Owens♦ | (1) Is "view properties" a true use case? That is, would one of these actors use the system to view properties and not carry out one of the other actions? Is there value if you were to deliver a system where you could only view properties? (2) Is the relationship truly an "extend" relationship and not an "include" relationship? Consider Martin Fowler's comments on ignoring extend relationships and the general uselessness of use case diagrams. (3) What would happen if you connected your actors to the more specific use cases? | |
| S Jun 14, 2022 at 23:32 | review | First questions | |||
| Jun 28, 2022 at 23:35 | |||||
| S Jun 14, 2022 at 23:32 | history | asked | EagleRex | CC BY-SA 4.0 |