Skip to Content
1 Votes
Version 18.1 by Dongxu Lu on 2023/03/28 14:30
Show last authors
1 === **Principles** ===
2
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
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
10
11 === **Origin** ===
12
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:
14
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.
18
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
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]]).
24
25 === **Method** ===
26
27 [[image:/xwiki/bin/download/Main/WebHome/SCE.PNG?rev=1.1||alt="SCE.PNG"]]**[[image:attach:SCE.PNG]]**
28
29 * The **Foundation **describes the
30 ** //Operational Demands// (e.g., stakeholders' values and needs, problem scenarios, work context),
31 ** //Technology //that will be used and/or (further) developed (e.g., cloud computing, AI frameworks) and
32 ** //Human Factors// knowledge that should be addressed in the design and evaluation of the technology to meet the operational demands.
33 * The **Specification **defines the
34 ** //Objectives//: the target outcomes
35 ** //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),
36 ** //Function //(requirement), i.e., what the machine shall do to serve the objectives in the corresponding use cases,
37 ** //Claim//, specifying the expected //Effect //of the situated Function (i.e., situated in the use case) to provide the justification (why).
38 * The **Evaluation **provides the outcomes of the tests with the Prototype and/or Simulation.
39
40 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 generated behavioral and declarative design knowledge is formalized and maintained for re-use and sharing via, respectively, **Design Patterns** and a corresponding **Ontology**.
41
42 Detailed information on the methodology can be found in the [[publications section>>url:https://scetool.ewi.tudelft.nl/?q=node/5]] of this site.
43
44 === References ===
45
46
47 |1.|[[1 >>url:https://confluence.ewi.tudelft.nl/display/SE/SCE+Example+Home#cite-1-1]](((
48 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]].
49 )))