Skip to Content
1 Votes
Last modified by Mark Neerincx on 2025/04/17 14:02
From version 31.1
edited by Dongxu Lu
on 2023/04/20 21:00
Change comment: There is no comment for this version
To version 21.1
edited by Dongxu Lu
on 2023/03/28 14:31
Change comment: Rollback to version 18.1

Summary

Details

Page properties
Content
... ... @@ -24,19 +24,10 @@
24 24  
25 25  === **Method** ===
26 26  
27 -{{html}}
28 -</td>
29 -<td>
30 -<img src="https://xwiki.ewi.tudelft.nl/xwiki//xwiki/bin/download/Main/WebHome/SCE.PNG?rev=1.1">
31 -</td>
32 -</tr>
33 -</table>
34 -{{/html}}
27 +[[image:/xwiki/bin/download/Main/WebHome/SCE.PNG?rev=1.1||alt="SCE.PNG"]]**[[image:attach:SCE.PNG]]**
35 35  
36 -**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).
37 -
38 38  * The **Foundation **describes the
39 -** //Operational Demands// (e.g., stakeholders values and needs, problem scenarios, work context),
30 +** //Operational Demands// (e.g., stakeholders' values and needs, problem scenarios, work context),
40 40  ** //Technology //that will be used and/or (further) developed (e.g., cloud computing, AI frameworks) and
41 41  ** //Human Factors// knowledge that should be addressed in the design and evaluation of the technology to meet the operational demands.
42 42  * The **Specification **defines the
... ... @@ -43,7 +43,7 @@
43 43  ** //Objectives//: the target outcomes
44 44  ** //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),
45 45  ** //Function //(requirement), i.e., what the machine shall do to serve the objectives in the corresponding use cases,
46 -** //Claim//, specifiying the expected //Effect //of the situated Function (i.e., situated in the use case) to provide the justification (why).
37 +** //Claim//, specifying the expected //Effect //of the situated Function (i.e., situated in the use case) to provide the justification (why).
47 47  * The **Evaluation **provides the outcomes of the tests with the Prototype and/or Simulation.
48 48  
49 49  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**.