Requirements Catalog
Legend
Priority
| Priority | Meaning |
|---|---|
| MUST | Indispensable requirement, to be implemented if at all possible |
| SHOULD | Important requirement, implemented if time and resources allow |
| COULD | Optional extension, additional value but not mandatory |
| Out of scope | Deliberately excluded, may serve as inspiration for future teams |
Effort & benefit
| Level | Meaning |
|---|---|
| Low | Implementable with little effort / little additional value |
| Medium | Noticeable but realistic effort / noticeable value |
| High | Complex implementation / high professional or strategic value |
Patient profiles
| Subcategory | Description | Effort | Benefit | Priority |
|---|---|---|---|---|
| Variety | Multiple profiles with different characteristics (age, gender, origin, skin color, weight, height) | High | High | MUST |
| Count | At least 2 different patient profiles | Medium | High | MUST |
| Count | At least 4 different patient profiles | High | High | MUST |
| Count | More than 4 different patient profiles | High | High | SHOULD |
| Disability | Patients with visible disabilities or limited mobility representable | High | High | MUST |
| Selection | Patient selection, random or targeted, via the web interface | Medium | High | MUST |
Patient file
| Subcategory | Description | Effort | Benefit | Priority |
|---|---|---|---|---|
| Basics | Digital patient file with patient-related information inside the VR application | High | Low | SHOULD |
Accessibility
| Subcategory | Description | Effort | Benefit | Priority |
|---|---|---|---|---|
| Color blindness | Application usable with different forms of color vision deficiency | Medium | High | MUST |
| Subtitles | Spoken content optionally displayable as subtitles | Low | High | Out of scope |
Technical quality
| Subcategory | Description | Effort | Benefit | Priority |
|---|---|---|---|---|
| Code comments | Source code comprehensibly commented | Medium | High | SHOULD |
| Refactoring | Codebase structurally reworked and cleaned up | Medium | High | SHOULD |
| Technical documentation | Documentation of architecture and further development | Medium | High | SHOULD |
Training & documentation
| Subcategory | Description | Effort | Benefit | Priority |
|---|---|---|---|---|
| Installation guide | Understandable guide for setting up the development environment | Medium | High | COULD |
| FAQ | FAQ section with answers to frequent questions | Low | High | COULD |
Patient interaction
| Subcategory | Description | Effort | Benefit | Priority |
|---|---|---|---|---|
| Audio | Patients with sound output | Medium | High | Out of scope |
| Dialog system | Rule-based or AI-supported dialog system | High | Medium | Out of scope |
| Multilingualism | Patient interactions in multiple languages | High | Medium | Out of scope |
Scenarios
| Subcategory | Description | Effort | Benefit | Priority |
|---|---|---|---|---|
| Patient-specific errors | Errors and hints depending on the respective patient profile | High | High | Out of scope* |
* Initially classified as out of scope; later included in the target agreement and implemented (see Goals Achieved and Missed).
Evaluation & support
| Subcategory | Description | Effort | Benefit | Priority |
|---|---|---|---|---|
| Hints | Hint function pointing to the next error | Medium | High | Out of scope |
| Mistake attempts | Configurable maximum number of wrong attempts | Medium | High | Out of scope* |
| Result display | Appealing result display after completion | Medium | High | Out of scope* |
| AI evaluation | AI-supported analysis of user behavior with hints | High | Medium | Out of scope |
* Implemented during the project as part of the reworked scoring system (mistake budget, evaluation dashboard).
Legal notes
Since no real personal patient data is processed within the project, data protection and compliance requirements currently play a subordinate role.
Should future features such as cloud services or real patient data be integrated, data protection and security requirements (esp. GDPR) must be re-evaluated.