In order to give our users the best user experience possible, we will be defining and implementing non-functional requirements which will shape our system constraints. To begin, our system is constrained to use by Alumni, the Alumni Association, and the Advancement Services, along with University Officials. Our solution is not for students, nor is it open to the general public.

**Scalability Needs:**To allow our app to scale to high numbers in use, we plan to roll out our solution, so it is not flooded with high volumes when we first release our solution. We also plan on using relational database platforms that are scalable to large use. The system must scale to support 30,000 users at a singular time.

**Availability Needs:**The system must be available 99.99% of the calendar year, leaving only 8.64 seconds of downtime per day. This is because the University of Washington has alumni living all over the world, so in order to make our solution available for functional use to all alumni, it needs to work at all times of the day, no matter the time zone the alumni is living in. We find this very important to our solution, as we want to be inclusive to all Alumni and give them a way to engage in a supportive alumni community, no matter where they live. While there is a tradeoff of running our server 99.99% of the day with having an unsustainable solution, we plan to look into other ways of making our platform sustainable.

**Sustainability Needs:**We are pursuing ideas of making our solution more sustainable such as pushing users to make sustainable choices and limiting the amount of data that is stored in databases to only that which is necessary to make our platform perform its duty and be functional. The system must delete posts after 3 months of storage to reduce the amount of ram needed to support our service.

**Performance Needs and Security Needs:**In order to create a pleasant user experience, users should have content loaded to their screen in 5 seconds of opening the app. To protect alumni security, alumni should not be able to access non-public information about other alumni, and our database must be encrypted with routine maintenance checks. People outside of the app should not be able to access information from the app at all.

**Interoperability Needs:**Our system needs to be interoperable with both the Advancement Services database, and the Alumni Associations database. It must confirm the alumnus identity with both databases within 4 minutes, to ensure users of the app are truly alumni, and if they are trying to join the Alumni Association page, that they are a part of the Association. The system must send the Advancement Services database updated alumni information when they create an account, or update their information within one week to ensure the advancement services have the correct data for alumni.

There are many non-functional requirements our solution must meet to give alumni the best user experience possible, as well as making our solution functional for use by alumni, the Advancement Services, and the Alumni Association.