Non-Functional Requirements
- Japneet Kaur (Deactivated)
- Madeleine Finn (Unlicensed)
Non-functional requirements are agnostic to the solution / features and apply generically to the website.
The design standards should be aligned with the NSW Government design standards- digital.nsw design standards.
Security
| ||
NF01 | Audit/alerts | The solution must provide audit trails of authentication activity and provide alerts of breaches |
NF02 | OWASP Top 10 | It protects against the OWASP Top 10 |
NF03 | Active Directory | Ability to integrate with Active Directory for user authentication and authorization |
NF04 | Permission control | The solution must support folder level security, based on roles |
NF05 | Ability to support people external to the organisation (e.g. Content authoring is outsourced to a 3rd party agency) | |
NF06 | The solution must have the ability to designate and modify administrator roles (e.g. system admin, web-site admin) | |
NF07 | The solution must provide the ability to manage role permissions for page based authoring | |
NF08 | Encryption | Solution should support the encryption at rest |
Scalability
| ||
NF09 | Disaster recovery | The solution should allow recovery from disaster in a timely manner and with minimal data loss |
NF10 | Cache support | The solution should easily integrate with front end caching services such as Content Delivery Networks (CDN) and provide mechanisms to set cache time to live and or cache invalidation via publishing workflows |
Availability
| ||
NF11 | Authoring availability | The solution should ensure 99.9% availability of the content management authoring system to allow for a stable working platform |
NF12 | Published content availability | The solution should ensure at least 99.95% availability of the published website |
Data management
| ||
NF13 | Data extraction | The solution should allow data to be extracted in retrievable, readable and understandable format? |
NF14 | Data archival | The solution should support archiving the website in accordance with https://www.nsw.gov.au/onecx/content-guidance/archiving-websites |
NF15 | Data retention | The solution should store records for as long as defined by the company in accordance with NSW State Records Act. |
NF16 | Data restoration | The solution should allow for data to be backed up and restored |
Integration
| ||
NF17 | Search integration | The solution should support the integration with 3rd party search engine platforms |
NF18 | CRM integration | The solution should support the integration with 3rd party CRM platforms if required |
NF19 | API integration | The solution should support the integration with API's (e.g. for form submission) |
Performance
| ||
NF20 | Response times | The solution should have the ability to serve rendered content pages in under 2 seconds PS: Avg load time of top ranking websites in google is under 3 seconds and below is the ranking, |
NF21 | Concurrent users | The solution should allow for multiple users to access the CMS concurrently without affecting performance of the system. For authoring instance, the solution should support at the least 20 concurrent user activities |
NF22 | Start-up time | The solution must be able to start up and restart (e.g. in a disaster recovery event) in a timely manner |
NF23 | Publishing times | The solution should allow for content to be updated on the website (and also unpublished) in a timely manner (< 2 mins) once approved and published |
Extensibility
| ||
NF24 | API access | Ability of the solution to allow secure external access to data and features via supported, open standards based API's |
Usability
| ||
NF25 | Accessibility | Ability of the solution comply with all relevant W3C standards for accessibility and usability It should meet the accessibility standards defined by the NSW Government- Accessibility on nsw.gov.au |
NF26 | Mobile optimised | The end user and authoring experience should cater for mobile devices and small screen sizes |
NF27 | Platform UI/ theming/ feature customisation flexibility | The solution should allow low code/ configuration ability |
NF28 |
| The solution should be enterprise grade |
NF29 |
| The solution should be proven in Government sector |
NF30 |
| The solution should have incremental costing based on usage volume |
NF31 |
| The solution should have the ability to store content on platform |
NF32 | Contextual help | The solution should provide in context help to CMS users to assist with content management and general use of the system |
NF33 | Data entry customisation | The solution should provide the ability to define and enhance data entry types to make content management easier for users |
NF34 | Data entry validation | The solution should allow for inline validation and ensure consistency is maintained across content |
Analytics | ||
NF35 | Page Tracking | The solution should support reporting page views, unique visitors, returning visitors etc. over time (e.g. number of unique visitors a month) for web sites as a whole and individual sections/pages |
NF36 | Bounce Rate | The solution should allow tracking of where visitors drop off, time spent on certain sections of the page. |
NF37 | Capture outbound link clicks | The solution should allow tracking when a user clicks on a link that redirects them to an external website, away from our domain. |