Typical "State" Software Patterns for Creating Cortex-M Microcontroller System Software Infrastructure in Real Time Embedded Systems

Розроблено типові програмні шаблони Стан (State pattern) в процедурному і об’єктно-орієнтованому програмуванні, які дозволяють уніфікувати вихідний код системного програмного забезпечення для мікроконтролерів архітектури Сortex-М різних вироб­ників. Програмне забезпечення адаптовано до математичної моделі кінцевого автомата (finite-state machine (FSM)). Результати пройшли випробування на мікроконтролерах серії STM32F1хх. Застосована методика [1] дозволяє поширити отримане рішення на мікроконтролери інших виробників, що підтверджує цінність розроблених шаблонів.

Ontology-Based Modelling of IoT Design Patterns

Due to the large and complex nature of the Internet of Things (IoT), various analysis and design methodologies are proposed. Design pattern is one of them to provide the solution for a design problem, which is recurring in nature. In this approach, we have presented design patterns for the IoT use cases such as service integration and IoT security. But the semi-formal nature of software patterns may lead to bugs in the proposed pattern. Hence, an ontology-based approach is considered for modelling of the IoT design patterns. Further, we have presented an ontology-based framework for the specification and refinement of IoT design patterns. In this approach, an analysis of meta-models and ontologies has also been performed for reducing the gap between high-level design abstraction of Unified Modeling Language (UML)-based IoT patterns and formal ontology.

The Stories We Tell: Experience, Research, or Patterns?

Several “story” formats are used by software researchers and practitioners to document research results and share best practices. Research papers are the staple of software conferences and journals: papers report the results of research projects and a wide range of empirical experiments. Experience reports and software patterns are two alternative formats to share results and propagate knowledge and best practices. Experience reports relate experience and cautionary tales while software patterns distill experience into a compact form. An XP2021 panel session orchestrated by Steven Fraser – featuring panelists Ademar Aguiar, Casper Lassenius, Mary Lynn Manns, Ken Power, and Rebecca Wirfs-Brock – discussed how “story” formats each have a role to advance the practice of software engineering.

Robotic Systems of Systems Based on a Decentralized Service-Oriented Architecture

Multi-robot systems are often static and pre-configured during the design time of their software. Emerging cooperation between unknown robots is still rare and limited. Such cooperation might be basic like sharing sensor data or complex like conjoined motion planning and acting. Robots should be able to detect other robots and their abilities during runtime. When cooperation seems to be possible and beneficial, it should be initiated autonomously. A centralized cloud control shall be avoided. Using software patterns belonging to service-oriented architectures, the robots are able to discover other robots and their abilities during runtime. These abilities are implemented as services and described by their interfaces. Composition of services can be done easily and flexibly. The software patterns originally belonging to cloud computing could be successfully adopted to decentralized multi-robot systems. The developed concept allows autonomous systems to cooperate flexibly and to compose multi-robot systems during runtime.