This is the RobMoSys Wiki for technical content and structures. For general information of the project or its open calls, please refer to the project website.
Please note: The RobMoSys consortium is continuously updating this wiki to provide early insights. See the changelog. If you came here through a RobMoSys document, please see the jumppage to find referred pages.
RobMoSys will enable the composition of robotics applications with managed, assured, and maintained system-level properties via model-driven techniques. It will establish structures that enable the management of the interfaces between different robotics-related domains, different roles in the ecosystem, and different levels of abstractions. Two documents provide an overview and introduction:
The glossary contains descriptions of used terms.
Start reading here to see what your role is in the RobMoSys ecosystem or learn more about Roles in the Ecosystem. Main ecosystem users are:
In addition to the regular RobMoSys ecosystem participants, there are also other roles in the RobMoSys ecosystem like the Model-Driven Engineering tool developers (see RobMoSys Composition Structures) and framework builders (see Software Baseline).
RobMoSys manages the interfaces between different roles (robotics expert, domain expert, component supplier, system integrator, installation and deployment, operation) and separates concerns in an efficient and systematic way by making the step change to a set of fully model-driven methods and tools for composition-oriented engineering of robotics systems. The following list of pages provide some fundamental principles in RobMoSys.
RobMoSys considers Model-Driven Engineering (MDE) as the main technology to realize the so far independent RobMoSys structures and to implement model-driven tooling. The Wiki pages below collect some basic modeling principles related to realizing the RobMoSys structures.
RobMoSys provides a set of tools and a software baseline that already conform to the RobMoSys approach. This set can serve as a starting-point for implementations or demonstrations.
RobMoSys follows a reuse-oriented approach. This means that reinvention should be kept to a minimum and existing approaches should be used wherever possible. The following list provides some common approaches that are considered relevant within the RobMoSys context.