1 Votes

Wiki source code of 0. Wiki Socio-Cognitive Engineering

Last modified by Mark Neerincx on 2025/04/17 14:02

version	line-number	content
11.1	1	=== Principles ===
4.1	2
11.1	3	The development of interactive, human-centered automation should be built on theory and empirical research. To support the research & development processes systematically, a Socio-Cognitive Engineering (SCE) method was constructed for building, maintaining and re-using design knowledge based on the following principles:
4.1	4
11.1	5	* Creating human-centered automation is a multi-disciplinary collaborative activity
	6	* Functional modules are defined and tested incrementally in an iterative refinement process
	7	* Design decisions are explicitly based on claims analyses, explicating the up-downside tradeoffs
	8	* Keeping and sharing the design rationale is key for progress and coherence in automation development
	9
4.1	10
11.1	11	=== Origin ===
4.1	12
11.1	13	In an international project, the European Space Agency asked to establish a sound requirements baseline for a "Mission Execution Crew Assistant" (MECA) for future manned deep space missions (e.g. to Mars). As a concise method was lacking for the research & development of the envisioned human-automation system, the first version of the SCE methodology was constructed and applied. This methodology combines approaches from user-centered design, cognitive engineering and requirements analyses to establish a coherent "self-explaining" requirements baseline consisting of:
4.1	14
11.1	15	1. The foundation that captures the relevant domain, human factors and technological knowledge.
	16	1. The specification of the objectives, use cases, functions (requirements) and the (expected) effects (//claims//).
	17	1. The evaluation validates these //claims// and advances the foundation knowledge.
4.1	18
11.1	19	The SCE activities that provide these outcomes can be performed in parallel. At "some time" they will be integrated into an evaluation (i.e., a prototype or simulation). For this we distinguish development cycles. Each development cycle provides a next version of a prototype. Milestones are specified for the SCE outcomes that need to be finished for such an evaluation (//note~:// a demonstration can be viewed as a very minimal evaluation).
	20
	21	For agile R&D, SCE defines the Minimal Viable Product (MVP) as a coherent and concise set of (interim) SCE outcomes, i.e. a coherent set of milestones that lead to the envisioned prototype or simulation.
	22
9.1	23	WiSCE is the successor to the Socio-Cognitive Engineering Tool (SCET) that was hosted on Atlassian Confluence. WiSCE provides design rationale templates and links design concepts to each other (see the [[SCE Guide>>url:https://confluence.ewi.tudelft.nl/display/SG]]). The top menu of WiSCE shows the SCE components (i.e., the "boxes" of the Figure: Foundation, Specification and Evaluation), the "meta-models" (i.e., Ontology and Design Patterns, and reference items. General information about the Socio-Cognitive Engineering methodology can be found at [[http:~~/~~/scetool.ewi.tudelft.nl/;>>url:https://confluence.ewi.tudelft.nl/pages/removepage.action?pageId=59539816]] an example application is provided by Neerincx et al. [[^^~[1~] ^^>>url:https://confluence.ewi.tudelft.nl/display/SE/SCE+Example+Home#cite-summary-1-1]]([[https:~~/~~/doi.org/10.3389/frobt.2019.00118>>url:https://doi.org/10.3389/frobt.2019.00118]]).
4.1	24
12.1	25	=== Method ===
	26
35.1	27	[[image:1707214691818-893.png\|\|height="328" width="608"]]
27.1	28
24.1	29	Figure: Socio-Cognitive Engineering method (SCE) with three main components (Foundation, Specification and Evaluation) and the underlying or abstracted behavioral & declarative design knowledge (resp. design patterns and ontology).
	30
12.1	31	* The Foundation describes the
22.1	32	** //Operational Demands// (e.g., stakeholders values and needs, problem scenarios, work context),
12.1	33	** //Technology //that will be used and/or (further) developed (e.g., cloud computing, AI frameworks) and
	34	** //Human Factors// knowledge that should be addressed in the design and evaluation of the technology to meet the operational demands.
	35	* The Specification defines the
	36	** //Objectives//: the target outcomes
	37	** //Use cases//: how the human-machine collaboration takes place, i.e., the structure and flow of actors' actions with the task allocations (who, when, where),
	38	** //Function //(requirement), i.e., what the machine shall do to serve the objectives in the corresponding use cases,
22.1	39	** //Claim//, specifiying the expected //Effect //of the situated Function (i.e., situated in the use case) to provide the justification (why).
12.1	40	* The Evaluation provides the outcomes of the tests with the Prototype and/or Simulation.
	41
36.1	42	The SCE method is iterative in nature, which means that usually several cycles of designing and testing are required to eventually arrive at a prototype or simulation. The identified human needs, generated behavioral and declarative design knowledge is formalized and maintained for re-use and sharing via, respectively, Values, Design Patterns and corresponding Ontologies.
12.1	43
	44	Detailed information on the methodology can be found in the [[publications section>>url:https://scetool.ewi.tudelft.nl/?q=node/5]] of this site.
	45
4.1	46	=== References ===
	47
	48
	49	\|1.\|[[1 >>url:https://confluence.ewi.tudelft.nl/display/SE/SCE+Example+Home#cite-1-1]](((
7.1	50	Neerincx, M.A. //et al.// (2019). “Socio-Cognitive Engineering of a Robotic Partner for Child’s Diabetes Self-Management,” //Frontiers in Robotics and AI//, vol. 6, [[https:~~/~~/doi.org/10.3389/frobt.2019.00118>>url:https://doi.org/10.3389/frobt.2019.00118]].
4.1	51	)))