Unifying Hardware and Software Components for Embedded System Development
Model-driven and component-based software development, using the UML, has become one of the dominant development paradigms, particularly in business and web application engineering. Unfortunately, model-driven and UML-based development methods are still inferior to conventional software development approaches when it comes to component-based embedded system development. One important aspect is the heterogeneity of embedded systems: they contain both, hardware and software components. Although, component-based development in embedded systems (with hardware components) has a long tradition, there is still a problem of combining it with component-based software development. One reason is the inability of contemporary component technologies to cope with the specific non-functional requirements of embedded systems (e.g., timing, resource consumption). Thus, the major question is how both approaches can be successfully combined.
The goal of this chapter is to discuss the problems of embedded systems engineering in the context of a component-based development approach, and to identify specific requirements for a development process under this paradigm. In addition, the chapter proposes an approach to specify software and hardware components in a uniform way, concerning their functional and non-functional properties, so that they can be applied in embedded system development. The method proposed is not yet solving all the problems associated with component-based embedded systems development, but it addresses important issues like hardware/software integration, and how timing and resource issues can be dealt with.
KeywordsUnify Modeling Language Embed System Hardware Component Device Driver Unify Modeling Language Diagram
Unable to display preview. Download preview PDF.
- 2.Booch, G.: Software Components with ADA: Structures, Tools and Subsystems. Benjamin-Cummings (1987)Google Scholar
- 3.Booch, G.: Object-Oriented Analysis and Design with Applications. Benjamin-Cummings (1994)Google Scholar
- 4.Chen, R., Sgroi, M., Martin, G., Lavagno, L., Sangiovanni-Vincentelli, A., Rabaey, J.: Embedded System Design Using UML and Platforms. In: Proceedings of the Forum on Specification & Design Languages 2002 (FDL 2002), Marseille, France, September 24-27 (2002)Google Scholar
- 5.D’Souza, D., Wills, A.: CATALYSIS practical rigor and refinement - extending OMT, fusion, and objectory. Technical report, ICON Computing Inc. (1995)Google Scholar
- 6.Filman, R.E., et al.: Aspect-Oriented Software Development. Addison-Wesley, Reading (2005)Google Scholar
- 7.Green, P., Edwards, M., Essa, S.: UML for System-Level Design, Forum on Design Languages. In: Proceedings of FDL 2001, Lyon, France, September 3-7 (2001)Google Scholar
- 8.Green, P.N., Edwards, M.D.: The modeling of Embedded Systems Using HASoC. In: Proceedings of Design, Automation and Test in Europe (DATE 2002) (2002)Google Scholar
- 11.de Jong, G.: A UML-Based Design Methodology for Real-Time and Embedded Systems. In: Proceedings of Design, Automation and Test in Europe (DATE 2002) (2002)Google Scholar
- 12.Kruchten, P.: The Rational Unified Process. An Introduction. In: Object Technology Series. Addison-Wesley, Reading (1998)Google Scholar
- 13.Object Management Group: Unified Modeling Language Specification (2000)Google Scholar
- 15.Selic, B., Rumbaugh, J.: Using UML for Modeling Complex Real-Time Systems, White paper, Rational (Object Time) (March 1998)Google Scholar
- 16.Selic, B.: A Generic Framework for Modeling Resources with UML. IEEE Computer Society, Los Alamitos (2000)Google Scholar
- 17.Szyperski, C.: Component Software, Beyond Object-Oriented Programming, 2nd edn. Addison-Wesley, London (1999)Google Scholar