Software Design: Class Diagram - Tag

[ezgy]

Issue Description

Since the use case diagram has been prepared, the design process will continue with the class diagram. In order to contribute to the class diagram collaboratively, the team has decided to separate classes by main operations in the use case diagram. This issue corresponds to the creation of Note class in the diagram.

• This issue is a sub-issue of Software Design: Class Diagram #86 .
• Note that Tag class is a supporting class for Note and search feature.
• In the use case diagram, implemented part corresponds to "add Tag" under notes, as can be seen on Software Design: Class Diagram - Note #96 .

In the requirements this class covers

1.1.3.2.4.5. Users shall connect, annotate and tag notes.

Step Details

Steps that will be performed:

• review relevant parts in the use case diagram
• review relevant requirements
• define the attributes
• define the methods/operations
• define the relationships and multiplicities with regards to other classes

Final Actions

Once a general template for how the class should be is defined, the proposal will be added to the diagram on lucidchart(link above). Upon reviews and the final discussion within the team, it will be finalized and added to the wiki.

Deadline of the Issue

04.04.2022 - Monday - 23.59

Reviewer

Egemen Atik

Deadline for the Review

05.04.2022 - Tuesday - 10.00

[egemenatikk]

Thank you for your work @ezgy. I reviewed Tag class you created. I think it contains all the fields and methods necessary. I could not think any other field to add, maybe after class diagram review meeting we come up with something to add.

One suggestion I can make is that maybe we can add a method called setTagText(). Other than that, it is all good.

[ezgy]

Thank you for your work @ezgy. I reviewed Tag class you created. I think it contains all the fields and methods necessary. I could not think any other field to add, maybe after class diagram review meeting we come up with something to add.

One suggestion I can make is that maybe we can add a method called setTagText(). Other than that, it is all good.

thank you for your suggestion, I will add it right away

[egemenatikk]

I have converted field names to snake form as @bahricanyesil suggested me for my parts of class diagram. Here is the final screenshot of Tag part of class diagram with all its fields, methods and relations:

I think problem of this issue is solved, so I am closing it. It can be reopened in the future if further work is needed.