Last modified by Rixt Hellinga on 2024/04/08 18:40

From version 4.3
edited by Rixt Hellinga
on 2024/02/29 08:55
Change comment: There is no comment for this version
To version 14.2
edited by Mark Neerincx
on 2024/03/18 15:53
Change comment: Added comment

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.RixtHellinga
1 +xwiki:XWiki.MarkNeerincx
Content
... ... @@ -1,68 +1,11 @@
1 -* Why do we use Socio-Cognitive Engineering? What are its aspect/perks and why is that applicable in our case?
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.
2 2  
3 -"How can the technology be designed such that the human is able to work with the technology?" - xwiki
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. According to [2] it is important to map the underlying motivation of parties in order to understand which activities they would be drawn to. 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.
4 4  
5 -**SCE**
5 += **//References//** =
6 6  
7 -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.
7 +[1] Week 3.1a slide 27.
8 8  
9 -* It provides a structure to work in (see the foundation, specification, evaluation image).
10 -* It considers multiple stakeholders and their values.
11 -* It uses user stories and value stories.
12 -* It is incremental and iterative.
13 -* It uses ontologies and design patterns.
14 -* It uses use cases, functions, effects, and claims in the specification
9 +[2] 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)
15 15  
16 -**HYBRID INTELLIGENCE GROWS BY...**
17 -Integrating technology into the situated practice via co-design by joint task performance and co-learning:
18 -
19 -* Common situated objectives
20 -* Value-sensitive agreements
21 -* Shared knowledge base & experiences
22 -* Mutual uptake & learning by explanation & feedback
23 -
24 -and is grounded by
25 -
26 -* Ontologies of the partnership
27 -* Collaboration patterns
28 -* Value models
29 -
30 -
31 -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.
32 -
33 -
34 -
35 -What is Human Centred design?
36 -
37 -**Usability**
38 -extent to which a system, product or service can
39 -be used by specified users to achieve specified
40 -goals with effectiveness, efficiency and
41 -satisfaction in a specified context of use
42 -**Effectiveness**
43 -accuracy and completeness with which users
44 -achieve specified goals
45 -**Efficiency**
46 -resources expended in relation to the accuracy
47 -and completeness with which users achieve
48 -goals
49 -**Satisfaction**
50 -freedom from discomfort and positive attitudes
51 -towards the use of the product
52 -**Context of use**
53 -users, tasks, equipment (hardware, software and
54 -materials), and the physical and social
55 -environments in which a product is used
56 -**User experience**
57 -person's perceptions and responses resulting from
58 -the use and/or anticipated use of a product, system
59 -or service
60 -**Stakeholder**
61 -individual or organization having a right, share,
62 -claim or interest in a system or in its possession of
63 -characteristics that meet their needs and
64 -expectations
65 -
66 -
67 -
68 -**Cyclic Process of Progression: **Source: after Carroll (2002), Figure 3.1, p. 68.
11 +
XWiki.XWikiComments[0]
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.MarkNeerincx
Comment
... ... @@ -1,0 +1,1 @@
1 +Maybe you can add something on the integration of disciplines and distributed R&D activities?
Date
... ... @@ -1,0 +1,1 @@
1 +2024-03-18 15:53:47.866