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
Fitting Schedulability Analysis Theory into Model-Driven Engineering
ECRTS '08 Proceedings of the 2008 Euromicro Conference on Real-Time Systems
Real-time utilities for Ada 2005
Ada-Europe'07 Proceedings of the 12th international conference on Reliable software technologies
A Component Model for On-board Software Applications
SEAA '10 Proceedings of the 2010 36th EUROMICRO Conference on Software Engineering and Advanced Applications
A new strategy for the HRT-HOOD to ada mapping
Ada-Europe'05 Proceedings of the 10th Ada-Europe international conference on Reliable Software Technologies
Preservation of timing properties with the ada ravenscar profile
Ada-Europe'10 Proceedings of the 15th Ada-Europe international conference on Reliable Software Technologies
An MDE approach to address synchronization needs in component-based real-time systems
Proceedings of the 15th ACM SIGSOFT symposium on Component Based Software Engineering
Ada-Europe'12 Proceedings of the 17th Ada-Europe international conference on Reliable Software Technologies
Hi-index | 0.00 |
We promote a model-driven software development that centres on component-orientation. In keeping with Dijkstra's principle of separation of concerns, we want the user design space to be limited to the internals of components --- for which strictly sequential functional code is to be used --- and the interfaces provided to and required from other components, where extra-functional requirements are declaratively specified by means of annotations. We want the user model to be directly amenable to response time analysis. To this end we prescribe that the component model must statically bind to a computational model that matches the analysis theory in use. We want to ensure semantic preservation across the entire transformation chain, from the user model, to the analysis model, to the implementation model (i.e., the code) and, eventually to the execution environment. The Ada Ravenscar Profile is an excellent candidate implementation language for use in our endeavour. In this paper we present a set of code archetypes written against the constraints of the Ravenscar Profile, which we developed in conformance with our notion of separation of concerns, to drive the model to code transformation step of our development infrastructure.