Google Git
Sign in
eclipse/gerrit/www.eclipse.org/app4mc/ce668e5e4d1ae4dfd4eefea7f9097072faac32ca/./index.xml
blob: 1ce14d5376a0f1265db172d77983981101cbd246 [file]
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Application Platform Project for MultiCore (APP4MC)</title>
<link>https://www.eclipse.org/app4mc/index.xml</link>
<description>Recent content on Application Platform Project for MultiCore (APP4MC)</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
<lastBuildDate>Wed, 16 Sep 2015 11:09:06 +0200</lastBuildDate>
<atom:link href="https://www.eclipse.org/app4mc/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>History</title>
<link>https://www.eclipse.org/app4mc/history/</link>
<pubDate>Wed, 16 Sep 2015 11:09:06 +0200</pubDate>
<guid>https://www.eclipse.org/app4mc/history/</guid>
<description>
&lt;hr /&gt;
&lt;h3 id=&#34;amalthea&#34;&gt;AMALTHEA&lt;/h3&gt;
&lt;hr /&gt;
&lt;p&gt;&lt;a href=&#34;https://itea3.org/project/amalthea.html&#34;&gt;AMALTHEA&lt;/a&gt; was a ITEA 2 funded European project
that developed an open and expandable tool platform for automotive embedded-system engineering
based on model-driven methodology.
Specific features include support for multi-core systems combined with AUTOSAR compatibility
and product-line engineering.
The resulting tool platform is distributed under an Eclipse public license.&lt;/p&gt;
&lt;dl class=&#34;dl-horizontal&#34;&gt;
&lt;dt&gt;Period&lt;/dt&gt;
&lt;dd&gt;Jul 2011 - Apr 2014&lt;/dd&gt;
&lt;dt&gt;Call&lt;/dt&gt;
&lt;dd&gt;ITEA 2 Call 4&lt;/dd&gt;
&lt;dt&gt;Challenge&lt;/dt&gt;
&lt;dd&gt;&lt;a href=&#34;https://itea3.org/challenge/engineering.html&#34; title=&#34;View challenge Engineering&#34; class=&#34;&#34;&gt;Engineering&lt;/a&gt;&lt;/dd&gt;
&lt;dt&gt;Website&lt;/dt&gt;
&lt;dd&gt;&lt;a title=&#34;http://www.amalthea-project.org/&#34; href=&#34;http://http://www.amalthea-project.org/&#34;&gt;http://www.amalthea-project.org/&lt;/a&gt;&lt;/dd&gt;
&lt;dt&gt;Partners&lt;/dt&gt;
&lt;dd&gt;15&lt;/dd&gt;
&lt;dt&gt;Effort&lt;/dt&gt;
&lt;dd&gt;58.39 &lt;abbr title=&#34;Person Year&#34;&gt;PY&lt;/abbr&gt; &lt;/dd&gt;
&lt;dt&gt;Countries&lt;/dt&gt;
&lt;dd&gt;&lt;img src=&#34;https://www.eclipse.org/app4mc/images/history/fin.png&#34; width=&#34;15&#34;&gt; &lt;a href=&#34;https://itea3.org/country/finland.html&#34;&gt;Finland&lt;/a&gt;&lt;/dd&gt;
&lt;dd&gt;&lt;img src=&#34;https://www.eclipse.org/app4mc/images/history/deu.png&#34; width=&#34;15&#34;&gt; &lt;a href=&#34;https://itea3.org/country/germany.html&#34;&gt;Germany&lt;/a&gt;&lt;/dd&gt;
&lt;dd&gt;&lt;img src=&#34;https://www.eclipse.org/app4mc/images/history/tur.png&#34; width=&#34;15&#34;&gt; &lt;a href=&#34;https://itea3.org/country/turkey.html&#34; &gt;Turkey&lt;/a&gt;&lt;/dd&gt;
&lt;/dl&gt;
&lt;hr /&gt;
&lt;h3 id=&#34;amalthea4public&#34;&gt;AMALTHEA4public&lt;/h3&gt;
&lt;hr /&gt;
&lt;p&gt;&lt;a href=&#34;https://itea3.org/project/amalthea4public.html&#34;&gt;AMALTHEA4public&lt;/a&gt; is a second ITEA 2 funded European project.
It has the goal to integrate the results of various publicly funded projects with new developments.
The intention is to position the open-source tool framework as a de-facto standard for future
software engineering design flows for automotive and other embedded systems.&lt;/p&gt;
&lt;dl class=&#34;dl-horizontal&#34;&gt;
&lt;dt&gt;Period&lt;/dt&gt;
&lt;dd&gt;Sep 2014 - Aug 2017&lt;/dd&gt;
&lt;dt&gt;Call&lt;/dt&gt;
&lt;dd&gt;ITEA 2 Call 8&lt;/dd&gt;
&lt;dt&gt;Challenge&lt;/dt&gt;
&lt;dd&gt;&lt;a href=&#34;https://itea3.org/challenge/engineering.html&#34; title=&#34;View challenge Engineering&#34; class=&#34;&#34;&gt;Engineering&lt;/a&gt;&lt;/dd&gt;
&lt;dt&gt;Website&lt;/dt&gt;
&lt;dd&gt;&lt;a title=&#34;http://www.amalthea-project.org/&#34; href=&#34;http://http://www.amalthea-project.org/&#34;&gt;http://www.amalthea-project.org/&lt;/a&gt;&lt;/dd&gt;
&lt;dt&gt;Partners&lt;/dt&gt;
&lt;dd&gt;20&lt;/dd&gt;
&lt;dt&gt;Effort&lt;/dt&gt;
&lt;dd&gt;80.90 &lt;abbr title=&#34;Person Year&#34;&gt;PY&lt;/abbr&gt; &lt;/dd&gt;
&lt;dt&gt;Countries&lt;/dt&gt;
&lt;dd&gt;&lt;img src=&#34;https://www.eclipse.org/app4mc/images/history/deu.png&#34; width=&#34;15&#34;&gt; &lt;a href=&#34;https://itea3.org/country/germany.html&#34;&gt;Germany&lt;/a&gt;&lt;/dd&gt;
&lt;dd&gt;&lt;img src=&#34;https://www.eclipse.org/app4mc/images/history/esp.png&#34; width=&#34;15&#34;&gt; &lt;a href=&#34;https://itea3.org/country/spain.html&#34; &gt;Spain&lt;/a&gt;&lt;/dd&gt;
&lt;dd&gt;&lt;img src=&#34;https://www.eclipse.org/app4mc/images/history/swe.png&#34; width=&#34;15&#34;&gt; &lt;a href=&#34;https://itea3.org/country/sweden.html&#34; &gt;Sweden&lt;/a&gt;&lt;/dd&gt;
&lt;dd&gt;&lt;img src=&#34;https://www.eclipse.org/app4mc/images/history/tur.png&#34; width=&#34;15&#34;&gt; &lt;a href=&#34;https://itea3.org/country/turkey.html&#34; &gt;Turkey&lt;/a&gt;&lt;/dd&gt;
&lt;/dl&gt;
</description>
</item>
<item>
<title>Downloads</title>
<link>https://www.eclipse.org/app4mc/downloads/</link>
<pubDate>Mon, 14 Sep 2015 16:35:03 +0200</pubDate>
<guid>https://www.eclipse.org/app4mc/downloads/</guid>
<description>
&lt;hr /&gt;
&lt;h3 id=&#34;current-release-0-8-0-2017-04-28&#34;&gt;Current Release (0.8.0 - 2017-04-28)&lt;/h3&gt;
&lt;hr /&gt;
&lt;h5 id=&#34;products&#34;&gt;Products&lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;APP4MC Platform 0.8.0 for &lt;strong&gt;Linux (64 Bit)&lt;/strong&gt; - &lt;a href=&#34;http://www.eclipse.org/downloads/download.php?file=/app4mc/products/releases/0.8.0/org.eclipse.app4mc.platform-0.8.0-20170428-125334-linux.gtk.x86_64.zip&#34;&gt;Zip-archive&lt;/a&gt; (316 MB)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;APP4MC Platform 0.8.0 for &lt;strong&gt;OSX (64 Bit)&lt;/strong&gt; - &lt;a href=&#34;http://www.eclipse.org/downloads/download.php?file=/app4mc/products/releases/0.8.0/org.eclipse.app4mc.platform-0.8.0-20170428-125334-macosx.cocoa.x86_64.zip&#34;&gt;Zip-archive&lt;/a&gt; (316 MB)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;APP4MC Platform 0.8.0 for &lt;strong&gt;Windows (32 Bit)&lt;/strong&gt; - &lt;a href=&#34;http://www.eclipse.org/downloads/download.php?file=/app4mc/products/releases/0.8.0/org.eclipse.app4mc.platform-0.8.0-20170428-125334-win32.win32.x86.zip&#34;&gt;Zip-archive&lt;/a&gt; (317 MB)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;APP4MC Platform 0.8.0 for &lt;strong&gt;Windows (64 Bit)&lt;/strong&gt; - &lt;a href=&#34;http://www.eclipse.org/downloads/download.php?file=/app4mc/products/releases/0.8.0/org.eclipse.app4mc.platform-0.8.0-20170428-125334-win32.win32.x86_64.zip&#34;&gt;Zip-archive&lt;/a&gt; (317 MB)&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h5 id=&#34;update-site&#34;&gt;Update Site&lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;direct link: &lt;a href=&#34;http://download.eclipse.org/app4mc/updatesites/releases/0.8.0/&#34;&gt;http://download.eclipse.org/app4mc/updatesites/releases/0.8.0/&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;for offline installation: &lt;a href=&#34;http://www.eclipse.org/downloads/download.php?file=/app4mc/products/releases/0.8.0/org.eclipse.app4mc.p2repo-0.8.0-201704281218.zip&#34;&gt;Zip-archive of APP4MC 0.8.0 p2 repository&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;hr /&gt;
&lt;p&gt;&lt;em&gt;For older versions please refer to:&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://projects.eclipse.org/projects/technology.app4mc/downloads&#34;&gt;Eclipse APP4MC project page&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://amalthea-project.org/index.php/downloads&#34;&gt;AMALTHEA/AMALTHEA4public project page&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
</item>
<item>
<title>Visit APP4MC/AMALTHEA4public at Digital Innovation Forum in Amsterdam</title>
<link>https://www.eclipse.org/app4mc/news/2017-05-10_DigitalInnovationForum_2017/</link>
<pubDate>Mon, 08 May 2017 00:00:00 +0000</pubDate>
<guid>https://www.eclipse.org/app4mc/news/2017-05-10_DigitalInnovationForum_2017/</guid>
<description>&lt;p&gt;On May, the 10 - 11th, APP4MC will be present at the exhibition of the Digital Innovation Forum in Amsterdam. We&amp;rsquo;ll present our latest platform developments and prototyps as well as some practitcal demonstrations developed with the APP4MC platform.
You can visit us at booth 8 on the exhibition floor
&lt;a href=&#34;https://dif2017.org/exhibition.html&#34;&gt;Digital Innovation Forum&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Demonstrators:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;SW distribution based on the Polarsys Rover chasis: (&lt;a href=&#34;https://wiki.eclipse.org/APP4MC/Rover&#34;&gt;https://wiki.eclipse.org/APP4MC/Rover&lt;/a&gt;)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;EBEAS - Emergency Braking &amp;amp; Evasion Assistance System:
Traceability throughout the engineering phases shown with an open source ADAS example&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img src=&#34;https://www.eclipse.org/app4mc/images/news/EBEAS_Designflow_small.png&#34; title=&#34;EBEAS Overview&#34; class=&#34;img-responsive&#34;&gt;&lt;/p&gt;</description>
</item>
<item>
<title>APP4MC - Release 0.8.0 published</title>
<link>https://www.eclipse.org/app4mc/news/2017-04-28_release_0.8.0/</link>
<pubDate>Fri, 28 Apr 2017 00:00:00 +0000</pubDate>
<guid>https://www.eclipse.org/app4mc/news/2017-04-28_release_0.8.0/</guid>
<description>&lt;p&gt;We released a new version of APP4MC with a couple of new features and improvements.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Extract of APP4MC 0.8.0&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;General&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Model changes (mainly to simplify handling)
Improved tooling: model utilities
New UI components: Multicore Wizard, Task-Visualizer (draft version)
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Model handling&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Model migration support (0.7.2 -&amp;gt; 0.8.0)
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Model changes / Improvements&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Simplified model handling: Mapping Model, Modes, Time
New classifiers to annotate Core and Memory
Reworked Property Constraints
Extended OS Overheads
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;For details see &lt;a href=&#34;https://projects.eclipse.org/projects/technology.app4mc/releases/0.8.0/bugs&#34;&gt;Release 0.8.0 issues&lt;/a&gt;
* Visit the &lt;a href=&#34;http://projects.eclipse.org/projects/technology.app4mc/downloads&#34;&gt;APP4MC download page&lt;/a&gt;&lt;/p&gt;</description>
</item>
<item>
<title>Visit APP4MC at DATE or Parallel conferences</title>
<link>https://www.eclipse.org/app4mc/news/2017-03-29_conferences_2017/</link>
<pubDate>Wed, 29 Mar 2017 00:00:00 +0000</pubDate>
<guid>https://www.eclipse.org/app4mc/news/2017-03-29_conferences_2017/</guid>
<description>&lt;p&gt;On March, the 30th, the talk &amp;lsquo;On Reducing Busy Waiting in AUTOSAR via Task-Release-Delta-based Runnable Reordering&amp;rsquo; (2pm) presents analyses regarding resource management based upon APP4MC at the &lt;a href=&#34;https://www.date-conference.com/conference/session/11.5&#34;&gt;Design, Automation and Test Conference and Exhibition (DATE)&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Furthermore, on Friday, March the 31st 10:40am, you can learn how to use APP4MC to analyize and optimize embedded multi-core systems and their performance at &lt;a href=&#34;https://www.parallelcon.de/veranstaltung-5701-performanceanalyse-und--optimierung-von-embedded-multicore-systemen.html?id=5701&#34;&gt;parallel2017&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Abstract DATE&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Below, please find the talk&amp;rsquo;s corresponding paper abstract for the DATE conference.&lt;/p&gt;
&lt;p&gt;The increasing amount of innovative software technologies in the automotive domain comes with challenges regarding inevitable distributed multi-core and many-core methodologies. Approaches for general purpose solutions have been studied over decades but do not completely meet the specific constraints (e.g. timing, safety, reliability, affinity, etc.) for AUTOSAR compliant applications. AUTOSAR utilizes a spinlock mechanism in combination with the priority ceiling protocol in order to provide mutually exclusive access to shared resources. The essential disadvantages of spinlocks are unpredictable task response times on the one hand and wasted computation time caused by busy waiting periods on the other hand. In this paper, we propose a concept of task-release-delta-based runnable reordering for the purpose of sequentializing parallel accesses to shared resources, resulting in reduced task response times, improved timing predictability, and increased parallel efficiency respectively. To achieve this, runnables that represent smallest executable program parts in AUTOSAR are reordered based on precedence constraints. Our experiments among industrial use cases show that task response times can be reduced by up to 18,2%.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Abstract parallel&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Based on the APP4MC Eclipse platform, we present the steps required in the development process to make the best use of Multicore controller&amp;rsquo;s resources. Depending on the development status and the need for analyses, different levels of detail are needed to make targeted evaluations. Examples show which data is required at which development process and what tools can be utilized to extract this data from different sources. The analyzes range from forecast generation in early development phases to the detailed distribution and optimization of the software artifacts to existing hardware.&lt;/p&gt;</description>
</item>
<item>
<title>APP4MC - Release 0.7.2 published</title>
<link>https://www.eclipse.org/app4mc/news/2017-01-31_release_0.7.2/</link>
<pubDate>Tue, 31 Jan 2017 00:00:00 +0000</pubDate>
<guid>https://www.eclipse.org/app4mc/news/2017-01-31_release_0.7.2/</guid>
<description>&lt;p&gt;The 1st official release of APP4MC is published. All IP checks are finally done and the official release review successfully passed.
We implemented some new features and enhancements according to project and user given requirements.
Further information and entire list of changes can be found in the APP4MC online help &lt;a href=&#34;https://www.eclipse.org/app4mc/documentation/&#34;&gt;https://www.eclipse.org/app4mc/documentation/&lt;/a&gt; or after platform installation&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Extract of APP4MC 0.7.2&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Model handling&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Model migration support (0.7.1 -&amp;gt; 0.7.2)
Improved back references
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Model changes&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;New core-specific runtimes (instructions) for runnables
New model elements for streaming communication (Channels)*
New Transmission Policy for communication (e.g. label accesses)
New Event-based Stimulus
New Data Consistency needs
New Counters for InterProcessActivation and EventStimulus
Harmonized model elements to describe probability
Storage of common elements (e.g. tags) in one central location
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Bug fixes / Improvements&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Model migration (ISR call graph, Section names, cross document references)
Back references (Memory -&amp;gt; Mapping, Scheduler -&amp;gt; CoreAllocation)
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Documentation&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;New model elements: Physical memory sections, Channels
New examples
&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;= Experimental feature (first modeling attempt that may change in future versions).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For details see Release 0.7.2 issues
* Visit the &lt;a href=&#34;http://projects.eclipse.org/projects/technology.app4mc/downloads&#34;&gt;APP4MC download page&lt;/a&gt;&lt;/p&gt;</description>
</item>
<item>
<title>APP4MC - milestone 0.7.1 published</title>
<link>https://www.eclipse.org/app4mc/news/2016-11-04_milestone_release_0.7.1/</link>
<pubDate>Fri, 04 Nov 2016 00:00:00 +0000</pubDate>
<guid>https://www.eclipse.org/app4mc/news/2016-11-04_milestone_release_0.7.1/</guid>
<description>&lt;p&gt;A new milestone of APP4MC is published. There are new features and enhancements implemented according to project and user given requirements.
Further information and entire list of changes can be found in the APP4MC help (after installation).&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Extract of APP4MC 0.7.1&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Model handling&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Model migration support (0.7.0 -&amp;gt; 0.7.1)&lt;/li&gt;
&lt;li&gt;Improved update of opposite references&lt;/li&gt;
&lt;li&gt;Storage of default values is enabled by default&lt;/li&gt;
&lt;li&gt;New check based model validations (performance, Timing-Architects conformance,..)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Model changes&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;New distribution &amp;ldquo;Beta Distribution&amp;rdquo;&lt;/li&gt;
&lt;li&gt;New stimuli type &amp;ldquo;Synthetic&amp;rdquo; (to &amp;ldquo;replay&amp;rdquo; activations from a hardware trace)&lt;/li&gt;
&lt;li&gt;New DataStabilityGroup&lt;/li&gt;
&lt;li&gt;Introduced SamplingType as new attribute for Deviation&lt;/li&gt;
&lt;li&gt;Introduced physical memory sections (PhysicalSectionConstraint, PhysicalSectionMapping)&lt;/li&gt;
&lt;li&gt;Reworked AffinityConstraints (removed Scheduler constraints, added Data constraints)&lt;/li&gt;
&lt;li&gt;Reworked Event / Event-Chain Constraints&lt;/li&gt;
&lt;li&gt;Reworked RunnableSequencingConstraints&lt;/li&gt;
&lt;li&gt;New types for DataSizes and DataRates&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To find out more:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;View Bugzilla list
(&lt;a href=&#34;https://bugs.eclipse.org/bugs/buglist.cgi?product=App4mc&amp;amp;target_milestone=0.7.1&#34;&gt;https://bugs.eclipse.org/bugs/buglist.cgi?product=App4mc&amp;amp;target_milestone=0.7.1&lt;/a&gt;)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Visit the &lt;a href=&#34;http://projects.eclipse.org/projects/technology.app4mc/downloads&#34;&gt;APP4MC download page&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;</description>
</item>
<item>
<title>Visit APP4MC at EclipseCon Europe 2016</title>
<link>https://www.eclipse.org/app4mc/news/2016-10-17_ECE_2016/</link>
<pubDate>Mon, 17 Oct 2016 00:00:00 +0000</pubDate>
<guid>https://www.eclipse.org/app4mc/news/2016-10-17_ECE_2016/</guid>
<description>&lt;p&gt;Learn more about APP4MC and see it in action at &lt;a href=&#34;https://eclipsecon.org/europe2016/&#34;&gt;EclipseCon Europe 2016&lt;/a&gt;. Explore APP4MC through a demo of a radio-controlled car at the &lt;a href=&#34;https://www.eclipsecon.org/europe2016/playground&#34;&gt;IoT Playground&lt;/a&gt; on Wednesday. Start the week by meeting members of the project team at the
&lt;a href=&#34;https://wiki.eclipse.org/Eclipse_Unconference_Europe_2016#Unconference_Agenda&#34;&gt;Unconference&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Unconference&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The APP4MC project team will be participating at this year&amp;rsquo;s &lt;a href=&#34;https://wiki.eclipse.org/Eclipse_Unconference_Europe_2016#Unconference_Agenda&#34;&gt;Unconference&lt;/a&gt; as part of a meeting of two new Working Groups in the automotive domain, OpenMDM and OpenPASS.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;APP4MC in the IoT Playground&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Drop by the &lt;a href=&#34;https://www.eclipsecon.org/europe2016/playground&#34;&gt;IoT Playground&lt;/a&gt; on Wednesday to explore the potential of the APP4MC platform when used to control a radio-controlled car. Implemented features include visual traffic cone detection and ultrasonic sensor-based obstacle detection. The platform creates models with various configurations and timing behaviors that can be observed and investigated, as well as selected and combined into different features of the car.&lt;/p&gt;</description>
</item>
<item>
<title>AMALTHEA4public - 2nd annual review passed</title>
<link>https://www.eclipse.org/app4mc/news/2016-09-28_itea-review/</link>
<pubDate>Wed, 28 Sep 2016 00:00:00 +0000</pubDate>
<guid>https://www.eclipse.org/app4mc/news/2016-09-28_itea-review/</guid>
<description>&lt;p&gt;The 2nd annual project review held in Bilbao is passed.
The project itself presented the work of the last year to show the outcome and usage of the AMALTHEA data model and the APP4MC platform.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;AMALTHEA4public&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Overall the results and feedback of the reviewers were positive. The expectation for the last period of the project is the broader usage and an increasing involvement of outside partners.&lt;/p&gt;
&lt;p&gt;To find out more:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Visit the &lt;a href=&#34;https://itea3.org/project/amalthea4public.html&#34;&gt;ITEA project page&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description>
</item>
<item>
<title>Capra Project Created</title>
<link>https://www.eclipse.org/app4mc/news/2016-08-05_capra_project_created/</link>
<pubDate>Thu, 04 Aug 2016 00:00:00 +0000</pubDate>
<guid>https://www.eclipse.org/app4mc/news/2016-08-05_capra_project_created/</guid>
<description>&lt;p&gt;Capra, the dedicated traceability management tool is now an official Eclipse EMF project. It allows the creation, management, visualisation, and analysis of trace links within Eclipse. Eclipse Capra is also one of the results of the Amalthea4public project and shares close ties with Eclipse APP4MC.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;About Capra&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Capra is a dedicated traceability management tool that allows the creation, management, visualisation, and analysis of trace links within Eclipse. Trace links can be created between arbitrary artefacts, including all EMF model elements, all types of source code files supported by the Eclipse Platform through specialised development tools, tickets and bugs managed by Eclipse Mylyn, and all other artefacts for which an appropriate wrapper is provided. Capra is highly configurable and allows users to create their own traceability meta-model.&lt;/p&gt;
&lt;p&gt;To find out more:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Visit the &lt;a href=&#34;https://projects.eclipse.org/projects/modeling.capra&#34;&gt;Capra project page&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Read the &lt;a href=&#34;https://projects.eclipse.org/projects/modeling.capra/reviews/creation-review&#34;&gt;Capra Creation Review&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Stay tuned for more over the coming weeks!&lt;/p&gt;</description>
</item>
<item>
<title>FMTV Challenge 2016</title>
<link>https://www.eclipse.org/app4mc/news/2016-07-05_fmtv_challenge/</link>
<pubDate>Tue, 05 Jul 2016 00:00:00 +0000</pubDate>
<guid>https://www.eclipse.org/app4mc/news/2016-07-05_fmtv_challenge/</guid>
<description>&lt;p&gt;The Formal Methods for Timing Verification challenge
(&lt;a href=&#34;https://waters2016.inria.fr/challenge/&#34;&gt;FMTV&lt;/a&gt;)
at International Workshop on Analysis Tools and Methodologies
for Embedded and Real-time Systems
(&lt;a href=&#34;http://waters2016.inria.fr/&#34;&gt;WATERS&lt;/a&gt;)
is based on an Amalthea model of a Bosch Engine Control.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;About the FMTV Challenge&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The purpose of the Formal Methods for Timing Verification (FMTV) challenge is to share ideas, experiences and solutions to a concrete timing verification problem issued from real industrial case studies. It also aims at promoting discussions, closer interactions, cross fertilization of ideas and synergies across the breadth of the real-time research community, as well as attracting industrial practitioners from different domains having a specific interest in timing verification.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The 2016 FMTV Challenge&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The 2016 challenge is proposed by Arne Hamann, Simon Kramer, Martin Lukasiewycz and Dirk Ziegenbein from Robert Bosch GmbH.&lt;/p&gt;
&lt;p&gt;An initial version of the challenge is available here:
&lt;a href=&#34;http://ecrts.eit.uni-kl.de/forum/download/file.php?id=35&#34;&gt;FMTV_challenge_2016_Bosch.pdf&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The model can be downloaded here:
&lt;a href=&#34;http://ecrts.eit.uni-kl.de/forum/download/file.php?id=36&#34;&gt;FMTV_Challenge_2016_Bosch_Engine_Control_Model.zip&lt;/a&gt;&lt;/p&gt;</description>
</item>
<item>
<title>Getting Started with APP4MC</title>
<link>https://www.eclipse.org/app4mc/gettingstarted/</link>
<pubDate>Mon, 04 Jul 2016 00:00:00 +0000</pubDate>
<guid>https://www.eclipse.org/app4mc/gettingstarted/</guid>
<description>
&lt;p&gt;This tutorial will get you started with APP4MC. It is based on APP4MC version 0.7.0.&lt;/p&gt;
&lt;hr /&gt;
&lt;h4 id=&#34;tutorial-1-create-an-amalthea-model&#34;&gt;Tutorial 1 - Create an AMALTHEA model&lt;/h4&gt;
&lt;hr /&gt;
&lt;p&gt;The purpose of this tutorial is to get familiar with the structure
of the AMALTHEA model itself as well as the currently available editor.&lt;br /&gt;
It contains step by step directions to create a project, a model folder
and several model files.&lt;br /&gt;
&lt;a href=&#34;../gs-create-model&#34;&gt;start tutorial&lt;/a&gt;&lt;/p&gt;
</description>
</item>
<item>
<title>Summer School Automotive 2016</title>
<link>https://www.eclipse.org/app4mc/news/2016-06-27_summer_school_automotive_2016/</link>
<pubDate>Mon, 27 Jun 2016 00:00:00 +0000</pubDate>
<guid>https://www.eclipse.org/app4mc/news/2016-06-27_summer_school_automotive_2016/</guid>
<description>&lt;p&gt;Summer School
at the University of Applied Sciences and Arts in Dortmund
from the 27th of June until the 1st of July 2016&lt;/p&gt;
&lt;p&gt;More about the &lt;a href=&#34;https://internationalresearchdortmund.wikispaces.com/Automotive2016&#34;&gt;Summer School&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h2 id=&#34;automotive-software-engineering&#34;&gt;Automotive Software Engineering&lt;/h2&gt;
&lt;h3 id=&#34;target-develop-a-software-system-for-a-multicore-microcontroller-with-the-amalthea-tool-chain&#34;&gt;Target: develop a software system for a multicore microcontroller with the AMALTHEA tool chain&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Trainers:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Lukas Krawczyk, Uwe Lauschner, Robert Hoettger, Phil Naerdemann (Dortmund University of Applied Sciences and Arts)&lt;/li&gt;
&lt;li&gt;Jan Meel (KU Leuven)&lt;/li&gt;
&lt;li&gt;Andreas Sailer (Timing-Architects Embedded Systems GmbH)&lt;/li&gt;
&lt;li&gt;Lothar Wendehals (itemis AG)&lt;/li&gt;
&lt;li&gt;Mikael Barbero (Eclipse Foundation Europe)&lt;/li&gt;
&lt;li&gt;Markus Schmidt (Behr-Hella Thermocontrol GmbH)&lt;/li&gt;
&lt;/ul&gt;</description>
</item>
<item>
<title>APP4MC Talk EclipseCon France 2016</title>
<link>https://www.eclipse.org/app4mc/news/2016-06-08__eclipsecon_france_2016__capra/</link>
<pubDate>Wed, 08 Jun 2016 00:00:00 +0000</pubDate>
<guid>https://www.eclipse.org/app4mc/news/2016-06-08__eclipsecon_france_2016__capra/</guid>
<description>&lt;p&gt;At EclipseCon France 2016, Toulouse - &lt;a href=&#34;https://www.eclipsecon.org/france2016/session/capra-configurable-and-extendable-emf-based-traceability-tool&#34;&gt;Capra: A Configurable and Extendable EMF based Traceability Tool&lt;/a&gt;&lt;br /&gt;
&lt;em&gt;Presentation by &lt;strong&gt;Salome Maro&lt;/strong&gt;, Gothenburg University&lt;/em&gt;
&lt;/p&gt;</description>
</item>
<item>
<title>Getting Started with APP4MC</title>
<link>https://www.eclipse.org/app4mc/gs-create-model/</link>
<pubDate>Fri, 13 May 2016 00:00:00 +0000</pubDate>
<guid>https://www.eclipse.org/app4mc/gs-create-model/</guid>
<description>
&lt;h1 id=&#34;general-model-content&#34;&gt;General model content&lt;/h1&gt;
&lt;p&gt;The purpose of this session is to get familiar with the structure of the &lt;strong&gt;AMALTHEA model&lt;/strong&gt; itself as well as the currently available editor. Therefore, a new model should be created in its own project using the following steps and content.&lt;/p&gt;
&lt;p&gt;The following image is a simplified overview of the model that will be created in this session.&lt;/p&gt;
&lt;div style=&#34;text-align: center&#34;&gt;&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/training-overview-model.png&#34; class=&#34;img-responsive&#34;&gt; &lt;/div&gt;
&lt;hr /&gt;
&lt;h2 id=&#34;general-model-setup&#34;&gt;General model setup&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Create a new general project named &lt;em&gt;org.eclipse.amalthea.training.model&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;From the &lt;strong&gt;File&lt;/strong&gt; menu, select the item &lt;strong&gt;New &amp;gt; Project&amp;hellip;&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;On the first page of the wizard, expand the item &lt;strong&gt;General&lt;/strong&gt;
and select &lt;strong&gt;Project&lt;/strong&gt;. Then click &lt;strong&gt;Next&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;On the second page of the wizard fill the &lt;strong&gt;Project name&lt;/strong&gt; field
with &lt;em&gt;org.eclipse.amalthea.training.model&lt;/em&gt;, then click &lt;strong&gt;Finish&lt;/strong&gt;&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/01-create-project.png&#34; class=&#34;img-responsive&#34;&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;The project created should appear in the &lt;strong&gt;Model Explorer&lt;/strong&gt; view
&lt;br /&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a new folder named &amp;ldquo;model1&amp;rdquo; inside the created project&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the created project&lt;/li&gt;
&lt;li&gt;In the context menu (right mouse button) select &lt;strong&gt;New &amp;gt; Folder&lt;/strong&gt;&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/02-create-folder.png&#34; class=&#34;img-responsive&#34;&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Fill the text field &lt;strong&gt;Folder name&lt;/strong&gt; with &lt;em&gt;model1&lt;/em&gt;, then click &lt;strong&gt;Finish&lt;/strong&gt;&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/03-create-folder.png&#34; class=&#34;img-responsive&#34;&gt;&lt;br /&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a new AMALTHEA model&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the folder named &lt;em&gt;model1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;In the context menu, select &lt;strong&gt;New &amp;gt; AMALTHEA Model&lt;/strong&gt;&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/04-create-model.png&#34; class=&#34;img-responsive&#34;&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;In the dialog
&lt;ul&gt;
&lt;li&gt;Keep the defaults (ie. folder: &amp;ldquo;model1&amp;rdquo;, filename: &amp;ldquo;default.amxmi&amp;rdquo;)&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;Finish&lt;/strong&gt; to create an empty model&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;The model is created and the standard AMALTHEA tree editor
is opened on the left side of the workbench.&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/05-create-model.png&#34; class=&#34;img-responsive&#34;&gt;&lt;br /&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;hr /&gt;
&lt;h2 id=&#34;adding-software-structure&#34;&gt;Adding software structure&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Right-click on the AMALTHEA model on the tree editor then select the menu item &lt;strong&gt;New Child &amp;gt; Sw Model&lt;/strong&gt;.&lt;br /&gt;
It will add a child node named &lt;strong&gt;Software&lt;/strong&gt; to the model&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/06-create-sw-model.png&#34; class=&#34;img-responsive&#34;&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a label named &lt;em&gt;LabelA&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Under the &lt;strong&gt;Software&lt;/strong&gt; item select the &lt;strong&gt;Labels&lt;/strong&gt; item and right-click on &lt;strong&gt;New Child &amp;gt; Label&lt;/strong&gt;.&lt;br /&gt;
This will add a new child under &lt;strong&gt;Labels&lt;/strong&gt; by default labeled &lt;strong&gt;Label&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Select this &lt;em&gt;Label&lt;/em&gt; then click on the &lt;strong&gt;Properties&lt;/strong&gt; tab below the tree editor to display the label properties.&lt;/li&gt;
&lt;li&gt;Click on the cell next to the property named &lt;strong&gt;Name&lt;/strong&gt; and fill it with &lt;em&gt;LabelA&lt;/em&gt;.&lt;br /&gt;
Press enter. The label item in the tree editor should be renamed &lt;em&gt;LabelA&lt;/em&gt;.&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/07-create-label.png&#34; class=&#34;img-responsive&#34;&gt;&lt;br /&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a label named &lt;em&gt;LabelB&lt;/em&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a Runnable named &lt;em&gt;Runnable1&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Under the &lt;strong&gt;Software&lt;/strong&gt; item select the &lt;strong&gt;Runnables&lt;/strong&gt; item and right-click on &lt;strong&gt;New Child &amp;gt; Runnable&lt;/strong&gt;.&lt;br /&gt;
This will add a new child under &lt;strong&gt;Runnables&lt;/strong&gt; by default labeled &lt;strong&gt;Runnable&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Select this &lt;em&gt;Runnable&lt;/em&gt; then click on the &lt;strong&gt;Properties&lt;/strong&gt; tab below the tree editor to name it &lt;em&gt;Runnable1&lt;/em&gt;.
&lt;br /&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create 2 additional runnables named respectively &lt;em&gt;Runnable2&lt;/em&gt; and &lt;em&gt;Runnable3&lt;/em&gt;.&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/08-create-runnables.png&#34; class=&#34;img-responsive&#34;&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Expand the runnable named &lt;em&gt;Runnable1&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Create an instance of * instructions (constant) 20 *
&lt;ul&gt;
&lt;li&gt;From the context menu under &lt;strong&gt;Runnable Items&lt;/strong&gt;, select &lt;strong&gt;New Child &amp;gt; Instructions Constant&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Select the child created then click on the &lt;strong&gt;Properties&lt;/strong&gt; tab above the tree editor.&lt;/li&gt;
&lt;li&gt;Change the value of the &lt;strong&gt;Value&lt;/strong&gt; property to &lt;em&gt;20&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;Create a &lt;em&gt;write access to LabelA&lt;/em&gt;
&lt;ul&gt;
&lt;li&gt;Create another runnable item by selecting the menu item &lt;strong&gt;New Child &amp;gt; Label Access&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Select the child created then click on the &lt;strong&gt;Properties&lt;/strong&gt; tab above the tree editor.&lt;/li&gt;
&lt;li&gt;Select for the &lt;strong&gt;Access&lt;/strong&gt; property the value &lt;em&gt;write&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Select for the &lt;strong&gt;Data&lt;/strong&gt; property the value &lt;em&gt;Label LabelA&lt;/em&gt;&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/09-create-runnable1-label-access.png&#34; class=&#34;img-responsive&#34;&gt;&lt;br /&gt;
&lt;br /&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Expand the runnable named &lt;em&gt;Runnable2&lt;/em&gt; and, under its runnable items:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Create a &lt;em&gt;read access to LabelA&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Create a &lt;em&gt;25 constant instructions&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Create a &lt;em&gt;write access to LabelB&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Expand the runnable named &lt;em&gt;Runnable3&lt;/em&gt; and, under its runnable items:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Create a &lt;em&gt;read access to LabelB&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Create a &lt;em&gt;10 constant instructions&lt;/em&gt;&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/10-create-runnables-final.png&#34; class=&#34;img-responsive&#34;&gt;&lt;br /&gt;
&lt;br /&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create 3 tasks named respectively &lt;em&gt;Task1&lt;/em&gt;, &lt;em&gt;Task2&lt;/em&gt; and &lt;em&gt;Task3&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Under the &lt;strong&gt;Software&lt;/strong&gt; item select the &lt;strong&gt;Tasks&lt;/strong&gt; item and right-click on &lt;strong&gt;New Child &amp;gt; Task&lt;/strong&gt;.&lt;br /&gt;
It will add a new child by default labeled &lt;strong&gt;Task&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Select this &lt;em&gt;Task&lt;/em&gt; then click on the &lt;strong&gt;Properties&lt;/strong&gt; tab above the tree editor to name it &lt;em&gt;Task1&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;Repeat these steps to create the 2 other tasks.&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a &lt;em&gt;CallGraph&lt;/em&gt; for the task &lt;em&gt;Task1&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Right-click on the task named &lt;em&gt;Task1&lt;/em&gt; then select the menu item &lt;strong&gt;New Child &amp;gt; Call Graph&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Create a Call Sequence &lt;em&gt;CS1&lt;/em&gt;
&lt;ul&gt;
&lt;li&gt;Expand the task &lt;em&gt;Task1&lt;/em&gt; to visualize its child&lt;/li&gt;
&lt;li&gt;Right-click on the &lt;strong&gt;Call Graph&lt;/strong&gt; child then select the menu item &lt;strong&gt;New Child &amp;gt; Graph Entries &amp;gt; Call Sequence&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Name this new call sequence &lt;em&gt;CS1&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;Create a Task Runnable Call to &lt;em&gt;Runnable1&lt;/em&gt;
&lt;ul&gt;
&lt;li&gt;Right-click on the call sequence &lt;em&gt;CS1&lt;/em&gt;&lt;br /&gt;
then select the menu item &lt;strong&gt;New Child &amp;gt; Calls &amp;gt; Task Runnable Call&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Select the created child then click on the &lt;strong&gt;Properties&lt;/strong&gt; tab&lt;br /&gt;
and set the &lt;strong&gt;Runnable&lt;/strong&gt; property to &lt;em&gt;Runnable Runnable1&lt;/em&gt;.&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a &lt;em&gt;CallGraph&lt;/em&gt; for the task &lt;em&gt;Task2&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Right-click on the task named &lt;em&gt;Task2&lt;/em&gt; then select the menu item &lt;strong&gt;New Child &amp;gt; Call Graph&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Create a Call Sequence &lt;em&gt;CS1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Create a Task Runnable Call to &lt;em&gt;Runnable2&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a &lt;em&gt;CallGraph&lt;/em&gt; for the task &lt;em&gt;Task3&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Right-click on the task named &lt;em&gt;Task3&lt;/em&gt; then select the menu item &lt;strong&gt;New Child &amp;gt; Call Graph&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Create a Call Sequence &lt;em&gt;CS1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Create a Task Runnable Call to &lt;em&gt;Runnable3&lt;/em&gt;&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/11-create-task-runnable-calls.png&#34; class=&#34;img-responsive&#34;&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;hr /&gt;
&lt;h2 id=&#34;add-stimuli-to-tasks&#34;&gt;Add Stimuli to Tasks&lt;/h2&gt;
&lt;p&gt;Stimuli are describing the activation of Tasks.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Create 3 Stimuli named &lt;em&gt;Stimuli1&lt;/em&gt;, &lt;em&gt;Stimuli2&lt;/em&gt;, and &lt;em&gt;Stimuli3&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Right-click on the AMALTHEA model on the tree editor then select the menu item &lt;strong&gt;New Child &amp;gt; Stimuli Model&lt;/strong&gt;.&lt;br /&gt;
It will add a child node named &lt;strong&gt;Stimuli&lt;/strong&gt; to the model.&lt;/li&gt;
&lt;li&gt;Create a Periodic Stimuli named &lt;em&gt;Stimuli1&lt;/em&gt; and set the recurrence to 10ms
&lt;ul&gt;
&lt;li&gt;Right-click on the Stimuli Model and select the menu item &lt;strong&gt;New Child &amp;gt; Stimuli &amp;gt; Periodic&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Expand the &lt;em&gt;Stimuli&lt;/em&gt; node to visualize the created child.&lt;/li&gt;
&lt;li&gt;Select the Child named by default &lt;em&gt;Periodic&lt;/em&gt; then rename it &lt;em&gt;Stimuli1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Right-click on the renamed stimuli and select the menu item &lt;strong&gt;New Child &amp;gt; Recurrence&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Select the created Recurrence&lt;/li&gt;
&lt;li&gt;Set the value of the &lt;strong&gt;Unit&lt;/strong&gt; property to &lt;em&gt;ms&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the value of the &lt;strong&gt;Value&lt;/strong&gt; property to &lt;em&gt;10&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;Create a seconde Periodic Stimuli named *Stimuli2&amp;rdquo; and set the recurrence to 30ms&lt;/li&gt;
&lt;li&gt;Create an Inter Process Stimuli named &lt;em&gt;Stimuli3&lt;/em&gt; and set the recurrence to 10ms
&lt;ul&gt;
&lt;li&gt;Right-click on the Stimuli Model and select the menu item &lt;strong&gt;New Child &amp;gt; Stimuli &amp;gt; Inter Process&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Select the Inter Process node and name it &lt;strong&gt;Stimuli3&lt;/strong&gt;&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/12-create-stimuli.png&#34; class=&#34;img-responsive&#34;/&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add the Stimuli &lt;em&gt;Stimuli1&lt;/em&gt; to the task &lt;em&gt;Task1&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Retrieve and select the task &lt;em&gt;Task1&lt;/em&gt; which is located under the nodes AMALTHEA / Softwares / Tasks.&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/13-task1-stimulus-1.png&#34; class=&#34;img-responsive&#34;/&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;On the &lt;strong&gt;Properties&lt;/strong&gt;, click on the button next to the field
(&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/ui-edit-button.png&#34;/&gt;)
to open relationship dialog&lt;/li&gt;
&lt;li&gt;Select the Stimuli &lt;em&gt;Periodic Stimuli1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Press the &lt;strong&gt;Add&lt;/strong&gt; button&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/14-task1-stimulus-2.png&#34; class=&#34;img-responsive&#34;/&gt;&lt;br /&gt;&lt;/li&gt;
&lt;li&gt;Press &lt;strong&gt;OK&lt;/strong&gt; to close the dialog.&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add the Stimuli &lt;em&gt;Stimuli2&lt;/em&gt; to the task &lt;em&gt;Task2&lt;/em&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add the Stimuli &lt;em&gt;Stimuli3&lt;/em&gt; to the task &lt;em&gt;Task3&lt;/em&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add an &lt;em&gt;Interprocess Activation&lt;/em&gt; from &lt;em&gt;Task2&lt;/em&gt; to &lt;em&gt;Task3&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Expand the &lt;em&gt;Task2&lt;/em&gt;,&lt;/li&gt;
&lt;li&gt;Expand its &lt;em&gt;Call Graph&lt;/em&gt; node&lt;/li&gt;
&lt;li&gt;Select the call sequence &lt;strong&gt;CS1&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Right-click on the node and select the menu item &lt;strong&gt;New Child &amp;gt; Calls &amp;gt; Inter Process Activation&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Select the created node and in the &lt;em&gt;Stimuli&lt;/em&gt; property, select the Stiuli named &lt;strong&gt;Inter Process Stimuli3&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;hr /&gt;
&lt;h2 id=&#34;create-simple-hardware-model&#34;&gt;Create simple hardware model&lt;/h2&gt;
&lt;p&gt;In this section we are creating a simple hardware model with 2 cores and 1 global memory.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Right-click on the AMALTHEA model on the tree editor then select the menu item &lt;strong&gt;New Child &amp;gt; Hw Model&lt;/strong&gt;.&lt;br /&gt;
It will add a child node named &lt;strong&gt;Hardware&lt;/strong&gt; to the model&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a new system name &lt;em&gt;DemoSystem&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the &lt;em&gt;Hardware&lt;/em&gt; node previously created&lt;/li&gt;
&lt;li&gt;Right-click on the item then select the menu item &lt;strong&gt;New Child &amp;gt; System&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Name the created item &lt;em&gt;DemoSystem&lt;/em&gt; [PK: Is it expected that there is no type from this System?]&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a new ECU named &lt;em&gt;Ecu1&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the system named &lt;em&gt;DemoSystem&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Right-click on the item then select the menu item &lt;strong&gt;New Child &amp;gt; ECU&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Name the created item &lt;em&gt;Ecu1&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a microcontroller named &lt;em&gt;MC1&lt;/em&gt; to the ECU &lt;em&gt;Ecu1&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the ECU &lt;em&gt;Ecu1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Right-click on the item then select the menu item &lt;strong&gt;New Child &amp;gt; Microcontroller&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Name the created item &lt;em&gt;MC1&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a memory type named &lt;em&gt;GlobalMemoryType&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the &lt;em&gt;Hardware&lt;/em&gt; node under the AMALTHEA model node&lt;/li&gt;
&lt;li&gt;Right-click on the item then select the menu item &lt;strong&gt;New Child &amp;gt; Memory type&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Set the name to &lt;em&gt;GlobalMemoryType&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the size of memory to &lt;em&gt;512&lt;/em&gt; (bytes)&lt;/li&gt;
&lt;li&gt;Set the type of memory to RAM&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a memory named &lt;em&gt;GlobalMemory&lt;/em&gt; to &lt;em&gt;MC1&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the microcontroller &lt;em&gt;MC1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Right-click on the item then select the menu item &lt;strong&gt;New Child &amp;gt; Memory&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Name the created item &lt;em&gt;GlobalMemory&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the type to &lt;em&gt;Memory Type GlobalMemoryType&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a quartz &amp;ldquo;100MHz&amp;rdquo; to &amp;ldquo;MC1&amp;rdquo;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the microcontroller &lt;em&gt;MC1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Right-click on the item then select the menu item &lt;strong&gt;New Child &amp;gt; Quartz&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Name the created item &lt;em&gt;100MHz&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Frequency&lt;/strong&gt; property to &lt;em&gt;100000000&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create a core type named &lt;em&gt;CT1&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the &lt;em&gt;Hardware&lt;/em&gt; node under the AMALTHEA model node&lt;/li&gt;
&lt;li&gt;Right-click on the item then select the menu item &lt;strong&gt;New Child &amp;gt; Core type&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Set the name to &lt;em&gt;CT1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set &lt;strong&gt;Instructions Per Cycle&lt;/strong&gt; roperty of the core type to &lt;em&gt;1&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a core &amp;ldquo;Core1&amp;rdquo; to &amp;ldquo;MC1&amp;rdquo;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the microcontroller &lt;em&gt;MC1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Right-click on the item then select the menu item &lt;strong&gt;New Child &amp;gt; Core&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Name the created item &lt;em&gt;Core1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set core type of &amp;ldquo;Core1&amp;rdquo; to &amp;ldquo;CT1&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a &lt;strong&gt;Prescaler&lt;/strong&gt; named &lt;em&gt;PS1&lt;/em&gt; to &lt;em&gt;Core1&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the core &lt;em&gt;Core1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Right-click on the item then select the menu item &lt;strong&gt;New Child &amp;gt; Prescaler&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Name the created item &lt;em&gt;PS1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Clock Ratio&lt;/strong&gt; property to &lt;em&gt;1.0&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Quartz&lt;/strong&gt; property to &amp;ldquo;100Mhz&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a core &amp;ldquo;Core2&amp;rdquo; to &amp;ldquo;MC1&amp;rdquo;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Set core type of &amp;ldquo;Core2&amp;rdquo; to &amp;ldquo;CT1&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a &lt;strong&gt;Prescaler&lt;/strong&gt; named &lt;em&gt;PS2&lt;/em&gt; to &lt;em&gt;Core2&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Add prescaler &amp;ldquo;PS2&amp;rdquo; to &amp;ldquo;Core1&amp;rdquo;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Clock Ratio&lt;/strong&gt; property to 2.0&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Quartz&lt;/strong&gt; property to &amp;ldquo;100Mhz&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a &lt;strong&gt;Latency Path&lt;/strong&gt; from cores to memory&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Create a &lt;strong&gt;Latency Access Path&lt;/strong&gt; named &lt;em&gt;Path1&lt;/em&gt;
&lt;ul&gt;
&lt;li&gt;Select the &lt;em&gt;Hardware&lt;/em&gt; node under the AMALTHEA model node&lt;/li&gt;
&lt;li&gt;Right-click on the item then select the menu item &lt;strong&gt;New Child &amp;gt; Access Paths &amp;gt; Latency Access Path&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Name the created item &lt;em&gt;Path1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Source&lt;/strong&gt; property to &lt;em&gt;Core Core1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Target&lt;/strong&gt; property to &lt;em&gt;Memory GlobalMemory&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;Create a &lt;strong&gt;Latency Access Path&lt;/strong&gt; named &lt;em&gt;Path2&lt;/em&gt;
&lt;ul&gt;
&lt;li&gt;Set the &lt;strong&gt;Source&lt;/strong&gt; property to &lt;em&gt;Core Core1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Target&lt;/strong&gt; property to &lt;em&gt;Memory GlobalMemory&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;Add a constant latency to &amp;ldquo;Path1&amp;rdquo; with access type &amp;ldquo;RW&amp;rdquo;, quartz &amp;ldquo;100Mhz&amp;rdquo; and value 20
&lt;ul&gt;
&lt;li&gt;Select the path &lt;em&gt;Path1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Right-click on the item then select the menu item &lt;strong&gt;New Child &amp;gt; Latencies &amp;gt; Latency Constant&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Select the created item&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Access Type&lt;/strong&gt; property to &lt;em&gt;RW&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Quartz&lt;/strong&gt; property to &lt;em&gt;Quartz 100Mhz&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Value&lt;/strong&gt; property to &lt;em&gt;20&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Optional: Feel free to add more memory elements to represent local memories
located at the cores with the proper latency access paths&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;At this point you should get a contents tree which looks like that:&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/15-hardware.png&#34; class=&#34;img-responsive&#34;&gt;&lt;/p&gt;
&lt;hr /&gt;
&lt;h2 id=&#34;create-simple-os-model&#34;&gt;Create simple OS model&lt;/h2&gt;
&lt;p&gt;Create a simple OS model, containing schedulers for both cores.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Right-click on the AMALTHEA model on the tree editor then select the menu item &lt;strong&gt;New Child &amp;gt; Os Model&lt;/strong&gt;.&lt;br /&gt;
It will add a child node named &lt;strong&gt;Operating System&lt;/strong&gt; to the model&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a new operating system with name &lt;em&gt;Default&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the &lt;em&gt;Operating System&lt;/em&gt; node previously created&lt;/li&gt;
&lt;li&gt;Right-click on the item then select the menu item &lt;strong&gt;New Child &amp;gt; Operating Systems &amp;gt; Operating System&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Name the created item &lt;em&gt;Default&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a Task Scheduler named &lt;em&gt;Scheduler1&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Right-click on the &lt;em&gt;Default&lt;/em&gt; operating system
then select the menu item &lt;strong&gt;New Child &amp;gt; Task Scheduler&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Name the created item &lt;em&gt;Scheduler1&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add scheduling algorithm OSEK to &lt;em&gt;Scheduler1&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Right-click on the &lt;em&gt;Scheduler1&lt;/em&gt; task scheduler
then select the menu item &lt;strong&gt;New Child &amp;gt; Scheduling Algorithm &amp;gt; OSEK&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a Scheduling HW Unit to &lt;em&gt;Scheduler1&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Right-click on the &lt;em&gt;Scheduler1&lt;/em&gt; task scheduler
then select the menu item &lt;strong&gt;New Child &amp;gt; Scheduling Unit &amp;gt; Scheduling HW Unit&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a Task Scheduler named &lt;em&gt;Scheduler2&lt;/em&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a scheduling algorithm OSEK to &lt;em&gt;Scheduler2&lt;/em&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a Scheduling HW Unit to &lt;em&gt;Scheduler2&lt;/em&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;At this point you should get a contents tree which looks like that:&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/16-operating-system.png&#34; class=&#34;img-responsive&#34;&gt;&lt;/p&gt;
&lt;hr /&gt;
&lt;h2 id=&#34;add-timing-requirements-for-tasks&#34;&gt;Add timing requirements for Tasks&lt;/h2&gt;
&lt;p&gt;Adding some deadline informations to the already created tasks.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Note: Doing this in a separate file, it can easy be reused for other models if the names of the tasks are the same!&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Create a new AMALTHEA model &amp;ldquo;constraints.amxmi&amp;rdquo; in the same folder as the already created AMALTHEA meta model&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the folder &lt;em&gt;model1&lt;/em&gt; created during the paragraph &lt;strong&gt;General model setup&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Right-click on the mouse and select the menu item &lt;strong&gt;New &amp;gt; AMALTHEA Model&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Press &lt;strong&gt;Next&lt;/strong&gt; to define the associated model file naming it &lt;em&gt;constraints.amxmi&lt;/em&gt;&lt;br /&gt;
then press on &lt;strong&gt;Finish&lt;/strong&gt; to create an empty model.&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Right-click on the AMALTHEA model on the tree editor then select the menu item &lt;strong&gt;New Child &amp;gt; Constraints Model&lt;/strong&gt;.&lt;br /&gt;
It will add a child node named &lt;strong&gt;Constraints&lt;/strong&gt; to the model&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a new Process Requirement named &lt;em&gt;DeadlineTask1&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the &lt;strong&gt;Constraints&lt;/strong&gt; item on the tree editor&lt;/li&gt;
&lt;li&gt;Right-click on the mouse and select the menu item &lt;strong&gt;New Child &amp;gt; Requirements &amp;gt; Process Requirement&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Name the created item &lt;em&gt;DeadlineTask1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Process&lt;/strong&gt; property to the value &lt;em&gt;Task Task1&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a Time Requirement Limit to &amp;ldquo;DeadlineTask1&amp;rdquo; Process Requirement&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Select the Process Requirement named &lt;em&gt;DeadlineTask1 Task1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Right-click on the mouse and select the menu item &lt;strong&gt;New Child &amp;gt; Limit &amp;gt; Time Requirement Limit&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Limit Type&lt;/strong&gt; property to &lt;em&gt;UpperLimit&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Metric&lt;/strong&gt; property to &lt;em&gt;ResponseTime&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Add limit to TimeRequirementLimit
&lt;ul&gt;
&lt;li&gt;Right-click the mouse on the &lt;em&gt;ResponseTime&lt;/em&gt; item and select the menu item &lt;strong&gt;New Child &amp;gt; Limit Value&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Unit&lt;/strong&gt; property of the new item to &lt;em&gt;ms&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Value&lt;/strong&gt; property to &lt;em&gt;10&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a new Process Requirement named &lt;em&gt;DeadlineTask2&lt;/em&gt; and set its &lt;strong&gt;Process&lt;/strong&gt; property to the value &lt;em&gt;Task Task2&lt;/em&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a Time Requirement Limit to &amp;ldquo;DeadlineTask2&amp;rdquo; Process Requirement&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Set the &lt;strong&gt;Limit Type&lt;/strong&gt; property to &lt;em&gt;UpperLimit&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Metric&lt;/strong&gt; property to &lt;em&gt;ResponseTime&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Add limit to the Time Requirement Limit
&lt;ul&gt;
&lt;li&gt;Right-click the mouse on the &lt;em&gt;ResponseTime&lt;/em&gt; item and select the menu item &lt;strong&gt;New Child &amp;gt; Limit Value&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Unit&lt;/strong&gt; property of the new item to &lt;em&gt;ms&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Value&lt;/strong&gt; property to &lt;em&gt;15&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a new Process Requirement named &lt;em&gt;DeadlineTask3&lt;/em&gt; and set its &lt;strong&gt;Process&lt;/strong&gt; property to the value &lt;em&gt;Task Task3&lt;/em&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a Time Requirement Limit to &amp;ldquo;DeadlineTask3&amp;rdquo; Process Requirement&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Set the &lt;strong&gt;Limit Type&lt;/strong&gt; property to &lt;em&gt;UpperLimit&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Metric&lt;/strong&gt; property to &lt;em&gt;ResponseTime&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Add limit to the Time Requirement Limit
&lt;ul&gt;
&lt;li&gt;Right-click the mouse on the &lt;em&gt;ResponseTime&lt;/em&gt; item and select the menu item &lt;strong&gt;New Child &amp;gt; Limit Value&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Unit&lt;/strong&gt; property of the new item to &lt;em&gt;ms&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Value&lt;/strong&gt; property to &lt;em&gt;15&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;At this point your model should look like this:&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/17-constraints.png&#34; class=&#34;img-responsive&#34;&gt;&lt;/p&gt;
&lt;hr /&gt;
&lt;h2 id=&#34;add-mapping-information-of-sw-elements-to-hardware&#34;&gt;Add mapping information of SW elements to hardware&lt;/h2&gt;
&lt;p&gt;The mapping represents which software elements are mapped to dedicated hardware elements.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Note: The mapping is separated into an extra file, which makes it easier to replace or change a mapping!&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Create a new AMALTHEA model &amp;ldquo;mapping.amxmi&amp;rdquo; in the same folder as the already created AMALTHEA meta model&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Right-click on the AMALTHEA model on the tree editor then select the menu item &lt;strong&gt;New Child &amp;gt; Mapping Model&lt;/strong&gt;.&lt;br /&gt;
It will add a child node named &lt;strong&gt;Mapping&lt;/strong&gt; to the model&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a &lt;strong&gt;Task Allocation&lt;/strong&gt; element to the Mapping&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Right-click the mouse on the &lt;em&gt;Mapping&lt;/em&gt; item and select&lt;br /&gt;
the menu item &lt;strong&gt;New Child &amp;gt; Process Allocation &amp;gt; Task Allocation&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Process&lt;/strong&gt; property to &lt;em&gt;Task Task1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Scheduler&lt;/strong&gt; property to &lt;em&gt;Task Scheduler Scheduler1&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a second &lt;strong&gt;Task Allocation&lt;/strong&gt; element to the Mapping and&lt;br /&gt;
set the &lt;strong&gt;Process&lt;/strong&gt; to &lt;em&gt;Task2&lt;/em&gt; and the &lt;strong&gt;Scheduler&lt;/strong&gt; to &lt;em&gt;Scheduler1&lt;/em&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a third &lt;strong&gt;Task Allocation&lt;/strong&gt; element to the Mapping&lt;br /&gt;
and set the &lt;strong&gt;Process&lt;/strong&gt; to &lt;em&gt;Task3&lt;/em&gt; and the &lt;strong&gt;Scheduler&lt;/strong&gt; to &lt;em&gt;Scheduler2&lt;/em&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Under the Mapping item add a &lt;strong&gt;Core Allocation&lt;/strong&gt; element&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Right-click the mouse on the &lt;em&gt;Mapping&lt;/em&gt; item&lt;br /&gt;
and select the menu item &lt;strong&gt;New Child &amp;gt; Core Allocation&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Core&lt;/strong&gt; property to &lt;em&gt;Core Core1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Scheduler&lt;/strong&gt; property to &lt;em&gt;Task Scheduler Scheduler1&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add a second &lt;strong&gt;Core Allocation&lt;/strong&gt; element and set
the &lt;strong&gt;Core&lt;/strong&gt; to &lt;em&gt;Core Core2&lt;/em&gt; and the &lt;strong&gt;Scheduler&lt;/strong&gt; to &lt;em&gt;Scheduler2&lt;/em&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Add an Abstract Element Mapping at least for all Labels to map them to &lt;em&gt;GlobalMemory&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Right-click the mouse on the &lt;em&gt;Mapping&lt;/em&gt; item and select&lt;br /&gt;
the menu item &lt;strong&gt;New Child &amp;gt; Mapping &amp;gt; Abstract Element Mapping&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Abstract Element&lt;/strong&gt; property to &lt;em&gt;Label LabelA&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Set the &lt;strong&gt;Mem&lt;/strong&gt; property to &lt;em&gt;Memory GlobalMemory&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Repeat the last 3 steps steps for the &lt;em&gt;Label LabelB&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Optional: If more memories are available, make a proper assignment to other memory elements.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;At this point your model should look like this:&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
&lt;img src=&#34;https://www.eclipse.org/app4mc/images/gs-create-model/18-mapping.png&#34; class=&#34;img-responsive&#34;&gt;&lt;/p&gt;
&lt;hr /&gt;
&lt;h2 id=&#34;solution&#34;&gt;Solution&lt;/h2&gt;
&lt;p&gt;The solution for this exercise is available in this plugin: &lt;a href=&#34;https://www.eclipse.org/app4mc/models/org.eclipse.app4mc.amalthea.solution1.zip&#34;&gt;org.eclipse.app4mc.amalthea.solution1&lt;/a&gt;&lt;/p&gt;
</description>
</item>
</channel>
</rss>