A reconfiguration pattern for distributed embedded systems

A reconfiguration pattern for UML-based projects of embedded (real-time) systems is defined. It enables to set up hardware/software configurations, and to specify conditions and methods for dynamic reconfiguration. The reconfiguration pattern was inspired by the reconfiguration management solution o...

Full description

Saved in:
Bibliographic Details
Published inSoftware and systems modeling Vol. 8; no. 1; pp. 145 - 161
Main Authors Gumzej, Roman, Colnarič, Matjaž, Halang, Wolfgang A.
Format Journal Article
LanguageEnglish
Published Berlin/Heidelberg Springer-Verlag 01.02.2009
Springer Nature B.V
Subjects
Online AccessGet full text

Cover

Loading…
More Information
Summary:A reconfiguration pattern for UML-based projects of embedded (real-time) systems is defined. It enables to set up hardware/software configurations, and to specify conditions and methods for dynamic reconfiguration. The reconfiguration pattern was inspired by the reconfiguration management solution of the Specification PEARL methodology, which is based on the standard for Multiprocessor PEARL whose original idea it was to extend the language to enable the programming of distributed real-time applications in PEARL. In Specification PEARL, the possibility for abstract descriptions of hardware and software architectures and for defining mappings from software to hardware components has been enhanced in correspondence with the standard. Here, a UML pattern for reconfiguration management in distributed embedded applications based on concepts from Specification PEARL is presented. Its behavioural, structural and functional aspects are outlined. It addresses stereotype entities from the Specification PEARL language, which were joined in a UML profile, and outlines the related reconfiguration management mechanisms, which were carried over to the mentioned UML pattern. The proposed reconfiguration pattern is to facilitate the development of distributed embedded application in UML with consistent and temporally predictable reconfiguration support. It should also support and enhance the applications’ flexibility and portability.
ISSN:1619-1366
1619-1374
DOI:10.1007/s10270-007-0075-7