Creating a Sequence Diagram for Approving Article

[mehmetemreakbulut]

Description:

Creating a Sequence Diagram of a use case for approving an article in the application. This search can be performed according to many criteria such as the article's tags, category, author and date.

Reviewer: @palahb

Task Deadline: 06.04.2022 12.00

Review Deadline: 06.04.2022 15.00

[canberkboun9]

I moved some arrows to depict the chronological sequnce of events.

[mehmetemreakbulut]

I think the final version of the diagram considering the suggestions in the meeting is appropriate. We can take action after review.

[palahb]

The sequence diagram seems good, but I have some suggestions:

• I think places of the alternatives need to be revised. I think it is redundant and somehow seems a bit odd to have 2 alternatives that says the same thing. The inner alternative is enough and also the correct one I think. Outer one is a bit weird.
• Also, status variable may not be necessary as it is suggested by the customer in the customer meeting 4.

[canberkboun9]

• Outer alternative is redundant because we should not assume that creating and object will be unsuccessful.
• Status needs to be changed as we talked in Meeting 6.3 and Customer Meeting 4.

[canberkboun9]

The changes were made.

[mehmetemreakbulut]

Everything looks fine. I am closing the issue.