Software application and automatization

With the creation of increasingly complex (technological) automation systems, the growth of robotic software architectures, and the growth of an ever-growing variety of applications and robots, the design, development and integration of software-based robotic systems are becoming a major problem in the technology community. Today, software architectures, and therefore software development platforms for robotics, are numerous and depend on the type of robot (service robot, collaborative, agricultural, medical, etc.).

Therefore, the maintenance efforts of these platforms and the cost of developing robots are significant. Therefore, robotics poses a fundamental question: how to reduce the cost of developing robotic software systems while improving their quality (in terms of software development: reusability, interoperability, maintainability, etc.).

Software testing and maintaining specificity in the independence of each system. This question raises several others: on the one hand, how to describe and encapsulate various functions that a robot must perform in the form of a set of software objects in interaction?

And, on the other hand, how to give these program objects the properties of modularity, portability, the possibility of reuse, etc. In order to use and share the knowledge and best practices of experts in this field. In our opinion, one of the most likely and promising solutions to this issue is to increase the level of abstraction in the definition of software objects that make up robotic systems.

To do this, we turn to software development with its many tools, including model-based modeling and, in particular, the development of a modeling language for specific areas (DSML). In this thesis, we will first conduct a comparative study of modeling languages and the methods used in the development of embedded real-time systems in general. The purpose of this work is to find out if there is something that can make it possible to answer the above questions of robots.

This study not only shows that these approaches are not adapted to the definition of robotic software architectures, but mainly leads to the creation of a structure that allows developers of embedded real-time systems and others to choose the method and / or modeling language that is most suitable for their design. Then we propose (a modeling language for robotic software architecture) for defining software architectures with integration of real-time properties.

To do this, we first identify the domain concepts that robotics use to define their applications. These concepts are hierarchized and structured in a metamodel to provide an abstract language syntax. Real-time properties are defined and included in related concepts. Then a specific syntax is defined that allows designers to define their architectures as models. Then we define the conversion rules used to develop our generators. These generators allow you to create your own documentation from the constructed models on the one hand and, on the other hand, create source code in C ++.

Software application and automatization. Companies that have begun the transformation, or are simply looking for ways to automate the installation and configuration of their environments, are often skeptical of the importance of automating application launches over automation tools. infrastructure. There are many tools, some of which seem to perform the same functions. Software that controls infrastructure automation. It also details the value propositions of each product, as well as the main area it covers and the benefits that it can offer in an integrated toolbox.

Many organizations strive to simplify the deployment of their applications while ensuring operational stability while adhering to and ensuring that application response goals are met. To ensure its survival, society must be able to more effectively respond to the vagaries of activity and “develop quickly and smoothly.” To achieve his competitive goals, he increasingly needs to automate the entire application stack. Unfortunately, the concept of “full stack” tends to take on different meanings depending on the service sector.