search

COS301-SE-2024 / TuneIn

Introducing TuneIn, where music becomes a shared experience that connects people, transcending distances and creating lasting bonds through the power of music.
4 stars 0 forks source link

Create Use Case Diagrams #5

Closed lkekana closed 4 weeks ago

lkekana commented 1 month ago

from demo 1 doc: "Draw high-level use case diagrams for your system’s use cases. Number them for traceability purposes. Ensure use cases are done using a service contract approach, as this will greatly assist in designing tests for your system. https://www.visual-paradigm.com/guide/umlunified-modeling-language/what-is-use-case-diagram/ "

lkekana commented 1 month ago

Also add estimates for user groups.

Advice from Chat:

Estimations in Use Case Diagrams

Estimations provide a way to assess the effort, time, and resources needed for each use case. This helps in project planning and resource allocation. Estimations can include:

  1. Effort Estimation

    • Time: "This use case is estimated to take 20 hours of development."
    • Complexity: "This use case has a complexity level of 3 out of 5."

  2. Resource Estimation

    • Personnel: "This use case requires 2 developers and 1 QA engineer."
    • Tools: "This use case requires access to the payment gateway API."
lkekana commented 1 month ago

@u22528492 also re-opening this for the same reason as https://github.com/COS301-SE-2024/TuneIn/issues/32, you can either link to the doc or the issue should only be closed after a PR to dev (once the relevant files are on the repo)

u22528492 commented 4 weeks ago

Final QR doc: https://docs.google.com/document/d/1HA9cM_GOdNC7_sUcTyf3_IuY3L1H81YqXYUcA0EHtWQ/edit

u22528492 commented 4 weeks ago

Wrong one

u22528492 commented 4 weeks ago

Final use case diagrams: https://github.com/COS301-SE-2024/TuneIn/blob/documentation/documentation/UseCases.drawio