Difference between revisions of "System-specified Behaviour"

From CIPedia
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 ===
<!-- Insert here definitions from international organizations, if available. Each new definition should be formatted as a heading level 4, followed by the unformatted text of the definition. An example follows below: ==== United Nations’ Definition ====
 
Insert the definition found in the document “2009 UNISDR Terminology on Disaster Risk Reduction” (this is an example). -->
 
 
 
=== National Definitions ===
 
=== National Definitions ===
<!-- Insert official national definitions, if available.  Each definition should be formatted as a heading level 4, followed by the text of the definition. An example follows below:
 
 
==== Country Name====
 
==== Country Name====
Insert the definition found on the DHS Lexicon (this is an example). -->
 
  
 
===Standard Definition===
 
===Standard Definition===
<!--Insert the text of the definition. Each definition should be formatted as a heading level 4, followed by the text of the definition. -->
+
-->
  
 
== Discussion Topic ==
 
== Discussion Topic ==

Latest revision as of 13:40, 30 January 2020


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