Please enable JavaScript.

Coggle requires JavaScript to display documents.

UML 2.0 (Behavioral Diagram (Use case diagram : (What (Be used by 1 actor…

- - - - Definition of functional requirements for the system
    - - Be used by 1 actor or an actor group
      - The smallest function of the application or the operation of a system
      - Behavior diagrams used to describe a set of actions
    - - Actor
      - Use Case
  - - - Detailed description of messages
      - Sequence of time
    - - Identify the sequence of event occurrences of a target group
      - Detailed description of messages
        
        Delete Message
        
        Create Message
        
        Reply or Return Message
        
        Self Message
        
        Synchronous Message
    - - Object or class
      - Lifelines
      - Message
  - - - Describe possible states
      - The transition between states when there are impact events
    - - The object has many states
    - - Initial State
      - Final State
      - State
      - Event or Transition
  - - - show instances, including objects and data values
      - class diagrams show classes, object diagrams display instances of classes
    - - instance specification
      - object
      - slot
      - link
  - - - evident deployment architecture so it will affect the design, development, performance, scalability of the system
    - - deployment specification
      - device
      - deployment artifact
      - deployment target
  - - - Interaction overview diagrams are defined as specialization of activity diagrams and as such they inherit number of graphical elements.
      - Interaction overview diagrams can only have inline interactions or interaction uses instead of actions, and activity diagram actions could not be used.
    - - interaction
      - interaction use
      - duration constraint
      - time constraint
  - - - A communication diagram offers the same information as a sequence diagram
      - a communication diagram emphasizes the messages exchanged between objects in an application.
      - Sequence diagrams can fall short of offering the "big picture.” so we should use communication diagram
    - - Model the logic of a sophisticated procedure, function, or operation.
      - Identify how commands are sent and received between objects or components of a process.
      - Visualize the consequences of specific interactions between various components in a process.
      - Plan and understand the detailed functionality of an existing or future scenario.
  - - - Activity diagram is a diagram that describes the steps taken, actions, decision buttons and branch conditions to control the execution flow of the system.
    - - initial node
      - flow final node
      - activity final node
      - decision node
      - merge node
      - fork node
      - join node
- - - - Structure and relationship between the components that make up the software
    - - class
      - feature
      - constraint
      - interface
      - association
      - dependency
      - association
  - - - Internal Structure Diagram
      - Collaboration Use Diagram
    - - Each element has some defined role in the collaboration.
      - interconnected elements that collaborate at runtime to achieve some purpose
      - shows the internal structure of a class and the collaborations that this structure makes possible.
  - - - show packages and relationships between the packages
    - - package
      - Table
      - Interface
      - package import
      - Object
      - pakage merge
  - - - port
      - class
      - connector
      - component
      - artifact
      - interface
      - component realization
      - usage
    - - show the service consumer - service provider relationship between the two components
      - A component is something required to execute a stereotype function
  - - - lifeline
      - duration constraint
      - timeline
      - timing ruler
    - - timing diagram is a representation of a set of signals in the time domain
      - the digital timing diagram can help find and diagnose digital logic hazards
  - - - show stereotypes as classes with the «stereotype» stereotype, and profiles as packages with the «profile» stereotype
      - indicates what metamodel element a given stereotype is extending.
    - - profile
      - profile application
      - metaclass
      - extensive