"UML for Embedded System Development: What we'd like to see in UML tools"

Abstract

In recent years, the functionalities implemented in embedded systems have grown tremendously both in number and complexity. As a result development became increasingly difficult to manage, predict and keep under control.

UML has been introduced both to raise the level of abstraction, and increase efficiency, especially through the use of CASE tools.

It was originally mainly intended for modeling software-intensive systems and hardware description, which is a must for embedded systems, is not included in the notation. The extension mechanisms of the notation, luckily, enable description of the hardware. However, as a new challenge, programmable logic devices are becoming more and more widespread, and at the same time blur the border between hardware and software.

Design often proceeds through applying (design) patterns. State-of-the-art UML tools support pattern usage to a certain extent, but this is another area where work can be done, e.g. in pattern visualization. Also the usage of multiple profiles simultaneously raises questions; among others also of visualization.