Skip to Content
Last modified by Rixt Hellinga on 2024/04/08 18:40
From version 13.1
edited by Rixt Hellinga
on 2024/03/15 17:24
Change comment: There is no comment for this version
To version 14.1
edited by Rixt Hellinga
on 2024/03/15 17:25
Change comment: There is no comment for this version

Summary

Details

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