Skip to Content
Last modified by Rixt Hellinga on 2024/04/08 18:40
From version 5.1
edited by Rixt Hellinga
on 2024/02/29 09:18
Change comment: There is no comment for this version
To version 6.3
edited by Rixt Hellinga
on 2024/02/29 16:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,3 +1,14 @@
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, through methods such as user stories and value stories. The incremental and iterative process taken in the SCE method combines human factors and related technology to form re-usable solutions.
2 +
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. 
4 +
5 +
6 +what is it -> see description
7 +
8 +why do we need it -> because robots are not in isolation
9 +
10 +(1) Source: Week 3.1a slide 27. This Hybrid intelligence is situated (source slide 28)
11 +
1 1  **Questions to answer here:**
2 2  
3 3  * Why do we use Socio-Cognitive Engineering? What are its aspect/perks and why is that applicable in our case?
... ... @@ -33,7 +33,6 @@
33 33  ** Stakeholder involvement in design and test activities
34 34  ** Producing re-usable design specifications and implementations
35 35  
36 -
37 37  //HYBRID INTELLIGENCE GROWS BY...//
38 38  
39 39  * Integrating technology into the situated practice via co-design by joint task performance and co-learning:
... ... @@ -46,25 +46,21 @@
46 46  ** Collaboration patterns
47 47  ** Value models
48 48  
49 -
50 -
51 51  //What is Human Centred design?//
52 52  
53 -* **Usability**
61 +* Usability
54 54  ** 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
55 -* **Effectiveness**
63 +* Effectiveness
56 56  ** accuracy and completeness with which users achieve specified goals
57 -* **Efficiency**
65 +* Efficiency
58 58  ** resources expended in relation to the accuracy and completeness with which users achieve goals
59 -* **Satisfaction**
67 +* Satisfaction
60 60  ** freedom from discomfort and positive attitudes towards the use of the product
61 -* **Context of use**
69 +* Context of use
62 62  ** users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a product is used
63 -* **User experience**
71 +* User experience
64 64  ** person's perceptions and responses resulting from the use and/or anticipated use of a product, system or service
65 -* **Stakeholder**
73 +* Stakeholder
66 66  ** 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
67 67  
68 -
69 -
70 70