Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Communications of the ACM
Component Software: Beyond Object-Oriented Programming
Component Software: Beyond Object-Oriented Programming
Mapping HRT-HOOD ® Designs to Ada 95 Hierarchical Libraries
Ada-Europe '96 Proceedings of the 1996 Ada-Europe International Conference on Reliable Software Technologies
The Ravenscar Tasking Profile for High Integrity Real-Time Programs
Ada-Europe '98 Proceedings of the 1998 Ada-Europe International Conference on Reliable Software Technologies
Mode Change Protocols for Real-Time Systems: A Survey and a New Proposal
Real-Time Systems
Automated Model-Based Generation of Ravenscar-Compliant Source Code
ECRTS '05 Proceedings of the 17th Euromicro Conference on Real-Time Systems
The worst-case execution-time problem—overview of methods and survey of tools
ACM Transactions on Embedded Computing Systems (TECS)
Real-time utilities for Ada 2005
Ada-Europe'07 Proceedings of the 12th international conference on Reliable software technologies
Temporal isolation with the ravenscar profile and Ada 2005
ACM SIGAda Ada Letters
Incorporating operating modes to an ada real-time framework
ACM SIGAda Ada Letters
Preservation of timing properties with the ada ravenscar profile
Ada-Europe'10 Proceedings of the 15th Ada-Europe international conference on Reliable Software Technologies
| Hi-index | 0.00 |
In this paper we present the rationale, the status and the planned enhancement of a set of code archetypes that implement common programming patterns suited for the development of Ravenscar-compliant real-time systems. There have been other attempts at building software frameworks that ease the construction of realtime software systems. Ours is not intended for direct access by the user, but for deployment in the back-end code generation engine of a model-based tool environment. A further distinguishing characteristic of our patterns is that they foster the principle of separation of concerns, whereby the functional code of the system (which we require to be purely sequential) stays under the responsibility of the user, whereas the code that realizes the intended concurrency and real-time semantics is obtained by instantiation of predefined, correct by construction, archetypes.