Create the use case diagram for our project.

[arincdemir]

Description

We need the use case diagrams for our project before going further.
We will use this link to access the collaborative webpage for our diagram:
draw.io link

Estimated Time

80 mins

Deadline

Date(31/03/2024) - 23:59

Reviewer

@ebrarkiziloglu - Deadline of the review(02/04/2024 - 23:50)

[set120120]

I've added search part. Could you please continue to add new parts? @ramazanoacar @arincdemir . Also, I've tried to write feed page but I could not do something. Could you please help to do this part?

[ramazanoacar]

@set120120 yes of course. I think @arincdemir did some of the parts too. I tried to add the remainings but LucidChart said we are out of free shapes. So, I will transfer this one the add the remainings to draw.io

[ramazanoacar]

https://drive.google.com/file/d/1QbJJS1J5EcyW7SQ38RSkC_Gb2j18wuqk/view?usp=sharing

it is now empty but i will do my work on this link

[ramazanoacar]

@set120120 @arincdemir I added the part for Feed Page and transferred everything to above link. However, I am not sure if the issue is completed or not. Do we need to add another parts such as Following and Personal Page or is this enough? If not, what should we add and how we should arrange them? Do you have any ideas? Also, @ebrarkiziloglu what do you think as a reviewer?

[ebrarkiziloglu]

Thanks everyone. The diagram looks very elaborate! I have a few notes and some design questions for you:

• Inside the Feed system boundary, the three use cases under the use case Interact with Post were separately connected to the Backend actor. So, I took the liberty of connecting Interact with Post directly with Backend actor instead.
• I believe delete history should extend see search history instead of the current include relation, since deleting the history is an optional functionality, wdyt?
• I see that the use cases publish a post and Interact with Post are in relation with the backend actor. With similar logic, should Search use cases be connected to Backend as well?
• Inside the search system boundary, all the filter by use cases are currently connected to their corresponding parent use cases by the include relations. I think these should be extends instead, since filter by functionalities are optional. Could you please provide your reasoning behind this design choice? I might have missed a key point here.

[ebrarkiziloglu]

@set120120 @arincdemir I added the part for Feed Page and transferred everything to above link. However, I am not sure if the issue is completed or not. Do we need to add another parts such as Following and Personal Page or is this enough? If not, what should we add and how we should arrange them? Do you have any ideas? Also, @ebrarkiziloglu what do you think as a reviewer?

Also, I too think that we can add Following use cases. Since we already have the search use case, we can add a sub-use case (generalization relation) for the search profile use case, and from there we can extend the follow user profile use case. Similarly, inside the search system boundary, the interact with post can have another child use case for follow the post owner use case, does this make sense?

For the personal page, we might consider adding a new system boundary of its own. We already have the create post and change profile details use cases. We might just enframe them with such a system boundary, wdyt?

[ramazanoacar]

@ebrarkiziloglu thanks for your review and comments. However, since we did this separately and individually with other assignees, I believe it would be better for us to make a small meeting and go over your points and make the necessary addition/deletions. What do you think @arincdemir @set120120 do you have time during the holiday?

[arincdemir]

@ramazanoacar I am free tomorrow and sunday, we can arrange something.

[set120120]

Hi Ebrar, I revised the search section according to the feedback you gave. Sorry for editing it a little late. Can you check again?

[ebrarkiziloglu]

Hi Ebrar, I revised the search section according to the feedback you gave. Sorry for editing it a little late. Can you check again?

Hi Süleyman, I see that you converted the include relations to extend ones, thank you.
Yet, I believe the arrows should point to the other directions.

Also, what do you think about my proposal on creating a sub-use case forsearch profile in my comment above?

[ramazanoacar]

@ebrarkiziloglu since i couldn't attend the meeting this evening. I will duplicate the draw.io file and add your proposals. So that If you decide to add during the meeting you can use duplicate and new one

[ramazanoacar]

You can use this links:

https://drive.google.com/file/d/1_Kl-MWNIcNKWRYGK8NUCJpuQAAdUNJvm/view?usp=sharing

https://app.diagrams.net/#G1_Kl-MWNIcNKWRYGK8NUCJpuQAAdUNJvm#%7B%22pageId%22%3A%225Y3wF6CpWj2z_y-06vuE%22%7D

[arincdemir]

I modified the file Ramazan shared above. this one

• I fixed the directions of the extend arrows.
• I moved the actors out of the system since that's how use case diagrams work I believe.
• I fixed the normal arrows in the "Feed" part. I changed them to include or extend as needed

[ramazanoacar]

I added the parts from @ebrarkiziloglu 's comment and changed some of the arrows. However, I mistakenly changed the orders of the system and couldn't revert it because I couldn't find when I did it. So, a check for the arrows and system would be useful in the meeting tonight because also the arrows got complicated with the last additions.

[ebrarkiziloglu]

We held a meeting with @set120120 to apply the latest changes. We also moved all of your changes from the second file to the original one.
Could you please have a look at it one last time? @ramazanoacar @arincdemir

[ramazanoacar]

@ebrarkiziloglu I looked at the changes. They seem nice and okey to me. Thanks for your effort! If @arincdemir is also okey with the changes, we can change the status label to needs review.

[arincdemir]

@ebrarkiziloglu Looks nice!

[ramazanoacar]

@ebrarkiziloglu I saw Arınç's comment now, can you review the issue?

[ebrarkiziloglu]

Hi everyone. Please adjust the feedback from TA (on discord) to the diagram.

[set120120]

I had a meeting with @ramazanoacar to apply the changes according to feedback. Can you please have a look? @ebrarkiziloglu @arincdemir

[ebrarkiziloglu]

I reviewed the changes you made according to the TA's feedback.
I just have one question, should Issue Log In Error be considered as a use case? Is it something the user can act on?
Otherwise, the diagram looks great to me, good work!

[set120120]

We thought that if the user enters the wrong information while logging in, we should forward him to a new page and ask him to log in again. That's why we didn't remove it.

[ebrarkiziloglu]

Okay that makes sense to me. Overall, the diagram is ready imo. Would you like to add it to wiki?

[set120120]

I've added necessary pages and links to wiki. You can close the issue now. Everything is done!

[ebrarkiziloglu]

Perfect. Great work everyone!