Break the functionality of the product into a set of functional requirements, at higher level (from the customer perspective), by using User Stories. Reading the set of high-level functional requirements is expected to give a clear understanding of what the system will allow its users to do. This set of requirements is structured in a logical manner. For example, if you list 20 functional requirements, it is expected that they are organized into a few groups in a logical manner. Also, it is expected that there is some logic behind the order in which the functional requirements are listed. Use the Wiki section (of Gitlab, for example) to define them.
Prioritize the requirements as must-have, should-have, could-have, or won't-have.
"Functional requirements - High level" should be written as a separate entry in the Wiki.
1. As a member of the public, I want to be able to report an injured or distressed animal quickly via web/mobile?? so that the wildlife rescue team can respond promptly.
2. As a volunteer, I want to be able to view and update the status of cases assigned to me so that I can manage my tasks and ensure timely rescue operations.
3. As a member of the public, I want to receive confirmation that my alert about an injured animal has been received, so I can be assured that help is on the way.
4. As a volunteer, I want to be able to set my availability status, so the system only assigns me cases when I am able to respond.
5. As a coordinator, I want to review volunteer profiles / feedback, so I can assign tasks to the most suitable volunteers based on their experience and reliability.
6. As an administrator I want to be able to create reports and statistics, so that I can analyze the effectiveness of our rescue efforts and make data-driven decisions.
7. As a volunteer I want to be able to access a knowledge base, so that I can find information and guidelines which can help me with volunteering work.
8. As a volunteer I want a chat function so that I can communicate quickly with coordinators and other volunteers (?) during rescue operations.
9. As a coordinator I want a chat function so that I can communicate quickly with volunteers during rescue operations or giving/receiving information.
10. As an administrator I want to be able to monitor the location of volunteers on a map, so that I can efficiently send emergency alerts to nearby volunteers.
11. As a volunteer I want to be able to create a profile so that I can save my information and history.
12. As an administrator I want the users? to have tags, so that I can send emergency alerts based on their experience and knowledge.
13. As a volunteer, I want to be able to set my location, so the system only assigns me to cases where I am the nearest volunteer.
14. As an administrator I want to be able to create reports of incoming alerts made via a phone call, so that these alerts would also be in the system.
15. As a coordinator, I want to be able to oversee different stages of the rescue process of the case, so that I can see that everything is going accordingly and deal with any problems.
16. As a member of the public, I want to be able to write in the report a photo/video of an injured or distressed animal, add an exact location, my contact details and the condition of the animal, so that the wildlife rescue team has all the information that I can give.
17. As a volunteer, I want to receive training updates and notifications about new guidelines added to the knowledge base, so that I stay informed and can follow best practices in rescue operations.
18. As a volunteer, I want to be able to submit feedback, so that I can share my experience and suggest improvements to the process.
19. As a volunteer, I want to receive push notifications for new alerts that match my expertise or location, so I can respond promptly to urgent cases.
20. As a coordinator, I want to be able to prioritize alerts based on severity and urgency, so that the most critical cases receive immediate attention.
21. As a volunteer, I want to be able to log my time spent on each case, so that I can provide accurate reports and receive appropriate credit for my work.
22. As a member of the public, I want to be able to track the status of my report in real-time, so I can stay informed about the progress of the rescue operation.
23. As a volunteer, I want to be able to view and track historical data on cases I’ve worked on, so that I can review past activities and identify patterns or areas for improvement.
24. As a coordinator, I want to be able to view a summary of recent volunteer activity and case resolutions, so that I can recognize and reward outstanding contributions.
25. As a member of the public, I want to be able to receive follow-up notifications after a case has been resolved, so I can be informed about the outcome and the condition of the animal I reported.
26. As an administrator, I want to be able to control access levels for volunteers, ensuring that those without authorization can only view information relevant to their role.
27. As a member of the public, I want to be able to fill out a form, so that I can apply for a volunteer position.
28. As a member of the public, who is temporarily taking care of an animal, I want to be able to access a chat, so that I can ask for help and recommendations regarding the animal.
29. As a member of the public, who is temporarily taking care of an animal, I want to be able to access a knowledge base with recommendations and information about the species, so that I can provide proper care.
\ No newline at end of file
The initial document specified **seven** main functions of the application, based on which the user stories are currently grouped together.
