Non‐Functional Requirements List (Iteration 1) - djgamekid/GDP-Group-I-bearcatmanager GitHub Wiki

Requirements

Security

1. Login information will be secured (via encryption) in a database with limited permissions.
2. Email 2FA verification will enhance a user's ability to prove themselves.

Scalability

1. The system will have an archive of previous events to reintroduce if they are reoccurring.
2. The amount of users able to access the events will have to be notified of new potential events. 

Usability

1. Users will have interactive buttons and small animations to ensure fluidity between pages.
2. The website's skeletal structure will be simplistic allowing for navigable pages.

Performance

1. The system will provide real-time synchronization of data as users and admins make their selections.
2. The site should be able to handle requests of multiple users concurrently.

Interoperability

1. The system will support common data formats (e.g., JSON, XML, CSV) to ensure easy data exchange between different systems.
2. APIs will be RESTful and follow standard practices, allowing external systems to interact with the application efficiently.
3. The system will support OAuth 2.0 or other secure authentication methods to enable secure integration with third-party systems.

Portability

1. The system will be platform-independent, and capable of running on multiple operating systems (e.g., Windows, Linux, macOS).
2. The system will be deployable in different environments, including on-premises servers, cloud platforms (e.g., AWS, Azure), and hybrid cloud 
environments.
3. Containerization: The system will support deployment via containerized solutions (e.g., Docker) to ensure consistency across development, 
testing, and production environments.