Skip to Content
1 Votes
Last modified by Mark Neerincx on 2025/04/17 14:02
From version 14.1
edited by Dongxu Lu
on 2023/03/28 14:27
Change comment: Attachment moved from xwiki:FOUNDATION.WebHome.
To version 16.1
edited by Dongxu Lu
on 2023/03/28 14:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -24,8 +24,10 @@
24 24  
25 25  === **Method** ===
26 26  
27 +[[image:/xwiki/bin/get/Main/?sheet=CKEditor.ResourceDispatcher&outputSyntax=plain&language=en&type=attach&typed=true&reference=SCE.PNG||height="529" width="1000"]]**[[image:attach:SCE.PNG]]**
28 +
27 27  * The **Foundation **describes the
28 -** //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),
29 29  ** //Technology //that will be used and/or (further) developed (e.g., cloud computing, AI frameworks) and
30 30  ** //Human Factors// knowledge that should be addressed in the design and evaluation of the technology to meet the operational demands.
31 31  * The **Specification **defines the
... ... @@ -32,7 +32,7 @@
32 32  ** //Objectives//: the target outcomes
33 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 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).
37 +** //Claim//, specifying the expected //Effect //of the situated Function (i.e., situated in the use case) to provide the justification (why).
36 36  * The **Evaluation **provides the outcomes of the tests with the Prototype and/or Simulation.
37 37  
38 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**.