Performance and Scalability requirements overview and checklist

Owned by Khalilah Gambrell
Last updated: Mar 07, 2022
2 min read

Overview 

This page provides several checklists to help POs include performance and scalability requirements throughout the product development lifecycle. It is critical that all POs and development teams consider ways to improve performance and usability of the platform. 

Questions POs should ask themselves and SMEs

Data Load

  • How many <<applicable record type total>> records will you store in <<app>>? 
  • How many <<applicable record type total number or percentage>> records will you add each year to the<< app>>?
  • How many <<applicable record type total>> records do you purge each year?

Usage

  • How many concurrent users are interacting with <<applicable record type>>?
  • How many concurrent users and actions happen? 
  • On average, how many transactions occur in an hour? day? 
  • Which apps are folks interacting with this <<applicable record type>> record? 
  • What are peak usage times (hour-hour) for interacting with <<applicable record type>>? 
  • What are peak usage times (day/week/month) for interacting with <<applicable record type>>? 

Record display

  • On one record, on average, how many <<applicable linked record type>> are attached?
  • Can you provide an example of a typical <<applicable record type>> record that you have in your current ILS? 
  • Can you provide an example of an <<applicable record type>> record that you consider an extreme case? 

Response Times 

  • How quickly should search results display?
  • How quickly should a user view a detail record? 
  • How quickly should a record be updated?  
  • Review document for proposed SLAs > /wiki/spaces/DQA/pages/2658550

Data retention & Purge data

  • How long should<<applicable record type>> records be retained? 
  • Should <<applicable record type>> records be purged? If so, what frequency?
  • When deleting a record via UI, should it be a hard delete? Meaning the record will not be stored once user takes delete action. Or should it be a soft delete? If so, how many versions of the record should be retained?  

User interface design requirement details 

  • Provide Kimie/UX designer examples and/or sample data that represents multiples.
  • Provide the typical number of records and let Kimie know if it is possible that the list will be in the 100s or 1000s.