PM Non-functional requirements

Owned by Khalilah Gambrell
Last updated: Jun 16, 2023 by Kathleen Moore

Must meet all applicable NFRs prior to being released.

  • NFRs define system attributes and constraints, which include:

    1. Non-functional elements of security (e.g. use of encryption, SSL)

    2. Non-functional elements of compliance

    3. Reliability (fault tolerance, failure prevention, etc.)

    4. Availability/Recovery

    5. Scalability/Performance (response time, throughput, data freshness, etc.)

What is a well-defined NFR

  • Bounded – When they lack bounded context, some NFRs are irrelevant (or even harmful). For example, performance considerations can be critical for the main application but unnecessary or too expensive for administration and support applications.

  • Independent – NFRs should be independent of each other so that they can be evaluated and tested without consideration of or impact from other system qualities.

  • Viable/Achievable – Each NFR comes at a cost and must be right-sized to be achievable for the organization. 

  • Testable – NFRs must be stated with objective, measurable, and testable criteria because if you can’t test it, you can’t ship it.

Category NFR verificationNotes/explanation

Reliability The upload and process of the data import job must complete successfully [TBD % of the time]


If the upload is not successful then []


If the processing of the data import job is not successful []


If a tenant on a multi-cluster environment, a job cannot impact the overall activities and performance of another tenant.


If a tenant on a multi-cluster environment, a job cannot impact the overall data import activities and performance of another tenant.


If a tenant is a part of a consortia, a job cannot impact the overall activities and performance of another tenant.


If a tenant is a part of a consortia, a job cannot impact the overall data import activities and performance of another tenant.


System activity needs to be accounted for 

Performance testing 

Provide baseline performance metrics for production-like settings:

  • Environments:
    • Single tenant
    • Multi-cluster environment with one tenant processing large jobs
    • Multi-cluster environment with multiple tenants processing large jobs simultaneously  
  • Background activity:
    • Typical off-hours background activity
    • Typical daytime background activity
  • Concurrent imports:
    • Single large job
    • Multiple large jobs
    • Large job + small job
    • Large job + single record import
  • Realistic representative profiles / job combinations (to be provided by SMEs):
    • Create TBD
    • Update TBD
  • Measure the impact on:
    • Check in/Check out

Recovery

Encoding

Format

ComplianceWCAG 2.1 AA compliance


Successful import should result in record availability in real-time via search





Cancel job 


Security 


Documentation