Usability. Software applications must be modern, intuitive, and easy to use. It should be built with accessibility (Web Content Accessibility Guidelines / Section 508) in mind. Layouts and features should remain simple, consistent throughout, and to the point.
Usability. Tenant has inspected the Premises and fixtures (or has had the Premises inspected on behalf of Tenant), and acknowledges that the Premises are in a reasonable and acceptable condition of usability for their intended use, and the agreed rent payments are fair and reasonable. If the condition changes so that, in Tenant's opinion, the usability and rental value of the Premises are adversely affected, Tenant shall promptly provide reasonable notice to Landlord.
Usability. Installation Installation instructions are available and up-to-date in the wiki of the project documentation (xxxxx://xxxx.xxxxxxxxxxxx.xxx). Moreover, an installation guide can be downloaded with the software (xxxx://xxx.xxxxxxxxxxxx.xxx/software/downloads). Operative documentation A user guide can be downloaded along with the OpenDaylight release. Additionally, a starting guide is also available in the website (xxxx://xxx.xxxxxxxxxxxx.xxx/resources/getting-started-guide). Development Development documentation A wiki is available for developers at (xxxxx://xxxx.xxxxxxxxxxxx.xxx). It is a live document so it is updated periodically as long as the OpenDaylight project evolves. There is also a set of mailing lists and an IRC channel. Documentation for application development Refer to previous point. Development roadmap Refer to each project section in the OpenDaylight developers’ wiki (xxxxx://xxxx.xxxxxxxxxxxx.xxx/view/GettingStarted:Developer_Main). Also, several sample applications are developed. (xxxxx://xxxx.xxxxxxxxxxxx.xxx/view/OpenDaylight_Controller:Sample_Applications) Toolchain Java 1.7 + Maven + OSGi IDE integration As reported in the wiki of the project (xxxxx://xxxx.xxxxxxxxxxxx.xxx/view/GettingStarted:_Eclipse), at present only the Controller and the OpenFlow plugin projects have been validated to import into Eclipse without compile errors. Deployment System requirements OpenDaylight Controller runs in a JVM. Being a Java application, it can potentially run on any operating system that supports Java. However, for best results a recent Linux distribution and Java 1.7 are recommended. The only information about system requirements for running the controller has been found is more than 1G RAM. Nonetheless, OpenDaylight provides a set of preconfigured VMs with the Hydrogen release of the controller installed. Such VMs contain a GNU/Linux Ubuntu server 13.04 distribution and recommend to allocate 4GB of RAM memory to run the controller. Although the OpenDaylight controller is developed as a normal Java project, it makes heavy use of the Xtend language in some places. While development is possible with bare tools, it is recommend to use Eclipse with the Xtend plugin. Reference target OS Recent Linux distribution is recommended although any OS running a Java 1.7 virtual machine should work. Runtime dependencies Java 1.7 Key features to support COSIGN extensions Supported OpenFlow OpenFlow versions 1.0 and 1.3 are supported. Supported protocols at D- ...
Usability. 7.1 You are using the SERVICES at your own risk and you are responsible for verifying its suitability for your needs. Use of the SERVICES does not guarantee a particular result or compliance with applicable law.
Usability. The ALPKA 1 scheme cannot be made multiple use, as the proxy requires the knowledge of the combined secret information from solely the sender and the receiver for the re-encryption key. – Transitivity: As this feature involves a property on the proxy re-encryption key, it is only relevant for ALPKA 1. Transitivity is obtained as the re- encryption key combines the secret information of both sender and receiver
Usability. The Contractor’s System must be designed to provide a browser based, or a Rich Internet Application, that will utilize feature rich applications that will be updated over the Wide Area Network (WAN) and the Internet, and will deliver a consistent User experience to Vermont Citizens, AHS employees, providers, contractors, and partners. The Contractor will send and retrieve data in the background without interfering with or delaying User interface behavior in the browser. As newer browsers are released and are more capable of supporting technologies such as HTML5, the Contractor will capitalize on those improvements and incorporate them in the application. The Contractor’s System shall provide a dynamic Graphic User Interface (GUI) that allows access to information based on a User’s role and associated permissions. Configurable functions as well as the current state of User interaction at any given point in time will be achieved via configurable business rules or branching logic that is associated with real-time responses within the application. The Contractor’s System shall present only what is relevant to, or required of, the User to accomplish a specific data entry or review scenario while still ensuring all pertinent data is captured. All fields will include appropriate User entry validation such as data type, masking, and length. The Contractor will use zero footprint technology, architecture, and applications that can be “styled” or “skinned” to the AHS color palette and logo. The Contractor will provide secure single sign-on options to integrate into an existing client portal. Single Sign-On Options will include:
1. XXXX 2.0 Tokens and Protocol
Usability. Operator opens the Offload Application and adds a new task to the queue by selecting a bus and the time to be downloaded. Task is created with status “waiting for bus” on the queue status pane. • The bus will be selected from a drop down list that is updated every time a new SVR is registered to the Video Offload Service. Upon bus arrival to garage, video offload request is sent to the bus and video is downloaded to the center. Status bar shows “downloading” status with progress. If video is not available on the bus (elapsed retention time) or there is a problem writing to the garage server, an Error status will be shown in the status bar. When download is completed a new case is opened on Inform and status changes to “case ID is ready on Inform”. Correlation between offload queue and inform case will be by the case name (with reference on the queue manager to the Inform case name).
Usability. Providing a regular working system is not enough when it comes to a CIS. A CIS shall always be under control: “when running a CIS has to report on its state and to give evidence of its well being. It is mandatory to know how the CIS is working and what difficulties it encounters or has encountered”. It is preferable to check the CIS continuously in order to help ensure that it is well under control. This reporting information is valuable both: For building a real time dashboard in order to detect earlier any possible deviation, And “off-line” for calculating key quality of service indicators. This allows for example to relate the CIS performance with its capacity, and to know how it reacts to overloading or any unforeseen event. It also covers requirements related to traceability (e.g. audit trails, etc.). In addition, “a CIS can be easily managed without impacting the quality of service”: Manipulations shall be risk-free (stopping/restarting the entire system and various components, etc.). On-site presence of highly skilled personnel shall be as reduced as possible.
Usability. 11-item questionnaire (10 items with 5-point Likert scale and 1 item with 10-point Likert scale) to assess the users’ interaction with app and interface of the system.
Usability. 4.10.1. The Supplier shall develop its training to meet user needs and the Digital Service Standards set out by the Government Digital Service.
4.10.2. The Supplier shall ensure that their products provide consistency of user experience within the CSL website. This includes ensuring that their products can be searched for or browsed within the existing Civil Service Learning website.
4.10.3. The Supplier shall ensure that Continuous Improvement is embedded across their processes and the Supplier shall be prepared to fully engage in continuous improvement initiatives that are initiated by CSL and its third-party suppliers.
