Quality Requirements

Requirement Description

Functional Suitability

  • The software has to manage ↑RPG (Role Playing Game) event data. This should include at least:

    • Event Calendar

    • Workshop Sessions

    • Gaming Tables

    • Locations

    • Game Masters

    • Players

    • Game Systems

Compatibility

  • The managed data has to integrate into spring-security.

Usability

  • The software has to be accessible via Web Browsers

  • The software has to be internationalized. There has to be localization for at least German and English languages.

Reliability

The systems needs to operate for world wide consumption.

Maintainability

The software should be easily maintainable. This includes using widely used frameworks so help can be given quite easily.

Security

The system needs to be secure and resilient. This includes IT security and data protection.

1. Quality Tree

quality-tree

2. Quality Scenarios

ID Scenario

Functional Suitability

FS01

Provide a nice interface to show events in a calendar view. This includes drill down to details.

FS03

Users should be able to use the system without help from admins.

FS04

There should be push notifcations when events change. Users should be able to subscribe or mute events.

FS05

Event Organizers should be able to display their events ongoing for all sessions in public displays.

Compatibility

CO01

The system should offer a discord bot to use the data.

CO02

The system should be able to display and search for 3words locations.

CO03

The system should display events using OpenStreetMap.

CO04

The system should be able to export and import data using Ical format. This requirement fulfills the constraint ↑CT-004 CalDav.

CO05

The system should offer direct links to Virtual Table Top systems like Roll20 or FoundryVTT.

CO06

The system should be able to export and import data using Google Calendar.

Usability

US01

The main interface should be web based.

US02

The system has to be available at least in German and English Other translations should be easy to add.

US03

Request have to be answered quickly. The following time percentiles are sufficient:

Percentage of requests Response Time

95%

1,5s

90%

2s

5%

5s

US04

The system should be as accessible as possible. This includes following the ↑W3C Accessibility Guidelines and the ↑EU-Richtlinie 2016/2102.

US05

The system should be usable on tablets as well as on desktop computers.

Reliability

RE01

RPG events happen around the world. So the systems have to work 24/7. There is no maintenance window available where no users would be affected.

Maintainability

MT01

Maintaining the software and the data must be possible for a small team (basically the full army of myself, me, and I).

MT02

Following the guidelines of 'The Twelve-Factor App' ↑12FACTOR support the maintainability and resilience of the system.

Security

FS02

The software needs to conform to the GDPR in Europe.

US06

The system should use ABAC (↑Attribute based access control) to manage permissions. Uses should be able to form groups and manage eents on group level.