Use Case Diagram

[Veromc24]

Following today's meeting, each team memer will send a message to this issue as a way to indicate that their workload has been completed. At the same time the will do a commit. Deadline 09/11/2024 - 23:59h.

[dgms02]

I have been researching about the functionality of mapping requirements with use cases.

The closest thing I have found is to map from a textual analysis (which is basically what is on github) transit it to a glossary (option transit to) and from there transit it again to the requirement that is in the list of requirements.

Finally from the glosary transit it to the the use case with the same name, creating a link in the use case.

By doing this we will be able to access from the use case to the glossary with the list of requirements, and from the glossary we will be able to see the attributes of that requirement or requirements. Open to suggestions on how to do this better

[dgms02]

I have created the use case diagram for log in and Classify_data_into_categories/Identify_and_classify/categorize_project data. I have also corrected some errors that I have seen in the rest of diagrams, I recommend reviewing them so that if you do not agree with the changes, comment here.

[Veromc24]

I have created the use case diagram for log in and Classify_data_into_categories/Identify_and_classify/categorize_project data. I have also corrected some errors that I have seen in the rest of diagrams, I recommend reviewing them so that if you do not agree with the changes, comment here.

I have made uptades on my diagrams as well as told about the changes to each team-mate :D

[oblivionwing26]

I updated 3 diagrams as we were discussing in order to have a fix structure client<-client.type in every use case diagram

[oblivionwing26]

Now 5 new UCs are uploaded with all the corrections in 4 of the previous ones

[dgms02]

I have started with UC diagram of the general functionaliries of every user, i havent finished it yet, but if any subdiagram you have to do is already implemented in the general one, use it as a base to do the corresponding subdiagram, or if you think something is not right, feel free to correct it. Keep in mind that this diagram is about the interaction of the client with the app, which means that most of the server's activities are not present, that goes in another diagram

[carlosrz022]

I have created 5 new UCDs and uploaded them.

[dgms02]

Client functionalities general diagram finished, i have started with server general diagram

[David-Fdz-Liz]

I have just made the 7 use case diagrams that corresponded to my part.