Difference between revisions of "TASTE Semantics"
(Created page with "= Introduction = This page gives a comprehensive description of the semantics behind the TASTE meta-model. = Interface View The '''interface view''' in TASTE captures the m...")
Revision as of 20:20, 28 January 2021
This page gives a comprehensive description of the semantics behind the TASTE meta-model.
= 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.
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:
A function contains data that is invisible from outside the function. Interfaces of the function can access this data when invoked.