Please enable JavaScript.

Coggle requires JavaScript to display documents.

UML Diagram (Structure Diagram (Class Diagram (Elements (class, interface,…

- - - - structure of the designed system at the level of classes and interfaces
      - features, constraints and relationships
    - - domain model diagram
      - diagram of implementation classes
    - - class
      - interface
      - feature
      - constraint
      - association
      - generalization
      - dependency
  - - - instance specification
      - object
      - slot
      - link
    - - UML 2.5 standard hierachy of diagrams (see UML 2.5 diagrams overview), shows class diagrams and object diagrams as completely unrelated
      - Some other authoritative UML sources state that component diagrams are deployment diagrams containing only instance specifications are also special kinds of object diagrams
    - - instance specifications of classes and interfaces (objects)
      - slots with value specifications
      - links (instances of association)
  - - - packages
      - relationships between packages
    - - package
      - packageable element
      - dependency
      - element import
      - package import
      - package merge
  - - - internal structure of classifier - internal structure diagram
      - classifier interactions with environment through ports
      - a behavior of collaboration - collaborations use diagram
    - - class
      - part
      - port
      - connector
      - usage
      - collaboration
  - - - components, provided and required interfaces
      - ports
      - relationships between components
    - - Component - Based Development (CBD) to describe systems with Service - Oriented Architecture (SOA)
    - - component
      - interface
      - provided interface
      - required interface
      - class
      - port
      - connector
      - artifact
      - usage
      - component realization
  - - - Architecture of the system as deployment (distribution) of software artifacts to deployment targets
    - - deployment
      - artifact
      - deployment target
      - node
      - device
      - execution environment
      - communication path
      - deployment specification
    - - Components were directly deployed to nodes in UML 1.x deployment diagrams
      - In UML 2.x artifacts are deployed to nodes, and artifacts could manifest (implement) components. Components are deployed to nodes indirectly through artifacts.
  - - - tagged values
      - constraints
      - lightweight extension mechanism to the UML by defining custom stereotypes
    - - profile
      - metaclass
      - stereotype
      - extension
      - reference
      - profile application
- - - - a set of use cases that system can perform in collaboration to provide some observable and valuable results
    - - Use Case
      - Actor
      - Subject
      - Extend
      - Include
      - Association
  - - - Sequence and conditions for coordinating lower-level behaviors
    - - activity
      - partition
      - action
      - object
      - control
      - activity edge
  - - - Use to describe
        
        An interaction by focusing on the sequence of message that are exchanged
      - Elements
        
        lifeline
        
        execution specification
        
        message
        
        combined fragment
        
        interaction use
        
        state invariant
        
        destruction occurrence
    - - Use to show
        
        the interaction between lifelines where the architecture of the internal and how this corresponds with the message passing is central
      - Elements
        
        lifeline
        
        message
    - - Use to
        
        focus on conditions changing within and among lifelines along a linear time axis
      - Elements
        
        lifeline
        
        state or condition timeline
        
        destruction event
        
        duration constraint
        
        time constraint
    - - Use to
        
        focus on the overview of the flow of control where the nodes are interactions or interaction uses
      - Elements
        
        initial node
        
        flow final node
        
        activity final node
        
        decision node
        
        merge node
        
        fork node
        
        join node
        
        interaction
        
        interaction use
        
        duration constraint
        
        time constraint
      - Note
        
        The Lifelines and the Message do not appear at this overview level
        
        That can only have inline interactions or interaction uses instead of invocation actions
  - - - Behavioral State Machine
        
        Use to show
        
        discrete behavior of a part of designed system through finite state transitions
        
        Elements
        
        behavioral state
        
        behavioral transition
        
        pseudostate
      - Protocol State Machine
        
        Use to express
        
        the usage protocol of part of a system
        
        Elements
        
        protocol transition
        
        protocol state
        
        pseudostate