The aim of OMEGA was the definition of a development methodology in UML for embedded and real-time systems based on formal techniques.
The objective of the OMEGA project was
— to define an UML profile adequate for modelling real-time systems and their requirements by anticipating some of the concepts of UML 2.0
— to build tool support for verifying and analysing designs and requirements expressed using this profile
— to validate the implemented methodology on case studies provided by the 4 industrial users participating in the project.
The UML profile
The choice of the subset of UML that we have made can be considered as relatively standard with respect to the choices of commercial UML tools for simulation and/or code generation for real-time and embedded systems, such as Rhapsody, Telelogic TAU and Rose Real-Time, emerging from ROOM. These tools mainly focus on what is called a “platform independent” description of the system, that is a model focussing on the software structure and on the functionality of an application, independently of the middleware, OS, hardware architecture,… it is going to be executed on.
A so-called “platform dependent” model should provide in addition, enough information to generate code or to analyze non-functional aspects for a given platform. Notice that the UML profile for Scheduling, Performance and Time (SPT) [SPT03] – focuses like we do – on the analysis of time related properties; to this aim, it provides concepts for defining different kinds of “resources”, “task” needing a resource to be executed and consuming some quantities, in particular time.
An aim of the OMEGA project is to handle these two aspects less independently as they are in most existing tools. The aim is to use less violent abstractions of one aspect when verifying the other, in cases where this is needed.
.... For more detials see here
The validation toolset
The OMEGA toolset depicted below is formed of four components linked by the common semantics of the OMEGA UML profile and by the use of the XMI format. Click on the image here to access more detailed information and other resources for each component.
VERIMAG had developed the IFx environment for UML in the OMEGA proejct.
The Case studies
In order to evaluate the OMEGA project methods and techniques, as well as to provide feedback to their development, four case studies apply these in the industrial context. After specification of the case study UML models the OMEGA tools are being applied to these models in order to investigate applicability, usability, scalability, complementary use, and methodological aspects of the employment of these tools in the industrial embedded real-time software development. .... for more se here
IAI case study The case study is a flight control mechanism that implements "sensor voting" and "sensors monitoring" operations in a typical flight control system.
NLR case study The case study involves the Medium Altitude Reconnaissance System (MARS), which counteracts the image quality degradation caused by the forward motion of an aircraft.
EADS case study The EADS ST case study presents the Flight Software of the European Ariane 5 Launcher and focuses on relevant real time behaviours.
FTR&D case study The FTR&D application is a telecomm service built on top of embedded platform and service components.
- IAI - Israeli Aircraft Industry
- France Telecom R&D
- EADS/Innovation Works (France)
- NLR - National Aerospace Laboratory
- Weizmann Institute of Science
- OFFIS e.V., Oldenburg, Germany
- CWI, Amsterdam
- Radboud Universiteit Nijmegen
- Christian-Albrechts University Kiel
People at Verimag involved