Difference between revisions of "TASTE Semantics"
(→Interface View) |
(→Interface View) |
||
Line 11: | Line 11: | ||
In the most abstract way, a system modeled with TASTE contains '''functions''' that exchange messages with other functions through '''interfaces'''. | In the most abstract way, a system modeled with TASTE contains '''functions''' that exchange messages with other functions through '''interfaces'''. | ||
− | + | The semantics of the interface view is largely inspired by the Specification and Description Language (SDL). There are a few differences that are explained below. | |
== Function == | == Function == |
Revision as of 20:28, 28 January 2021
Introduction
This page gives a comprehensive description of the semantics behind the TASTE meta-model.
THIS PAGE IS WORK IN PROGRESS
Interface View
The interface view in TASTE captures the model of the system logical architecture, independently from a software implementation.
In the most abstract way, a system modeled with TASTE contains functions that exchange messages with other functions through interfaces.
The semantics of the interface view is largely inspired by the Specification and Description Language (SDL). There are a few differences that are explained below.
Function
There are several forms of functions in TASTE :
- functions that represent an active component of the system (e.g. a state machine or a control law), something that can communicate with surrounding functions.
- nesting functions, that allow to structure the system in a hierarchical way (grouping by context, or for better readability). Nesting is recursive with no limit.
- function types, which contain a generic behavior and that can be instantiated
- function instances
Graphically, terminal functions have this simple shape including the name of the function:
While nesting function generally appear like this (depending on the tool) - showing a mini-view of the function content.
Function types have a slightly different shape:
Semantics
A function contains data that is invisible from outside the function. Interfaces of the function can access this data when invoked.