Common use of Timing Analysis Clause in Contracts

Timing Analysis. Timing modeling in EAST-ADL results from the work done in the TIMMO project, which produced a dedicated language called TADL (see TIMMO deliverable D6 for instance available from ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/). TADL concepts were integrated in the course of the ATESST2 project in the EAST-ADL language. Essentially three packages structure the timing concepts: Timing which defines core elements and their organization, Events which lists various kinds of events that can be associated to structural elements, such arrival of data on ports, and TimingConstraints which lists all possible constraints one can model – delays, synchronization, etc. The modeling principle is the following. TimingConstraints are associated to an EventChain, which defines the scope of the constraint. The EventChain in turn relates to various Events, such as arrival of a data on a Port. Events point to structural elements, such as Ports or Functions Based on this modelling concepts timing analysis can be performed. However TADL does not cover implementation level concepts such as tasks, which are needed to conduct a detailed schedulability analysis for instance. Thus the analysis that one can perform at this level is restricted to feasibility assessment regarding e.g. response times, age, synchronization and resource load balancing and assessing. This provides an interesting insight on how the software implementation could later be defined. To go beyond this, one needs to go to the implementation level (i.e. Autosar architecture) where the allocation of execution to tasks is defined. For this, ▇▇▇▇▇ provides a good basis. In the experiments done on timing analysis in ATESST2, the extra information needed in EAST-ADL models were added using ▇▇▇▇▇ constructs. The following section provides a summary of the main elements in both languages, EAST-ADL (and TIMMO) and ▇▇▇▇▇. 3.4.1 EAST-ADL/TADL

Timing Analysis. Timing modeling modelling in EAST-ADL results from the work done in the TIMMO project, which produced a dedicated language called TADL (see TIMMO deliverable D6 for instance available from ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/). TADL concepts were integrated in the course of the ATESST2 project in the EAST-ADL language. Essentially three packages structure the timing concepts: Timing which defines core elements and their organizationorganisation, Events which lists various kinds of events that can be associated to structural elements, such arrival of data on ports, and TimingConstraints which lists all possible constraints one can model – delays, synchronizationsynchronisation, etc. The modeling modelling principle is the following. TimingConstraints are associated to an EventChain, which defines the scope of the constraint. The EventChain in turn relates to various Events, such as arrival of a data on a Port. Events point to structural elements, such as Ports or Functions Based on this modelling concepts timing analysis can be performed. However TADL does not cover implementation level concepts such as tasks, which are needed to conduct a detailed schedulability analysis for instance. Thus the analysis that one can perform at this level is restricted to feasibility assessment regarding e.g. response times, age, synchronization synchronisation and resource load balancing and assessing. This provides an interesting insight on how the software implementation could later be defined. To go beyond this, one needs to go to the implementation level (i.e. Autosar AUTOSAR architecture) where the allocation of execution to tasks is defined. For this, ▇▇▇▇▇ provides a good basis. In the experiments done on timing analysis in ATESST2, the extra information needed in EAST-ADL models were added using ▇▇▇▇▇ constructs. The following section provides a summary of the main elements in both languages, EAST-ADL (and TIMMO) and ▇▇▇▇▇. 3.4.1 EAST-ADL/TADL