Skip to Content
Last modified by Tjalling Haije on 2025/09/15 08:07
From version 1.1
edited by Tjalling Haije
on 2025/06/04 12:47
Change comment: Imported from XAR
To version 6.1
edited by Tjalling Haije
on 2025/09/08 13:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -General SCE Vocabularly
1 +c. Definitions and Concepts
Parent
... ... @@ -1,1 +1,1 @@
1 -doc.Team Design Pattern Vocabularly.WebHome
1 +0\. Introduction.WebHome
Content
... ... @@ -1,5 +3,3 @@
1 -Created by Mark Neerincx, last modified on 25 Jan, 2021
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  
... ... @@ -33,4 +33,6 @@
33 33  |**Use case**|A use case is a sequence of interactions between multiple roles or actors. A use case is situated, i.e. related to a given circumstance/context/activity (as opposed to design patterns).
34 34  |**Value**|A value is something a person finds very important to protect and support. It is a driving force in decision making and goal selection. An instrumental value is worth having as a means to something else that is good. An intrinsically valuable thing is worth having for itself. Intrinsic and instrumental goods are not mutually exclusive categories. Some things are both good in themselves, and also good for getting other things that are good.
35 35  
36 -
34 +=== Can't  find the definition you are looking for? ===
35 +
36 +Check the [[SCE FAQ>>Documentation.SCE FAQ.WebHome]], or send a mail to a TNO member listed on the [[a. Project Information>>0\. Introduction.Project Information.WebHome]] page.