On mapping RT-UML specifications to RT-Java API: bridging the gap

Two recent standards have a great potential to impulse the use of object orientation in the development of real-time applications. The first is the Real-Time Specification for Java (RT-Java), consisting in an application programming interface (API) for real-time object-oriented programming. The other is the emerging RT-UML standard, which addresses the specification of real-time requirements and time using extended UML diagrams. This work proposes an approach for bridging the gap between the two emerging standards, aiming to provide a clear link between the modeled real-time constraints and the programming entities that provide their implementation. The main idea is to enhance the traceability as well as readability of timing constraints from a model-based requirements model to implementation. Relationships between the stereotypes and tags used to decorate the UML diagrams and their code representation are explained. An assessment of the benefits achieved using both standards as well are as some proposed enhancements are also discussed