Quality Requirements
| Requirement | Description |
|---|---|
|
|
|
|
|
|
The systems needs to operate for world wide consumption. |
|
The software should be easily maintainable. This includes using widely used frameworks so help can be given quite easily. |
2. Quality Scenarios
| ID | Scenario | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The system is created for integrating into Spring Security. |
|||||||||||||
The software needs to conform to the GDPR in Europe. |
|||||||||||||
The data transfer between keycloak and the system should be possible. |
|||||||||||||
The system should offer a discord bot to use the data. |
|||||||||||||
The main interface should be web based. |
|||||||||||||
The system has to be available at least in German and English language. Other translations should be easily addable. |
|||||||||||||
Request have to be answered quickly. The following time percentiles are sufficient:
|
|||||||||||||
Torg Eternity is played around the world. So the systems have to work 24/7. There is no maintenance window available where no users would be affected. |
|||||||||||||
Following the guidelines of 'The Twelve-Factor App' {12factor} support the maintainability and resilience of the system. |
|||||||||||||
Maintaining the software and the data must be possible for a small team (basically the full army of myself, me, and I). |