<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1 plus MathML 2.0 plus SVG 1.1//EN" "http://www.w3.org/2002/04/xhtml-math-svg/xhtml-math-svg.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8"/>
    <title>Team:AOSTE2</title>
    <link rel="stylesheet" href="../static/css/raweb.css" type="text/css"/>
    <meta name="description" content="Overall Objectives - Overall Objectives"/>
    <meta name="dc.title" content="Overall Objectives - Overall Objectives"/>
    <meta name="dc.subject" content=""/>
    <meta name="dc.publisher" content="INRIA"/>
    <meta name="dc.date" content="(SCHEME=ISO8601) 2018-01"/>
    <meta name="dc.type" content="Report"/>
    <meta name="dc.language" content="(SCHEME=ISO639-1) en"/>
    <meta name="projet" content="AOSTE2"/>
    <script type="text/javascript" src="https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-MML-AM_CHTML">
      <!--MathJax-->
    </script>
  </head>
  <body>
    <div class="tdmdiv">
      <div class="logo">
        <a href="http://www.inria.fr">
          <img style="align:bottom; border:none" src="../static/img/icons/logo_INRIA-coul.jpg" alt="Inria"/>
        </a>
      </div>
      <div class="TdmEntry">
        <div class="tdmentete">
          <a href="uid0.html">Team Aoste2</a>
        </div>
        <span>
          <a href="uid1.html">Team, Visitors, External Collaborators</a>
        </span>
      </div>
      <div class="tdmActPage">
        <a href="./uid3.html">Overall Objectives</a>
      </div>
      <div class="TdmEntry">Research Program<ul><li><a href="uid5.html&#10;&#9;&#9;  ">The Algorithm-Architecture Adequation
methodology and Real-Time Scheduling</a></li><li><a href="uid6.html&#10;&#9;&#9;  ">Probabilistic Worst Case Reasoning for Real-Time
Systems</a></li><li><a href="uid11.html&#10;&#9;&#9;  ">Real-Time Systems Compilation</a></li></ul></div>
      <div class="TdmEntry">Application Domains<ul><li><a href="uid15.html&#10;&#9;&#9;  ">Avionics</a></li><li><a href="uid16.html&#10;&#9;&#9;  ">Many-Core Embedded Architectures</a></li><li><a href="uid17.html&#10;&#9;&#9;  ">Railways</a></li></ul></div>
      <div class="TdmEntry">
        <a href="./uid19.html">Highlights of the Year</a>
      </div>
      <div class="TdmEntry">New Software and Platforms<ul><li><a href="uid21.html&#10;&#9;&#9;  ">SynDEx</a></li><li><a href="uid25.html&#10;&#9;&#9;  ">EVT Kopernic</a></li><li><a href="uid29.html&#10;&#9;&#9;  ">LoPhT-manycore</a></li></ul></div>
      <div class="TdmEntry">New Results<ul><li><a href="uid33.html&#10;&#9;&#9;  ">Uniprocessor Mixed-Criticality Real-Time Scheduling</a></li><li><a href="uid34.html&#10;&#9;&#9;  ">Multiprocessor Real-Time Scheduling</a></li><li><a href="uid35.html&#10;&#9;&#9;  ">Safe Parallelization of Hard Real-Time Avionics Software</a></li><li><a href="uid36.html&#10;&#9;&#9;  ">Real-time Platform Modeling</a></li></ul></div>
      <div class="TdmEntry">Bilateral Contracts and Grants with Industry<ul><li><a href="uid40.html&#10;&#9;&#9;  ">Bilateral Contracts with Industry</a></li></ul></div>
      <div class="TdmEntry">Partnerships and Cooperations<ul><li><a href="uid42.html&#10;&#9;&#9;  ">National Initiatives</a></li><li><a href="uid53.html&#10;&#9;&#9;  ">European Initiatives</a></li></ul></div>
      <div class="TdmEntry">Dissemination<ul><li><a href="uid67.html&#10;&#9;&#9;  ">Promoting Scientific Activities</a></li><li><a href="uid94.html&#10;&#9;&#9;  ">Teaching - Supervision - Juries</a></li></ul></div>
      <div class="TdmEntry">
        <div>Bibliography</div>
      </div>
      <div class="TdmEntry">
        <ul>
          <li>
            <a id="tdmbibentyear" href="bibliography.html">Publications of the year</a>
          </li>
          <li>
            <a id="tdmbibentfoot" href="bibliography.html#References">References in notes</a>
          </li>
        </ul>
      </div>
    </div>
    <div id="main">
      <div class="mainentete">
        <div id="head_agauche">
          <small><a href="http://www.inria.fr">
	    
	    Inria
	  </a> | <a href="../index.html">
	    
	    Raweb 
	    2018</a> | <a href="http://www.inria.fr/en/teams/aoste2">Presentation of the Team AOSTE2</a></small>
        </div>
        <div id="head_adroite">
          <table class="qrcode">
            <tr>
              <td>
                <a href="aoste2.xml">
                  <img style="align:bottom; border:none" alt="XML" src="../static/img/icons/xml_motif.png"/>
                </a>
              </td>
              <td>
                <a href="aoste2.pdf">
                  <img style="align:bottom; border:none" alt="PDF" src="IMG/qrcode-aoste2-pdf.png"/>
                </a>
              </td>
              <td>
                <a href="../aoste2/aoste2.epub">
                  <img style="align:bottom; border:none" alt="e-pub" src="IMG/qrcode-aoste2-epub.png"/>
                </a>
              </td>
            </tr>
            <tr>
              <td/>
              <td>PDF
</td>
              <td>e-Pub
