1. GOVT. ENGINEERING COLLEGE, AJMER. A SEMINAR PRESENTATION ON UNIFIED MODELING LANGUAGE(UML) SUBMITTED TO:-PRESENTED BY:- Dr. REENA DADHICHPALLAVI VASHISTHA MCA 5 th Sem

2. Contents -  Models Use-case model Design model (Class diagram)  Diagrams Use-case diagram and activity diagram Sequence diagram and communication diagram Component diagram and deployment diagram Topic diagram and browse diagram

3. What Is a Model? A model is “a complete description of a system from a particular perspective.” A model is a simplification of reality.

4. Why Model? Modeling achieves four aims: – Helps you to visualize a system as you want it to be. – Permits you to specify the structure or behavior of a system. – Gives you a template that guides you in constructing a system. – Documents the decisions you have made. You build models of complex systems because you cannot comprehend such a system in its entirety. You build models to better understand the system you are developing.

5. Four Principles of Modeling The model you choose influences how the problem is attacked. Every model may be expressed at different levels of precision. The best models are connected to reality. No single model is sufficient.

6. What Is the UML? The UML is a language for Visualizing Specifying Constructing Documenting the artifacts of a software-intensive system. The Unified Modelling Language (UML) is an industry standard for object oriented design notation, supported by the Object Management Group (OMG).

7. The UML Is a Language for Visualizing Communicating conceptual models to others is prone to error unless everyone involved speaks the same language. There are things about a software system you can’t understand unless you build models. An explicit model facilitates communication.

8. The UML Is a Language for Specifying The UML builds models that are precise, unambiguous, and complete.

9. The UML Is a Language for Constructing UML models can be directly connected to a variety of programming languages. – Maps to Java, C++, Visual Basic, and so on – Tables in a RDBMS or persistent store in an OODBMS – Permits forward engineering – Permits reverse engineering

10. The UML Is a Language for Documenting The UML addresses documentation of system architecture, requirements, tests, project planning, and release management. Use Case Diagram Actor A Use Case 1 Use Case 2 Use Case 3 Actor B Class Diagram Sequence Diagram user mainWndfileMgr : FileMgr repositorydocument : Document gFile 1: Doc view request ( ) 2: fetchDoc( ) 3: create ( ) 4: create ( ) 5: readDoc ( ) 6: fillDocument ( ) 7: readFile ( ) 8: fillFile ( ) 9: sortByName ( ) ƯÁ¤¹®¼­¿¡ ´ëÇÑ º¸±â¸¦ »ç¿ëÀÚ°¡ ¿äûÇÑ´Ù. È­ÀÏ°ü¸®ÀÚ´Â Àоî¿Â ¹®¼­ÀÇ Á¤º¸¸¦ ÇØ´ç ¹®¼­ °´Ã¼¿¡ ¼³Á¤À» ¿äûÇÑ´Ù. È­¸é °´Ã¼´Â ÀоîµéÀÎ °´Ã¼µé¿¡ ´ëÇØ À̸§º°·Î Á¤·ÄÀ» ½ÃÄÑ È­¸é¿¡ º¸¿©ÁØ´Ù. Deployment Diagram Window95 ¹®¼­°ü¸® Ŭ¶óÀ̾ðÆ®.EXE Windows NT ¹®¼­°ü¸® ¿£Áø.EXE Windows NT Windows95 Solaris ÀÀ¿ë¼­¹ö.EXE Alpha UNIX IBM Mainframe µ¥ÀÌŸº£À̽º¼­¹ö Windows95 ¹®¼­°ü¸® ¾ÖÇø´ ºÐ»ê ȯ°æÀÇ Çϵå¿þ¾î¹× ³×Æ®¿÷À¸·ÎÀÇ Á¤º¸ ½Ã½ºÅÛ ¿¬°á ¸ðµ¨ - À©µµ¿ì 95 : Ŭ¶óÀ̾ðÆ® - À©µµ¿ì NT: ÀÀ¿ë¼­¹ö - À¯´Ð½º ¸Ó½Å: ÀÀ¿ë ¼­¹ö ¹× µ¥ÀÌŸ ¼­¹ö, Åë½Å ¼­¹ö - IBM ¸ÞÀÎÇÁ·¹ÀÓ: µ¥ÀÌŸ ¼­¹ö, Åë½Å ¼­¹ö

