UML for Embedded Systems

Abstract

One of the models we studied in Chap. 3 is the heterogeneous object-oriented model. The majority of software systems are implemented using this model, as it is close to real-life systems. Unified Modeling Language (UML) is an object-oriented modeling language standardized by Object Management Group (OMG) mainly for software system development. In software development, UML has become de-facto standard as CASE methodology. Now it is invariably used in embedded systems because of the growing complexity of embedded systems. In this chapter, we use the term system engineering as an equivalent CASE for embedded systems. An embedded system is represented in UML using multiple models through different diagrams. Each model describes the system from a distinctly different perspective. In industry, any project cycle has several people involved in different roles with certain tasks assigned. Section 5.2 describes typical tasks and roles in system engineering. Section 5.3 describes different diagrams supported in UML. Section 5.4 describes with examples, different structural diagrams, viz, class, association, concept of aggregation, composition, signals, and interfaces. Section 5.5 explains different behavioral diagrams with examples, viz, use cases, state, activity, and sequence diagrams. To summarize, Unified Modeling Language (UML) is very established standard to represent a system, its static and dynamic behavior. End to end development of systems, whether it is software system or any embedded system, can be specified. The models can be easily exchanged across design teams. The UML models will be very useful for documentation, skeleton code generation, and verifying the behavior well before coding. Though several books are available to learn UML, we have included this chapter just sufficient to start off the design with UML standard and to represent the extensive set of models we have studied in Chap. 3.