The Vorto project comprises of the meta information model, the tool set to create information models, the code generators and the repository to manage existing information models. The meta information model and also the tool set are based on the Eclipse EMF (Eclipse Modeling Framework) framework.
The purpose of Andmore is to provide Android Eclipse tooling without having to go through multiple steps.
The technology development will involve integrating and refactoring the Google ADT plugins as necessary to work with the project. Similarly, the former MOTODEV plugins have many useful components that can be integrated into the project. Once these are integrated, new components may be added.
Titan provides an Eclipse-based IDE for TTCN-3. The user of the tool can develop test cases, test execution logic and build the executable test suite for one or more platforms.
The project aims to develop and sustain the necessary tooling that will assist Cloud application lifecycle management operations, using open standards and languages, where appropriate. As aforementioned, these operations are classified into three distinct categories: (1) application description, (2) application deployment and (3) application monitoring. CAMF will follow the Eclipse OSGi plug-in based software architecture for each of the aforementioned operations and will inherit the same look-and-feel that Eclipse users are accustomed to.
MDM@WEB includes multiple components for handling measured data. These components are structured to allow for high re-usability of core components like the communication with the ODS server or the import and export of data. In addition to these core components the project includes a web-based front-end.
The list of components includes:
Many development tools that are deployed on the desktop create two challenges for large organizations: configuration and compliance. When a developer or system administrator needs to install a tool individually on each machine, or each tool needs a reconfiguration for each branch / project / issue, there is a lot of manual step-by-step configuration tasks that a developer or admin must perform (repeatedly) to achieve a proper configuration.
score is a generic engine that is able to execute workflows. A workflow has a logical structure that resembles a flow-chart.
Workflows contains both logical operations and actions. A workflow must be compiled using one of the available orchestration languages before use.
A compiled workflow is known as content and can take several forms such as jar files or a binary object stored in a database.
The fundamental architecture of the project consists of:
Moquette is a Java implementation of an MQTT 3.1 broker. Its code base is small. At its core, Moquette is an events processor; this lets the code base be simple, avoiding thread sharing issues.
The Moquette broker is lightweight and easy to understand so it could be embedded in other projects. By default it lives standalone, but could be integrated into an OSGi container to create more significant integrations, for example running inside an embedded OSGi broker like Concierge.
The Oomph project provides tools based on extensible frameworks, packaged as fine-grained features that allow consumers to pick and choose. The basic building blocks include the following: