Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Case Diagram #52

Closed
sudek0 opened this issue Apr 4, 2023 · 3 comments
Closed

Use Case Diagram #52

sudek0 opened this issue Apr 4, 2023 · 3 comments
Assignees
Labels
effort: high Work requiring very high effort priority: high Very urgent issue, needs to be done A.S.A.P. status: done Work is finished type: new feature Work that adds a non-existing feature

Comments

@sudek0
Copy link
Contributor

sudek0 commented Apr 4, 2023

creating use case diagram

@MericKeskin MericKeskin self-assigned this Apr 5, 2023
@MericKeskin MericKeskin added status: in review Work is currently under review priority: high Very urgent issue, needs to be done A.S.A.P. effort: high Work requiring very high effort type: new feature Work that adds a non-existing feature labels Apr 5, 2023
@begumyivli
Copy link
Contributor

updated according to some deficiencies (search and sorting search results both guests and registered users), view IAs for guests

@bakikucukcakiroglu
Copy link
Contributor

Explanation: This issue is assigned to a sub-group. Since all steps of the issue is related, it can not be separated into small chunks. All other individual efforts will be reported additionally.

Tasks to be done:

  • Create a shared Figma file

  • Define Use Cases according to features of the platform and the fundamental needs of the user

  • Define a common structure to draw diagram.

  • Draw sequence diagrams.

@bakikucukcakiroglu
Copy link
Contributor

bakikucukcakiroglu commented Apr 8, 2023

All the work for creating this diagram is evenly shared between sub-group members. Group members cannot state their individual work since we worked simultaneously in a shared Figma file. The way we work to accomplish this task prevented us to create distinct issues for every sub-task even if it can be considered as an issue management issue.

The work can be seen by the following image, link to the actual source file will be shared later as a measurement against a violation of intellectual property rights.

Screen Shot 2023-04-09 at 00 26 44

@MericKeskin MericKeskin changed the title use case diagram Use Case Diagram Apr 9, 2023
@MericKeskin MericKeskin added status: done Work is finished and removed status: in review Work is currently under review labels Apr 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: high Work requiring very high effort priority: high Very urgent issue, needs to be done A.S.A.P. status: done Work is finished type: new feature Work that adds a non-existing feature
Projects
None yet
Development

No branches or pull requests

6 participants