<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
	<link rel="self" type="application/atom+xml" href="http://localhost/app.php/feed/topic/100" />

	<title>Tools and Benchmarks for Real-Time Systems</title>
	<subtitle>ECRTS Community Forum</subtitle>
	<link href="http://localhost/index.php" />
	<updated>2017-06-12T08:19:08+01:00</updated>

	<author><name><![CDATA[Tools and Benchmarks for Real-Time Systems]]></name></author>
	<id>http://localhost/app.php/feed/topic/100</id>

		<entry>
		<author><name><![CDATA[loic_fejoz]]></name></author>
		<updated>2017-06-12T08:19:08+01:00</updated>

		<published>2017-06-12T08:19:08+01:00</published>
		<id>http://localhost/viewtopic.php?t=100&amp;p=199#p199</id>
		<link href="http://localhost/viewtopic.php?t=100&amp;p=199#p199"/>
		<title type="html"><![CDATA[Re: Abstract: Time4Sys in a Nutshell]]></title>

		
		<content type="html" xml:base="http://localhost/viewtopic.php?t=100&amp;p=199#p199"><![CDATA[
Just to let you know that the opening process has begun, even if this is early <strong class="text-strong">alpha</strong> stage.<br><br>The code can be found at <a href="https://github.com/polarsys/time4sys" class="postlink">https://github.com/polarsys/time4sys</a><br>One can download our nightly build (highly experimental) from our continuous build system : <a href="https://hudson.polarsys.org/time4sys/job/Time4Sys%20develop/" class="postlink">https://hudson.polarsys.org/time4sys/jo ... 20develop/</a><br><br>Unfortunately there is not that much documentation yet. Some might be found from <a href="https://github.com/polarsys/time4sys/tree/develop/Time4Sys/plugins/org.polarsys.time4sys.marte/docs" class="postlink">https://github.com/polarsys/time4sys/tr ... marte/docs</a><br>We are preparing full bundle of Capella / Time4Sys / RTaW-Pegase++ all together with videos of its usage nothing official yet.<p>Statistics: Posted by <a href="http://localhost/memberlist.php?mode=viewprofile&amp;u=69">loic_fejoz</a> — Mon Jun 12, 2017</p><hr />
]]></content>
	</entry>
		<entry>
		<author><name><![CDATA[Sophie Quinton]]></name></author>
		<updated>2017-06-07T09:30:23+01:00</updated>

		<published>2017-06-07T09:30:23+01:00</published>
		<id>http://localhost/viewtopic.php?t=100&amp;p=192#p192</id>
		<link href="http://localhost/viewtopic.php?t=100&amp;p=192#p192"/>
		<title type="html"><![CDATA[Abstract: Time4Sys in a Nutshell]]></title>

		
		<content type="html" xml:base="http://localhost/viewtopic.php?t=100&amp;p=192#p192"><![CDATA[
<strong class="text-strong">Title:</strong> Time4Sys in a Nutshell<br><br><strong class="text-strong">Authors:</strong><br>Yassine Ouhammou (LIAS/ISAE-ENSMA, Poitiers)<br>Loïc Fejoz (RealTime-at-Work)<br><br><strong class="text-strong">Abstract:</strong> Waruna project is a collaboration between academic and industrial actors funded through the French government grant called FUI (Fond Unique Interministriel). The underlying idea behind this four-years project (2015-2019) is that the temporal performance verification phase of real-time systems development life-cycle shall not be a barrier for non-experts of the domain. Hence, the main objective of Waruna project is to ease the integration of the temporal performance verification in engineering practices. Time4Sys is the framework derived from the Waruna project and whose development is in progress. As an integrated framework aiming to fill the gap between system engineering design models and timing models, Time4Sys is based on two components. The front-end which is dedicated to modellers in order to design real-time systems using a graphical language. The back-end shall be a customized part which allows modellers to analyze iteratively and accurately their designs with different analysis tools. The customization of the back-end consists of managing the transformation between designs and analysis tools and the orchestration of tests that correspond to the designs under-analysis. In other words, the flexibility of the back-end part enables to capitalize the experience of temporal verification analysts as a referential followed by modellers via the front-end without being obliged to have a deep knowledge of the temporal verification. Time4Sys is based on model-driven engineering settings and developed as a Polarsys plugin. Modeling, traceability, transformation, analysis, and result reporting activities are the pillars of the Time4Sys structure and are explicitly formalized as a set of meta-models.<br><br><strong class="text-strong">Attached paper:</strong><div class="inline-attachment"><dl class="file"><dt><span class="imageset icon_topic_attach"></span> <a class="postlink" href="http://localhost/download/file.php?id=80&amp;sid=44f9fbe1f9de38c7d9f0d0baf55fd8f2">WATERS_2017_Time4Sys.pdf</a></dt></dl></div><p>Statistics: Posted by <a href="http://localhost/memberlist.php?mode=viewprofile&amp;u=55">Sophie Quinton</a> — Wed Jun 07, 2017</p><hr />
]]></content>
	</entry>
	</feed>
