User scenarios Sample Clauses

User scenarios. The following user scenarios highlight how the stakeholders can benefit from the learning analytics services within the Go-Lab portal and apps. Scenario LA-1: Learning analytics for the lab repository. Physics teacher Xxxxxx is recommended by his colleagues to check out the Go-Lab lab repos- itory to engage his students more in his course. On the landing page Xxxxxx finds a set of the most popular labs, apps and shared ILS. Xxxxxx is attracted by a lab on radioactivity because he cannot do such an experiment in his class- room. On the detail page of this lab, he finds next to more detailed information on the lab, a wide variety of additional resources he can use in combination with the lab. For instance, there is an available list of the most used inquiry learning apps that other teachers have used together with this lab in their ILS. Further- more, a list of popular ILS created by other teachers using this lab is shown, where Xxxxxx can check what learning activities other teachers created. In a sidebar some statistics are shown that illustrate how often and when the lab has been used as well as a small map to illustrate where. Xxxxxx sees that this lab is actually used most in his country so he assumes it will be well aligned with his curriculum. Next to this, there is a list of experts who can assist him with this lab. He discovers that some of them are fellow teachers who have taught sev- eral courses with the lab and even the software developer of the lab is available. For now Xxxxxx decides to try things out before requesting help and creates an ILS with this lab. Scenario LA-2: Learning analytics on the ILS platform level. While Nor- man builds an ILS in the portal for his upcoming lesson, he is adding relevant material. Xxxxxx wants to monitor the progress of his students and see how much time each student spent on the single phases of the inquiry learning cycle and whether some students are left behind. Additionally he wants to see which learning resources are used by his students. Therefore Xxxxxx searches the lab repository and finds two apps that visualise the time spend in phases and statistics on resource usage. Now he can assemble a teacher dashboard from these analytics apps in a dedicated subspace of his ILS. The analytics apps re- quire the tracking of the user activities inside the ILS. This is done by a dedicated user tracking agent. This agent is an artificial space member, and hence can access all activities inside the ILS. It can be ...
AutoNDA by SimpleDocs
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.
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):

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.

  • 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.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • 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.

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