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

Summary

Details

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