Embedded software engineering: The state of the practice

Abstract

focus 0 7 4 0 -7 4 5 9 / 0 3 / $ 1 7 . 0 0 © 2 0 0 3 I E E E P u b l i s h e d b y t h e I E E E C o m p u t e r S o c i e t y I E E E S O F T W A R E6 1 products are growing. This creates a big challenge for embedded-software development. In the years to come, the key to success will be the ability to successfully develop high-quality embedded systems and software on time. As the complexity, number, and diversity of applications increase, more and more companies are having trouble achieving sufficient product quality and timely delivery. To optimize the timeliness, productivity, and quality of embedded software development, companies must apply software engineering technologies that are appropriate for specific situations.Unfortunately, the many available software development technologies don't take into account the specific needs of embedded-systems development. This development is fundamentally different from that of nonembedded systems. Technologies for the development of embedded systems should address specific constraints such as hard timing constraints, limited memory and power use, predefined hardware platform technology, and hardware costs. Existing development technologies don't address their specific impact on, or necessary customization for, the embedded domain. Nor do these technologies give developers any indication of how to apply them to specific areas in this domain-for example, automotive systems, telecommunications, or consumer electronics. Consequently, tailoring a technology for a specific use is difficult. Furthermore, Embedded Software Engineering:The State of the Practice M any products today contain software (for example, mobile telephones, DVD players, cars, airplanes, and medical systems). Because of advancements in information and communication technology, in the future even more products will likely contain software. The market for these "enhanced" products is forecasted to grow exponentially in the next 10 years. 1 Moreover, these embedded systems' complexity is increasing, and the amount and variety of software in these the state of the practice An inventory of eight European companies reveals what tools developers of embedded-systems software are and aren't using, and why. The need exists for more specific, yet flexible, tools.

Tool Support for Distributed Software Engineering

“…Therefore, the applicability of SoftFab to other development phases strongly depends on the usage of automated tools in those phases. Previous research shows that in the early phases of the life-cycle, i.e., requirements engineering and architecture development, tool support is still limited [14]. During later phases usage of automated tools is more common.…”

Practical and Incremental Maintenance of Software Resources in Consumer Electronics Products

“…Nowadays, brand-new consumer electronics products are rarely developed [2] because we should release products quickly and cheap. Instead of brand-new products, we release new products by revising existing products and by using their related resources.…”

An industrial case study in reconstructing requirements views

“…The creation of requirements views necessitates an accurate traceability matrix, which, in practice, turns out to be very hard to obtain and maintain (Gotel and Finkelstein 1994;Dömges and Pohl 1998;Graaf et al 2003;Ramesh et al 1995;Lindvall and Sandahl 1996). The tools currently available on the market, such as Telelogic DOORS and IBM Rational RequisitePro, are often not sufficient: keeping the traceability consistent using these tools is hard and involves significant effort (Lormans et al 2004;Alexander 2002).…”