Other Nonfunctional Requirements

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 3

5.

Other Nonfunctional Requirements

5.1 Performance Requirements

 The system shall respond to user actions within 2 seconds.


 The system shall be able to handle up to 1000 simultaneous users.
 The system shall be able to generate reports within 10 seconds.
 The system shall be able to handle up to 100,000 records of student information.
 The system shall be able to handle up to 500 concurrent lesson bookings per hour.
 The system shall be able to generate financial reports within 15 seconds.

5.2 Safety Requirements

 The system shall perform daily backups of all data.


 The system shall have an error handling mechanism that prevents the loss of student
progress data.
 The system shall have a disaster recovery plan in place in case of hardware or
software failure.
 The system shall have a logging mechanism to track all user actions and system
events.
 The system shall have a mechanism to prevent duplicate records of student
information.
 The system shall have a mechanism to prevent the scheduling of lessons with
unqualified instructors.

5.3 Security Requirements

 The system shall require user authentication to access any information.


 The system shall encrypt all sensitive data (such as student information and payment
details) during transmission and storage.
 The system shall have access control mechanisms to prevent unauthorized access to
sensitive information.
 The system shall have a password policy requiring strong passwords.
 The system shall have a mechanism to prevent SQL injection attacks.
 The system shall have a mechanism to prevent cross-site scripting attacks.

5.4 Software Quality Attributes

 The system shall have a reliability rate of 99%.


 The system shall be maintainable and scalable to accommodate future updates and
changes.
 The system shall have an easily navigable and user-friendly interface to improve
usability.
 The system shall have a low defect rate of less than 0.1%.
 The system shall be portable across different operating systems and web browsers.
 The system shall be easily extensible to add new features.

5.5 Business Rules

 The system shall process payments securely and in compliance with relevant
regulations.
 The system shall have a scheduling mechanism that allows for flexibility in lesson
scheduling.
 The system shall have a pricing mechanism that is transparent and consistent with
industry standards.
 The system shall have a mechanism to prevent students from scheduling lessons if
they have an outstanding balance.
 The system shall have a mechanism to allow students to rate instructors after
completing a lesson.
 The system shall have a mechanism to generate marketing reports to track the
effectiveness of advertising campaigns

6. Other Requirements
 The system shall be developed using Java programming language and the Spring
framework.
 The system shall use MySQL as the database management system.
 The system shall be developed using Agile software development methodology.
 The system shall be deployed on a cloud-based server.
 The system shall have a user manual and online help system for users.
 The system shall have a training program for instructors and administrative staff.
 The system shall be compliant with relevant privacy regulations and standards.
 The system shall have a mechanism for handling feedback and support requests from
users.

Appendix A: Glossary

 Glossary of terms used in the system shall be provided in Appendix A.


 Terms shall be defined and explained to ensure clarity and understanding.

Appendix B: Analysis Models

 System analysis models such as use cases, activity diagrams, and class diagrams shall
be provided in Appendix B.
 These models shall help to illustrate the system's functionality and behavior.

Appendix C: To Be Determined List


 A list of requirements or features that are still to be determined shall be included in
Appendix C.
 This list shall be reviewed and updated periodically throughout the development
process.

Glossary :

The web server 

Data base managment system

Operating sysytem

http and https

sql

cloud-based server

You might also like