Academia.eduAcademia.edu

Outline

Title
Abstract
Figures
Introduction
Related Works
SRM Profile Overview
Conclusion and Future Prospects
References
All Topics
Computer Science
Software Engineering

Software Real-Time Resource Modeling

Profile image of Jerome DelatourJerome Delatour

2008, Lecture Notes in Electrical Engineering

https://doi.org/10.1007/978-1-4020-8297-9_12
visibility

…

description

6 pages

link

1 file

Abstract
sparkles

AI

This paper focuses on modeling real-time embedded (RTE) execution platforms using the Unified Modeling Language (UML), particularly within the context of real-time operating systems (RTOS). It highlights the challenges faced by real-time embedded system engineers in designing more complex systems while addressing issues of reusability, maintainability, and portability. The work proposes the development of UML artifacts to characterize RTOS APIs, enabling effective modeling of RTE execution platforms and enhancing the scheduling and performance analysis of UML specifications.

Figures (7)
Figure 1 - Overview of the UML MARTE Profile The third, "Real-Time Embedded Design modeling" package provides support for modeling high-level model constructs to depict real-time embedded features of applications, but also for enabling the description of software and hardware execution platforms. The SRM profile deals with the software execution part.
Figure 1 - Overview of the UML MARTE Profile The third, "Real-Time Embedded Design modeling" package provides support for modeling high-level model constructs to depict real-time embedded features of applications, but also for enabling the description of software and hardware execution platforms. The SRM profile deals with the software execution part.
Figure 5 illustrates the use of an AssociationClass to describe interactions among concurrent resources. Since the “InteractionResource” stereotype extends the UML Classifier metaclass, an UML AssocationClass may be stereotyped as any InteractionResource substereotype e.g. “NotificationResource”, “MessageComResource”, and “MutualExclusionResource”). In this example, the execution support provides concurrency resources “Alarm” and “Task”) to compute instructions. These resources are described as UML classes and respectively stereotyped as “Alarm” and “SchedulableRessource”. In this example, an “Alarm” resource may interact with a
Figure 5 illustrates the use of an AssociationClass to describe interactions among concurrent resources. Since the “InteractionResource” stereotype extends the UML Classifier metaclass, an UML AssocationClass may be stereotyped as any InteractionResource substereotype e.g. “NotificationResource”, “MessageComResource”, and “MutualExclusionResource”). In this example, the execution support provides concurrency resources “Alarm” and “Task”) to compute instructions. These resources are described as UML classes and respectively stereotyped as “Alarm” and “SchedulableRessource”. In this example, an “Alarm” resource may interact with a
Figure 2 - SRM profile overview We have implemented the domain view as an UML 2.0 profile. Each set of concepts presented on table 1, table 2, and table 3 becomes a set of stereotypes. Figure 2 provides on overview of the profile architecture.
Figure 2 - SRM profile overview We have implemented the domain view as an UML 2.0 profile. Each set of concepts presented on table 1, table 2, and table 3 becomes a set of stereotypes. Figure 2 provides on overview of the profile architecture.
Figure 6 describes a “taskSpawn()” service as both task creating and task activating. In the same way, to activate a task, the user can either call the “taskSpawn()” or the “taskA ctivate()” service. This also allows users to express the same semantics for multiple features through use of the same tag (see priorityElements in figure 6). Figure 6 - Examples of tagged values
Figure 6 describes a “taskSpawn()” service as both task creating and task activating. In the same way, to activate a task, the user can either call the “taskSpawn()” or the “taskA ctivate()” service. This also allows users to express the same semantics for multiple features through use of the same tag (see priorityElements in figure 6). Figure 6 - Examples of tagged values
Figure 7 shows the main use cases in which the SRM profile is likely to be involved. Potential key users of this description include software designers engaged in defining real-time system software architectures, platform providers who develop and sell real-time operating systems, and methodology providers who specify the process in which the description is used (e.g. an MDA Y -chart). Figure 7 - Typical SRM use cases
Figure 7 shows the main use cases in which the SRM profile is likely to be involved. Potential key users of this description include software designers engaged in defining real-time system software architectures, platform providers who develop and sell real-time operating systems, and methodology providers who specify the process in which the description is used (e.g. an MDA Y -chart). Figure 7 - Typical SRM use cases
“trajectoryControl” operation body is the code which has to be executed in the context of that schedulable resource.
“trajectoryControl” operation body is the code which has to be executed in the context of that schedulable resource.
Figure 10 - ARINC-653 design
Figure 10 - ARINC-653 design

Related papers

A Comparison of the Use of Aspects and Objects for Modeling Distributed Embedded Real-Time Systems with RT-UML
Franz Rammig

