Overview of UML Diagrams

Overview of UML Diagrams

• 1.
  UML : Unified ModellingLanguage
• 2.
  • UML standsfor “Unified Modeling Language” • It is a industry-standard graphical language for specifying, visualizing, constructing, and documenting the artifacts of software systems • The UML uses mostly graphical notations to express the OO analysis and design of software projects. • Simplifies the complex process of software design What is UML ?
• 3.
  UMLModelling Structural Behavioral Architectural - Static featuresof a system. - Dynamic Feature of a system. - Blue print of the entire system.
• 4.
  Structural Classes diagrams Objects diagrams Deploymentdiagrams Package diagrams Composite structure diagram Component diagram
• 5.
  Behavioral Activity diagrams Interaction diagrams Usecase diagrams
• 6.
  Structural Behavioral Architectural
• 7.
  • Use CaseDiagram • Class Diagram • Sequence Diagram • Collaboration Diagram • State Diagram Types of UML Diagram
• 8.
  • Used fordescribing a set of user scenarios • Mainly used for capturing user requirements • Work like a contract between end user and software developers 1. Use Case Diagram
• 9.
  Library System Borrow Order Title FineRemittance Client Employee Supervisor Boundary Actor Use Case An Example of Use Case Diagram
• 10.
  • Provide aconceptual model of the system in terms of entities and their relationships • Used for requirement capture, end-user interaction. • Detailed class diagrams are used for developers. Class Diagram
• 11.
  • Each classis represented by a rectangle subdivided into three compartments • Name • Attributes • Operations • Modifiers are used to indicate visibility of attributes and operations. • ‘+’ is used to denote Public visibility (everyone) • ‘#’ is used to denote Protected visibility (friends and derived) • ‘-’ is used to denote Private visibility (no one) • By default, attributes are hidden and operations are visible. Class Representation
• 12.
  An example ofClass ` Account_Name - Customer_Name - Balance +addFunds( ) +withDraw( ) +transfer( ) Name Attributes Operations
• 13.
  1. The purposesof interaction diagrams are to - visualize the interactive behavior of the system. 2. Visualizing interaction is a difficult task. The solution is to use different types of models to capture the different aspects of the interaction. a. Sequence Diagram. b. Collaboration Diagram Interaction Diagram
• 14.
  Interaction Diagram :Sequence Diagram A Sequence diagram is an interaction diagram that shows how processes operate with one another and in what order.
• 15.
  Interaction Diagrams: Collaborationdiagrams 1. Shows the relationship between objects and the order of messages passed between them. 2. The objects are listed as rectangles and arrows indicate the messages being passed. 3. The numbers next to the messages are called sequence numbers. 4. convey the same information as sequence diagrams, but focus on object roles instead of the time sequence.
• 16.
  State Diagrams (BillingExample) State Diagrams show the sequences of states an object goes through during its life cycle in response to stimuli, together with its responses and actions; an abstraction of all possible behaviors. Unpaid Start End Paid Invoice created paying Invoice destroying