Note: This is a snapshot of the RobMoSys Wiki as of June 27th 2019. Live Version for this page.

general_principles:architectural_patterns:managing_transitive_system_states

Table of Contents

Architectural Pattern for Managing Transitions of System States

Architectural Pattern for Managing Transitions of System States

(To be extended)

(i.e. System-Mode Transitions)
synchronize system-modes over shared IDs
recognize (i.e. awareness about) transitive system-states

Context

…

Problem

…

Solution

…

Discussion

…

Acknowledgement

This document contains material from:

Lotz2018 Alex Lotz, "Managing Non-Functional Communication Aspects in the Entire Life-Cycle of a Component-Based Robotic Software System", Dissertation, Technische Universität München, München 2018.
Lutz2017 Matthias Lutz, “Model-Driven Behavior Development for Service Robotic Systems: Bridging the Gap between Software- and Behavior-Models,” 2017. (unpublished work)
Stampfer2018 Dennis Stampfer, "Contributions to System Composition using a System Design Process driven by Service Definitions for Service Robotics". Dissertation, Technische Universität München, München, Germany, 2018.

general_principles:architectural_patterns:managing_transitive_system_states · Last modified: 2019/06/27 15:54
http://www.robmosys.eu/wiki-sn-04/general_principles:architectural_patterns:managing_transitive_system_states