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

Aspect-Oriented UML Modeling for Developing Embedded Systems

Workshop on Aspect-Oriented Modeling with UML

Aspect-Oriented UML Modeling forDeveloping Embedded Systems

Product Lines

Workshop on Aspect-Oriented Modeling with UMLInternational Conference on Aspect-Oriented SoftwareJORGE L. DÍAZ-HERRERA, JASMIN CHADHA, AND NEIL PITTSLEY

School of Computing & Software Engineering

Southern Polytechnic State University

1100 South Marietta Parkway, Marietta, GA 30060-2896

Tel: +1 770-528-5558 FAX: 1 770-528-5511 E-mail: 1 Introduction

Plummeting hardware costs are pushing for a rapid computing growth in new application areas, andespecially in the embedded systems arena. Indeed, computers in systems products and services havebecome very pervasive, and the market is expected to continue to grow rapidly [1]. Embedded systemapplications range from “small” scale devices such as smart phones, personal digital assistants (PDAs),set-top boxes, to large enterprise servers and network computers, radar systems, automotive, avionics, etc.

In today’s post-PC era, embedded systems are increasingly more software-driven, as more and moreof the functionality is placed in software. Although the conventional software industry has been relativelysuccessful, little progress has been observed in the area of development methodologies for embeddedsystems, and current approaches are not entirely satisfactory. For the most part, embedded software is stillwritten by hand in response to natural language descriptions of functionality, which is custom-writtenrepetitively from scratch each time a system is built for the hardware being considered. Embedded systemdevelopment life cycle processes are fundamentally waterfall, top-down, single system driven. The resultsare monolithic (i.e., without interchangeable parts), one-of-a-kind systems that are difficult to change inorder to upgrade and customize. Product behavior is inevitably validated late in the development cycle,with typical consequences of costly errors, lower overall quality, delayed delivery, and high overalldevelopment costs.

Increasing industry pressures to boost productivity and to reduce time-to-market, point to the need tolook for ways to change the current situation. One direction is to move our focus from engineering singlesystems to engineering families of systems using a component-based, reuse-driven approach rather thanthe traditional monolithic, one-of-a-kind designs. For software intensive systems, a reuse-driven approachwill potentially reduce time-to-market, and improve product quality while reducing uncertainty on costand schedule estimates [2]. Additional benefits include longer time-IN-market, amortization of up-frontdevelopment cost, and reduced training and maintenance costs [3].

A factor that holds back reuse in the embedded systems domain is the general lack of firm standardsin many areas. For example, the complexity of embedded systems has driven a proliferation of specializedmodeling notations. There are many languages in used today ranging from a varaiety hardwaredescription languages, continuous modeling languages, protocol specification languages, dynamicsynchronization languages, architrecture description languages, programming and module interconnectionlanguages, and a pletora of formal languages and mathematical notations. (For a fairly complete list see[4], and for a good survey see [5]). Nevertheless, current notations are not entirely satisfactory for allaspects of embedded systems development.

第1页

你可能喜欢

热门文档

相关文档

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