1. UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School of Electronics, SNIST.

2. UML for Embedded Systems.2 Software Development Life Cycle: The various stages that comes during the development of a software are :  Analysis  Requirements  Design  Coding  Implementation  Testing  Maintenance.

3. UML for Embedded Systems.3 Design Phase: Once all the requirements are completed ie. both functional and non-functional, then the next phase is design phase. During this phase, the results of analysis and the requirement phase are implemented with the help of diagrams and the language used to draw diagram is UML.

4. UML for Embedded Systems.4 History of UML

5. UML for Embedded Systems.5 History of UML…. In the beginning, there were three principal methods: The Booch method, devised by Grady Booch, Object-oriented Modeling Technique (OMT), devised by Jim Rumbaugh, Object-oriented Software Engineering (also known as Objectory), devised by Ivar Jacobson. The three methods had many ideas on common, yet different notation for expressing those ideas (for example, OMT classes were represented by rectangle boxes, whereas in Booch methods they were represented as cloud shapes).

6. UML for Embedded Systems.6 U M L Unified Unified: Unification of earlier object-oriented analysis and design methods. Same concepts and notation through the whole development lifecycle. ~ ~ Modeling: Representing in terms of Models or Diagrams Diagrams emphasize something about the system Language: A graphical language ~

7. UML for Embedded Systems.7 Cont…. Later all these three methods were Unified with a common notation and a new modeling language came into existence known as Unified Modeling Language. In the year 1997, a new version UML 1.0 was released by an organization known as OMG. To use UML we have various software's like Rational Rose, Umbrella,TogetherJ, Net Beans, Eclipse and so on….

8. UML for Embedded Systems.8 UML The Unified Modeling Language (UML), in the field of software engineering, is a standardized specification language for object modeling. Unified Modeling Language is defined as industry standard general-purpose modeling language that consists of graphical and textual notations that describes the various aspects of software systems. UML is defined as a visual modeling language that provides a set of rules to creates a blue print of a software.

9. UML for Embedded Systems.9 Acc. to Grady Booch…. According to Booch, it is defined as a language for 1.Visualizing 2.Specifying 3.Constructing 4.Documenting the artifacts of a software intensive system.

10. UML for Embedded Systems.10 More on UML …………. UML is not dependent on any programming language or any technology. A language for modeling object oriented systems. It’s a standard maintained by Object Management Group. The main goal of UML was that they need a standard notation to describe the structure and behavior of the system. UML is a language for communicating about the system and its requirements.

11. UML for Embedded Systems.11 Importance of Modeling…….

12. UML for Embedded Systems.12 Why do we model? To understand requirements To communicate with everyone involved in the project i.e. customer, analyst, domain expert, designer To manage complexity

13. UML for Embedded Systems.13 Basic Buildling blocks: In UML, they are three kinds of building blocks: 1. Things 2. Relationships 3. Diagrams Things represents objects in a model. Relationships is connection between things so that they can communicate with each other by sending messages. Diagrams is collection of things and relationships in a meaningful format.

14. UML for Embedded Systems.14 Types of Things: 1. Class 2. Interface 3. Collaboration 4. Use-case 5. Active Class 6. Node 7. Component 8. Interaction 9. State Machine 10. Package 11. Note

15. UML for Embedded Systems.15 Types of Relationships 1. Dependency 2. Association 3. Generalization 4. Realization

16. UML for Embedded Systems.16 Types of Diagrams: The UML diagrams are categorized into two: 1.Structural Diagrams or Static Diagrams 2.Behavioural Diagrams or Dynamic Diagrams

17. UML for Embedded Systems.17 Structural Diagrams Structural modeling assists in understanding and communicating the elements that make up a system and the functionality the system provides.

18. UML for Embedded Systems.18 Types of Structural Diagrams 1. Class Diagrams 2. Object Diagrams 3. Component Diagrams 4. Deployment Diagrams

19. UML for Embedded Systems.19 Behavioural Diagrams Behavioural Modeling assists in understanding and communicating how elements interact with each other and collaborate to provide the functionality of the system.

20. UML for Embedded Systems.20 Types of Behavioural Diagrams 1. Use Case Diagrams 2. Sequence Diagrams 3. Collaboration Diagrams 4. State Chart Diagrams 5. Activity Diagrams

21. UML for Embedded Systems.21 Use Case diagrams  It is a technique which is used to capture the functional requirements of the system.  This diagram consists of use cases, actors and relationships between them.  A Use Case represents a unit of interaction (for a type of functionality) between a user (human or machine) and the system.  An actor can be any entity that performs a role with in a given system or machine or human.

22. UML for Embedded Systems.22 Class Diagrams Provides a structural view of the classes of a system, their features and the inter-relationships between the classes. Probably the most popular UML diagram used to convey system structure.

23. UML for Embedded Systems.23 Sequence Diagrams This diagram displays the time sequence of the objects participating in the interaction. This consists of the vertical dimension (time) and horizontal dimension (different objects).

24. UML for Embedded Systems.24 Collaboration Diagram This diagram displays the interaction between objects and their links to one another irrespective of time. Numbers are used to show the sequence of messages.

25. UML for Embedded Systems.25 State Diagrams State diagrams are used to describe the behaviour of a system. State diagrams describe all of the possible states of an object as events occur. In other words it describes how an object changes its state that govern its behavior in response to stimuli from the environment Each diagram usually represents objects of a single class and track the different states of its objects through the system.

26. UML for Embedded Systems.26 State Chart Diagram….

27. UML for Embedded Systems.27 Activity Diagrams  Activity diagrams describe the workflow behaviour of a system.  Activity diagrams are similar to state diagrams because activities are the state of doing something.  The diagrams describe the state of activities by showing the sequence of activities performed.  A key feature of Activity diagrams is the ease of showing parallelism.

28. UML for Embedded Systems.28

29. UML for Embedded Systems.29 Component Diagram Component Diagram displays the high level packaged structure of the code itself. Dependencies among components are shown, including source code components, binary code components, and executable components. Some components exist at compile time, at link time, at run times well as at more than one time.

30. UML for Embedded Systems.30 Deployment Diagram Deployment Diagram describes the hardware components and their relationships. In other words, this diagram consists of objects known as Nodes and these nodes are connected to each other with the help of association relationship. Examples of Nodes are Servers, Systems or Printers.

31. UML for Embedded Systems.31 Any Questions…………….

32. UML for Embedded Systems.32