The growing design complexity of today's real-time systems requires new techniques aiming the raising of the abstraction level since earlier stages of design in order to deal with such complexity in a suitable way. This paper reports a case study, which provides an assessment of two well-know high-level paradigms, namely Aspect-(AO) and Object-Oriented (OO) paradigms.

View PDFchevron_right
Application of Platform Models in Model Driven Engineering of Embedded Software
PAULO CEZAR STADZISZ

Journal of Computer Science, 2015

This paper presents two UML 2.0 profiles for designing embedded software based on Real-Time Operating Systems (RTOS). The first profile, named Application Modeling Profile (AMP), defines the necessary elements for the application modeling. The second one, named swxRTOS, defines a set of stereotypes to describe platform models and the mapping between application and platform. These profiles are used for the development of Application and Platform separately from the model transformations in the context of the Model Driven Engineering (MDE) approach.

View PDFchevron_right
Towards a model-driven engineering approach for developing embedded hard real-time software
lucas cordeiro

2008

Model-Driven Engineering (MDE) has been advocated as an effective way to deal with today's software complexity. MDE can be seen as an integrative approach combining existing techniques such as Domain-Specific Modeling Languages (DSML) and Transformation Engines. This paper presents the ezRealtime, an MDE-based tool that relies on the Time Petri Net (TPN) formalism and defines a DSML to provide an easy-to-use environment for specifying Embedded Hard Real-Time (EHRT) systems and for synthesizing timely and predictable scheduled C code. The ezRealtime adopts the universal XML-based transfer syntax for Petri nets, named as PNML. The main idea of this work is to propose a generative programming method and tool to boost code quality and improve developer productivity with automated software synthesis. The ezRealtime tool reads and automatically translates the specification to a time Petri net model through composition of building blocks with the purpose of providing a complete model of all tasks in the system. Therefore, this model is used to find a feasible schedule by applying a depth-first search algorithm. Finally, the scheduled code is generated by traversing the feasible schedule, and replacing transition's instances by the respective code segments. We also present the application of the proposed method in a case study.

View PDFchevron_right
Key Research Challenges for Successfully Applying MDD Within Real-Time Embedded Software Development
Wouter Joosen, Bert Vanhooff

Lecture Notes in Computer Science, 2006

Model-Driven Development (MDD) is a software development paradigm that promotes the use of models at different levels of abstraction and perform transformations between them to derive one or more concrete application implementations. In this paper we analyze the current status of MDD regarding its applicability for the development of Real-Time Embedded Software. We discuss different modeling framework approaches used to specify the various models, and compare OMG/MDA-based approaches (MOF, UML Profiles and executable UML) with a generic MDD-based approach (GME). Finally, we identify the key challenges for future MDD research in order to successfully apply MDD within RTES Development. These challenges are mainly situated in the field of modeling and standardization of abstraction levels, model transformations and code generation, traceability, and integration of existing software within the MDD development process S.

View PDFchevron_right
Model Based Approach for Heterogeneous Application Modelling for Real Time Embedded Systems
Leandro Moller

Modelling and simulation are essential methods in state of the art embedded system design. Especially modelling at high levels of abstraction helps designers to handle the design complexity and heterogeneity. This paper presents a model based approach for modelling and validation of heterogeneous application together with a multicore Network-on-Chip (NoC) platform. We use the MARTE profile to capture the structure and real time features of our system model and we model the application using UML sequence diagrams and directly simulate the diagrams in the Ptolemy II framework. As the case study shows, our approach sufficiently covers both communication and computation aspects of real time and heterogeneous systems.

View PDFchevron_right
A Method for the Development of Platform Models in the Model Driven Architecture Context
PAULO CEZAR STADZISZ

Journal of Computer Science, 2012

The application of the Model Driven Architecture (MDA) approach to the design of embedded software based on Real-Time Operating Systems (RTOS) is encouraged by the fact that such software has a wide variety of platforms. In this way, the creation of methods for the development of platform models that meet such diversity of platforms is necessary. This study proposes a method called PM-MDA for the development of platform models that design embedded software based on RTOS in the context of MDA. In addition, this study defines the swxRTOS metamodel, a UML 2.0 profile for RTOS based on embedded software design. Such profile defines a set of stereotypes to describe Platform Models (PMs) and is intended to generically describe the services provided by a given embedded system platform of the RTOS. This profile promotes the creation of Platform Models, which will be used as input parameters in the model transformation. Due to the inherent complexity in embedded software design and the existence of a wide variety of platform models, new methods that support the development of such software become crucial.

View PDFchevron_right
Evaluating Aspect-and Object-Oriented Concepts to Model Distributed Embedded Real-Time Systems Using RT-UML
Carlos Eduardo Pereira

Proc. of 17th IFAC World …, 2008

