Software Design: Sequence Diagram - Annotate

[onurkomurcu]

Issue Description

We were started to make sequence diagrams. I will make a sequence diagram which is related to annotation.

• This issue is a sub-issue of Software Design: Sequence Diagram #107.
• Sequence diagram is a collective work. This is only one portion of it.
• Following diagrams will be considered during work.
• Progress can be observed through Lucidchart.

Use Case Diagram:

Class Diagram:

Step Details

Steps that will be performed:

• Analyze annotation related diagrams which are provided above.
• Research about how to implement sequence diagram.
• Create the diagram in Lucidchart.
• Provide screenshot of the work.

Final Actions

After the work is done, it will be merged with our teammates' works.

Deadline of the Issue

06.04.2022 - Wednesday - 10.00

Reviewer

Ezgi Aysel Batı

Deadline for the Review

06.04.2022 - Wednesday - 11.00

[onurkomurcu]

I select the create action for the annotation sequence diagram. It is ready to be reviewed now.

[ezgy]

Thank you for your work, @onurkomurcu. I have a few suggestions to improve this diagram:

• instead of directly adding the created object to the DB, the diagram can include the Annotation class and the connection through the Enrollment class.
• once there are multiple classes communicating, you should also consider that return/reply messages are generally represented with dashed lines.

[onurkomurcu]

I revised my work after your review, @ezgy . The points you have mentioned can be observed in the following diagram. If you have any further question or suggestion, let me know. If not, you can close this issue. Thank you for your contribution.

PS: @egemenatikk help me to revise the sequence diagram. I want to thank him too.

[xltvy]

Closed #118