co! 5 S 337: SYSTEM. ANALY S15 BND DESIGN TOPIC: UNI HIED MODELLig LANGUAGE (UML) LECTURE NOTE 1.0 Introduction The U: Unified Modelling Language (UML) is a standardized modelling language used tp specify, visualize, construct, €nd document the artifacts of a software system. It provides a common language for developers, analysts, and designers to visualize the design of a system, The visual effet of the UML. diagram isthe most important part ofthe entire proces, ll te pet men are “used to niake it complete. The elements in a UML are like components which'can be'associated in’ different ways to make a'complete UML’pictiré, Which is known as diagram. Thus, it is very important to understand the different diagrams to implement the kriowledge’iiieal-life systems, Any complex system is best understood by making some kind of diagrams’ or pictures. These diagrams have a better impact but Uhdetstaliting! He look around, we will realize that the diagrams are not a new concept but it i8 used widely in different forms in different industries. We prepare UML diagrams to understand the System in a better and simple way. A single diagram is not enough to cover all the aspects of the system. UML defines various kinds of diagrams to cover most of the aspects of i systetii ‘ae generally made in an incremental and iterative way. There’ aré-'tWo" broad ‘categories You can also create your own set of diagrams to meet your requirements. ‘Didigha (structural and Behavioral) of diagrams and they are again divided into ‘subcategotic 11 Structural Diagrams pis ten wher The structural diagrams represent the static aspect of the system. ‘These’ static aspects represent those parts of a diagram, which forms the main structure and aire therefore'stable, ‘These static parts are represented by classes, interfaces, objects, components, and nodes:"The four structural diagrams are - : eae: + Ch agram + Object diagram + Component diagram + Deployment diagram a. Class Diagram ; Class diagram is a static diagram. It FPTESENIS the static yiew of ‘an tipplication: ‘Class diagram is not only used for visualizing, 4¢scribing, and documenting different aspects of a‘ 7 f the s : i System but also for constructing executable code o! oftware application, Class diagram Aescribes the atributes and operations of a class and also the ogni imposed on the System. The class diagrams are widely used in the Modeling gp object ‘oriented systems because they are the only UML diagrams, which can be mappeq directly with object-oriented languages. Class diagram shows a collection of Classes, iNterfaces, associations. collaborations, and constraints. It is also known as a structural diagram. Class diagrams are sts of classes, interfaces, tthe object-oriented view the most common diagrams used in UML. Class diagram consi Associations, and collaboration. Class diagrams basicaly represen of a system, which is static in nature. Active class is used in a class diagram to represent the Concurrency’ of te syst Class diagram represents the object orientation of a systerh, Hence, it ig generally used for development purpose. This is the most widely used Giagram at the’ time ‘of systein construction, i, Purpose of Class Diagrams 7 ‘The purpose of class diagram is to model the Static view of an application’ Class diagrams are ‘he only diagrams which can be directly mapped with object-oriented languages and’ thus widely used at the time of construction, UML diagrams like activity diagram, sequence diagram can only give the'séquence flow of the application, however class diagram is a bit different. It is the most popular UML didgraim in the coder community ‘The purpose of the class diagram can be summarized as ~ Analysis and design of the static view of an application. + Describe ‘sponsibilities ofa system, 2 H Base for component and deployment diagrams poate * Forward and reverse engineering fi How to Draw a Class Diagram f Class diagrams are the most popular Un, diagrams used for construction of software applications. I is very important o lear ty 1 drawing procedure of class diagram. Class diagrams have a lot of properties © consider while drawing but here the diagram will nsider be considered from a top level view, \ \ \Class diagram is basi sical 'Y graphical representation of the static View of the system and represents different as pects of i ; whole system, the application. A collection of class diagrams represent the The following poii & Points should be remembered while drawing a class diagram = The na me Of the class diagram ghould be meaningful to describe the aspect of the system. Each el te “ee and their relationships should be identified in advance. . sponsibility (attributes and methods) of each class should be clearly identified For each class, minimum number of properties should be specified, as unnecessary properties will make the diagram complicated. Use notes whenever required to describe some aspect of the diagram, AF the end of the drawing it should be understandable to the developerieoder: Finally, before making the final version, the diagram should be drawn’ on plain paper ind reworked as many times as possible to make it correct. The following diagram is an example of an Order System of an application. It describes a particular aspect of the entire application «First of all, Order and Customer are identified as the two clements of ‘the system. ‘They have a one-to-many relationship because a customer can have multiple orders. * Order class is an abstract class and it has two concrete classes (inheritance relationship) SpecidlOrder and NormalOrder «The two inherited classes have all the properties as the Order lass.’ In addition! they have additional fictions like dispatch (and receive (. The following class diagram has been drawn considering all the points mentioned above.Customer name Sting |, location String fe sendOraer) receiveQrdert) dateDale umber String confi) closet) dispatch) Figure 1.1 Sample Class Diagram iti ‘Where to Use Class Diagrams Class diagram is a static diagram and it is used to model the static view of a system. The static view describes the vocabulary of the system. Class diagram is also considered as the foundation for component and deployment diagrams. Class diagrams are not only used to visualize the statie view of the system but they are also used to construct the executable code for forward and reverse engineering of any system. Generally, UML diagrains are not directly mapped with any object-oriented programming languages but the class diagram is an exception Class diagram clearly shows the mapping with object-oriented languages such as Tava, cH, etc, From practical experience, class diagram is generally used for construction purpose. Ina nutshell it can be said, class diagrams are used for ~ + Describing the static view of the system. *+ Showing the collaboration among the elements of the static view. + Describing the functionalities performed by the system e oriented languages. Construction of software applications using object b. Object Diagram Object diagrams can be described n instance of class diagram. Thus, these diagrams are ed as a more close to real-life seenariog where we implement & system: wherObject diagram: 7 ‘ St CABFEMS ALE a Set OF objects and thet relationship is just Hike class diagrams. ‘They also represent the static view of thes P system. The 1 usage of object diagrams is similar to class diagrams but they are used to build prototype of a system from a practical perspective & Component Diagram Component diagrams represent a set of components and their relationships, These components consist of classes, interfaces, or collaborations. Component diagrams represent the implementation’ view of a system. mies During the design phase, software artifacts (classes, interfaces, etc.) of a system are arranged in different groups depending upon their relationship. Now, these groups are known as components. Finally, it can be said component diagrams are used to visualize the implementation, d. Deployment Diagram Deployment diagrams are a set of nodes and their relationships. These nodes are physical entities where the components are deployed. Deployment diagrams are used for visualizing the deployment’ view “of*a°systém: This ‘is generally used by the deployment team. i Note — If the above descriptions and usages are observed carefully then itis very clear that all the diagrams have some relationship with one another. Component diagram’ até dependent upon the classes, interfaces, ete. which are part of class/object diagram. Again, the deployment diagram is dependent upon the Components, which are used to make component diagrams. Deployment diagrams are used to visualize the topology of the physical components of a system, where the software components are deployed, Deployment diagrams are used 10 deseibe the static deployment view of a system Deployment diagrams consist of nodes and their relationships, i. Purpose of Deployment Diagrams ‘the term Deployment itself describes the PUFPOFE of the diagram, Deployinent diagrams are sed for deseribing the hardware componenis Where sofware components are deployed Component diagrams and deployment diagrams ® closely relate Component diagrams are used to deseribe ie sot tages tow how they are deployed in hardware.i . However, these two UML is mainly designed to focus on the software artifacts of a system. é used to focus on software and hardware component diagrams are special diagram: ¢ diagrams Most of the UML diagrams are used to handle logical components but deployme are made to focus on the hardware topology of a system. Deployment diagrams are used by the system engineers. ‘The purpose of deployment diagrams can be described as ~ + Visualize the hardware topology of a system. + Describe the hardware components used to deploy software components fa system. Bowe: + Desetibe the iiintime processing nodes. How to Draw a Deployment Diagram Deployment diagram ‘represents the deployment view of a Systelil. ‘It "fs" relatedto" he component diagram because the components are deployed using the deployment diagrams. A deployment diagram consists of nodes. Nodes are nothing but physical hardware used to deploy the application. Deployment diagrams are useful for system engineers. An efficient deployment diagram is very important as it controls the following parameters — : : + Performance + Scalability + Maintainability + Portability Before drawing a deployment diagram, the following artifacts should be ideritified + Nodes + Relationships among nodes ‘ Following is a sample deployment diagram to provide an idea of the deployment view of order management system. Here, we have shown nodes as * + Monitor + Modem. + Caching server + Server Snr The application is assumed to be a web-based application, which is deployed in a clustered Environment using Server 1, server 2, and server 3. The user connects to the application using the Internet. The control flows from the caching server to the clustered environment,2 Cty The followin, : 8 deployme, i abv: ‘Mt diagram has been drawn considering all the points Mentioned Internet Connection User Figure 1.2 Deployment Diagram iii. Where to Use Deployment Diagrams Deployment diagrams are mainly used by system engineers, These diagrams are used to describe the physical components (hardware), their distribution, and association, Deployment diagrams can be visualized as the hardware components/nodes on which the software components reside. . Software applications are developed to model complex business processes. Efficient software applications are not sufficient to mect the business requirements, Business requirements can be described as the need to support the increasing number of users, quick response time, etc. To meet these types of requirements. hardware components should be designed efficiently and in a cost-effective way. Now-a-days software applications are very COMPlex in nature. Software applications can be standalone, web-based. distributed. maiMfF8M€-based and rmany’ mize.” Hence, it 8 Very important to design the hardware components Cfficiently,Deployment diagrams can be used ~ + To model the hardware topology of a system. + To model the embedded system. ' To model the hardware details for a client/server system. To model the hardware details of a distributed application. + For Forward and Reverse engineering. 12 Behavioral Diagrams Any system can have two aspects, static and dynamic. So, a model is considered as complete when both the aspects are fully covered. Behavioral diagrams basically capture the dynamic aspect of a system. Dynamic aspect can be further described as the changing/moving parts of a system. UML has the following five types of behavioral diagrams — + Use case diagram + Sequence diagram * Collaboration diagram . + State chart diagram det fs enasidiere + Activity diagram a. Use Case Diagram Use case diagrams are a set of use cases, use case view of a system. A ‘use case Hence, actors, and thei relationships. They represent the Tepresents a particular functionality of a system, lise case diagram is used to describe the relationships among the functionalities and their internal/external controllers. These controlle the most important aspect is to ca behavior ofthe system when it ig rs are known as actors. To model a system, ture the dynamic behavior. Dynamic behavior means tke Tunning /operating. Only static behavior is not Sufficient to model a system rather dynamic behavior is’ more important than static behavior, Gynamic nature and use case case diagram is dynamic jin n In UML, there are five diagrams available to model the ‘agram is one of them. Now as we have to discuss that thé use ature, there should be some inténtdll Sr etna! Riots foe maki 7 : en : cn taUON These intemal and external agents ae know a ite U8 cae Aiagrams consist of actors ig 1 Use the system/subsystem Of an application. A single use case diagram captures a Particular functionality of system, cases and their relationships. The diagram is used to modelHence to model the ENtire sys, ; S 7 Purpose of Use Case The purpose of use case dig m, a number of use case diagrams are used. Diagrams definition is too generi ‘8tam is to capture the dynamic aspect of a pystem. However, this , “ 10 describe the purpose, as other four diagrams (activity, sequence, collaboration, and State ch, Purpose. which will disting Use case diagrams are us, art) also have the same purpose. We will look into some specific ish it from other four diagrams. 'd 10 gather the requirements of a system including intemal and external influences. These requirements are mostly design requirements. Hence, when a suse 38 analyzed to, gather its inctionalies’ use cased” re’ pliiidred:and adiors-are identified. When the initial task is complete, use case diagrams are modelled to present the outside view. z In brief, the purposes of use case diagrams can be said to be as follows ~ ‘“*~' = Be * Used to gather the requirements ofa system. eek. + Used to get an outside view ofa system, + Identify the external and intemal factors influencing the system. Show the interaction among the requirements and actors. ii, How to Draw a Use Case Diagram? Use case diagrams are considered for high level requirement analysis of a system. When the requirements of a system are analyzed, the functionalities are captured in use cases, We can say that use cases are nothing but the system functionalities written in an organized manner. The second thing which is relevant to use cases are the actors. Actors can be as something that interacts with the system. defined Actors can be a human user, some internal applications, or may be some extemal applications. When we are planning 10 draw a use case diagram, we should have the following items identified. + Functionalities to be represented as use case iss vty + Actors * Relationships among the use cases and Actors, Use case diagrams are drawn to capture the functional requirements of a system. After identifying the above items. we have to use the following g iclines to draw an efficient use case diagram * The name of a use case is very important: The name should be chosen in such a way So that it can identify the functionalities performed,* Give a suitable name for actors. Show relationships and dependences Clearly inthe diagram, Do not try to include al types of relationships, 3 the main poioel of bs inceat to identify the requirements. + Uses whenever required to clarify Some important points, Following is a sample use case diagram representing the order management system, Hence, if ‘We Took into the dingrait thea "wo ill And three’ qoastte! (Order, SpecialOrder, and NormalOrder) and one actor which is the customer, The SpecialOrder and NormalOrder use cases are extended from. Order usecase. Hence. they © identify the system boundary. ‘side the system as it is an external wn as: have extended relationship. Another important Point sis t which is shown in the picture. The actor Customer lies out user of the system. A sample of a Use case diagram is sho | US® case diagram of an order management system 7 <> Extohds / relationship Ne Oa ceases v Customer | t : ye | “or { Normalorder Extenad i» | Folatéonship | i ' System ___———" boundary | Figure 13 Use Case Diagram Where fo Usea Use Case Diagram? : AS we have already discussed there are five diagrams in UML to model the dynamic view of ® system. Now each and every model has some specific purpose to use, Actually these Specific purposes are different angles of a running system. To understand the dynamics of a system, we need to use different types of diagrams. Use case diagram is one of them - a specific purpose is to gather system requirements and ators. Use case diagrams men e SYens OF @ s)8tem and their ows, yy use case diagram never describes how they are implemented. Use case diagram can be imagined asa black box where only the input, output, and the function of the Back box is kngnThese diagrams \ rams are used at a Very high level of design. This high level design is refined apain and again to get a complete and : Practical picture of the system. A well-structured use case also describ es the Pre-condition, post condition, and exceptions. These extra elements are € test cases when Performing the testing, Although use case is not a ‘800d candidate for forward and reverse engineering, stil] they are used in a slightly different Way to make forward and reverse engineering. The same is true for reverse engineering. Use case diagram is used differently to make it suitable for reverse engineering. used to mak In forward engineering, use case diagrams are used to make’ test ‘cases and in reverse engineering use cases are used to prepare the requirement details fromthe existing application: * re Use case diagrams can be used for — + Requirement analysis and high level design. rao sill hey + Model the context of a system. cag + Reverse engineering. ms ; * Forward engineering. b. Sequence Diagram ! eel A sequence diagram is an interaction diagram. From the name, it is clear that the diagram deals with some sequences, which are the sequence of messages flowing from one object to another. Interaction among the components of a system is very important’ from implementation and execution perspective. Sequence diagram is used io visualize the sequence of calls in a system to perform a specific functionality © Collaboration Diagram Collaboration diagram is another form of interaction diagram. It represents the ‘structural organization of a system and the messages sent/received. Structural organization consists of objects and links. The purpose of collaboration diagram is similar to sequence diagram. However, the specific purpose of collaboration diagram is to viguatize'the’ orgcizition of objects and their interaction. d. State chart Diagram b Any real-time system ig expected to be reacted bY some kind of intennaliextermal events the sysi ‘These events are responsible for state change of the system,Statechart diagram is used to represent the event driven state change of a system. It basically describes the state change of a class, interface, etc. State chart diagram is used to visualize the reaction of a system by internal/external factors. Activity Diagram Activity diagram describes the flow of control in a system. It consists of activities and links The flow can be sequential, concurrent, or branched, Activities are nothing but the functions of a system. Numbers of activity diagrams are prepared to capture the entire flow in a system. Aclivity diagranis are used to visualize the flow of controls ina Systehi! PRIS TS prepared io have an idea of how the system will work when executed, Note — Dynamic nature of a system is very difficult to capture. UML has provided features to capture the dynamics of a system from different angles. Sequence diagramis and collaboration diagrams are isomorphic, hence they can be converted from one another without losing any information. This is also true for Statechart and activity diagram. Activity diagram is another important diagram in UML to describe the dynami aspects of the system. Activity diagram is basically a flowchart to represent the flow from one activity to ‘another activity. 'The activity can be described as an operation of the system. The control flow is drawn fiom oné Operation to another. This flow can be sequential, branched, or concurrent. Activity diagrams Y eonfiems © an order rauest oe * v \ dui | ote pl | order) sieaisckige Orr Figure 1.4 Activity Diagram iii Where to Use Activity Diagrams : The basic usage of activity’ diagram is similar to other four UML diagrams. The specific usage is to model the control flow from one activity to another. This control flow does not include messages. Activity diagram is suitable for modeling the activity flow of the system. An application can have multiple systems. Activity diagram also captures these systems and describes the flow from one system to another. This specific usage is not available in other diagrams. These systems can be database, external queues, or any other system. We will now look into the practical applications of the activity diggram. Prom the above discussion, itis clear that an activity diagram is drawn from a very high level. So it gives high level view of a system. This high level yiew is mainly for business users or any other person who is not a technical person, This diagram is used to model the aetiyities which are nothing but business requirements, The diagram has more impact on busines understanding rather than on implementalion dels, Activity diagram can be used for + Modeling work flo ae = Modeling maine Lea ‘Quirements,Se + High level understangi + Investigating business Ng of the system's functionalities. Fequirements at a later stage.