Note: This is a snapshot of the RobMoSys Wiki as of June 23rd 2017.
Live Version for this page.
general_principles:architectural_patterns:managing_transitive_system_states
Table of Contents
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:
- Lotz2017 Alex Lotz, “Managing Non-Functional Communication Aspects in the Entire Life-Cycle of a Component-Based Robotic Software System,” 2017. (unpublished work)
- Lutz2017 Matthias Lutz, “Model-Driven Behavior Development for Service Robotic Systems: Bridging the Gap between Software- and Behavior-Models,” 2017. (unpublished work)
- Stampfer2017 Dennis Stampfer, “Contributions to Composability using a System Design Process driven by Service Definitions for Service Robotics,” 2017. (unpublished work)
general_principles:architectural_patterns:managing_transitive_system_states · Last modified: 2019/05/20 10:49
http://www.robmosys.eu/wiki-sn-01/general_principles:architectural_patterns:managing_transitive_system_states
http://www.robmosys.eu/wiki-sn-01/general_principles:architectural_patterns:managing_transitive_system_states
Page Tools
This project has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No 732410.