Glossary (Dezyne Reference Manual)

13 Glossary

Term	Context	Definition	Chapter
Action	Concept	Statement as part of the response to a trigger event.	-
behavior	Keyword	Start of the behavior section within an interface or component definition; this keyword must be followed by {}.	See Behavior and See Component Behavior
Bind	Concept	To associate two ports within a system section using the Dezyne language’s <=> operator.	-
blocking	Keyword	Qualifier to indicate that the executing of the trigger is blocked till a corresponding reply is given on the port of the trigger	See Blocking
bool	Keyword	Boolean type identifier.	See Types and Expressions
Compliance	Concept	Whether or not, the behavior of a component complies to the behavior specification of the interface of each provides port.	-
Component	Concept	Unit of definition and instantiation. A component has zero or more ports. A component has a behavior section, sysinstantiationtem section, or none.	-
component	Keyword	Begins the definition of a component; this keyword must be followed by an identifier and {}.	See Components
condition	Concept	`if`.	-
else	Keyword	Else part of condition statement.	See Identifiers
enum	Keyword	Enumeration type definition.	See Types and Expressions
Event	Concept	An event is declared as part of an interface and represents the type of the messages communicated between components. An event is implemented as a function call.	-
extern	Keyword	Type definition which can be used for data variables and data parameters. Followed by an identifier and $$’s. The part between $$’s is used in the generated code as the type definition for these data variables and parameters.	See Types and Expressions
external	Keyword	Qualifier of a provides port definition indicating that the out events can be possibly delayed which is taken into account during verification.	See External
false	Keyword	Boolean value false.	See Identifiers
Guard	Concept	A boolean expression between [ ] as prefix of a statement	-
Hand-written	Concept	A hand-written component is defined as a component without a behavior or system section in the component definition. The implementation should be provided in the target source language.	-
if	Keyword	The `if` keyword is followed by a boolean expression and a statement and optionally the keyword `else`; followed by a second statement	See Identifiers
illegal	Keyword	`illegal`. As a direct response indicates that the given event in the given state is not allowed to be communicated. Within a component, the `illegal` is also allowed within a function or `if`, indicating that the `illegal` should never be executed, i.e. comparable with `assert(FALSE)`; of the C-language.	See Illegal and See Component Illegal
import	Keyword	The file following the import keyword is loaded and expanded at the location of the `import`	See Identifiers
in	Keyword	Indicates for an event of an interface that the event is an incoming event ”’or”’ indicates for a data parameter of an event or function that the value of the parameter is incoming	See Interfaces
inevitable	Keyword	A trigger event that will inevitably occur provided no other events occur.	See Using inevitable and optional
injected	Keyword	Qualifier of a required port to indicate that the binding of the port occurs at a higher level in the system hierarchy.	See Components
inout	Keyword	Indicates for a data parameter of an event or function that the value of the parameter is incoming at the begin of the event or function call, and outgoing at the end.	-
Interface	Concept	An interface defines a set of events and the underlying protocol how components communicate between each other via their ports.	-
interface	Keyword	Begins the definition of an interface; this keyword must be followed by an identifier and {}.	See Interfaces
namespace	Keyword	-	See Namespaces
on	Keyword	Identifies an `on` which for one or more trigger events defines the corresponding response.	See Imperative Statements
optional	Keyword	A trigger that optionally can happen.	See Using inevitable and optional
otherwise	Keyword	Defines a catch-all guard which is true only if all the other guard expressions in a list of `guard`s evaluate to false.	See Declarative Statements
out	Keyword	Indicates for an event of an interface that the event is an outgoing event ”’or”’ indicates for a data parameter of an event of function that the value of the parameter is outgoing	See Interfaces
Port	Concept	Within a component definition, a named instance of an interface.	-
provides	Keyword	Used in a component to define a port and its type which the component will provide.	See Ports
reply	Keyword	Statement that defines the value that will be returned as result of the triggering event.	See Imperative Statements
requires	Keyword	Used in a component to define a port and its type which the component will use.	See Ports
return	Keyword	`return`; specifies the return value of a function (if any) and exits the function.	See Functions
Sequence view	Window	Message sequence chart (result of simulation or verification).	-
State	Concept	A state consists of all values of a model’s member variables.	-
subint	Keyword	A type representing a finite sequence of integers, expressed as {m..n} where m and n are integers and m <= n, for example {-2..1}.	See Types and Expressions
System	Concept	A component containing a system section.	-
system	Keyword	Starts the system section of a component. A system section consists of two parts: instantiations of subcomponents, followed by all the bindings among the sub-components and ports of the component.	See Systems
Trace	Concept	An execution trace is a sequence of events representing a possible execution scenario.	-
true	Keyword	Boolean value true.	See Identifiers
Type	Concept	An enum, subint, bool, or extern.	-
Variable	Concept	Declared within a behavior section. A member variable can be either a state variable which can be used a part of a guard of condition or a data variable which can be used as a parameter of events or functions	-
Verification	Concept	The execution of the verification engine which verifies for interfaces and components whether they are free of livelock, deadlock, and illegal behavior. Also, for a component it is verified whether a component adheres to all the protocols (behavior) of the interfaces of the ports of the component. During verification, all possible execution scenarios are considered guaranteeing a 100% coverage.	-