Franca is a powerful framework for definition and transformation of software interfaces. It is used for integrating software components from different suppliers, which are built based on various runtime frameworks, platforms and IPC mechanisms. The core of it is Franca IDL (Interface Definition Language), which is a textual language for specification of APIs.
As you are reading this, the migration of the Franca homepage and git repository to github is done. The old page at EclipseLabs is still available (at least parts of it), but it will soon be switched to read-only. Please clone or fork from the github repository, and also use the issue tracker available on Franca's github site.
The latest Franca User Guide (incl. a reference chapter for the IDL) is available here.
More information about Franca can be found here: http://franca.github.io/franca and in the wiki on this page.
As Franca is based on Eclipse, there are some powerful tools which can be used to work with Franca. Most important, Franca offers a user-friendly editor for reviewing and editing Franca IDL files.
The following diagram shows the major benefits of using Franca.
Franca offers a framework for building transformations from/to other IDLs (e.g., D-Bus, OMG-IDL or others) and code generation. We recommend using Xtend for building the generators, but it is generally possible to use other tools and languages which are based on EMF models or Java APIs for the task.
Support for the D-Bus Introspection format is available as installable feature of Franca.
With Franca, the dynamic behavior of client/server interactions can be specified using protocol state machines. Tools are available to use these specifications for validating implementations, e.g., checking runtime traces against the expected order of events on the interface. A graphical viewer for protocol state machines is part of Franca.
In specific application domains, it may be necessary to extend interface specifications by platform- or target-specific information. This is supported by Franca's deployment models, which allow these kind of extensions in a type-safe way. Thus, role-based development workflows can be established: Platform architects own the deployment specifications, whereas project architects and developers are responsible for providing the platform-specific data for their actual interfaces.
Generate a test environment for your interface instantly and see your interface in action! This is accomplished by generating eTrice models from Franca interfaces and generate executable Java code from these models. The test environment will consist of a client component (acting as dynamic test case executor) and a server component (acting as an intelligent mock object).
If you want to generate C++ code directly from Franca interface specifications, CommonAPI C++ might be the proper solution. It is designed to decouple generated API from the actual IPC stack and cooperates seamlessly with Franca. CommonAPI was created in the context of the GENIVI Alliance initiative. In summer of 2021, GENIVI has been transformed into COVESA.
For feedback and discussions around Franca there is a Franca forum at Google Groups, see http://groups.google.com/group/franca-framework.
There is an online Franca presentation available. This can also be used nicely from smartphones and tablets.
The Franca framework has been built using the open source projects EMF, Xtext and Xtend. Thanks to all committers of those projects for their great and helpful contributions!
Build status on develop:
