Timing Analysis with Qompass Sample Clauses

Timing Analysis with Qompass. The Qompass plug-in developed originally for schedulability analysis of XXXXX models, has been adapted and extended its application on EAST-ADL models. XXXXX models, originally input of the Qompass tool, contained a set of tasks and scheduling information (priorities, shared resources protocols, etc) where functions are mapped into tasks and signals are mapped into messages. The Qompass tool is able, on these tasks models, to perform response-time analysis. During MAENAD, however, it was immediately clear that the most detailed information provided by EAST-ADL did not cover the task set definition. In order to make the Qompass tool relevant for EAST-ADL models we worked on two different axes: (i) extend Qompass with so-called early-stage schedulability analysis, i.e. a schedulability assessment able to detect allocation errors preventing schedulability of the system and (ii) extend Qompass with an automatic transformation of EAST-ADL model to XXXXX functional models (without task set and scheduling information), containing end-to-end chains of function activations, estimated execution times for each function, end-to-end deadlines, and functional allocation to hardware nodes and buses. Procedures Relevant EAST-ADL information for timing analysis includes design the chains of function activations that compose a system response and subject to a deadline; the allocation of functions to nodes; the estimation of the resource demand of each function, the maximal utilization capacity of resources. Figure 5-12 shows an excerpt of the timing information annotating the design functional graph. Activation semantics is added to that functional graph through events definition and timing constraints among these events. This gives a timed partial order of execution for functions and end-to-end timing constraints, which are needed to make timing analysis. Figure 5-12.Excerpt of the timing model for the BBW EAST-ADL relevant information is then transformed in a UML/XXXXX model as shown in Figure Figure 5-13 and Figure 5-14.The XXXXX model is represented by an UML Activity, corresponding to the EAST-ADL functional graph, annotated with XXXXX stereotypes, containing timing and allocation information coming from the EAST-ADL model. On this XXXXX model it is now possible to launch the analysis. Various indicators for schedulability are calculated by the analysis as the node utilization Figure 5-15 and bus utilization Figure 5-16.