UML Use Case Diagram

[set120120]

Description

Use Case Diagram should be drawn.

Tasks

• Create Use Case Diagram

Estimated Time

5 hours

Deadline

19.10.2024 - 23.59

Reviewer

@ebrarkiziloglu - Deadline of the review(dd/mm/yyyy - hour)

[set120120]

The first version of the UML Use Case Diagram is ready thanks to the efforts of me, @arincdemir and @ramazanoacar . Now we are waiting for your feedback @ebrarkiziloglu . Changes will be made according to your feedback.

[set120120]

You can access the link

[ebrarkiziloglu]

Hello friends. Thank you for your great work. I want to add some remarks:

1. See profile details have several children use-cases. I think they should be connected via the include connections, since when the user view the profile details, they also directly see all of these additional informations.
2. Create Question use-case has 3 specialized child use-cases. We can consider adding an include connection from these children cases to Choose question type use-case.
3. For the Create Quiz use-case, do we have functionality to “add tags” to quizzes?
4. A quiz must have at least one question. Thus, what about adding an include connection from Create Quiz to a new Add Question use case which further extends to the existing Create Question use-case?
5. Should be further elaborate on the Edit Quiz use-case? Such as edit title, description, or edit question etc?
6. Create a Forum Post should include Adding a title to Forum, Adding tags to Forum (at least 1 tag is required).
7. I believe See Forum Page should include a View specific Post use-case. The existing Search Post use-case should also connects this use-case. And the commenting to Posts use-cases should be extended from this new use-case. It should include See comments but extend Make Comment to Post

[arincdemir]

1. I added extends to those since the profile details probably have submenus, and its possible for the user to see some of them while not seeing others.
2. I added a Choose question type use-case. I connected the question types using the generalization relationship instead of the include since they include and cover all the cases.
3. I deleted the "add tags" use-case because we didnt talk about that in the requirements.
4. Good idea! I added a new Add Question use-case and connected the Create Question and Add Favorited Question with generalization
5. Good idea! I added Edit Title, Edit Questions, Edit Description and Edit Picture with extends.
6. I added Add title to a post, Add Tags to a post, Add Body to a post with include.
7. I modified it as you said.

Also, some of the include and extends were created without the straight and dotted line, I changed them. I think they should be straight and dotted because of the UML conventions.

I also changed the stuff under Change Profile Details from generalization to extends since the user can do multiple of them at once. Generalization is for choosing one and only one of them.

Thank you for your review @ebrarkiziloglu. You noticed a lot of important stuff!

[ebrarkiziloglu]

@arincdemir, thanks for the great changes!

For the 2. point, should Pick Question Word be connected to Create Question with the current include connection, instead of being connected to Choose Question Type?

For the 7. point, Thank you for adding the use-case. I think See Forum Page should also directly include the See specific post use-case, since it is possible to view specific posts from the feed without searching for anything. At least this was what I imagined.

[arincdemir]

I fixed the 2. point.
You are right, searching for posts should not be a prerequisite for seeing posts. I fixed it.
Thank you.

[set120120]

For the 7. point, you are right, because it is possible to see posts from the feed without searching. I changed it to "include" from "extends".
Thank you.

[ebrarkiziloglu]

LGTM!! Thanks for you efforts everyone, closing the issue now.