| ID | Description | Rational |
| 01 | The system should be available and operable for at least 99% of the time. | Availability |
| 02 | The database of the system should be protected. | Security |
| 03 | The system should be backed up every 24 hours. | System Backup |
| 04 | The system should be designed with direct and indirect accessibility consideration. | Accessibility |
| 05 | The system should support the most common browsers and also be able to be used from a mobile device. | Platform compatibility. |
| 06 | The system should meet the legislation of this kind of application. | Legal and licensing issues |
| 07 | The system design should be clear to understand. | User Friendliness |
| 08 | The system should respond in under 5 seconds for every request. | Effectiveness |
For the first non functional requirement, we better specify the availability as percentage. Up time of 362 days a year is equal to almost 99.2% availability. This is a good availability as it is above two nines (99%). The level of availability usually expected by user is high availability [1]. It means that there shouldn’t be any unplanned outage of the system. The only outage is for planned maintenance or upgrade of LessonPlan 2.0. The rational is better to be called as availability.
———
[1] Piedad, Floyd, and Michael Hawkins. High availability: design, techniques, and processes. Prentice Hall Professional, 2001.
Fix it, thank you!