Repository navigation
Non Functional Requirements Demo 2
Keegan edited this page Jul 31, 2026
·
6 revisions
- NF1.1: All sensitive user information that is stored should be encrypted using Blowfish-encryption and should not be transmitted to users or used in URL parameters for any endpoint.
- NF1.2: Role based access to ensure only authorised users can access sensitive information.
- NF2.1: An exception within the backend should not bring the system down and should be thrown as an exception.
- NF2.2: Overall testing coverage should be at least 85% to improve Reliability.
- NF3.1: New features should be developed and put onto dev within 3 days.
- NF3.2: All new features should pass automated regression testing to ensure that past code is not affected by the new changes.
- NF4.1: Each page should have a rating of 80% or higher on Google Lighthouse for accessibility.
- NF4.2: The component's colour scheme has to follow the WCAG standards .
- NF5.1: Recovery within 5 minutes of failure
- User Stories
- Use Cases
- Use Case Diagrams
- Functional Requirements
- API Service Contracts
- Quality Requirements
- Constraints
- Technologies Required
- Architecture Diagram
- Domain Model
- Introduction
- User Stories
- Use Case Diagrams
- Functional Requirements
- Non-Functional Requirements
- Domain Model
- Introduction
- User Stories
- Use Case Diagrams
- Functional Requirements
- Non-Functional Requirements
- Domain Model
- Introduction
- Architectural Requirements
- Technology Requirements
- API Contracts
- Deployment
- NFR Testing
- NFR Traceability Matrix
- Introduction
- User Stories
- Use Case Diagrams
- Functional Requirements
- Non-Functional Requirements
- Domain Model
- Introduction
- Architectural Requirements
- Technology Requirements
- API Contracts
- Deployment
- NFR Testing
- NFR Traceability Matrix