Determine Estimates for User Stories

[lkekana]

don't forget to close https://github.com/COS301-SE-2024/TuneIn/issues/5 first

[lkekana]

extra 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]

also from my notes in today's meeting:

service contracts user stories: user x has input y, expects z and the system does xyz to provide z

room subsystem content management

profile management

• content they want
• how the above affects profile info
• how users are affected by their content iteraction
• music streaming API is not an actor in use case
• remove data analytics & insights

@u22528492 you might need to research that before fixing. my notes confused me too