We’re here to help you

Menu

Glossary

Term or keyword Context Definition(s) Related chapter

Action

Concept

Statement as part of the response to an event.

-

async

Keyword

The 'dzn.async' interface represents a component implemented in the Dezyne runtime. Its purpose is to provide an out-event in a new call context without relying on an event from the environment.

Using async

behaviour

Keyword

Start of the behaviour section within an interface or component definition; this keyword must be followed by {}.

Interface and component behaviour

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 event is blocked till a corresponding reply is given on the port of the event.

Using blocking

bool

Keyword

Boolean type identifier.

Types and expressions

Compliance

Concept

Whether or not, the behaviour of a component complies to the behaviour specification of the interface of each provided port.

-

Component

Concept

Unit of definition and instantiation. A component has zero or more ports. A component has a behaviour section, system section, or none.

-

component

Keyword

Begins the definition of a component; this keyword must be followed by an identifier and {}.

Component models

condition

Concept

If-then-else statement.

-

else

Keyword

Else part of condition statement.

Identifiers

enum

Keyword

Enumeration type declaration.

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.

-

Event table

Window

A tabular representation of the state machine as specified by the behaviour of a component or interface. The events are leading.

Viewing event tables

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.

Types and expressions

external

Keyword

Qualifier of a provided port definition indicating that the out events can be possibly delayed which is taken into account during verification.

Using external

false

Keyword

Boolean value false.

Identifiers

Guard

Concept

A boolean expression between [ ] as prefix of a statement

-

Hand-written

Concept

A hand-written component or native component is defined as a component without a behaviour 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

Identifiers

illegal

Keyword

illegal statement. As a direct response indicates that the given event in the given state is not allowed to be communicated. Within a component, the illegal statement is also allowed within a function or if-then-else statement, indicating that the illegal statement should never be executed, i.e. comparable with "assert(FALSE);" of the C-language.

Using illegal

import

Keyword

The file following the import keyword is loaded and expanded at the location of the import statement

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

Specifying events

inevitable

Keyword

Qualifies an event that will inevitably occur provided no other events occur.

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.

Component models

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 {}.

Interface models

namespace

Keyword

-

Namespaces

on

Keyword

Identifies an on-event statement which for one or more events defines the corresponding response.

Specifying actions

optional

Keyword

Qualifies an event that may or may not happen.

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 guarded statements evaluate to false.

Specifying stateful behaviour

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

Specifying events

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.

Specifying ports

reply

Keyword

Statement that defines the value that will be returned as result of the event.

Using reply

requires

Keyword

Used in a component to define a port and its type which the component will use.

Specifying ports

return

Keyword

return statement; specifies the return value of a function (if any) and exits the function.

Using functions

Sequence view

Window

Message sequence chart (result of simulation or verification).

Viewing sequence diagrams

State

Concept

A state consists of all values of the state variables in scope.

-

State chart

Window

A graphical representation of the state machine as specified by the behaviour of a component or interface.

Viewing state charts

State table

Window

A tabular representation of the state machine specified by the behaviour of a component or interface. The states are leading.

Viewing state tables

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}.

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.

Decomposing a component

Trace

Concept

An execution trace is a sequence of events representing a possible execution scenario.

-

true

Keyword

Boolean value true.

Identifiers

Type

Concept

An enum, subint, bool, or extern.

-

Variable

Concept

Declared within a behaviour section. A 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 behaviour. Also, for a component it is verified whether a component adheres to all the protocols (behaviour) of the interfaces of the ports of the component. During verification, all possible execution scenarios are considered guaranteeing a 100% coverage.

-

If you have questions that weren’t answered by this Guide,
let our support team help you out.

Enjoy this article? Don't forget to share.