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. 7.1 [Performance, availability, capacity, characteristics, etc.]
7.2 Ex: [***]
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. A non-functional requirement is more concerned with specific criteria that can be used to judge the operation of a system. In the eDIANA context, this includes requirements such as performance, reliability, safety, power consumption, as well as other more generic aspects such as design constraints (e.g., technology, architecture) and compliance with standards. Most of the requirement attributes are quite self-defined and others were originated from deliverable D1.2-B (Requirements Support Ontology). However some of them are somehow vague and need some clarifications: Priority • High: Must be implemented no later than in the first iteration of the Construction phase. • Medium: Must be implemented no later than by the end of Construction. • Low: May be implemented if time permits. (Functional) Category • COM – Communication: functionality related to communication between separated nodes. • FUN - Functions/Operations: functionality covering computation/processing operations. • IS - Information Storage/Flow: functionality related to information storage or transmission. • UI - User Interface: functionality associated to user interfaces. • DI - Device Interface: functionality related to interfaces of devices. • MOD - Operational Mode: description of required operational modes. An operational mode identifies a segment within the system execution that is characterized by a given configuration. Information Direction: Only applicable if the functional category is Information Storage/Flow. • Required: the information is required by the component defined in the attribute eDIANA Component. • Provided: the information is offered by the component defined in the attribute eDIANA Component. • Shared: the information is shared (read/write) by multiple eDIANA components. • Undefined: the information direction exists, but it is not defined at this stage of the requirement elicitation.
Non-Functional Requirements. (Please see Bidder’s Response form Part 4 for requirements to be added)
Non-Functional Requirements. Software require- ments Code language Can be developed in any web program- ming language Runtime environment needed Not specific runtime environment needed Operating systems and architecture (x86 or x64) No specific OS is needed External libraries dependencies No specific libraries are needed Other? - RAM memory NFR-3-TRST: Should be able to run at least in a pc with 8GB of memory Other? - Communication re- quirements: Internet connection • NFR-4-TRST: A data repository where patient data should be available communicating through appropriate APIs • NFR-5-TRST: The model repository and the in Silico Trial and Prediction Repository should provide the necessary APIs Security and Privacy: 1. NFR-8-TRST: Physical security should be ensured. ● User authentication ● User authorization 2. NFR-9-TRST: Access by user role or types should be ensured. ● User has access to his data only ● Medical Expert has access to his patient’s data only. Other Require- ments: - Comments: -
Non-Functional Requirements. Navigation
Non-Functional Requirements. 2.2.1.4.1 The system must have an easy to use interface.
2.2.1.4.2 Performing a task on the system must be understandable by the user
2.2.1.4.3 The system interface must support accessibility to all users including users with impaired vision, hearing or loss of motor skills.
2.2.1.4.4 The system must be scalable to support additional stakeholders.
2.2.1.4.5 The system must be flexible to support current and future standards
2.2.1.4.6 The system must be compatible to work on common operating systems for mobile devices and tablets for availability everywhere
2.2.1.4.7 Response time speed for screen refresh must be 2 seconds on the average
2.2.1.4.8 The system must include on-line help.
2.2.1.4.9 The help desk specialists must be trained to use the applications to support the system.
2.2.1.4.10 Users must be able to recover or reset lost passwords on the system
2.2.1.4.11 The system must include standards for encryption to protect the confidentiality of a patient’s health information
2.2.1.4.12 The system must be operated on a secure hardware and software with back up storage that meets technology standards to protect personally identifiable information
2.2.1.4.13 Must provide login credentials and multi factor key authentication for authorized users at every access level
2.2.1.4.14 Must adhere to all written confidentiality and privacy to all written confidentiality and privacy practices applicable by law to protect patients’ privacy whereby the system contains their health information
2.2.1.4.15 The system must support providers to achieve the goal for CKD in Healthy People 2020
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. 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
