Heldenhelfer arc42 section 1
Introduction and Goals
Requirements Overview
A detailed description about the Goals and Requirements of the HELD-Application can be found in the technical modelling file, which is internally available.
The epics and user stories are maintained in JIRA
Quality Goals
The main quality goals of the project are the following:
- A member is not able to see the email addresses of other members that are not in the same club.
- A member of a club tries to access private information of another club of which he is not a member and fails to do so.
- Users with disabilities can use all the functions of the HELD portal.
- The HELD applications gives clear feedback within error messages and helps the user to solve them.
- A member wants use the Hero portal and is able to do so with an ordinary device.
Stakeholders
Explicit overview of stakeholders of the system, i.e. all person, roles or organizations that
- should know the architecture
- have to be convinced of the architecture
- have to work with the architecture or with code
- need the documentation of the architecture for their work
- have to come up with decisions about the system or its development
| Role/Name | Contact | Expectations |
|---|---|---|
| Product Manager | Smarte Region Würzburg (https://www.stadt-land-wue.de/stadtlandwue/index.html) | Reliable and efficient in terms of providing the necessary requirements |
| Product Owner | Smart and Public Team (https://smartandpublic.de/) | Flexible with regard to new functions |
| Developer | Smart and Public Team (https://smartandpublic.de/) | Flexible and reliable in terms of code maintenance and testability. |
| Tester | Smart and Public Team (https://smartandpublic.de/) | Reliable in terms of testing the functional requirements as well as the quality scenarios. |