Difference between revisions of "System-specified Behaviour"
Jump to navigation
Jump to search
Line 11: | Line 11: | ||
System-specified Behaviour is behaviour of [[component]]s or [[scenario]]s that is either too basic or too complicated to be described as [[user-specified behaviour]] and therefore has to be implemented in a programming language by a developer. | System-specified Behaviour is behaviour of [[component]]s or [[scenario]]s that is either too basic or too complicated to be described as [[user-specified behaviour]] and therefore has to be implemented in a programming language by a developer. | ||
}} | }} | ||
− | + | <!-- | |
=== Other International Definitions === | === Other International Definitions === | ||
− | |||
− | |||
− | |||
=== National Definitions === | === National Definitions === | ||
− | |||
==== Country Name==== | ==== Country Name==== | ||
− | |||
===Standard Definition=== | ===Standard Definition=== | ||
− | + | --> | |
== Discussion Topic == | == Discussion Topic == |
Latest revision as of 13:40, 30 January 2020
Contents
Definitions
European Project Definitions
CIPRNet project
The CIPRNet project [1] uses the following definition:
System-specified behaviour is behaviour of components or scenarios that is either too basic or too complicated to be described as user-specified behaviour and therefore has to be implemented in a programming language by a developer.
DIESIS project
The DIESIS project [2] gives the following definition:
System-specified Behaviour is behaviour of components or scenarios that is either too basic or too complicated to be described as user-specified behaviour and therefore has to be implemented in a programming language by a developer.
Discussion Topic
See also
Notes
References