<?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>Project-Team:TEA</title>
    <link rel="stylesheet" href="../static/css/raweb.css" type="text/css"/>
    <meta name="description" content="Overall Objectives - Motivations"/>
    <meta name="dc.title" content="Overall Objectives - Motivations"/>
    <meta name="dc.subject" content=""/>
    <meta name="dc.publisher" content="INRIA"/>
    <meta name="dc.date" content="(SCHEME=ISO8601) 2015-01"/>
    <meta name="dc.type" content="Report"/>
    <meta name="dc.language" content="(SCHEME=ISO639-1) en"/>
    <meta name="projet" content="TEA"/>
    <!-- Piwik -->
    <script type="text/javascript" src="/rapportsactivite/piwik.js"></script>
    <noscript><p><img src="//piwik.inria.fr/piwik.php?idsite=49" style="border:0;" alt="" /></p></noscript>
    <!-- End Piwik Code -->
  </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">Project-Team Tea</a>
        </div>
        <span>
          <a href="uid1.html">Members</a>
        </span>
      </div>
      <div class="TdmEntry">Overall Objectives<ul><li><a href="./uid3.html">Introduction</a></li><li><a href="./uid4.html">Context</a></li><li class="tdmActPage"><a href="./uid5.html">Motivations</a></li><li><a href="./uid6.html">Challenges</a></li></ul></div>
      <div class="TdmEntry">Research Program<ul><li><a href="uid8.html&#10;&#9;&#9;  ">Previous Works</a></li><li><a href="uid11.html&#10;&#9;&#9;  ">Modelling Times</a></li><li><a href="uid19.html&#10;&#9;&#9;  ">Modelling Architectures</a></li><li><a href="uid25.html&#10;&#9;&#9;  ">Application to Scheduling Theory</a></li><li><a href="uid31.html&#10;&#9;&#9;  ">Virtual Prototyping</a></li></ul></div>
      <div class="TdmEntry">Application Domains<ul><li><a href="uid36.html&#10;&#9;&#9;  ">Automotive and Avionics</a></li><li><a href="uid37.html&#10;&#9;&#9;  ">Factory Automation</a></li></ul></div>
      <div class="TdmEntry">
        <a href="./uid39.html">Highlights of the Year</a>
      </div>
      <div class="TdmEntry">New Software and Platforms<ul><li><a href="uid42.html&#10;&#9;&#9;  ">The Eclipse project POP</a></li><li><a href="uid46.html&#10;&#9;&#9;  ">The Polychrony toolset</a></li><li><a href="uid59.html&#10;&#9;&#9;  ">SigCert: translation validation from Signal to C</a></li><li><a href="uid64.html&#10;&#9;&#9;  ">ADFG: Affine data-flow graphs scheduler synthesis under Eclipse</a></li></ul></div>
      <div class="TdmEntry">New Results<ul><li><a href="uid69.html&#10;&#9;&#9;  ">Polychronous automata</a></li><li><a href="uid71.html&#10;&#9;&#9;  ">Runtime verification and trace analysis</a></li><li><a href="uid72.html&#10;&#9;&#9;  ">Integration of Polychrony with QGen</a></li><li><a href="uid74.html&#10;&#9;&#9;  ">Formal semantics and model-based analysis of AADL specifications</a></li><li><a href="uid75.html&#10;&#9;&#9;  ">Refinement types for reactive system models</a></li><li><a href="uid77.html&#10;&#9;&#9;  ">Formal verification of timing aspects of cyber-physical systems using a contract theory</a></li></ul></div>
      <div class="TdmEntry">Bilateral Contracts and Grants with Industry<ul><li><a href="uid79.html&#10;&#9;&#9;  ">Bilateral Contracts with Industry</a></li><li><a href="uid87.html&#10;&#9;&#9;  ">Bilateral Grants with Industry</a></li></ul></div>
      <div class="TdmEntry">Partnerships and Cooperations<ul><li><a href="uid94.html&#10;&#9;&#9;  ">National Initiatives</a></li><li><a href="uid122.html&#10;&#9;&#9;  ">International Initiatives</a></li><li><a href="uid180.html&#10;&#9;&#9;  ">International Research Visitors</a></li></ul></div>
      <div class="TdmEntry">Dissemination<ul><li><a href="uid184.html&#10;&#9;&#9;  ">Promoting Scientific Activities</a></li><li><a href="uid206.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="tdmbibentmajor" href="bibliography.html">Major publications</a>
          </li>
          <li>
            <a id="tdmbibentyear" href="bibliography.html#year">Publications of the year</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 
	    2015</a> | <a href="http://www.inria.fr/en/teams/tea">Presentation of the Project-Team TEA</a> | <a href="https://team.inria.fr/TEA">TEA Web Site
	  </a></small>
        </div>
        <div id="head_adroite">
          <table class="qrcode">
            <tr>
              <td>
                <a href="tea.xml">
                  <img style="align:bottom; border:none" alt="XML" src="../static/img/icons/xml_motif.png"/>
                </a>
              </td>
              <td>
                <a href="tea.pdf">
                  <img style="align:bottom; border:none" alt="PDF" src="IMG/qrcode-tea-pdf.png"/>
                </a>
              </td>
              <td>
                <a href="../tea/tea.epub">
                  <img style="align:bottom; border:none" alt="e-pub" src="IMG/qrcode-tea-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="./uid4.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="./uid6.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">Motivations</h3>
        <p>Beyond the buzzword, a CPS is nothing new. In fact, it is an ubiquitous object of our everyday life. CPSs have evolved from individual independent units (e.g an ABS brake) to more and more integrated networks of units, which may be aggregated into larger components or sub-systems. For example, a transportation monitoring network aggregates monitored stations and trains through a large scale distributed system with relatively high latency. Each individual train is being controlled by a train control network, each car in the train has its own real-time bus to control embedded devices. More and more, CPSs are mixing real-time low latency technology with higher latency distributed computing technology.</p>
        <p>In the past 15 years, CPS development has moved towards Model Driven Engineering (MDE). With MDE methodology, first all requirements are gathered together with use cases, then a model of the system is built (sometimes several models) that satisfy the requirements. There are several modelling formalisms that have appeared in the past ten years with more or less success. The most successful are the <i>executable</i> models, models that can be exercised, tested and validated. This approach can be used for both software and hardware.</p>
        <p>A common feature found in CPSs is the ever presence of concurrency and parallelism in models.
Large systems are increasingly mixing both types of concurrency. They are structured hierarchically and comprise multiple synchronous devices connected by buses or networks that communicate asynchronously. This led to the advent of so-called GALS (Globally Asynchronous, Locally Synchronous) models, or PALS (Physically Asynchronous, Logically Synchronous) systems, where reactive synchronous objects are communicating asynchronously. Still, these infrastructures, together with their programming models, share some fundamental concerns: parallelism and concurrency synchronisation, determinism and functional correctness, scheduling optimality and calculation time predictability.</p>
        <p>Additionally, CPSs monitor and control real-world processes, the dynamics of which are usually governed by physical laws. These laws are expressed by physicists as mathematical equations and formulas. Discrete CPS models cannot ignore these dynamics, but whereas the equations express the continuous behaviour usually using real numbers (irrational) variables, the models usually have to work with discrete time and approximate floating point variables.</p>
      </div>
      <!--FIN du corps du module-->
      <br/>
      <div class="bottomNavigation">
        <div class="tail_aucentre">
          <a href="./uid4.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="./uid6.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>
