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

Creating the Use Case Diagram #41

Closed
enfurars opened this issue Mar 25, 2023 · 4 comments
Closed

Creating the Use Case Diagram #41

enfurars opened this issue Mar 25, 2023 · 4 comments
Assignees
Labels
Priority: High Serious problem that could block progress. Status: Done Work on the issue is finished Type: Documentation Indicates a need for improvements or additions to documentation Type: Research Research is needed for this issue Type: Wiki Wiki related issues

Comments

@enfurars
Copy link
Contributor

enfurars commented Mar 25, 2023

Problem Definition

A well designed use case diagram is needed to represent all possible interactions between the system(the prediction poll platform) and all types of users that can use the system.
Note: Types of users can be found in requirements page.

Problem Context

The PDF System design which is on our CMPE352 Moodle page will be our guideline for this task. Also research done by @AliNasra at #34 will be beneficial for us during the work.

Acceptance Criteria

  • As stated in the problem definition all possible interactions shall be represented and added to wiki page.
  • While preparing the diagram, functional requirements of the project shall be considered and diagram shall follow the requirements.
  • During the preparation of the diagram if any missing functional requirement is noticed by team members, it should be reported and resolved under this issue before going on with the diagram.
@enfurars enfurars added Priority: High Serious problem that could block progress. Status: To Do The issue has been reported and is waiting for the team to action it. Type: Documentation Indicates a need for improvements or additions to documentation Type: Research Research is needed for this issue Type: Wiki Wiki related issues labels Mar 25, 2023
@enfurars enfurars self-assigned this Mar 25, 2023
@enfurars enfurars added Status: In Progress Assignee is working on the issue and removed Status: To Do The issue has been reported and is waiting for the team to action it. labels Apr 1, 2023
@enfurars
Copy link
Contributor Author

enfurars commented Apr 2, 2023

Use case diagrams are prepared by @enfurars, @aemresafak, @selinisik and @YigitSekerci and then shared with the team members. The latest versions of them will be uploaded to wiki later on.

@enfurars
Copy link
Contributor Author

enfurars commented Apr 2, 2023

Additionally I was responsible for taking notes of missing requirements during the work of use case diagrams and we have noticed that the requirement about viewing the existing comments is missing. It will be added to requirements page as well.

@enfurars
Copy link
Contributor Author

enfurars commented Apr 2, 2023

I have added the missing requirement about viewing the comments as the requirement 1.1.4.5.

@EmreBatuhan
Copy link
Contributor

The use case diagrams have been created. They may need revision however the current state is up to date.

@selinisik selinisik added Status: Done Work on the issue is finished and removed Status: In Progress Assignee is working on the issue labels Apr 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High Serious problem that could block progress. Status: Done Work on the issue is finished Type: Documentation Indicates a need for improvements or additions to documentation Type: Research Research is needed for this issue Type: Wiki Wiki related issues
Projects
None yet
Development

No branches or pull requests

3 participants