Responsiveness:
The system will be operating on various monitor sizes and a wide variety of resolutions, from 1024 x 600 through 1900 x 1200, and responsive with all the variations.

Cycle Time:
The cycle time at expected performance will be 1.0-1.2 with 5-10 concurrent users. After that, the system will operate with a 1.21 – 1.30 load of 11-25 simultaneous users or a moderate lag. With a user base of 26-45, the system will operate with a 1.31-1.50 or a heavy lag. Finally, the system will work with 1.51 – 1.70 with a load of 46-50 concurrent users or a very heavy lag. Any number of simultaneous users over 50 will cause system performance to halt until another user finishes.

Speed Per Transaction:
The speed per transaction will be between 20 – 100 milliseconds, depending on cycle time. The system will be able to process anything between 10 – 50 transactions per second.

Test Requirements:
The test requirements will mandate a standard load test, testing all functional specifications and their speed per transaction.

Reliability:
Average time of 1 hour or less of downtime within three months. Downtime is for maintenance and system updates. On release, the system should be 100% operational for the first year of operation.

Minimum Bug Counts:

Execution Speed:
The execution speed of the home page using a high-speed internet connection should load within 100-200 milliseconds, depending on cycle time.

Storage Utilization:
Storage utilization should be within 75%-85% of available storage to avoid using all storage and causing technical issues if emergency storage is needed.

Robustness:
The time to restart after a failure or crash should be under 1 hour. The probability of corruption of data due to failure must remain under 1%. The percentage of events that cause system failure will stay under 0.5%

Browser Compatibility:
The system will be a web-based app. It will use all major web browsers (e.g., Google Chrome, Mozilla, Firefox, Safari, and Internet Explorer). In addition, it will include functionality to provide alternatives if the browser does not have JavaScript installed on it.

Computer and OS compatibility:
The system will operate on various types of operating systems, including Windows, macOS, and Linux. In addition, the site is accessible with any computer which can run a browser that is supported.

Login/Password System:
The system will have a login and password system to maintain user preferences, Journey, accomplishments, and collaborators. Security will be implemented with account creation and email confirmation. In addition, there will be a password retrieval system via security questions if the user forgets their password. It will permit the user to retrieve and reset their login credentials.

Encryption:
The website will not include end-to-end encryption at the stage of initial system delivery. Users are not encouraged to store personally identifying information on the platform. Moreover, there will be no sensitive information data storage features.

Access Control:
The development team will have frontend and backend access. Users and visitors will have user-level access.

Spam Protection:
The site will ask users to enter a string of characters shown in a picture to create an account to prevent bots from creating false user accounts.

Resource Utilization:
Resources such as the MySQL database will be accessed through the usernames and passwords provided by Florida Atlantic University on-campus servers. With appropriate documentation and licensing, the system tools for use and access are Bootstrap, React, Express, Node.js, and MongoDB.

Platform Compatibility:
The system will be a web-based app. Mobile and tablet versions may be implemented at a later stage.

Percentage of Target-Dependent Statements:
This version of the system will have 0% of target-dependent statements. In a future mobile and tablet version, 30% of statements will be target-dependent.

Coding Standards:
The system will be developed in a range of 75-80% of coding standards for HTML 5 and CSS3. The code will be produced, reviewed, tested, and reviewed again for efficiency purposes.

Naming Conventions:
HTML classes and id tags will be coded in lowercase except in situations where there is more than one word in a name; then camelCase will be used. The team will agree on SQL tables and data names. First letter capitalization and lowercase followed by lowercase letters will be the standard.

Accessible Times:
Our system will be available 24 hours per day, seven days a week. In addition, the site will be running if FAU lamp servers are available.

Downtime Impact:
Downtime will be minimal but will have a splash page informing that the system is down for maintenance. Scheduled downtime will be announced ahead of time and is expected to be minimal.

Support:
There will be a FAQ page with the most common issues and ways to fix them. There will also be help available by email that will filter to assigned developers. Emails will receive a response within 24 hours.

Exception Handling:
Exception handling will be implemented in all situations where an error may occur. Users will be provided with an explanation for the exception and have a chance to input the correct answer or be taken back to the home page.

There will not be self-checking software implemented since this system is not critical enough to warrant it.