Here is a set of non-functional requirements for a ticket issuing system, setting out its expected reliability and response time also called non functional testing
Reliability: The ticket issuing system shall have a reliability of 99.5% and shall be available 24/7 for users to access.
Response Time: The ticket issuing system shall respond to user requests within 2 seconds during normal business hours and within 5 seconds during off-peak hours.
Capacity: The ticket issuing system shall be able to handle a minimum of 1000 concurrent users without any performance degradation.
Scalability: The ticket issuing system shall be able to scale to meet the growing needs of the business without any significant impact on performance.
Security: The ticket issuing system shall be designed to protect the confidentiality and integrity of user data and shall be compliant with relevant security standards.
Error Handling: The ticket issuing system shall have robust error handling mechanisms in place to ensure that errors are logged, monitored, and resolved in a timely manner.
Backup and Recovery: The ticket issuing system shall have a robust backup and recovery process in place to ensure that user data is protected in the event of a disaster or system failure.
Maintenance: The ticket issuing system shall be designed with maintenance in mind, and shall have a process in place to ensure that it is regularly updated and maintained to ensure its continued reliability.
0 Comments