After a complete failure of the complete system (or major parts), the system is restored to a fully functional state in at most 12h. This includes restoring data that might have been corrupted due to the failure.
Restored to fully functional state 12h after complete failure
Related Quality Requirements
- Access find function in three seconds | #usable
- Accurate estimate of insurance contract rate | #usable #suitable
- Available 7x24 with 99% uptime | #operable #usable #reliable
- Avoid common vulnerabilities | #reliable #secure
- Compliance with UI styleguide | #usable
- Consistent keyboard shortcuts | #usable #efficient
- Core functions can be used on multiple OSs | #flexible #usable #operable
- Detect inconsistent user input | #usable #reliable
- Easily understandable acceptance test cases | #usable #suitable #efficient
- Easily understandable generated code | #efficient #usable #suitable
- Expressive error messages | #usable
- Fast and accurate sensor | #efficient #reliable
- Fast rollout of changes | #efficient #operable
- Good code readability score | #reliable
- Interoperable with Java 12 | #operable
- Interruptable backend process | #usable
- Low effort deployment | #operable
- Near instant search results | #usable #efficient
- New Features Introduce No Bugs | #reliable
- Portable Business Data Checker | #flexible #operable
- Precise calculation of gamma coefficient | #reliable
- Quick unit tests | #operable
- Server fails |
- Severe errors are detected and the system shuts down into safe state | #operable #safe #reliable
- System can run >12h without re-booting the operating system | #operable #reliable
- Usable Despite Color Blindness | #usable
- Usable With Gloves | #usable
- User Interface can be used in Current Browsers | #flexible #usable #operable
- system continues to operate without downtime | #reliable