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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.MarkNeerincx
1 +XWiki.DongxuLu
Content
... ... @@ -24,12 +24,10 @@
24 24  
25 25  === **Method** ===
26 26  
27 -[[image:1707214691818-893.png||height="328" width="608"]]
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  
29 -**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).
30 -
31 31  * The **Foundation **describes the
32 -** //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),
33 33  ** //Technology //that will be used and/or (further) developed (e.g., cloud computing, AI frameworks) and
34 34  ** //Human Factors// knowledge that should be addressed in the design and evaluation of the technology to meet the operational demands.
35 35  * The **Specification **defines the
... ... @@ -36,10 +36,10 @@
36 36  ** //Objectives//: the target outcomes
37 37  ** //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),
38 38  ** //Function //(requirement), i.e., what the machine shall do to serve the objectives in the corresponding use cases,
39 -** //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).
40 40  * The **Evaluation **provides the outcomes of the tests with the Prototype and/or Simulation.
41 41  
42 -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 identified human needs, generated behavioral and declarative design knowledge is formalized and maintained for re-use and sharing via, respectively, **Values**, **Design Patterns** and corresponding **Ontologies**.
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**.
43 43  
44 44  Detailed information on the methodology can be found in the [[publications section>>url:https://scetool.ewi.tudelft.nl/?q=node/5]] of this site.
45 45  
1707214691818-893.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.MarkNeerincx
Size
... ... @@ -1,1 +1,0 @@
1 -195.7 KB
Content
XWiki.AverageRatingsClass[0]
Average Vote
... ... @@ -1,1 +1,0 @@
1 -5.0
Manager Identifier
... ... @@ -1,1 +1,0 @@
1 -ratings
Number of Votes
... ... @@ -1,1 +1,0 @@
1 -1
Voted Entity Reference
... ... @@ -1,1 +1,0 @@
1 -document:xwiki:Main.WebHome
Scale of votes
... ... @@ -1,1 +1,0 @@
1 -5
Date of last update
... ... @@ -1,1 +1,0 @@
1 -2025-04-17 14:02:44.116