The growing design complexity of today's embedded real-time systems requires new techniques aiming the raising of the abstraction level since earlier stages of design in order to deal with such complexity in a suitable way. This paper reports a case study, which provides an assessment of two well-know high-level paradigms, namely Aspect- (AO) and Object-Oriented (OO) Paradigms. Concepts of both paradigms were applied at modeling phase of a Distributed Embedded Real-Time System (DERTS). The handling of DERTS functional and non-functional requirements (at modeling level) using AO and OO concepts is discussed. Both paradigms are compared using of a set of software engineering metrics, which were adapted to be applied at modeling level. The presented results show the suitability of each paradigm for DERTS specification in terms of reusability quality of model elements.

View PDFchevron_right
A Case Study to Evaluate Pros/Cons of Aspect- and Object-Oriented Paradigms to Model Distributed Embedded Real-Time Systems
Dalimir Orfanus

2008 5th International Workshop on Model-based Methodologies for Pervasive and Embedded Software, 2008

The growing design complexity of today's embedded real-time systems requires new techniques aiming the raising of the abstraction level since earlier stages of design in order to deal with such complexity in a suitable way. This paper reports a case study, which provides an assessment of two well-know highlevel paradigms, namely Aspect-(AO) and Object-Oriented (OO)

View PDFchevron_right
A co-design methodology based on model driven architecture for real time embedded systems
Philippe Soulard

Mathematical and Computer Modelling, 2011

This paper presents the MOPCOM design methodology, developed to enable the efficient design of real time embedded systems, in particular radio (such as software defined radio) communication and video processing equipment. Based on UML and the model driven architecture approach, it could be advantageously applied for the design of a system on a chip or a system on a programmable chip. The MOPCOM methodology defines a set of rules for building UML models for embedded systems, from which Hardware Description Language code is automatically generated by means of a set of model transformations. The MARTE profile is used to describe real time properties and to perform platform modeling. A wireless communication demonstrator is presented to illustrate the methodology and the tooling.

View PDFchevron_right
Critical evaluation of two UML Profiles for Distributed Embedded Real-Time Systems Design
Radziah Mohamad

The successful implementation of Service-Oriented Computing (SOC) for the development of Distributed Embedded Real-time Systems (DERTS) in the recent years has proved the importance of service-orientation over previous paradigms. However, efforts are still needed on systematic service-oriented design of DERTS, especially on the modeling of DERTS. Several UML profiles are proposed for modeling of embedded real-time system and SOC separately. However, a holistic modeling solution, covering both the domains, is still missing. Therefore, a thorough investigation of existing UML profiles is necessary before proposing the holistic modeling solution. In this regard, this paper investigates two UML profiles: MARTE and SoaML profiles from the view of service-oriented development of DERTS. The paper highlights the portions of the two profiles that can be adopted and provides some suggestions that can be used for service-oriented modeling of DERTS. The results of this investigation would be useful in developing a service-oriented based metamodel for DERTS.

View PDFchevron_right

References (16)

  1. References
  2. The Open Group Base Specifications, "Portable Operating System Interface (POSIX)", ANSI/IEEE Std 1003.1, 2004.
  3. OSEK/VDX Group, "OSEK/VDX OS specification", Version 2.2.3, http://portal.osek-vdx.org/files/pdf/specs/os223.pdf, 2005.
  4. Airlines electronic engineering committee, "Avionics Application Software Standard Interface, ARINC Specification 653-1", Aeronautical radio, INC., Annapolis, Maryland, USA. October 2003.
  5. Object Management Group, "MDA guide version 1.1," http://www.omg.org/mda/, June 2003.
  6. Object Management Group, "UML 2.1.1 OCL 2nd revised submission, 2007," OMG document: ad/2007-02-03.
  7. Object Management Group, "UML Profile for Modeling and Analysis of Real-Time and Embedded systems (MARTE)", RFP 2005.,OMG document: realtime/05-02-06.
  8. B. Selic, "On Software Platforms, Their Modeling with UML2, and Platform-Independent Design," Eighth IEEE International Symposium on Object-Oriented Real-Time Distributed Computing (ISORC 2005), May 2005.
  9. A. Sangiovanni-Vincentelli and G. Martin, "Platform-based design and software design methodology for embedded systems," Design & Test of Computers, IEEE, Nov/Dec 2001.
  10. Yann Tanguy, Sébastien Gérard, Ansgar Radermacher and François Terrier, "Model Driven Engineering for Real Time Embedded Systems", In 3rd European Congress Embedded Real Time Software (ERTS), Toulouse (France), January 2006.
  11. Object Management Group, "UML Profile for Schedulability, Performance, and Time", Version 1.1, 2005. OMG document: formal/05-01-02.
  12. P. Kukkala, J. Riihimâki, M. Hämäläinen and K. Kronlöf, "UML 2.0 Profile for Embedded System Design," Automation and Test in Europe Conference (DATE 2005), pp. 710-715, March 2005.
  13. R. Chen, "UML and Platform-based Design," UML for Real: Design of Embedded Real-Time Systems, Kluwer Academic Publishers, pp. 107-126, May 2003.
  14. VxWorks 5.5 Documentation Page, http://www.windriver.com.
  15. OSEK/VDX Group, "OIL specification" Version 2.5, 2004. http ://portal.osek-vdx.org/files/pdf/specs/oil25.pdf.
  16. F. Jouault, "Contribution à l'étude des langages de transformation de modèles", PhD Thesis, Université de Nantes, 2006.

