Skip to Content

Changes for page General SCE Vocabularly

Last modified by Dongxu Lu on 2023/03/21 12:11
From version 3.1
edited by Dongxu Lu
on 2023/03/21 12:10
Change comment: There is no comment for this version
To version 1.1
edited by Bart Vastenhouw
on 2022/08/23 10:40
Change comment: Imported from XAR

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.DongxuLu
1 +xwiki:XWiki.BartVastenhouw
Content
... ... @@ -1,6 +1,6 @@
1 -|**Claim**|
1 +Created by Mark Neerincx, last modified on 25 Jan, 2021
2 2  
3 -(((
3 +|**Claim**|(((
4 4  A claim refers to an intended and/or side effect of a particular functionality of the system (described in a functional requirement). Claims are used to formulate hypotheses about the beneficial and detrimental effects of adding a particular functionality to the design specification. These hypotheses can be tested in evaluation studies to investigate the beneficial effect of including a certain functionality in the design.
5 5  
6 6  Claims can refer to both positive effects (benefits) of using the system, but also to possible negative side effects (downsides) of using the system. Usually the positive and negative claims pose a trade-off for a specific functionality. Yet ultimately, the positive effects should outweigh the negative effects of including the respective functionality in the design.
... ... @@ -7,7 +7,6 @@
7 7  
8 8  Claims are generally considered to be admissible if there has been previous scientific evidence supporting the claim, for instance in research related to existing theories from human factors knowledge. Most claims are related to or derived from human factors theories and/or principles.
9 9  )))
10 -
11 11  |**Design specification**|The design specification is the collection of use cases, requirements, claims, and ontology. Together they describe the outline of the system's behaviour, functionalities, and intended effects. This should be sufficient to provide a blueprint for developers to implement the design in an operational, interactive version of the system (a prototype). A specification refers to an explicit set of requirements to be satisfied by a design, system, product, or service.
12 12  |**Functional requirement**|In the SCE method, functional requirements describe functional properties of the system that follow directly from the user requirements and/or the operational demands. Functional requirements are described as “the system shall do <requirement>”. The MoSCoW (Must have, Should have, Could have, Won't have this time) method can be used to prioritise the requirements.
13 13  |**Human Factors concept**|A Human Factors (HF) concept is an idea, principle, or theory based in the human factors literature. The concept is deemed relevant to the design if it can be used to stipulate the design rationale, claims, or design pattern premises.