Non-Functional Requirements. This section covers the mandatory non-functional requirements for the NDR. Any tender should reflect an understanding and demonstrate wherever appropriate how any proposed solutions will fulfil these requirements. Ref Requirement type Requirements Outline N01 Integrity The consumer must be able to trust the Register and have confidence in its integrity & authenticity. The Register will be the Database of Record for all Energy Assessments and in the event of dispute provides the definitive statement regarding the actual Energy Document that was produced and lodged along with the Model Data that was used to produce that Energy Document. Therefore the Operator must ensure that the Register: • maintains its internal integrity • be safeguarded from any unauthorised tampering. • protected from both internal and external threats. • reduce any risks of fraud and abuse that may take place across the end to end process. N02 Data Consistency Due to the highly distributed nature of the marketplace there is a significant issue with enforcing consistency across the entire marketplace. A particular area where consistency is essential is in the identification and addressing of each Property being reported on. A shared central database of Property & Address details is the most obvious way of achieving consistency both cost effectively and in the required timescales. Some scenarios where consistency is required are: • A Property may have a number of different addresses associated with it in addition to the primary or “official” address for example the street may have more than one name or the owner decided to give the house a name or a building has been sublet by units or floors. In order to maintain consistency it is essential that all Energy Documents relating to a property consistently have the same correct address shown • Over time the identifying characteristics of a Property can change e.g. a Royal Mail Postcode reorganization may result in a postcode change for the Property therefore the address of the Property is not sufficient • A Property in Wales has both an English and a Welsh Address and when producing Energy Documents in one of those languages the EA should consistently use the correct address in the relevant language. It is the up to NDR Operator to select appropriate data-sets or service providers – such as Ordnance Survey Addresspoint, Royal Mail Postal Address File (PAF), National Land & Property Gazetteer (NLPG) or National Land Information Service (NLIS)...
Non-Functional Requirements. Navigation
Non-Functional Requirements. 27
3.3.1 Use case requirements 28 3.3.2 Cross platform requirements 29
4.1 Reference Architecture Design Principles 30
4.2 Reference Architecture Model 31
Non-Functional Requirements all other requirements.
1.2 The Contractor shall, and shall ensure that the Services and Deliverables shall, deliver and comply with the requirements set out in this Schedule 3.
Non-Functional Requirements. (Please see Bidder’s Response form Part 4 for requirements to be added)
Non-Functional Requirements. (maximum marks) The architecture proposed for the NFR shall be assessed for: 10
i. Operating systems: Number of Operating systems supported by the Software (one xxxx for each OS subjected to maximum of 2 marks) (Microsoft windows as mandatory, UNIX, Linux, MAC etc. ) 2
Non-Functional Requirements. These requirements, although not linked to functional characteristics are needed for some domains (aeronautics, automotive, transportation) where failure or malfunction has a very measurable impact which must be taken in to account.
Non-Functional Requirements. 1. The system shall comply with local, state and federal regulations.
2. The system shall be web-based and platform agnostic. County of Orange MA-042-20012181 Health Care Agency Page 29 of 65 Folder No. C025988
3. The system shall be accessible 24 hours a day, 7 days a week. 4.The system shall have a network uptime of 99.999%
Non-Functional Requirements. ID NFR#1 Priority (MoSCoW) M Comment ID NFR#2 Priority (MoSCoW) M ID NFR#3 Priority (MoSCoW) M Comment ID NFR#4 Priority (MoSCoW) M Comment ID NFR#5 Priority (MoSCoW) M Comment ID NFR#6 Priority (MoSCoW) M
Non-Functional Requirements. The ISO/IEC 25010 standard offers us a product quality evaluation system with a reasonably rigorous classification for NFR’s. A non-functional requirement (NFR) specifies how a component should perform. NFRs define the desired qualities and rules of conduct in the ecosystem, whereas functional requirements define the vehicles for functional delivery. They are used to describe key operational characteristics of the components and services that make up the CCT’s RM&DM&CM platform, rather than specific behaviours. The requirements listed below will either be provided by the RM&DM&CM solution or controlled and provided by another service within the IT landscape, for example, single sign-on logically fits within the access provisioning of ICT whilst a single user-GUI to access all the modules of the RM&DM&CM system is a non-functional requirement that usually is fulfilled by the RM&DM&CM solution. The solution should be easily scaled up to work for a Multi-location environment that might require replicating Image Servers and load-balancing Web Servers. A required document management system should have easy to use XML API's and Web- Services interfaces to facilitate integration with other business systems like Workflow, Records Management, and Image Enabling of ERP & CRM applications, Core Insurance & Banking applications. For clarity, the NFRs are used to describe qualities that are observable during execution such as performance, accessibility, and usability characteristics; and qualities that describe how the ecosystem develops, such as testability, maintainability, extensibility and scalability, which are vital for a platform to be dynamic, and evolve.
