index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Time4Sys</title>
    <link>https://polarsys.org/time4sys/</link>
    <description>Recent content on Time4Sys</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 17 Nov 2017 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://polarsys.org/time4sys/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>About</title>
      <link>https://polarsys.org/time4sys/about/</link>
      <pubDate>Fri, 17 Nov 2017 00:00:00 +0000</pubDate>
      
      <guid>https://polarsys.org/time4sys/about/</guid>
      <description>PolarSys Time4Sys provides a framework that fills the gap between the capture of timing aspects in the design phase of a real-time system and the ability of specific/dedicated tools to verify the consistency and performances of a given scheduling.
Time4Sys is composed of two building blocks (the Design and the Analysis pivot models) as well as a set of transformation rules between them.
Design Pivot Model Time4Sys Design model uses a subset of the MARTE OMG standard as a basis to represent a synthetic view of the system design model that captures all elements, data and properties impacting the system timing behaviour and required to perform scheduling analysis or simulation (e.</description>
    </item>
    
    <item>
      <title>Building the website</title>
      <link>https://polarsys.org/time4sys/news/hello-world/</link>
      <pubDate>Fri, 17 Nov 2017 00:00:00 +0000</pubDate>
      
      <guid>https://polarsys.org/time4sys/news/hello-world/</guid>
      <description>&lt;p&gt;Article by &lt;strong&gt;Aurelien DIDIER&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We are starting to build a website for the PolarSys Time4Sys project.&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Community</title>
      <link>https://polarsys.org/time4sys/community/</link>
      <pubDate>Fri, 17 Nov 2017 00:00:00 +0000</pubDate>
      
      <guid>https://polarsys.org/time4sys/community/</guid>
      <description>Communication channels Communications Channels
Learn about Time4Sys, join the community, connect with other users, get support and service:
 Forum: Not yet available. Polarsys Wiki: Wiki providing additional resources about Time4Sys and Polarsys. Report a bug: Bugzilla for bug reporting and enhancement requests. [Mailing-list]: Not yet available. Polarsys project page: information about the project development.  Source Repositories You can use the code from these repositories to experiment, test, build, create patches, issue pull requests, etc.</description>
    </item>
    
    <item>
      <title>Downloads</title>
      <link>https://polarsys.org/time4sys/downloads/</link>
      <pubDate>Fri, 17 Nov 2017 00:00:00 +0000</pubDate>
      
      <guid>https://polarsys.org/time4sys/downloads/</guid>
      <description> Current Release (version - 2017-03-0) Products  Time4Sys - version for Windows (64 Bit) - [[Zip-archive]()(317.7 MB)  </description>
    </item>
    
    <item>
      <title>Polarsys Time4Sys</title>
      <link>https://polarsys.org/time4sys/</link>
      <pubDate>Fri, 17 Nov 2017 00:00:00 +0000</pubDate>
      
      <guid>https://polarsys.org/time4sys/</guid>
      <description>Context Usually, the industrial practices rely on the subjective judgment of experienced software architects and developers to predict how design decisions may impact the timing behavior of real-time embedded systems. This is however risky since eventual timing errors are only detected after implementation and integration, when the software execution can be tested on system level, under realistic conditions. At this stage, timing errors may be very costly and time consuming to correct.</description>
    </item>
    
    <item>
      <title>Videos</title>
      <link>https://polarsys.org/time4sys/videos/</link>
      <pubDate>Fri, 17 Nov 2017 00:00:00 +0000</pubDate>
      
      <guid>https://polarsys.org/time4sys/videos/</guid>
      <description>    </description>
    </item>
    
    <item>
      <title>Documentation</title>
      <link>https://polarsys.org/time4sys/documentation/</link>
      <pubDate>Wed, 07 Jun 2017 00:00:00 +0000</pubDate>
      
      <guid>https://polarsys.org/time4sys/documentation/</guid>
      <description> User Manual:
FirstSteps.pdf
Developer Manual:
UserInterface.pdf
Related documentation  Waruna: http://www.waruna-projet.fr/ Capella: https://polarsys.org/capella/ MoSaRT: https://forge.lias-lab.fr/projects/mosart  </description>
    </item>
    
    <item>
      <title>Getting Started with OpenCert</title>
      <link>https://polarsys.org/time4sys/gettingstarted/</link>
      <pubDate>Wed, 07 Jun 2017 00:00:00 +0000</pubDate>
      
      <guid>https://polarsys.org/time4sys/gettingstarted/</guid>
      <description>This section guides the end-user through the use of OpenCert.
Installation It must be noted that the pre-existing OpenCert tools are designed to follow client-server architecture approach:
 OpenCert server - installed in a central host machine One or many OpenCert clients - each of which installed on specific user machines  This installation relates to a standalone version of OpenCert, including Papyrus/CHESS plugins.
OpenCert can also use the Eclipse Process Framework (EPF) toolset.</description>
    </item>
    
  </channel>
</rss>