Please enable JavaScript.

Coggle requires JavaScript to display documents.

4 + 1 View Model (Process View (Diagram (Communication Diagram (Define:…

- - - - Purpose: depicts interaction between objects in a sequential order
      - Component and relationship
    - - Define: extension of object diagram that shows the objects along with the messages that travel from one to another
      - Purpose: shows the messages the objects send each other.
      - Component and relationships
    - - Defined: flowchart to represent the flow from one activity to another activity
      - Purpose: described as an operation of the system
      - Component and relationship
    - - Purpose: Give an abstract description of the behavior of a system
      - Define: Type of diagram used in computer science and related fields to describe the behavior of systems
      - Components:
    - - Purpose: provide a high level of abstraction an interaction model
      - Component and relationship
    - - Purpose: show interactions when a primary purpose of the diagram is to reason about time
      - Component and relationship
- - - - Purpose: shows the execution architecture of a system, including nodes such as hardware or software execution environments, and the middleware connecting them
      - Using in: visualize the physical hardware and software of a system
      - Component and relationship
        
        Package
        
        Use to group elements, and to provide a namespace for the grouped elements.
        
        Object
        
        Use to represent instances of a class or of classes.
        
        Component
        
        Use to defines its behavior in terms of provided and required interfaces.
        
        Interface
        
        Use to define sets of operations that other model elements, such as classes, or components must implement.
        
        Dataflow
        
        Use to explains how data is processed and transferred in a system.
        
        Note
        
        Use to contains comments or textual information.
        
        Constraint
        
        Use to refine the semantics of a UML model element.
- - - - subsystem component: structured classifier from Composite structure diagram
      - interfaces
        
        required interfaces: designed on-the-fly
        
        provided interfaces: realized by the component itself
      - port: used to connect subcomponent
      - connector: inside subcomponent
  - - - package
      - packagable element
    - - dependency
      - element import
      - package import
      - package merge
  - - - Data layer
      - Business layer
      - Presentation layer
- - - - name
      - members
        
        visibility
        
        public
        
        private
        
        protected
        
        package
        
        scope
        
        classifier member: static
        
        instance member: individual
        
        member types:
        
        fields: properties/attributes
        
        methods: operations
    - - dependency
      - association
      - aggregation
      - composition
    - - Domain Model Diagram
        
        Describe the relationships of classes and interfaces with only fields
        
        components and relationships: classes, interfaces, associations, usage, realization, multiplicity
      - Diagram of implementation classes
        
        Describe the relationships of classes and interfaces with only controls and methods
        
        components and relationships: classes, interfaces, associations, usage, realization
      - Object Diagram
        
        Describe the relationships of instances
        
        components and relationships: instance specifications, value specifications, slots, and links
  - - - Internal Structure Diagram
        
        Decompose internal structure of classifier into properties, parts and relationships
        
        Components
        
        Internal structure
        
        Part box
        
        Role: the abstract superclass of specified concrete class, could be reference
        
        Part: instance name
        
        Could be nested
        
        Multiplicity: of role or part
        
        Connector: connect part box by association
        
        External interfaces
        
        Connect via port
      - Collaboration Use Diagram: Describe only the relevant aspects of the cooperation of a set of instances
- - - - association: use on linkable or combinable instances
      - generalization: directed from a more general to a more specific classifier
      - multiplixity
      - extend: supplementary
      - include: simplify large use case or extract common parts of use cases
    - - Business use case diagram
        
        Business actor
        
        Business use case
      - System use case diagram
        
        actors
        
        subjects
        
        use cases
  - - - Role: type of user/who/persona
      - Goal: capability/desire/what
      - Reason: benefit/why
    - - Story: or task, can be subdivided
      - Epic: large body of work broken down into stories
      - Initiative: collection of epics driving toward a common goal
      - Theme: large focus areas spanning the organization