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 12.1
edited by Dongxu Lu
on 2023/03/24 10:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,7 +16,6 @@
16 16  1. The **specification **of the objectives, use cases, functions (requirements) and the (expected) effects (//claims//).
17 17  1. The **evaluation **validates these //claims// and advances the foundation knowledge.
18 18  
19 -
20 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 21  
22 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,6 +23,23 @@
23 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  
25 +=== **Method** ===
26 +
27 +* The **Foundation **describes the
28 +** //Operational Demands// (e.g., stakeholders values and needs, problem scenarios, work context),
29 +** //Technology //that will be used and/or (further) developed (e.g., cloud computing, AI frameworks) and
30 +** //Human Factors// knowledge that should be addressed in the design and evaluation of the technology to meet the operational demands.
31 +* The **Specification **defines the
32 +** //Objectives//: the target outcomes
33 +** //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),
34 +** //Function //(requirement), i.e., what the machine shall do to serve the objectives in the corresponding use cases,
35 +** //Claim//, specifiying the expected //Effect //of the situated Function (i.e., situated in the use case) to provide the justification (why).
36 +* The **Evaluation **provides the outcomes of the tests with the Prototype and/or Simulation.
37 +
38 +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**.
39 +
40 +Detailed information on the methodology can be found in the [[publications section>>url:https://scetool.ewi.tudelft.nl/?q=node/5]] of this site.
41 +
26 26  === References ===
27 27  
28 28