Keyword: «robot software»

The article describes how, in teaching robotics on ROS, virtual practice in a three-dimensional environment, assembling software from nodes and packages, and transition to real hardware are combined. It explains how practices from web software development can be transferred to robotic systems that are more demanding for the following reasons: the cyber-physical loop is safety-critical; scenarios in simulation and in the field differ; time and hardware are limited. The argument draws on the ROS 2 survey, guidance on runtime verification and field testing of ROS-based systems, a review of regression-test optimization for autonomous ROS stacks, a systematic survey of software testing in robotics, and a description of the Robotics-Academy environment. Practical guidelines are formulated for organizing courses and team projects.

The article discusses how robotics education on ROS combines virtual practice in a three-dimensional environment, assembling software from nodes and packages, and transition to real hardware. It explains how practices from web software development map onto robotic systems that are more demanding because the cyber-physical loop is safety-critical, scenarios differ between simulation and field tests, and time and hardware are limited. The argument draws on the ROS 2 survey, guidance on runtime verification and field testing for ROS-based systems, a review of regression-test optimization for autonomous ROS stacks, a systematic survey of software testing in robotics, and a description of the Robotics-Academy environment. Practical guidelines are formulated for course design and team projects.