Unifi Non Functional Requirements Mapping
Non Functional
The following table is a list of the non functional requirements for the service.
info
These are based on the assumptions provided in the [[Security System Brief]] briefing.
| Req | Description | Category | Response | Fit |
|---|---|---|---|---|
| NFR1 | Security: The system should ensure the confidentiality, integrity, and availability of sensitive information. | Must | The system would be implemented in a local only configuration. Cloud based backups would be the only offsite environment. All access to the service is via secure SSL connections, and the data on the device can be encrypted. | Comply |
| NFR2 | Reliability: The system should operate reliably and consistently, with minimal downtime or errors. | Must | The system is made up of two components: UDM as the management backplane, and the Access Chassis. Both components would be fed by protected UPS power, and therefore have some protection from power events. The Chassis can operate with an optional integrated 48v battery in the event of a power failure. The UDM can also operate with an optional redundant power source and have a mirrored fully redunant device in shadow mode in the event of a hardware failure. | Comply |
| NFR3 | Usability: The system should be easy to use for users, administrators, and IT personnel. | Must | The system uses a web based console for all applications and functions. This is built to web accessibility standards and intuitive and easy to use. | Comply |
| NFR4 | Performance: The system should be able to process access requests quickly and efficiently. | Must | The system is a high performing solution with distributed processing and no central point of bottleneck. The UDM is rated with a 10G backplane and allowing a full 5G IPS/IDS routing capability. | Comply |
| NFR5 | Power Requirements: The system should have a suitable power supply and battery backup in case of power outages. | Must | Additional batteries can be installed in the Chassis and also as an option to the UDM if required. As UPS power is being provided, this is not specified. | Comply |
| NFR6 | Environmental Resistance: The system should be resistant to environmental factors such as temperature, humidity, and vibration. | Must | Operating temperatures and performance is typical of these types of devices. | Comply |
| NFR7 | Compliance: The system should comply with relevant security standards and regulations (e.g., GDPR, HIPAA). | Must | All data is maintained on-premise, and controls deployed around access and governance. | Comply |
| NFR8 | Maintenance: The system should be easy to maintain and repair, with minimal technical expertise required. | Should | The system is using commercially available components and non specialised elements that ensure that access to skilled assistance is available. | Comply |
| NFR9 | Cost-Effectiveness: The system should provide good value for money, considering the cost of implementation, maintenance, and upgrades. | Should | Using enterprise grade, publicly available off the shelf components helps ensure lower costs initially. The license free aspects of the service ensure that operating costs are maintained post deployment. There are no additional maintenance costs for hardware post deployment. | Comply |
| NFR10 | Interoperability: The system should be able to integrate with other security systems and devices from different manufacturers. | Should | The system itself is running proprietary OS and hardware, however access to the consoles, underlying OS and API allows for good interoperability. Using plugins for identity and access management, together with open standards helps ensure external interoperability. | Comply |
| NFR11 | Scalable: The system should allow for expansion onsite for additional security components. | Must | The system is modular. The initial design would allow for 100% additional capacity in the future for a further 4 doors. If more doors were required, these can be deployed individually, or as another eight door system chassis. | Comply |
| NFR12 | Security Standards: The system should use recognised industry standards for cards and data encryption. These include and not limited to: - MIFARE Classic - MIFARE DESFire EV1/EV2 - ISO 14443A, 14443B, 15693 | Must | The system allows for 3rd party compatible cards to be used based on the standards required. | Comply |