Changes for page 2. Socio-Cognitive Engineering

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,37 +1,69 @@
	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	+
	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	+
	5	+
	6	+**Questions to answer here:**
	7	+
1	1	* 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
2	2
	11	+**More explanation:**
3	3
4		-What is Human Centred design?
	13	+//SCE//
5	5
6		-**Usability**
7		-extent to which a system, product or service can
8		-be used by specified users to achieve specified
9		-goals with effectiveness, efficiency and
10		-satisfaction in a specified context of use
11		-**Effectiveness**
12		-accuracy and completeness with which users
13		-achieve specified goals
14		-**Efficiency**
15		-resources expended in relation to the accuracy
16		-and completeness with which users achieve
17		-goals
18		-**Satisfaction**
19		-freedom from discomfort and positive attitudes
20		-towards the use of the product
21		-**Context of use**
22		-users, tasks, equipment (hardware, software and
23		-materials), and the physical and social
24		-environments in which a product is used
25		-**User experience**
26		-person's perceptions and responses resulting from
27		-the use and/or anticipated use of a product, system
28		-or service
29		-**Stakeholder**
30		-individual or organization having a right, share,
31		-claim or interest in a system or in its possession of
32		-characteristics that meet their needs and
33		-expectations
	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
34	34
	32	+//HYBRID INTELLIGENCE GROWS BY...//
35	35
	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
36	36
37		-**Cyclic Process of Progression: **Source: after Carroll (2002), Figure 3.1, p. 68.
	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	+= **//References//** =
	64	+
	65	+[1] Week 3.1a slide 27.
	66	+
	67	+[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)
	68	+
	69	+