User interface requirements Sample Clauses

User interface requirements. The user interface of the system should provide the end-users with the means to collaborate on, consume and reason about the raw and derived data streams as well as to manipulate and create new data stream computation instances. Using graphical and multi-modal query languages, the complexities of the underlying, textual query language are hidden from the end-users for a more intuitive access to the information contained within the data streams. Call for Action Express / Refine queries Set of queries for DSMS Suitable interaction conceptualizations are to be researched, taking into account the different use cases and scenarios in which the system is utilized, as well as the challenges arising from the volatile and real-time nature of the underlying data streams. The interaction conceptualizations are to be integrated into a collaboration tool, for multiple end-users with their roles to reason about the information and coordinate and agree upon and take actions. Furthermore part of the user interface will use appropriate modalities to notify end-users proactively about noteworthy occurrences regarding the system's state with respect to the users' observable activities. The collaborative visual environment should enable two different types of interactions, providing support to: 1. synchronous collaboration between co-located users 2. asynchronous distributed collaboration between remote users To support these tasks and enable collaboration among different workers, the user interface has to identify and provide accessible, flexible and editable artifacts for both individual-based and group- based exploration of data streams. This requires the definition of a group interaction space for collaborative data analysis, where users can interactively access data streams, as well as create, layout, arrange and share artifacts connected with data streams. Each artifact should be enriched with contextual information (such as labels, scales, legends, etc.) that allows users to correctly interpret the information being displayed. Users collaborating in a shared group interaction space should be able to jointly interact with a single shared view of data streams, or to create different views of the same data streams in a personalized workspace that can optionally be shared with other participants and mapped to or fuse with other views. By enabling the sharing and coordination of multiple views of data streams in a common workspace, the visual environment allows users with d...
AutoNDA by SimpleDocs
User interface requirements. 6.1 Users shall be able to view the position of their fleet vehicles at any point of time via a standard web browser (eg. Microsoft Internet explorer, version 8.0 (or later)) on their personal computer. The primary display shall be a map view of state wide fleet vehicles as well in individual regions via login passwords 6.2 The system shall allow viewing of a vehicle in motion leaving tracks or "breadcrumbs" as it travels showing all operations (GPS & Telematic data) as they occur. Users shall be able to view the above mentioned data for their entire fleet or select a specific vehicle(s) for a login session using a Filter Tool. Unit Max Max 6.3 The map display shall be such that vehicle position and status automatically updates on screen without any input from the end-user. Additionally, end-users shall be able to view the status of monitored on-board vehicle equipment with each fix or report. 6.4 The system must have an easy "intuitive" navigation sequence (i.e. navigator bar and/or tabs for easy access to various functional screens). Tools shall include but not be limited to: Map navigational tools (zoom in/out, center, pan, etc.); Automatic Vehicle Location Tool; Breadcrumbs; Filter Tool; Historical Data; and Reports. 6.5 User shall have options to select from different map views of the map in order to accommodate varying business requirements, desktop equipment performance, and Internet connectivity.
User interface requirements. 6.1 Users shall be able to view the position of their fleet vehicles at any point of time via a standard web browser (eg. Microsoft Internet explorer, version 8.0 (or later)) on their personal computer. The primary display shall be a map view of state wide fleet vehicles as well in individual regions via login passwords 6.2 The system shall allow viewing of a vehicle in motion leaving tracks or "breadcrumbs" as it travels showing all operations (GPS & Telematic data) as they occur. Users shall be able to view the above mentioned data for their entire fleet or select a specific vehicle(s) for a login session using a Filter Tool. Unit Max Max 6.3 The map display shall be such that vehicle position and status automatically updates on screen without any input from the end-user. Additionally, end-users shall be able to view the status of monitored on-board vehicle equipment with each fix or report.

Related to User interface requirements

  • Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Maintenance Requirements The Contractor shall ensure and procure that at all times during the Maintenance Period, the Project Highway conforms to the maintenance requirements set forth in Schedule-E (the “Maintenance Requirements”).

  • CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.

  • Service Requirements Grantee shall:

  • Project Requirements 1. Project must conform to regulations under 24 CFR Part 92, commonly known as the HOME Regulations.

  • DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-­‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.

  • Subcontract Requirements As required by Section 6.22(e)(5) of the Administrative Code, Contractor shall insert in every subcontract or other arrangement, which it may make for the performance of Covered Services under this Agreement, a provision that said subcontractor shall pay to all persons performing labor in connection with Covered Services under said subcontract or other arrangement not less than the highest general prevailing rate of wages as fixed and determined by the Board of Supervisors for such labor or services.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!