Skip to Content
Last modified by Rixt Hellinga on 2024/04/08 18:40
From version 6.1
edited by Rixt Hellinga
on 2024/02/29 15:41
Change comment: There is no comment for this version
To version 15.2
edited by Rixt Hellinga
on 2024/03/19 22:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,74 +1,23 @@
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) framework. SCE provides an iterative and incremental
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 is a framework that among other things promotes human collaboration and learning with technology-based systems [3].
2 2  
3 -what is it -> see description
3 +It 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.
4 4  
5 -why do we need it -> because robots are not in isolation
5 +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. Within different fields of studies we can find relevant philosophies and approaches applicable to our problem.
6 6  
7 +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 PwD, 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.--
7 7  
8 -**Questions to answer here:**
9 +//Computer science//
9 9  
10 -* Why do we use Socio-Cognitive Engineering? What are its aspect/perks and why is that applicable in our case?
11 -* "How can the technology be designed such that the human is able to work with the technology?" - xwiki
11 +//Cognitive science//
12 12  
13 -**Short answer:**
13 +//User centerd design//
14 14  
15 -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.
15 +[[https:~~/~~/www.researchgate.net/publication/32231480_Socio-cognitive_Engineering>>https://www.researchgate.net/publication/32231480_Socio-cognitive_Engineering]] [3]
16 16  
17 -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.
17 += **//References//** =
18 18  
19 -"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.
19 +[1] Week 3.1a slide 27.
20 20  
21 +[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)
21 21  
22 -**More explanation:**
23 -
24 -//SCE//
25 -
26 -* It provides a structure to work in (see the foundation, specification, evaluation image).
27 -* It considers multiple stakeholders and their values.
28 -* It uses user stories and value stories.
29 -* It is incremental and iterative. (**Cyclic Process of Progression: **Source: after Carroll (2002), Figure 3.1, p. 68.)
30 -* It uses ontologies and design patterns.
31 -* It uses personas and problem scenarios, and scenario-based design.
32 -* It uses use cases, functions, effects, and claims in the specification
33 -* It is: (source Week 3.2b - SCEmodule2b_ScenarioBasedDesign2024 slide 4)
34 -** Iterative incremental process
35 -*** Quick start
36 -*** Focused refinement of core functions and design rationale
37 -*** Coherent specification
38 -** Theory and empirical driven
39 -** Combined operational (domain), human factors and technology perspective
40 -** Stakeholder involvement in design and test activities
41 -** Producing re-usable design specifications and implementations
42 -
43 -//HYBRID INTELLIGENCE GROWS BY...//
44 -
45 -* Integrating technology into the situated practice via co-design by joint task performance and co-learning:
46 -** Common situated objectives
47 -** Value-sensitive agreements
48 -** Shared knowledge base & experiences
49 -** Mutual uptake & learning by explanation & feedback
50 -* and is grounded by
51 -** Ontologies of the partnership
52 -** Collaboration patterns
53 -** Value models
54 -
55 -
56 -//What is Human Centred design?//
57 -
58 -* **Usability**
59 -** 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
60 -* **Effectiveness**
61 -** accuracy and completeness with which users achieve specified goals
62 -* **Efficiency**
63 -** resources expended in relation to the accuracy and completeness with which users achieve goals
64 -* **Satisfaction**
65 -** freedom from discomfort and positive attitudes towards the use of the product
66 -* **Context of use**
67 -** users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a product is used
68 -* **User experience**
69 -** person's perceptions and responses resulting from the use and/or anticipated use of a product, system or service
70 -* **Stakeholder**
71 -** 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
72 -
73 -
74 74  
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