Imagine you have developed software to localize a robot in the environment and you are interested in making it available in robotics.
- You are
- an SME, specialized in a certain domain
- e.g. a component supplier for robot navigation
- You want to
- express your offer with pivotal features such that others can find your component (yellow pages)
- ensure that others can use your component (composability + compositionality)
- explicate non-functional properties of your component
and define its variation points
Imagine you as an integrator are willing to develop an application which needs a localization module and you are interested in integrating the third-party localization software on your intralogistics mobile platform.
- You are
- an SME that wants to access robotics technology and that wants to build a robot application
- You want
- to select components from the market matching your expressed needs
- your application to be correct by construction: you expect that building blocks seamlessly fit together
- to view components as grey-boxes and use them “as-is”: adjust only at explicated variation points within modeled boundaries, do not modify source code.
RobMoSys’ results will
- enable the increase of the quality of the developed component thanks to the use of formal models and validation of functional and non-functional properties supported by industry-grade tools
- enable distribution of robotics software with a description and information about its quality, maturity and usage constraints
- enable an integrator or end-user to integrate a localization module that was developed in a given environment (e.g. ROS, Yarp, SmartSoft, MOOS, Orocos, Reflexxes, MoveIT), in his own proprietary environment thanks to proper bridges between the platform-independent model and the target platform
- increase the quality of the integration thanks to formal techniques implemented in industry- grade tools.