SAD 6

• Unified Modeling Language (UML) is a standardized modeling language used in software engineering to visually represent systems
• UML


  Offers common language for developers, analysts, and stakeholders to communicate and understand system architecture, design, and behavior
• UML diagrams offer visual representations of complex systems
• Visualizations aid in identifying system components, relationships, and interactions more intuitively
• Modelling with UML


  • Requirement Analysis
  • Conceptual Modeling
  • Use Case Diagrams
  • Class Diagrams
  • Sequence Diagrams
  • Activity Diagrams
  • State Machine Diagrams
• Use case diagrams


  Provide a visual representation of the interactions between actors and the system to achieve specific goals
• Actors


  External entities (human users, systems, or devices) interacting with the system to accomplish tasks
• Use cases


  Describe specific functionalities or behaviors provided by the system
• Components of Use Case Diagrams

  • Actors
  • Use Cases
  • Associations
  • Inclusions
  • Extend
  • Generalizations
  • System Boundary
• Classes


  • Encapsulate attributes and behaviors
  • Serve as templates for creating objects
  • Represent real-world entities, concepts, or modules within the system
• Attributes


  Properties or data fields associated with a class
• Operations


  Behaviors or methods that the class can perform
• Association


  Bi-directional relationship between classes, indicating that instances of one class are connected to instances of another class
• Aggregation


  Whole-part relationship between classes, where one class is composed of or contains instances of another class
• Composition


  Stronger form of aggregation, indicating that the composed class is a part of the composite class and has a lifecycle dependent on it
• Multiplicity


  Specifies the number of instances of one class related to the other class in an association
• Sequence diagrams


  Illustrate the interactions between objects within a system over time
• Actors


  Entities outside of the system that interact with the system
• Objects


  Instances of classes within the system
• Lifeline


  Represents the existence of an object over a period of time within the sequence diagram
• Activation Bar (Execution Occurrence)

  Represents the period during which an object is actively processing or executing a message
• Messages


  Communications between objects, depicted as arrows between lifelines
• Statechart diagrams


  Depict the various states that an object or system can be in and the transitions between these states triggered by events
• States


  Conditions or situations during the lifecycle of an object
• Transitions


  Movement from one state to another triggered by events
• Events


  Occurrences that trigger state transitions
• Activity diagrams


  Represent workflows or processes within a system
• Activities


  Specific tasks or actions that need to be performed within the system
• Initial (Start) and Final Node

  Start represents the starting point, Final represents the ending point of the activity diagram
• Activity Nodes


  Represent specific tasks or actions that need to be performed within the system
• Control Flow


  Represents the flow of control or the sequence in which activities are performed
• Decisions


  Represent conditional branches in the workflow
• Merge Node


  Represents a point where multiple alternative control flows converge back into a single flow
• Forks and Joins


  Forks represent parallel paths in the workflow, Joins merge multiple parallel paths back into a single flow