| <html xmlns:th="https://www.thymeleaf.org"> |
| <head th:include="fragment :: fragment_head"> |
| </head> |
| <body> |
| <div th:replace="fragment :: fragment_nav"></div> |
| <div class="banner"></div> |
| <div class="container col-md-7"> |
| <div class="row" style="margin-top: 100px"> |
| <div class="col text-center"> |
| <div class="content-heading"> |
| <h1>About Eclipse APP4MC</h1> |
| </div> |
| </div> |
| </div> |
| <div class="col-md-18 padding-bottom-30" style="margin-top: 130px; margin-bottom:100px"> |
| <p> |
| <br> |
| </p> |
| |
| <p> |
| <strong>Eclipse APP4MC</strong> is a platform for engineering |
| embedded multi- and many-core software systems. The platform enables |
| the creation and management of complex tool chains including |
| simulation and validation. As an open platform, proven in the |
| automotive sector by Bosch and their partners, it supports |
| interoperability and extensibility and unifies data exchange in |
| cross-organizational projects.<span id="dots">...</span> |
| </p> |
| |
| <div id="more" style="display: none;"> |
| <p> |
| <img src="https://www.eclipse.org/app4mc/images/system-model.png" |
| class="img-responsive" style="width: 100%"> |
| </p> |
| |
| <p> |
| <strong><em>Multi- and Many-Core Development Process |
| Support</em></strong> |
| </p> |
| |
| <p>The Amalthea platform allows users to distribute data and |
| tasks to the target hardware platforms, with the focus on |
| optimization of timing and scheduling. It addresses the need for |
| new tools and techniques to make effective use of the level of |
| parallelism in this environment.</p> |
| |
| <p> |
| <strong><em>Common Data Exchange and Simulation</em></strong> |
| </p> |
| |
| <p>The System Model contains the information required to |
| simulate, analyze and optimize performance. It contains extensive |
| information about software, hardware, timing behavior, and |
| constraints for the system under development.</p> |
| |
| <p> |
| Based on the <a href="http://www.eclipse.org/modeling/emf/">Eclipse |
| Modeling Framework</a>, its capabilities not only include hardware and |
| software modelling but in addition, tools for visualization and |
| processing. The unified data model enables tool interoperability |
| and data exchange with other systems such as <a |
| href="http://www.autosar.org">Autosar</a> and simplifies the |
| exchange and storage of data. |
| </p> |
| |
| <p> |
| <strong><em>Event Tracing</em></strong> |
| </p> |
| |
| <p>The AMALTHEA definitions of task states and transitions |
| provides the basis for evaluating systems with tracing tools, |
| identifying problems and discovering improvements. These |
| definitions are already in use in both commercial and open source |
| tools.</p> |
| |
| <p> |
| <strong><em>Customizable Workflow</em></strong> |
| </p> |
| |
| <p> |
| The AMALTHEA workflow engine supports a continuous development |
| workflow, allowing data exchange along the entire toolchain. |
| Workflow elements can be customized and extended according to user |
| needs. As a basis, a standard workflow developed with <a |
| href="http://www.eclipse.org/Xtext/documentation/306_mwe2.html">Eclipse |
| Xtext(MWE2)</a> is included. |
| </p> |
| |
| </div> |
| <button onclick="readMoreOrLess()" id="myBtn" class= "btn btn-secondary" style="border-radius: 40px">Read more</button> |
| </div> |
| |
| </div> |
| <script> |
| function readMoreOrLess() { |
| var dots = document.getElementById("dots"); |
| var moreText = document.getElementById("more"); |
| var btnText = document.getElementById("myBtn"); |
| |
| if (dots.style.display === "none") { |
| dots.style.display = "inline"; |
| btnText.innerHTML = "Read more"; |
| moreText.style.display = "none"; |
| } else { |
| dots.style.display = "none"; |
| btnText.innerHTML = "Read less"; |
| moreText.style.display = "inline"; |
| } |
| } |
| </script> |
| |
| </body> |
| </html> |