Related papers

Model driven engineering for embedded real-time systems
A. Radermacher

In order to keep competition at bay, industries have no other choice than ever increasing the innovative part in their products at a lower cost and within a shorter time-to-market. Obviously, this tends to make products drastically more and more complex and hard to realize. The Accord|UML research project, driven for several years by the CEA-List, aims to provide solutions to manage complexity in the development of real-time embedded systems (RTES). Accord|UML consists in a methodology and a set of dedicated tools. The methodology is based on a generative modelcentered process that covers the whole RTES development cycle from the very early requirement analysis steps to the generation of an executable prototype. This paper will analyze how model driven engineering may be valued in a RTES development context. Especially, referring to the Accord|UML project, it will illustrate abstraction and refinement through the presentation of minimal language extensions for real-time concerns, code generation and validation of embedded real-time features.

View PDFchevron_right
Towards a Meta-Model for Real-Time Embedded Systems
Soukaina Moujtahid

American Journal of Embedded Systems and Applications, 2017

Embedded real-time systems are combinations of hardware and software fully integrated into the systems they control. Due to the continuous technological evolution in the hardware and software and the diversity of the targeted areas of application, these systems have become omnipresent in our professional and personal lives. Thus, various approaches based on model driven engineering (MDE) have been proposed in order to control the inefficiency of the methods of their current design. Each of these approaches has its own meta-model and its corresponding UML profile, specialized or adapted to a particular category of these systems. Indeed, in this paper we will propose a generic meta-model, taking advantage of a large number of these meta-models, which can be adapted to the majority of embedded real-time systems.

View PDFchevron_right
A Meta-model for Real-Time Embedded Systems
Soukaina Moujtahid

2017

Embedded real-time systems are combinations of hardware and software fully integrated into the systems they control. Due to the continuous technological evolution in the hardware and software and the diversity of the targeted areas of application, these systems have become omnipresent in our professional and personal lives. Thus, various approaches based on model driven engineering (MDE) have been proposed in order to control the inefficiency of the methods of their current design. Each of these approaches has its own meta-model and its corresponding UML profile, specialized or adapted to a particular category of these systems. Indeed, in this paper we will propose a generic meta-model, taking advantage of a large number of these meta-models, which can be adapted to the majority of embedded real-time systems.

View PDFchevron_right
Model-driven resource management for distributed real-time and embedded systems
David Juedes

2004

We propose a model-driven resource management technique designed for online resource management of distributed real-time and embedded systems. We have implemented this technique in the QARMA resource manager and related design tools. This paper describes a visual modeling tool used by QARMA, the specification languages it generates, as well as QARMA's underlying model and software architecture.

View PDFchevron_right
UML-Based Development of Embedded Real-Time Software on Multi-Core in Practice: Lessons Learned and Future Perspectives
Detlef Scholle

IEEE Access, 2016

Model-driven engineering has got a foothold in industry as an effective way to tame the complexity of modern software, which is meant to run on embedded systems with real-time constraints by promoting abstraction, in terms of prescriptive models, and automation, in terms of model manipulations. In the plethora of modeling languages, the unified modeling language (UML) has emerged and established itself as a de facto standard in industry, the most widely used architectural description language and an ISO/IEC standard. In the SMARTCore project, we have provided solutions for the UML-based development of software to run on multicore embedded real-time systems with the specific focus of automating the generation of executable code and the optimization of task allocation based on a unique combination of model-based and execution-based mechanisms. In this paper, we describe the lessons learned in the research work carried out within SMARTCore and provide a set of perspectives that we consider to be highly relevant for the forthcoming future of this research area to enable a wider adoption of UML-based development in industry in general, and in the multicore embedded real-time domain in particular. INDEX TERMS Model-driven engineering, UML, ALF, task allocation optimization, embedded, real-time, code generation.

View PDFchevron_right

Related topics

  • Model Transformation
  • Model Driven Development
  • Software Requirements
  • Real time and Embedded Systems
    • 580 California St., Suite 400
    San Francisco, CA, 94104
    © 2025 Academia. All rights reserved