Proposals

Eclipse Data Analysis Services (Daanse) is an open source software designed to analyze large amounts of data and extract valuable insights from it. With a steady rise of digital data production in business, science and technology, the importance of data analysis has grown tremendously. Data Analysis Services offers a wide range of tools, technologies and expertise to interpret data in meaningful ways and help decision makers formulate strategies and identify patterns and trends. There are several important features of Data Analysis Services: Data cleansing and integration: One of the crucial steps in data analysis is the preparation of the data. Often data are flawed or incomplete. Data Analysis Services helps to clean, transform and bring data into a unified form to enable sound analysis. Data Visualisation: Data can be complex and numbers alone are sometimes not enough to convey information. Data Analysis Services uses visualisation tools to present data in the form of charts, graphs and interactive dashboards. This simplifies the communication of results and insights. Statistical Analysis: Data Analysis Services uses statistical methods and models to analyse data and identify patterns, correlations or significance. This includes descriptives, inferential statistics, regression analysis, time series analysis and more. Business Intelligence: Data Analysis Services helps management to extract business-critical insights that help improve business processes, optimise resources and identify new business opportunities. Big Data Analysis: In a world characterised by huge amounts of data, Big Data analysis is an integral part of Data Analysis Services. Processing and analysing large and complex data sets require specialised tools and technologies.

Eclipse Daanse combines the following technologies to cover different applications scopes:

XMLA (XML for Analysis)

XMLA provides a detailed specification for accessing analytical data sources. This specification describes the structure of XMLA messages and the supported operations for accessing OLAP data sources. The Test and Compatibility Kit (TCK) can be used to check compliance of different implementations with the XMLA specification and to ensure interoperability between systems. Eclipse Daanse offers a Java API via Jakarta XML Bind and flexible customisable SOAP messages.

MDX (Multidimensional Expressions):

MDX is a query language for multidimensional data sources and is closely related to XMLA. The scope and delimitation of MDX are as follows: Stringd can be converted into an implementation or API model using parsers.



OLAP

OLAP (Online Analytical Processing) is a powerful technology widely used in data analysis and reporting. It is based on several important components: The DataCube Provider makes it possible to create and provide multidimensional data cubes that offer efficient and flexible data organisation for complex analyses. OLAP's Access and Security Model regulates access rights to data sources and ensures that only authorised users can access the information they need, while sensitive data remains protected. The Calculation Model enables complex calculations and aggregations to be performed on the multidimensional data. This enables the creation of meaningful reports and analyses that provide deeper insights into the data. OLAP's Dynamic Function Model allows dynamic functions to be used to respond to changes in data sources or query results. This allows users to customise analyses and include real-time data in their reports. Parts of this implementation are a Fork ot the Pentaho  Mondrian Project

Databases:

Different databases can be integrated via JDBC (Java Database Connectivity) which allows developers to interact with different databases by providing a standardised method for connecting and querying. The JDBC Database Dialect Abstraction Layer makes it possible to work with different databases without having to worry about the specific syntax differences. OLAP data can thus also be accessed by means of OLAP database-schema mapping.



Clients:

Eclipse Daanse enables access to analytical data sources from various client applications: In addition to the possibility of integrating your own applications using the client libraries (in several languages like Java and Typescript), Eclipse Daanse includes its own web client for tables, charts and maps as well as dashboards. In addition, further reporting tools can be connected via adapters and templates.



Dashboards:

In addition to XMLA data sources, the Eclipse Daanse client's dashboard engine enables other data sources such as SensorThingsAPI, REST and OCG (WMS, WFS) to be connected and merged with each other. These data sources can feed a variety of visualisations such as charts, tables, maps, infographics ,texts and more. Visualisations can be combined to different widgets and designed interactively via input and control options such as (fields, buttons, sliders, map events ... ). In addition to classic dashboards, interactive maps, infographics or interfaces for e.g. building management systems can also be realised in this way.

Eclipse Symphony enables end-to-end orchestration experience and addresses it as a distinct concern. Its objective is to provide an easy-to-adopt, cost-effective, and consistent application programming interface (API) for managing workloads that involve multiple device types and service vendors at multiple locations. Eclipse Symphony enables developers and adopters to utilize their current systems as-is, without making any alterations, and to unify disparate systems into a coherent entirety. The key benefit of Eclipse Symphony is its ability to codify a consistent workflow across these systems and tool chains, ensuring their seamless integration and harmonious operation.

Eclipse Symphony enables solution orchestration by a separation of concerns into 3 constructs, Unified Object Model, Orchestration API, and Providers.

