文档下载 文档下载导航
设为首页 | 加入收藏
搜索 请输入内容:  
 导航当前位置: 文档下载 > 所有分类 > Aspect-Oriented UML Modeling for Developing Embedded Systems
侵权投诉

Aspect-Oriented UML Modeling for Developing Embedded Systems

Workshop on Aspect-Oriented Modeling with UML

Development environments are fragmented, with little interoperability between various levels oftools, and poor portability across environments. Industry-adopted connectivity standards betweendevelopment environments involving mixing languages, cross-platform compilers, and multilingualdebuggers are not readily available. A fundamental problem we are facing is the inability of representingall the design information in an appropriate standard modeling notation, one that is suitable at variouslevels of abstraction and that can present the design from various view points.

In response to these issues our effort in the Yamacraw Embedded Systems (YES) project [6] isdirected at bringing modern software engineering to the embedded software development world. Indeed,modern software engineering, development processes, and construction technology are not commonlyfound in embedded systems projects. For example, only recently has there been some discussion on theuse of object technology [7]. Advancements in mainstream software technology, such as aspect-orienteddesign and separation of concerns, have not found their way into embedded systems development yet.

Our work fundamentally impacts current practice on several fronts, more specifically on thefollowing:

A broad-spectrum notation and integrated methodology for specifying requirements and

designs from high-level behavioral descriptions to the register-transfer logic (RTL) level A product line design approach (domain engineering) that promotes IP reuse

An aspect-oriented, component-based implementation (application engineering) that increases

productivity

Application-specific development environments with support for early validation

2 A broad-spectrum notation

We propose to use a unified notation to address the multiple-language, multiple-analyses problem ofembedded systems design. Previous attempts to address this problem have taken two avenues, a co-simulation approach based on a common backplane, and a compositional approach based on a single,“integrated” model. In the former the various analysis tools corresponding to the different notations arecognizant of the semantics of an underlying common backplane. The basis for the second, compositional,approach is the translation of all different notations into a single “integrated” model with its own analysistools. Our approach is a variant of the latter.

The idea is to use a general modeling language such as UML [8] and to define syntactic isomorphicmappings, and corresponding semantic homomorphism, to existing notations, each supporting variousmodeling techniques familiar to embedded systems designers. It is worth mentioning that UML itself isan attempt to unify several orthogonal object-oriented modeling elements such as data (classes), behavior(states), and execution flow (actions), each with its own set of notations and semantics. The UMLdefinition, however, as it stands at the time of writing, is not entirely satisfactory for modelingapplications in the real-time embedded systems domain. It lacks sufficient semantics in the fundamentalconcepts that are critical for this domain1.

Nevertheless, UML includes built-in extension mechanisms that allow refinements of the notation toinclude concepts found in a particular domain. There are several implementations as part of support toolsto respond to the real-time, embedded systems challenge [9, 10, 11, 12]. These extensions, known asprofiles, however, are still fairly low-level, and they do not directly address system-level modelingconcepts, nor do they include full support for all the abstractions of an embedded systems methodologythat covers partitioning, Hw/Sw co-design/co-simulation, etc.

In this regard, we propose a broad-spectrum notation combining levels of abstraction (verticalintegration), and heterogeneous conceptual models (horizontal integration), built as a series of extensions

1

At the time of writing, there are four OMG’s request-for-proposals to deal with the deficiencies, one dealing with ActionSemantics, another with Scheduling, Performance, and Time, and the last two related to quality of service (non-time related),and modeling of complex systems.

上一页第2页

你可能喜欢

热门文档

相关文档

站点地图 | 文档上传 | 侵权投诉 | 手机版
本站所有资源均来自互联网,本站只负责收集和整理,均不承担任何法律责任,如有侵权等其它行为请联系我们.
文档下载 Copyright 2013 doc.guandang.net All Rights Reserved.  -  email