Project code is hosted on http://git.eclipse.org/c
The symbolic execution platform of the E-FMP project will be organized around a symbolic execution infrastructure as illustrated in Figure 1.
Figure 1. The symbolic execution platform of the E-FMP project
tinydtls is a library for Datagram Transport Layer Security (DTLS) covering both the client and the server state machine. It is implemented in C and provides support for the mandatory cipher suites specified in CoAP.
The MDM|BL comprises a bottom to top architecture view of three parts.
The first one is a specific openMDM application model definition for the ASAM ODS data storage. The standardization provides a structured representation for common use case related data in all openMDM application. The data model is split into the base model, which covers the most common use cases, and extensions for additional use cases.
Papyrus-RT is an industrial-grade, complete modeling environment for the development of complex, software intensive, real-time, embedded, cyber-physical systems.
The initial version of Papyrus-RT is based on the UML-RT approach, so the discussion below is representative of this decision. This decision was made from feedback from active interested parties, sponsors, and experience of the development team.
The project starts with the module Feed-In Management ("Last- und Einspeisemanagement") based on the German Electricity Feed-In Act. The future demand for electric energy is to be adapted to the supply and availability of renewable energy. Based on specific rules and parameters the Feed-In Management calculates a bluepint for electric switching stations and power plants based on renewable energy. Implementing the calculation input data is needed from electric networks, switching stations, power plants, electric demands and feed-in capabilities.
Eclipse Plug-ins for Gradle is a collection of Eclipse plug-ins that provide support for building software using Gradle.
The Ignite|IoT methodology has two main perspectives:
Haystack is a project to implement a data historian. It is written in Java and licensed under the EPL. It is based on Hadoop and HBase to allow for scalability. The original use case was to provide a historian for the Eclipse SCADA project. From the start the aim was to provide interfaces for any other interested party. That means none of the available interfaces is dependent in any way on the Eclipse SCADA project. This approach allows the ease of reuse of existing data collectors by implementing a thin shim to use with the Haystack interfaces.