Non-Functional Questions v1.0.2
ID | S63 |
|---|---|
Version | 1.0.2 |
Type | Overarching Standard |
Status | Retired |
Effective Date | Jul 5, 2019 |
Framework(s) |
Description
Non-functional requirements describe how the Solution works, not what the Solution should do, and serve as constraints or restrictions on the design of the Solution. The following non-functional questions are to enable NHS Digital to assess the risk associated with the Compliance Assessment of the Solution against the overarching Service Management, Information Governance, Security, Testing, and Business Continuity and Disaster Recovery Standards. Supplier’s answers will also demonstrate they understand the non functional landscape of the market they are selling into.
Non-Functional Questions Model
The non-functional questions (NFQs) model illustrated within Figure A attempts to show the relationships between the Supplier Solution and the non-functional requirements (NFRs) required to meet the Overarching Standards, provide appropriate levels of service and, where relevant, satisfy the required service SLAs.
Suppliers are responsible for ensuring the non-functional elements of their Solutions are capable of meeting any defined service levels for specific Capabilities provided, as well as any other NFRs specified by NHS Digital across other Standards.
Suppliers must provide an appropriate answer to the non-functional questions - the level of information and evidence required in the answer will depend on the Capabilities and scale of deployment of the Supplier’s Solution and this will be determined and specified in the guidance provided as part of the Capability Mapping and Standards Compliance On-Boarding process.
Figure A - Non-Functional Questions Model
Non-Functional Categories
Usability
ID | Sub-category | Description | Evidence Example | Assessment Criteria |
|---|---|---|---|---|
GP-NFQ-U-3 | Supported browser versions | Which browsers are supported and what are the minimum and recommended versions? How do you approach the deprecation and uplift of browser versions? | Provide declaration and any supporting documented evidence and rationale. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-U-6 | UI standards | What user interface standards does the Solution meet? Are you following ISO 9241-210:2010 - the ‘six principles for human centred design'? | Provide declaration and any supporting documented evidence and rationale. | Demonstrate systematic approach and rationale of how evidence is derived. |
Performance and Scalability
ID | Sub-category | Description | Evidence Example | Assessment Criteria |
|---|---|---|---|---|
GP-NFQ-PS-3 | Number of concurrent sessions | What is the peak number of concurrent user sessions the Solution can support? | Provide a value, show how the figure is derived, including any considerations which may impact this value. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-PS-5 | Response times | What are the expected response times in a given percentage of cases for a given operation e.g. Login or Open Patient Record? Provide different types of operation including command and query operations. | Provide values, show how the figures are derived, including any considerations which may impact these values. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-PS-6 | Transactions per second | How many user transactions per second are supported? Define what a user transaction consists of and how it is measured. | Provide a value, show how the figure is derived, including any considerations which may impact this value. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-PS-7 | Online service transaction volumes | How many online batch transactions per second are supported? Define what a batch transaction consists of and how it is measured. | Provide a value, show how the figure is derived, including any considerations which may impact this value. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-PS-11 | System Response Times | Describe how measurements are calculated for system response times to meet SLAs. | Provide values, show how the figures are derived, including any considerations which may impact the values. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-PS-12 | End User Interaction Timings | Describe how measurements are calculated for end user interaction timings to meet SLAs. | Provide values, show how the figures are derived, including any considerations which may impact the values. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-PS-13 | Interface Mechanism Response Times | Describe how measurements are calculated for interface mechanism response times to meet SLAs. | Provide values, show how the figures are derived, including any considerations which may impact the values. | Demonstrate systematic approach and rationale of how evidence is derived. |
Volume and Performance
ID | Sub-category | Description | Evidence Example | Assessment Criteria |
|---|---|---|---|---|
GP-NFQ-VP-1 | Model | Describe what volumetric model(s) are provided to enable volume and performance tests encompassing load, ramp, stress and soak phases? | Provide model(s), show how the model(s) are derived, including any considerations which may impact the model(s). | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-VP-2 | V&P Performance | What V&P work has been undertaken to ensure the Solution will meet expected volume and performance SLAs. | Provide statement of V&P assessment activities and associated test reports. | Demonstrate systematic approach of how the evidence is derived. |
GP-NFQ-VP-3 | Spine | What V&P testing of National Spine interactions (e.g. Personal Demographics Service, Summary Care Record, e-Referral Service, ..) is planned, to ensure supplier’s Solution has no impact on National Spine services? | Provide statement of testing and test coverage. | Validate test coverage. |
Non Functional Testing
ID | Sub-category | Description | Evidence Example | Assessment Criteria |
|---|---|---|---|---|
GP-NFQ-T-1 | Test Plan | Describe what test plan and schedule of non-functional testing is in place and with what associated documentation? | Provide test plan to include sufficient details of scope and coverage. | Validate scope and non-functional test coverage. |
GP-NFQ-T-2 | Data Protection Testing | What Data Protection testing is in place to show legislation is met? | Provide statement of test activity, the scope, coverage and attributable legislation. | Validate scope and non-functional test coverage. |
GP-NFQ-T-3 | ITHC / Penetration Testing | What ITHC / penetration testing is planned? | Provide statement of test activity, the scope and coverage. | Validate scope, process and testing and any recommendations required corrective actions completed. acted upon. |
GP-NFQ-T-4 | Ready for Operations (RFO) Testing | What RFO testing is planned? | Provide details of RFO test coverage, examples: • application / component failure and recovery • monitoring and reporting of SLAs | Validate test coverage. |
Recoverability
ID | Evidence Example | Assessment Criteria | ||
|---|---|---|---|---|
GP-NFQ-R-1 | Disaster recovery point objective (RPO) | What RPO is possible with this Solution and how does that map to the required SLA? | Provide a value, show how the figure is derived, including any considerations which may impact this value. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-R-2 | Disaster recovery time objective (RTO) | What RTO is possible with this Solution and how does that map to the required SLA? | Provide a value, show how the figure is derived, including any considerations which may impact this value. | Demonstrate systematic approach and rationale of how evidence is derived. |
Backup capability
ID | Sub-category | Description | Evidence Example | Assessment Criteria |
|---|---|---|---|---|
GP-NFQ-B-1 | Capability | Describe in detail what backup and recovery mechanisms are implemented. | Confirm formal processes and mechanisms are in place. Provide design and documentation of implementation and operational processes. | Demonstrate systematic approach and rationale of design, implementation and processes. |
GP-NFQ-B-2 | Validation and Testing | Describe what testing has been undertaken to demonstrate the mechanism and processes support your operational requirements. | Provide appropriate statement of test activity, coverage and outcomes | Demonstrate systematic approach and rationale of design, implementation and processes. |
GP-NFQ-B-3 | Periodic Testing | Describe what periodic testing of backup and recovery is undertaken? | Provide appropriate statement of test activity, coverage and outcomes. | Demonstrate systematic approach and rationale of design, implementation and processes. |
Availability
ID | Sub-category | Description | Evidence Example | Assessment Criteria |
|---|---|---|---|---|
GP-NFQ-A-1 | Availability | What is your service availability during agreed service hours. 90% ("one nine") 36.5 days 72 hours 16.8 hours | Provide a value, show how the figure is derived, including any considerations which may impact this value. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-A-2 | Service hours | What are the standard business operating hours the Solution needs to be available for users? | Provide details of service hours, where a solution may deliver a number of capabilities, a declaration of appropriate service hours is required. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-A-3 | Scheduled maintenance windows | What are the requirements for any scheduled periods of unavailability to perform Solution maintenance? | Provide statement, the underlying rationale and any impact considerations. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-A-4 | External system impacts | Does the availability of any external systems affect this Solution? | Provide statement, the underlying rationale and any impact considerations. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-A-5 | Fault tolerance | Describe any Single Points of Failure (SPOF) within the Solution or external that the Solution relies upon for operation. | Provide statement of any SPOF inherent within the Solution and where applicable, any associated mitigation.. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-A-6 | Degradability | Describe the ability of the solution to operate with reduced capacity or functionality in the event of an unexpected event, e.g. site failure | Provide details of any reduced operations capability, the levels of functionality and details of supporting documentation | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-A-7 | Disaster recovery minimum recovery operating level (MROL) | In the event of a disaster what are the minimum business services that need to be recovered to continue operating? | Provide details of any reduced operations capability, the levels of functionality and details of supporting documentation | Demonstrate systematic approach and rationale of how evidence is derived. |
Resilience
ID | Sub-category | Description | Evidence Example | Assessment Criteria |
|---|---|---|---|---|
GP-NFQ-RS-1 | Service Level Agreements (SLAs) | Describe how the hardware and software design supports the SLAs? | Provide details of how solution design supports the delivery of any SLA declaration, including any impact considerations. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-RS-2 | Hardware Design | Describe what level of resilience is provided in the hardware design? | Provide documented evidence and rationale, including any impact considerations. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-RS-3 | Software Design | Describe what level of resilience is provided in the software design? | Provide documented evidence and rationale, including any impact considerations. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-RS-4 | Business Impact of Service Incidents | Describe what mapping of business impacts of service incidents against levels of resilience has been undertaken? | Provide documented evidence and rationale, including any impact considerations. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-RS-5 | Component Failure Impact Analysis | Describe what CIFA documentation has been produced? | Confirm CFIA analysis has been completed, provide documented evidence of analysis. | Demonstrate systematic approach and rationale of how evidence is derived. |
Information Governance
ID | Sub-category | Description | Evidence Example | Assessment Criteria |
|---|---|---|---|---|
GP-NFQ-IG-1 | Data retention | What NHS Digital data retention policies are enforced by the Solution? See GP-IG-14.2-4 in the Information Governance Standard. | Provide documented evidence and rationale, including any impact considerations. or Provide list of policies | Demonstrate systematic approach and rationale of how evidence is derived. or How well do the policies map to requirements and legislation |
GP-NFQ-IG-2 | Data archiving | What data archiving policies must be enforced by the Solution? | Provide documented evidence and rationale, including any impact considerations. or Provide list of policies | Demonstrate systematic approach and rationale of how evidence is derived. or How well do the policies map to requirements and legislation |
Security
ID | Sub-category | Description | Evidence Example | Assessment Criteria |
|---|---|---|---|---|
GP-NFQ-S-1 | Data classification | What is the classification of data being processed by the Solution? Note: Refer to document for defining data classification used in Cloud and https://www.gov.uk/government/publications/government-security-classifications | Completion of the risk assessment | Confirm classification of data is as expected |
GP-NFQ-S-2 | Encryption | Describe what encryption is implemented to protect data at rest and in transit and which standards are implemented? | Provide statement of encryption level | Confirm encryption is at minimum level |
GP-NFQ-S-3 | Authentication | Describe what authentication mechanisms are supported? | Provide list of authentication mechanisms supported | Confirm authentication is appropriate for given Solution/ data |
GP-NFQ-S-4 | Authentication retry limits and account locking | Describe how protection against unauthorised authentication is implemented? | Provide documented evidence and rationale, including any impact considerations. | Demonstrate systematic approach and rationale of how evidence is derived. |
GP-NFQ-S-5 |