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. 10.1 Navigation
Non Functional Requirements all other requirements.
Non Functional Requirements. 1. The system shall be scalable to accommodate additional users and modules as needed.
Non Functional Requirements. 2.2.1.4.1 The system must have an easy to use interface.
Non Functional Requirements. In order to be more precise, this section is divided into three points: Common non-functional requirements. These requirements relate to the whole system. Online processing requirements. These are special requirements for the online processing service. This service will be used to process input in the journalist use case, where the system will recommend content based on user input. Background processing requirements: These are special requirements for the background processing service. This service will be used to process items that may be recommended or searched for in the future.
Non Functional Requirements. ID NFR#1 Priority (MoSCoW) M Source D5.2 Version V1 Description The ATE Service will operate on a 24/7 basis Comment ID NFR#2 Priority (MoSCoW) M Source D5.2 Version V1 Description The ATE Service MUST allow to configure privacy and security setting for user requests Comment Privacy and security functions and settings, e.g. to define the anonymity level of a request, whether the query/request will be publicised and available for a wider audi- ence, etc. ID NFR#3 Priority (MoSCoW) M Source D5.2 Version V1 Description Private discussions will be shown only to the participant in the discussion Comment ID NFR#4 Priority (MoSCoW) M Source D5.2 Version V1 Description Public discussions will be shown only to all AUTHENTICATED users Comment ID NFR#5 Priority (MoSCoW) M Source D5.2 Version V1 Description The ATE server will create weekly backups of the service DB Comment ID NFR#6 Priority (MoSCoW) M Source Internal Version V1 Description The content published on the ATE server must meet certain legal requirements. Comment The minimum legal requirements include: (a) legal and copyright notices, (b) in- formed consent if cookies are used, (c) disclaimer for content to state the liability of the consortium and of the EC, and (d) data protection notice making explicit how any personal information collected from users will be used.
Non Functional Requirements. The functional and non-functional requirements are discussed in D2.1. For the sake of completeness and to avoid unnecessary switching between deliverables, the common non-functional requirements are summarized below. Note that D2.1 also contains non-functional requirements with respect to the text, audio and video processing tools. Adhering to these requirements is the concern of the developers of these tools, and will not be further discussed in this document.
Non Functional Requirements. 8.5.6 Extensibility NON-EXT-TPR-09 NON-EXT-TPR-10 3rd Line Application Support Suggested Support Model 01 Aug 2013 This requirement has been deleted.
Non Functional Requirements. (Please see Bidder’s Response form Part 4 for requirements to be added)