</td>
            </tr>
          </table>
        </div>
      </div>
      <!--FIN du corps du module-->
      <br/>
      <div class="bottomNavigation">
        <div class="tail_aucentre">
          <a href="./uid1.html" accesskey="P"><img style="align:bottom; border:none" alt="previous" src="../static/img/icons/previous_motif.jpg"/> Previous | </a>
          <a href="./uid0.html" accesskey="U"><img style="align:bottom; border:none" alt="up" src="../static/img/icons/up_motif.jpg"/>  Home</a>
          <a href="./uid5.html" accesskey="N"> | Next <img style="align:bottom; border:none" alt="next" src="../static/img/icons/next_motif.jpg"/></a>
        </div>
        <br/>
      </div>
      <div id="textepage">
        <!--DEBUT2 du corps du module-->
        <h2>Section: 
      Overall Objectives</h2>
        <h3 class="titre3">Overall Objectives</h3>
        <p>The recent advances in merging different technologies and engineering domains
has led to the emergence of Cyber-Physical Systems (CPS). In such systems,
embedded computers interact with, and control physical processes. These
embedded computers (cyber) may communicate from a tightly coupled way, for
example through a serial CAN bus in the automotive domain or through an AFDX
bus in the avionics domain to control engine(s) or brakes (physics), to a
loosely coupled way for example through the internet network to offer
multimedia services or data-base accesses. Because of the heterogeneity of the
involved components (multi-physics, sensors, actuators, embedded computers),
CPS may feature very complex design and implementation phases as well as
complex computer platforms (multi/manycore, multiprocessor, distributed and
parallel computers), ever raising the need for effective approaches in order to
build reliable systems.</p>
        <p>Most of these CPS are time sensitive, i.e. time is a crucial issue which must
be carefully mastered, that yet increases their complexity. Mastering time in
such CPS is the major objective of the team. Due to their heterogeneous nature,
the different components may have different levels of criticality, e.g. engine
and brakes have a higher criticality level than multimedia services, which
increase the difficulty in the design and implementation phases since lower
criticality parts must not interfere with higher criticality parts. In the team
we mainly address mixed-criticality issues in term of software safety. However,
we started to take into account, in addition, security issues (cyber attacks).</p>
        <p>The members of the team beeing involved for a long time in <i>synchronous
languages</i>, we address the functional specification of CPS with models
compliant with the semantics of these languages. Theses models are basicaly
graphs and more specifically “clocked graphs” that model data dependences
beetween functions as well as “logical clocks” that are attached to every
function. These logical clocks may be related to physical clocks which
correspond to periods of functions. These periods are defined by automatic
control engineers and are not dependent of the platform. Such approach allows
verifications on the functional specification, guaranteeing that the output
events of the control system obtained “in reaction” to some input events, are
consistent with the input events that triggered them. Verifying functional
specifications very early in the design phase, prevents a lot of classic errors
found usually later on during the implementation phase. This approach is an
important step for providing “correct by construction”
implementations. However, non functional specifications must also be taken into
consideration. Indeed, to perform real-time schedulability analyses used to
guarantee that the implementation is correct in terms of time, we need the worst
case execution times (WCET) of each function and the worst case communication
times (WCCT) of each dependence. Both, worst case execution and communication
times are dependent of the platform. Using these worst case times,
schedulability analyses are able to compute the worst case response time of each
function and some end-to-end worst case execution times, possibly in the case
where the implied functions are allocated to different cores. Worst case
response times and end-to-end execution times must verify real-time constraints,
i.e. deadlines and latencies. These constraints are imposed by automatic control
engineers while they usually do not know the platform that will be used later
on in the developpement process.</p>
        <p>This is the reason why, in the non functionnal specifications we need precise
models that encompass important features found at different levels of the
platform architecture, e.g. at a high level the number of cores and
communications mediums, at a low level the structure of the caches, pipelines,
etc. Depending on the complexity of the platform the problem of estimating
these worst case times may be more or less difficult. In the case of simple
predictable processors and buses, both used presently in the industry for
critical avionics and railways applications, the estimation of worst case times
is relatively easy. For this purpose we use, for example, static analyses or
techniques based on measurements for estimating WCETs. However, due to the ever
increasing smartphone market, the microprocessor industry provides more and more
general purpose platforms based on multicore and, in a near future, based on
manycore. These platform have complex architectures that are not predictable due
to, e.g. multiple levels of cache and pipeline, speculative branching,
communicating through shared memory or/and through a network on chip,
etc. Therefore, nowadays the CPS industry has to face the great challenge of
using such off the shelf platforms and consequently to estimate the
corresponding worst case times of the programs (functions) that they will
execute.</p>
        <p>From functional and non functional specifications of the design phase we intend
to synthesize, as automatically as possible, based on the real-time
schedulability theory, an implementation that is correct by construction. This
synthesizing process is close to the process used in language compilation but,
in addition, it must take into account more complex non functional
specifications. On the other hand, when platforms are not predictable an
alternative to the classic estimation of worst case times mentioned
previously, consists in reformulating the different problems in a probabilistic
framework.</p>
        <p>The overall objectives given above lead to three main research programs that
are detailed below.</p>
      </div>
      <!--FIN du corps du module-->
      <br/>
      <div class="bottomNavigation">
        <div class="tail_aucentre">
          <a href="./uid1.html" accesskey="P"><img style="align:bottom; border:none" alt="previous" src="../static/img/icons/previous_motif.jpg"/> Previous | </a>
          <a href="./uid0.html" accesskey="U"><img style="align:bottom; border:none" alt="up" src="../static/img/icons/up_motif.jpg"/>  Home</a>
          <a href="./uid5.html" accesskey="N"> | Next <img style="align:bottom; border:none" alt="next" src="../static/img/icons/next_motif.jpg"/></a>
        </div>
        <br/>
      </div>
    </div>
  </body>
</html>
