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. The following user scenarios highlight how the stakeholders can benefit from the learning analytics services within the Go-Lab portal and apps. in order to control the tracking of user activities. Hence, before the course ses- sion starts Xxxxxx makes sure that the tracking agent is member of the space as an observer. After Xxxxxx has successfully finished the ILS, he shares a secret URL with his students so they can access the ILS. During the session, he realises by observing the teacher dashboard, that students that have used the reading material in the orientation phase finish the experimentation phase more quickly with better results. After the course is over he recommends these reading materials to his colleagues who create similar ILS. After class, the teacher wants to review the previous session in order to detect potential lack of knowledge of the students and to get information on how future sessions can be improved. As described in scenario LA-2, he has added some pre-configured analytics apps to his personal space. He uses one of these apps to investigate individual concept maps created by the students but also an ag- gregated concept map which is an overlay of all created maps. This helps him to detect a common misunderstanding of the relation between electric current and voltage especially in the early phase of the session. Additionally, another analytics app that displays frequent sequential patterns of student actions while interacting with the lab, displays that many of the students do not adjust the voltmeter after they adjusted the resistors. This convinces him that his students have a common misconception of the relations between electric current, voltage and the influence of resistors and he decides to revise these things again in with his students in the next class.
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. 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.
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. 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):
1. Oncologist/nurse/social worker: Assesses the need for referral to the psychological Team/Unit.
2. Oncologist/nurse/psychologist/social worker: Assesses patient progress on psychological functioning/well-being and resilience levels.
3. Oncologist/social worker: Assesses likely impact of patient biomedical and psychological characteristics and resilience levels on overall adaptation to illness.
4. Psychologist/social worker: Assesses patient resilience levels and/or psychological well- being in order to inform the patient and the medical team.