• Unified Object Model defines the units of orchestration and the target state for these units.
• Orchestration API provides the orchestration capabilities that are state seeking, information graph and workflow.
• Providers encapsulate and isolate platform-specific operations for each of the systems and devices that participate in the system orchestration task and enable extensibility.

Eclipse Apoapsis consolidates the requirements from the tooling side (e.g. fast scan times, configuration as code,...) on the one hand and the requirements from the institutionalized operation side in medium to large organizations on the other hand (e.g. user access, role concept, organization specific structures, ...). Concerning concepts and wording it is based on the capability map created by the Open Chain Automation Workgroup in the context of Open Source Management (https://github.com/Open-Source-Compliance/Sharing-creates-value/tree/master/Tooling-Landscape/CapabilityMap). It is planned to incrementally work out the API-specification bottom-up starting from the reference implementation in the course of the project. Additionally it is intended to collect Blueprints (e.g. central pipeline, decentral SBOM generation with centralized metadata analysis, semi-automated analysis with central metadatabase, ...) and use cases (e.g. security vulnerability monitoring, identification of TOP100 used components in the organization, as a ... I want to... so that ...) that address generic problemspaces observed in the community , which can be used by interested parties to easily match their own problem space (birds of a feather) and map to a potential solution concept.

In an initial phase, the Eclipse Apoapsis project's ORT-server provides a concrete solution for a blueprint, where central Software Composition Analysis pipelines are used at scale while covering a large range of project setups (e.g. from Mobile Apps using Cocoapods to Cloud Services using Java/Maven) and configurable extent of analysis (e.g. from mere SBOM-creation to full-blast Dependency Analysis including Vulnerabilities and Copyright/License reports). To achieve this, the Eclipse Apoapsis project's ORT-server is based on the OSS Review Toolkit and makes use of its integration APIs for dependency analysis, license scanning, vulnerability databases, rule engine, and report generation. The Eclipse Apoapsis project itself concentrates on the server functionality including user and role management and the necessary APIs.

Necessary API harmonizations are indirectly worked-out in close collaboration with the original authors of the respective upstream-projects (e.g. ORT's technical steering committee).

The OpenChain Automation Workgroup developed a capability map in the context of Open Source Management (https://github.com/Open-Source-Compliance/Sharing-creates-value/tree/master/Tooling-Landscape/CapabilityMap). Within this Workgroup the OSS Review Toolkit provides a reference implementation for Open Source Management Automation and will be part of the first blueprint for the server setup.

It is planned to incrementally work out additional server-setups to support further blueprints in the course of the project.

The Eclipse Foundation Development Process (EDP) is the foundational goverance document for Eclipse projects and committers. It describes the manner in which we do open source software. The EDP does not prescribe any particular development methodology; it is more concerned with the larger-scale aspects of open source project lifecycle, including such things as reviews, processes for running votes and elections, bringing new committers onto a project, etc.

The Eclipse Foundation Specification Process (EFSP) extends the EDP to describe the process by which specifiations are created in open source.

The Eclipse Vhant project maintains the Eclipse Foundation Development Process, the Eclipse Foundation Specification Process, the Standard Top-Level Project Charter, and related resources.

Eclipse ThreadX provides a vendor-neutral, open source, safety certified OS for real-time applications published on under a permissive license.

The Eclipse ThreadX suite encompasses:

• ThreadX - advanced real-time operating system (RTOS) designed specifically for deeply embedded applications
• NetX Duo - advanced, industrial-grade TCP/IP network stack designed specifically for deeply embedded real-time and IoT applications
• FileX - high-performance, FAT-compatible file system that’s fully integrated with ThreadX kernel
• GUIX - provides a complete, embedded graphical user interface (GUI) library
• USBX - high-performance USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated with ThreadX kernel
• LevelX - Flash Wear Leveling for FileX and stand-alone purposes
• GuiX Studio - design environment, facilitating the creation and maintenance of all graphical elements for CUIX
• TraceX - analysis tool that provides a graphical view of real-time system events to better understand the behavior of real-time systems

The Eclipse SysON project provides an open-source web-based tooling to edit SysML v2 models. It includes a set of editors (graphical, textual, form-based, etc.) enabling users to build the various parts of system models. Capitalizing on the capabilities of the Sirius Web platform, SysON offers a user-friendly interface, facilitating seamless model creation, modification, and visualization.

Furthermore, Eclipse SysON is the core of the SysMLv2 model editing feature of Papyrus and seamlessly enables co-design of SysMLv2 models alongside Eclipse Capella.

Additionally, Eclipse SysON embraces the standard API for interconnection, enhancing the interoperability of these vital modeling resources and will support the SysML v2 textual specifications as an exchange format, to ensure seamless transitions. 

Through this initiative, we seek to foster growth within the MBSE community by providing a robust and accessible tool that harmonizes seamlessly with modern modeling landscapes.

 

The Eclipse Simultaneous Release process works as follows:

• The simrel.aggr model specifies precisely what is to be aggregated.
• The simrel.build change-requests jobs validate each pull request to the simrel.aggr model before the change is committed to the main branch.
• The simrel.build main job promotes each succesfull aggregation build of the current simrel.aggr model on the main branch to the appropriate current subdirectory of staging to produce the SimRel p2 Staging Repository.
• The Eclipse Packaging Product's CI jobs produce an EPP p2 Repository and corresponding EPP Products using the SimRel p2 Repository as input.
• Various Releng jobs periodically promote staging repositories to more permanent locations.

The Eclipse OS-Gov project provides guidelines and best practices for the governance and management of open source projects. Developed by recognised open source experts, it covers a wide range of topics, from tooling to communication and security. It only provides recommendations, as projects should adapt their practices to their own context.

We intend to develop these recommendations in a collaborative manner with the community, and publish various outputs (PDF, epub, HTML) freely available to everybody.

Eclipse openDuT automates the testing and validation process for automotive software and applications. This includes offering a framework for the testing and validation process but also includes process descriptions of the intended use.

It focuses on reliable, repeatable, and observable automated test and validation executions. The main building blocks are:

• Model or description language of test cases that can be kept private or can be part of the open-source context, for example to offer a common implementation of a required topic for legal assessments.
• Test Execution Engine as OSS reference implementation and open APIs to plug-In private engines for private Test Cases.
• Test Management and Execution as component taking care about the needed capabilities to execute test cases and collect the results and insights.
• Management Service to orchestrate, observe and establish communication between distributed Hardware ECUs and Emulated ECUs. Distribution means that the (virtual) devices can be in different networks and even separated by proxies and the internet.
• Hardware Abstraction, Automotive Applications and Communication for uniform interaction with an abstract driver for different automotive networks e.g., CAN.

Main Use Cases are:

• (Fully automated) grey-box tests for single ECUs or clusters of ECUs
• Execution of tests over distributed test benches
• Realization of functional and explorative tests
• Coverage of Complete Security attack scenarios
• Easy interfacing and usability of the framework (Compatibility with external protocols, modularization, …)
• Observation of the test setup to verify if the test has been effective.
• Cloud/on-premises/hybrid deployments
• Adaption and full functional integration of 3rd party components (OSS, proprietary/ private source)

Qrisp is a high-level programming language for working with quantum computers. Qrisp is designed to enable programmers to write complex quantum algorithms with the ease of a modern day programming language, while still compiling down to the circuit level. By automating much of the low-level coding duties, such as gate-by-gate assembly or qubit management, we aim to open this field of research to a broad audience of developers. Qrisp was originally developed at Fraunhofer FOKUS funded by the German ministry for economic affairs and climate action.

The state of the art in programming a quantum computer pretty much resembles programming in assembler – even worse, while assembler provides at least some basic commands more abstract than the actual hardware gates, in quantum computing using gates and qubits only, is the standard. Frameworks like Qiskit or Cirq allow the user to create sub-circuits which can be reused in larger, more complex circuits. However, the handling of the circuits is still rather cumbersome.

Qrisp aims to tackle this challenge by trying to hide the qubit and gate structure of the underlying circuits as much as possible. This is achieved by conceptually replacing gates and qubits by functions and variables. This permits the creation of much more complex circuits than would ever be possible with handling gates and qubits directly. Of course, moving to variables and functions does not end programming with gates and qubits. The elementary quantum functions still need their implementation - under the hood - compiled using gates and qubits. This is why Qrisp comes with its own circuit creation module, which has most of the relevant features known from the established circuit creation frameworks.

Variables and functions not only simplify the management of highly complex circuits – due to the structure of an actual programming language many circuits can be created in a highly modular manner. This improves the possibility to easily maintain or upgrade certain parts of the code.

Apart from allowing highly complex circuit creation, Qrisp can also serve a pedagogical aspect, opening up this realm to non-physicists. This is because in Qrisp many quantum functions and control structures are already pre-programmed and therefore do not require the understanding of complex linear algebra that is needed when comprehending gate sequences.