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

Plan Use Case Diagrams #92

Closed
hikasap opened this issue Mar 21, 2024 · 3 comments
Closed

Plan Use Case Diagrams #92

hikasap opened this issue Mar 21, 2024 · 3 comments
Assignees
Labels
planning This issue needs planning priority: medium Urgent issue status: in progress Work is in progress workload: 2 issues that are requiring medium effort

Comments

@hikasap
Copy link
Contributor

hikasap commented Mar 21, 2024

It is needed to define use cases for use case diagrams before creating them. The assignee of this task should make an analysis of what kind of use case diagrams we will have. Provide a list of use case diagram names in the comments.

Reviewer

@furkansenkal

Deadline

25 March 2024

@hikasap hikasap added planning This issue needs planning priority: medium Urgent issue workload: 2 issues that are requiring medium effort labels Mar 21, 2024
@mahmutbugramert mahmutbugramert added the status: in progress Work is in progress label Mar 23, 2024
@iremnuy
Copy link
Contributor

iremnuy commented Mar 25, 2024

I read about use-case diagrams and suggest everyone to look at this website to get familiar with the use-cases which will help us a lot to abstract our system's interactions with various actors. I defined our potential actors that we will be serving.You can find our initial draw.io template at our project repo.

Actors can be anyone that our system will have any kind of interaction with, we should ask ourselves the following questions to elicitate our actors.

  • Who uses the system?
  • Who installs the system?
  • Who starts up the system?
  • Who maintains the system?
  • Who shuts down the system?
  • What other systems use this system?
  • Who gets information from this system?
  • Who provides information to the system?
  • Does anything happen automatically at a present time?

So defining them is a good starting point for defining the overall use-case diagrams.I suggest to decide on actors at our next meeting so that we can then define their actions-functions accurately.

Also some important headlines that we should discuss are:

  • System boundary ( which defines the overall frame of the system, its scope )

  • Extend-Include relationships, where we have which one of them etc.

  • Is wikidata API an actor?

@iremnuy
Copy link
Contributor

iremnuy commented Apr 30, 2024

Planning process helped me a lot, I created and added use case diagrams to our repo.

@furkansenkal
Copy link
Contributor

I reviewed your work. It is crystal clear explained and helped us a lot before discussion. Well done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
planning This issue needs planning priority: medium Urgent issue status: in progress Work is in progress workload: 2 issues that are requiring medium effort
Projects
None yet
Development

No branches or pull requests

5 participants