Wiki source code of 2. Socio-Cognitive Engineering

Version 9.1 by Rixt Hellinga on 2024/02/29 16:25

Hide last authors
Rixt Hellinga 7.1 1 The issue at hand, as discussed in previous chapters, requires a combination of human and robot solutions. To design and develop such a solution we can use the Socio-Cognitive Engineering (SCE) method. SCE provides a clear structure, consisting of a foundation, specification, and evaluation. It allows us to take into account stakeholders and their values, and create claims through functions, effects, and use cases. The incremental and iterative process taken in the SCE method combines human factors and related technology to form re-usable solutions.
Rixt Hellinga 6.1 2
Rixt Hellinga 7.1 3 Generally, technology does not work in isolation (1). In the context of our problem, the robot's environment, knowledge, and goals are intertwined with that of the human. SCE allows us to combine the human and technological aspects or our problem. Each of the involved parties (the robot, the subject, the guardian) can be modeled through the SCE method. Through methods such as user stories and value stories we can create a well-rounded description of a stakeholder and their goals. The difference in for example environments, abilities, and goals are easy to map out through SCE.
Rixt Hellinga 6.3 4
Rixt Hellinga 6.1 5
6
Rixt Hellinga 8.1 7
Rixt Hellinga 9.1 8 (1) Source: Week 3.1a slide 27.
Rixt Hellinga 6.1 9
Rixt Hellinga 4.9 10 **Questions to answer here:**
11
Rixt Hellinga 2.1 12 * Why do we use Socio-Cognitive Engineering? What are its aspect/perks and why is that applicable in our case?
Rixt Hellinga 4.9 13 * "How can the technology be designed such that the human is able to work with the technology?" - xwiki
Rixt Hellinga 2.2 14
Rixt Hellinga 4.9 15 **Short answer:**
Rixt Hellinga 4.1 16
Rixt Hellinga 4.9 17 We need an agent that takes care of some of the needs of Pwds. We cannot see these people outside of their environment and have to integrate that into our solution. so we need sce.
Rixt Hellinga 2.2 18
Rixt Hellinga 2.5 19 AI does not work in isolation. We have to integrate technology into human's work and living environment. Source: Week 3.1a slide 27. This Hybrid intelligence is situated (source slide 28). It's a combination of the agent, the human, and their environment, each of which practice self-regulation.
20
Rixt Hellinga 4.9 21 "Identifying the underlying motivation for an individual with dementia to engage in different activities is important for matching a person with activities that will be satisfying." (Han, A., Radel, J., McDowd, J. M., & Sabata, D. (2016). Perspectives of people with dementia about meaningful activities: a synthesis. American Journal of Alzheimer's Disease & Other Dementias, 31(2), 115-123) So we need SCE to identify these motivations and stuff.
22
23
24 **More explanation:**
25
26 //SCE//
27
Rixt Hellinga 4.3 28 * It provides a structure to work in (see the foundation, specification, evaluation image).
29 * It considers multiple stakeholders and their values.
30 * It uses user stories and value stories.
Rixt Hellinga 4.9 31 * It is incremental and iterative. (**Cyclic Process of Progression: **Source: after Carroll (2002), Figure 3.1, p. 68.)
Rixt Hellinga 4.3 32 * It uses ontologies and design patterns.
Rixt Hellinga 4.8 33 * It uses personas and problem scenarios, and scenario-based design.
Rixt Hellinga 4.3 34 * It uses use cases, functions, effects, and claims in the specification
Rixt Hellinga 4.7 35 * It is: (source Week 3.2b - SCEmodule2b_ScenarioBasedDesign2024 slide 4)
Rixt Hellinga 4.5 36 ** Iterative incremental process
37 *** Quick start
38 *** Focused refinement of core functions and design rationale
39 *** Coherent specification
40 ** Theory and empirical driven
41 ** Combined operational (domain), human factors and technology perspective
42 ** Stakeholder involvement in design and test activities
43 ** Producing re-usable design specifications and implementations
Rixt Hellinga 4.3 44
Rixt Hellinga 4.9 45 //HYBRID INTELLIGENCE GROWS BY...//
Rixt Hellinga 3.2 46
Rixt Hellinga 4.9 47 * Integrating technology into the situated practice via co-design by joint task performance and co-learning:
48 ** Common situated objectives
49 ** Value-sensitive agreements
50 ** Shared knowledge base & experiences
51 ** Mutual uptake & learning by explanation & feedback
52 * and is grounded by
53 ** Ontologies of the partnership
54 ** Collaboration patterns
55 ** Value models
Rixt Hellinga 4.2 56
Rixt Hellinga 4.9 57 //What is Human Centred design?//
Rixt Hellinga 2.5 58
Rixt Hellinga 6.3 59 * Usability
Rixt Hellinga 4.9 60 ** extent to which a system, product or service can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use
Rixt Hellinga 6.3 61 * Effectiveness
Rixt Hellinga 4.9 62 ** accuracy and completeness with which users achieve specified goals
Rixt Hellinga 6.3 63 * Efficiency
Rixt Hellinga 4.9 64 ** resources expended in relation to the accuracy and completeness with which users achieve goals
Rixt Hellinga 6.3 65 * Satisfaction
Rixt Hellinga 4.9 66 ** freedom from discomfort and positive attitudes towards the use of the product
Rixt Hellinga 6.3 67 * Context of use
Rixt Hellinga 4.9 68 ** users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a product is used
Rixt Hellinga 6.3 69 * User experience
Rixt Hellinga 4.9 70 ** person's perceptions and responses resulting from the use and/or anticipated use of a product, system or service
Rixt Hellinga 6.3 71 * Stakeholder
Rixt Hellinga 4.9 72 ** individual or organization having a right, share, claim or interest in a system or in its possession of characteristics that meet their needs and expectations
Rixt Hellinga 2.6 73
Rixt Hellinga 4.9 74