Dynamic Configuration for Distributed Systems
IEEE Transactions on Software Engineering
Dynamic reconfiguration of distributed applications
Dynamic reconfiguration of distributed applications
Chameleon: A Software Infrastructure for Adaptive Fault Tolerance
IEEE Transactions on Parallel and Distributed Systems
System Design with SystemC
Petri Net Based Design of Reconfigurable Embedded
DIPES '02 Proceedings of the IFIP 17th World Computer Congress - TC10 Stream on Distributed and Parallel Embedded Systems: Design and Analysis of Distributed Embedded Systems
Communication Synthesis for Reconfigurable Embedded Systems
FPL '99 Proceedings of the 9th International Workshop on Field-Programmable Logic and Applications
Implementation Approaches for Reconfigurable Logic Applications
FPL '95 Proceedings of the 5th International Workshop on Field-Programmable Logic and Applications
Dynamic Reconfiguration to Support Concurrent Applications
FCCM '98 Proceedings of the IEEE Symposium on FPGAs for Custom Computing Machines
HardwareC -- A Language for Hardware Design (Version 2.0)
HardwareC -- A Language for Hardware Design (Version 2.0)
Software Development for Real-Time Safety-Critical Applications
SEW '05 Proceedings of the 29th Annual IEEE/NASA Software Engineering Workshop - Tutorial Notes
Safety and security in industrial control
Proceedings of the Sixth Annual Workshop on Cyber Security and Information Intelligence Research
Hi-index | 0.00 |
A safety shell for real-time applications to be developed with UML is defined based on a re-configuration management pattern. Inspired by the architectural specifications in the Specification PEARL methodology, the pattern is parameterised by defining the properties of its components as well as by defining how the software is to be mapped to the hardware architecture. The initial and alternative scenarios are defined as well as the method for switching between them. This article includes the description of the UML pattern and of its parameterisation method, with the goal to obtain clearly specified operation scenarios with well-defined transitions among them. In order to achieve safe and timely operation, the pattern must provide a safety shell for all scenarios, i.e., enable their deterministic, temporally predictable operation, and transitions between them.