Introduction to UML | P La Learning Objectives ... {) To know about Unified Modeling Language (UML) jg) To study reasons for learning UML. ff Tolearn about three building blocks of UML. {@) To get information on different types of UML diagrams. @ To know different Things and Relationships in UML. § To study UML rules and UML Architecture. @ To get knowledge of UML Advantages and disadvantages. SS eee wm CONCEPT OF UML [[S-18, W-18, S-19}} * UML stands for Unified Modeling Language. UML is a standard graphical language for modeling object-oriented software. * UML can be described as a general-purpose visual modeling language which is used to Visualize, specify, construct, and document software systems. * UML is not a programming language, but tools can be used to generate code in various languages using UML diagrams. UML was created by Object Management Group (OMG) and UML 1,0 specification draft Was proposed to the OMG in January 1997. It was developed in the mid-1990s as a collaborative effort by James Rumbaugh, Grady Booch and Ivar Jacobson, Definition: Tt can be defined as “UML is a language for visualizing, specifying, constructing and documenting artifacts of a software intensive system”. _ Inthis definition, © Visualizing means UML has the standard diagramming notations for drawing or Presenting pictures of software systems. © Specifying means building models that are exact, unambiguous and complete. © Constructing is related to actually implementation of design into coding. © Documentation plays a vital role in any type af system development, which helps during developing a system and after its deployment. UML addresses document- tation of system architecture and other details. (3.1)32 ng — Sa a ase 1984 (cA) - Sem. VI UML . Goals of ML: visual modeling lan 2se188 ‘Mowing are main goals oe to-use, nee eHaRe role ith a ready- dels. ; : with a ready torn : : 2 Poe snd exchange meaningful jon mechanisms to extend the cents adiag cerelp sd epectaliza nguages and developmen, Sy conne Provide extensibility an Jar programming a! it eo f particula’ * Be independent o: i Proc! We ar: for understanding the modeling language, fy Be iec 10m i arket. Provide a formal nea opject Orientation tools m of Encourage the grow?! ‘UML > above the name is Fig. 3.9: Representation Of Artis the focus shown in Fig. 3.9. In an act (viii) Node: perform * Anode can be defined as a physical element that exists at run time. Graphic * Anode isa physical element that exists at run time and C7 withan represents @ computational resource, generally having san distingu atleast some memory and, often processing capability. A set of components may reside on a nod 5.3] e € al migrate from node to node, maeavalee a * Graphically, a node is shown asa ¢ b i i rete mt ch erlyitsname,asinFig.310,”“S¥éllyincluding Fi of Nodes _ a2 Behavioral Things tpt * Behavioral things are the dynary; fnodel, representing behavior over ear'> Of UML models, These are the verbs( PACkags re e OVer ti phavioral things as given below,” “'™® @Rd Space, tn UML, there are three kind Package behavio * Interaction is defined as a b, He pci ehavi ; packe aan Clements to accompli ape sits °F @ group of messages excl! °PP0sed ion involye ‘ask, connectors, ape tierce ; sonst sac Graphically, a messave ; ” Including messages, actio™’ groupin line, almost always “ a Fig, 3.21: Representation of Generalization ay Fig. 3.22 shows an example of 8eneralization, Aa Generalization It is a semantic relationship detwe go. ¢ er contract that another Classifier n a Wherein one classifier spec o 1 a ‘Carry out, o 2 ae) °Seti ee ee ee Introduction to UML ‘cose 185a(CA) Sem. VI 33 Realization can be defined as ‘a relationship in which ~ Co, : ents are connected” my two elem Printer RI Fe ternent describes some responsibility which is not "implemented and the other one implements them. This zy relationship exists in the case of interfaces. Realization + Graphically, a realization relationship is displayed as a =™Ple op cross between a generalization and a dependency [oo 2 soap “Itionsh, relationship, as in Fig. 3.23 ®}. For example, in the Fig. 324, printing preferences that fig. a.24 Example of ; : are set using the Printer setup interface are being Realization ‘SS op implemented by the Printer. e “ONeep¢ | other Important Terms used in UML: icity: a 2 zedeqamm 2 Multiplicity: Passengers * tis the active logical association when the cardinality of -— I a class in relation to another is being depicted. It is also *\ called Cardinality. Multipicty For example, one fleet may include multiple airplanes, while one commercial airplane may contain zero to many passengers. The notation 0..* in the diagram means “zero to many”, (See Fig. 3.25). Fig. 3.25: Example of Multiplicity Airplane a RULES OF UML fe any language, the UML has a number of rules that specify what a well-formed model should look like. A well-formed model is one that is semantically self-consistent and in harmony with allits related models. The UML has syntactic and semantic rules for: 1 Names: Whatcan you call things, relationships and diagrams? 2, Scope The context that gives specific meaning toa name. 3. Visibility : How can those names be seen and used by others? How things properly and consistently related to one another? What does it mean to run or simulate a dynamic model? ig the development of a software-intensive system tend to evolve by many stakeholders in different ways and at different times. common for the development team to not only build models that it also to build models that are: Certain elements are hidden to simplify the view. Certain elements may be missing. The integrity of the model is not guaranteed.oo: sen V_ HITECTURE users like develope; E [BBA (CA) - 5 UML ARCHITE 4 by aifferent ing a system th, = used PY 5 pefore desiem the ee x % mo! vee i in min’ various people, analysts an Y Fes in il Feet Oo made with different persP js to visualize the ake ee pa This vie een ea understand the DENe™ t perspective: a * UML plays an importan mentation, epl ec : ay/oesign. IPP ome 4, The im perspectives are Logic Case View. assemb config indepe syster compo captur intera: 5. The D hardw the di: systen diagre $9 | ADV: Various ai PHYSICAL CONCEPTUAL Implementation View Logical View Class, Object, Package, Composite Structure, State Machine Component Use Case View Use case, Activity Process View Deployment View Sequence, Communication, Activity, Timing, Interaction Overview Deployment . # g ¢ ° e 8 S 5 = 3 = 2. It is, 3. Itise 5. Itisb system, a the vorabulary gfe ees the classes, interfi# ¢ aie fact Tequiremenge or” and its solution onal should contr , ide to its eng 7. Mosti ‘softwstate diagrams and activity diagrams, 5. The Deployment View of a system includes the nodes that form the system's hardware topology on which the s system. With the UML, the static aspects of this view are captured in interaction diagrams, state dia; grams and activity diagrams. : Bl ADVANTAGES OF UML Various advantages of UML are listed belo 1. Itis a formal language: Each element has model a system, we can model with co; understood by everyone. “ 2, It is concise: The entire language is made u, ribe the behat notation. 3. Itis comprehensive: It describes all important aspects ofa system. Itis scalable: Wherever needed, the lan system modeling projects, verload. ment a strongly defined meaning. When we nfidence that the designed model is ip of simple and straightforward iguage is formal enough to handle massive but it also scales low to small Projects, avoiding is built on lessons learned: UML is the result of best mmunities over the past few years. is standard: UML is controlled by an open standard group with active tributions from a world-wide 8roup of vendors and academics. tly used: It is the most useful method of visualization and documenting ftware system design. is independent: It uses object-oriented design concepts and it is independent of ‘ming language. practices in object-orientedOSE [BBA (CA) - Sem. V) ~ DISADVANTAGES OF UML - e listed belo Disadvantages of UML ar a) : UML has still no s 4. Lack of formality: UI Seats ructure and specification for Mode, format. interfaces. UML does not define a stan’ ; hs d when using UML is the time it takes te 2. Time: Some developers might fin and maintain UML diagrams. To wo) synchronized with the software code, which requires time to set up and m and adds work to a software development project. Diagrams can get overcomplicated: When creating an UML dia conjunction with software development, the diagram might becg a t rk properly, UML diagrams complicated, which can be confusing and frustrating for developers, . Too much importance on design: UML places much im; can be problematic for some developers and companies. . Synchronizing code with models is difficult: makes it difficult to keep them consistent with be added by hand, ects int Show Using multiple models/qj; 3.16 SET 00s ag each other and much Code Tit in portance on design, EE ie 2 Pes behavioral features! What sh i with ‘ould happe €ach other to cre’ Peas e