Skip to Content
1 Votes
Last modified by Mark Neerincx on 2025/04/17 14:02
From version 11.1
edited by Dongxu Lu
on 2023/03/21 12:33
Change comment: There is no comment for this version
To version 10.1
edited by Dongxu Lu
on 2023/03/21 12:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,26 +1,18 @@
1 -=== **Principles** ===
1 +This space provides an overview and short examples of the **Wiki Socio-Cognitive Engineering (WiSCE) tool,** which is built and maintained in XWiki (a wiki content tool for teams to collaborate and share knowledge efficiently). WiSCE provides guidance and structure for capturing, maintaining and refining functional (user) requirements with the design rationale, in addition to providing [[a library of validated team and interaction design patterns>>tdplibrary:Main.WebHome]]. 
2 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:
3 +The SCE methodology entails an iterative incremental research and development (R&D) process of human-agent systems with an explicit description of the design rationale. The methodology distinguishes three main components, each providing specific R&D outcomes (see Figure):
4 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 -
5 +* **Foundation**: Operational Demands, Technology and Human Factors.
6 +* **Specification**: Objective, Use Case, Function (requirement) and Effect (claim).
7 +* **Evaluation**: Prototype and Simulation (test).
10 10  
11 -=== **Origin** ===
9 +[[image:https://confluence.ewi.tudelft.nl/download/attachments/56033679/image2021-1-25_14-31-59.png?version=1&modificationDate=1612194452000&api=v2||height="250"]]
12 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 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.
12 +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).
18 18  
14 +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.
19 19  
20 -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).
21 -
22 -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.
23 -
24 24  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]]).
25 25  
26 26  === References ===