11. Diagrams Diagrams graphically depict a view of a part of your model. Different diagrams represent different views of the system that you are developing. A model element will appear on one or more diagrams.

12. UML Diagrams in Software Architecture Activity Diagrams Sequence Diagrams Communication Diagrams State Machine Diagrams Deployment Diagrams Component Diagrams Composite Structure Diagrams Class Diagrams Use-Case Diagrams Model

13. Key Diagrams in UML

14. Process ViewDeployment View Logical View Use-Case View Implementation View End-user Functionality Programmers Software management Performance, scalability, throughput System integrators System topology, delivery, installation, communication System engineering Analysts/Designers Structure Different diagrams of system for different people

15. What is a Use-Case Model? A use-case model: – Is a model of a system’s intended functions and its environment – Serves as a contract between the customer and the developers – Contains the following diagrams: Use case: Shows a set of use cases and actors and their relationships Activity: Shows the flow of events within a use case Sequence: Shows how a use case will be implemented in terms of collaborating objects

16. Use-Case Diagram (Example)

17. Activity Diagram Action A step in the flow of events Decision Flows split based on a guard condition Flow Show the sequence of activities Fork Beginning of concurrent flows Join End of concurrent flow

18. Activity Diagram (Example) Synchronization Bar (Fork) Guard Condition Synchronization Bar (Join) Decision Concurrent Threads Transition Select Course [ add course ] Check Schedule Check Pre-requisites Assign to Course Resolve Conflicts Update Schedule Delete Course [ checks completed ][ checks failed ] [ delete course ] Activity/Action

19. What is a Design Model? A design model: – Describes the realization of use cases in terms of design elements – Describes the design of the application – Contains the following diagrams: Class: Shows UML classes and relationships Component: Shows the structure of elements in the implementation model Communication and Sequence: Show how objects and classes interact State Machine: Shows event-driven behavior

20. Class Diagram (Design Model) Class diagrams show the static structure of the model, in particular, its classes, their internal structure, and their relationships to other classes. Class diagrams do not show temporal information. Class A description of a set of objects Attribute Named property of a class Aggregation Represents a part-whole relationship Operation Class behavior Generalization Shows an inheritance relationship

21. Sequence Diagram used to show how objects interact to perform the behavior of all or part of a use case as part of a use-case realization. Lifeline Shows the life of the object Object/Class Shows the object/class involved in the interaction Messages Show data exchanged between objects Execution Occurrence Shows object executing

22. Sequence Diagram (Example) Activity/Action 1: create schedule( ) 2: get course offerings( ) 3: get course offerings(for Semester) 4: get course offerings( ) 6: display blank schedule( ) :RegisterForCoursesForm:RegistrationControllerSWTSU Catalog : CourseCatalogSystem : Student : Course Catalog 5: display course offerings( ) Select Offerings ref

23. Communication (Collaboration) Diagram provide another way to show how objects interact to perform the behavior of a particular use case or a part of a use case. Where sequence diagrams emphasize the interactions of objects over time, communication diagrams are designed to emphasize the relationships between objects. Object/Class Shows the object/class involved in the interaction Message Shows data exchanged between objects

24. Communication Diagram (Example) : Student : RegisterForCoursesForm : RegistrationController : CourseCatalogSystem 5: display course offerings( ) 6: display blank schedule( ) : Course Catalog 1: create schedule( ) 2: get course offerings( ) 3: get course offerings(forSemester) 4: get course offerings( ) Links Messages

25. Component Diagram Component Modular parts of the system Class Included to show implementation relationships. It shows the runtime structure of the system at the level of software components. Components are the modular parts of the system and are made up of groups of related objects that are hidden behind an external interface.

26. Deployment Diagram Artifact Represents a physical file Node Represents a physical machine Owned Element Relationship Shows another way of showing nested elements Deployment diagrams show the deployment architecture of the system, that is, which of the system’s software artifacts reside on which pieces of hardware.

27. THANK YOU