User Interfaces Clause Samples
The 'User Interfaces' clause defines the requirements and standards for the design, functionality, and accessibility of interfaces through which users interact with a product or service. It typically outlines expectations for usability, compatibility with various devices or platforms, and may specify compliance with accessibility guidelines such as those for users with disabilities. By setting these parameters, the clause ensures that end-users have a consistent, effective, and accessible experience, reducing the risk of misunderstandings or barriers to use.
User Interfaces. Prior to launch of any Information Service, LICENSOR will submit the user interface for such Information Service to AT&T for review and approval or disapproval.
User Interfaces. There are two distinct user interfaces associated with the CDN Services:
3.2.1 Partner Control Center (PCC) – An optional web accessible user interface provided to large enterprise customers to provision CDN sub-accounts to separate billing, reporting and analytics screens for different departments or web properties within the parent organization. There is a monthly recurring fee for each Partner Control Center deployed.
3.2.2 Media Control Center (MCC) – Used to configure and monitor a single web property. Through the MCC, webmasters configure their accounts, upload and purge files to the CDN and monitor their end user’s access to their web site with the MCC’s reporting and analytics package (see below).
User Interfaces. Activities Business Objects Business Objects Interface Proxies Interface Proxies Naming/ Trading Service Transaction Service Workflow Facility Solution Component Solution Component Interface Skeletons Interface Skeletons Activities Activities Business Objects Interface Proxies Business Objects Interface Proxies Extent Extent Application Application
User Interfaces. All users will interact with PACIS II via a Graphical User Interface (GUI).
User Interfaces. The default language for Acsepto and CTM download user interfaces (messages and screens, online documentation) is English.
User Interfaces. It is of utmost importance for a solution to have a wide range of user interfaces allowing a convenient interaction with the testbed. We present here the major ones classified by category. It is important that any singular testbed belonging to the federation can use its own user interfaces and still have access to the federated resources. This is not compatible to the possibility of having an extra UI shared by the federated testbeds. • sfi.py (in the Generic SFA wrapper codebase) • omni: ▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇.▇▇▇.▇▇▇/gcf/wiki/Omni • sfaclientlib (in the Generic SFA wrapper codebase) • java client library [no url] • sface: ▇▇▇▇://▇▇▇.▇▇▇▇▇▇.▇▇/?p=▇▇▇▇▇.▇▇▇;a=summary • MySlice (recommended): ▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇.▇▇▇▇ (see Section 4.4) • ▇▇▇▇▇▇ webUI (now integrated with the current clearinghouse implementation)
User Interfaces. User interfaces must be developed for the functions described in Section 4. Standard drop-down lists are used wherever possible to present standard values for selection by the User. Command buttons, Pop-up windows, and other aids should be used where possible to make the product easier to use. Online help should be available for each screen developed for this application. Web page formats must follow the State of Washington guidelines found at the following web site: Information Technology Division March 16, 2010 Page 12 Planning and Project Office SRS version 2.1 This section specifies the functional capabilities of the product. These requirements are organized by the major functions described in section 2.2.
User Interfaces. The main user interface to Porto is a scripting shell based on ECMAScript. It will be possible to use the scripting both as batch processes and as an interactive process. Different Porto-modules and extensions can be loaded at run-time.
User Interfaces. 1) The system will normally be operated through a remote interface using a SCADA setup based on the Cromi software.
2) In Cromi, the communication of variables is based on OPC connection between the SCADA server software and the high level control system (Schneider PLC) and data is logged into SQL database (local, remote or both).
3) A cloud based SQL database will be set up that will allow the project stakeholders to access the operational data over the internet.
4) VTT has Matlab scripts written for extracting the data from the SQL database that may be shared to the project participants. Participants may also develop their own tools to access the data on the server, if preferred.