User scenarios Sample Clauses

User scenarios. Four user scenarios are illustrated to show how the add-on services work to- gether in the Go-Lab portal. They can be seen as a whole. Scenario AO-1: Xxxx is a school teacher and wants to give his students a physics class with an online lab on buoyancy. He logs in to the ILS platform and creates an inquiry learning space. He adds the WebLab Aquarium remote lab into his ILS to investigate the density of fluids. He wants to demonstrate the We- bLab Aquarium to his students during one of his physics classes on Wednesday morning in one of the coming three weeks. Thus, Xxxx goes to the lab repos- itory, browses to the detailed description page of this lab and clicks the “How to book” button. After which he follows a wizard with instructions how to book the lab and clicks the button “Book the lab”. A calendar of WebLab Aquarium pops up and shows there is only one time slot available in two weeks that fits his physics class. He books it right away by adding the class name and number of students. He is notified that 3 remote lab instances are recommended and booked for his class of 25 students. He also receives an email and notification in his inquiry learning space which hosts this lab. During his class, he connects to the lab transparently without further setup and is able to use the remote lab user interface with his students to control different objects floating or sinking in the aquarium to observe the force. Scenario AO-2: The next days, Xxxx finds it would be nice if he could show some live observation of the galaxy during his physics class. In the Go-Lab lab repository, he finds the Faulkes Telescope lab. Again, he clicks the “How to book” button and gets an instructional page that describes that he first has to go to the Faulkes project web site and register. After registration, he should send an email to the Faulkes project team to book a time session. With this clear booking process instruction on the Go-Lab portal, Xxxx is able to book a session with the Faulkes project team smoothly. Xxxx finds it convenient that the lab repository provides guidelines to book this specific lab. Scenario AO-3: Another school teacher, Xxxx, wants to use WebLab Aquar- ium on the next day. However, WebLab Aquarium is already booked by other users and is not available for her class. Xxxx searches on the lab repository by inputting her class time and the class subject. A list of labs available at the requested time and for her topic is shown. Xxxx is glad to find one and bo...
Sample 1
AutoNDA by SimpleDocs
User scenarios. Usage scenarios contribute a value in guiding the conversation during the design process, giving it context and scope. They indicate what to include, exclude, how wide, how deep to go, when to stop and they provide variations to test the design. User scenarios can be used during many stages of a system development, being associated with different objectives. Used at the analysis stage, they can prevent costly error corrections at later stages of the development. At the current stage, user scenarios will serve as a guiding tool to identify, preview and analyse the functionalities of the BOUNCE system, as well as to determine the technical requirements, both functional and non-functional, of the system being developed. The interaction steps of BOUNCE end users with BOUNCE system throughout the breast cancer treatment continuum, e.g. the collection of different types of data and the resilience assessment after diagnosis and at regular visits, as identified during the user requirements procedure (reported in D1.2) are summarized in Figure 3. Figure 3: Steps in the BOUNCE care path The following BOUNCE User Scenarios have been identified, and reported in detail in D1.2, per end users of the BOUNCE system (oncologist, nurse, social-worker, psychologist, patient, developer):
Sample 1
User scenarios. The scenarios outlined below are only simplified examples and should be considered as first reference to e-business processes only. Within the REGNET-Project there will be an own Work Package dealing with the elaboration of business cases (functions and processes) based on actual needs of all relevant partners within the Cultural Heritage domain.
Sample 1

Related to User scenarios

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Programming Phase 2.2.1.2. Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4.

  • Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Escorting Visitors Visitors to areas where PHI COUNTY discloses to 4 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY is 5 contained shall be escorted and such PHI shall be kept out of sight while visitors are in the area.

  • Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.

Time is Money Join Law Insider Premium to draft better contracts faster.