Please enable JavaScript.

Coggle requires JavaScript to display documents.

Chapter 5: UML - Coggle Diagram

- - - - Call on the system to deliver service
    - - The goal use case try to satisfy
    - - Other actors system communicates
        
        While
        
        Carry out the use case
  - - - Relationship between actors & use cases
      - Actor involved in interaction described by use case
      - Arrow head
        
        Indicate direction of invocation, primary actor
        
        Indicate control flow
    - - Directed relationship between 2 use cases
    - - Behavior of extension use case may be inserted in
        extended use case under some conditions
    - - Common behaviors
      - Requirements
      - Constraints
      - Assumptions
- - - - Run vertically down the page
    - - Show when the participant is active in interaction
      - Optional
    - - Look at behavior of several objects in single use case
      - Good at showing collaborations among objects
      - Single object across many use cases
      - Use a state diagram
      - Behavior across many use cases or threads
        
        Consider activity diagram
- - - - Thrived in 1908s and 1990s
    - - System development life cycle (SDLC)
      - Structured systems analysis and design (SSAD)
      - Waterfall
      - DFD and ERD
    - - Based on
        
        Abstraction
        
        Encapsulation
        
        Modularity
        
        Hierarchy
      - Combination of object in systems
  - - - Essence of sketching is selectivity
      - Forward sketching
        
        Rough out some issues in code
        
        Discussing them with group of people in your team
      - Aim is to help communicate ideas and alternatives about what to do
      - Sessions can be very short
    - - Completeness
      - Blueprints are developed by designer
        
        Build detailed design for a programmer to code up
      - Should be sufficiently complete in that design decisions are laid out
      - Programmer able to follow as pretty straightforward activity
      - Designer is more senior developer
        
        Designs for a team of programmers
    - - Developers draw UML diagrams
        
        Compiled directly to executable code
        
        Become source code
      - Demands particularly sophisticated tooling
      - Model behavioral logic
        
        Interaction diagrams
        
        State diagrams
        
        Activity diagrams
  - - - Structural view
        
        Class diagram
        
        Object diagram
        
        Composite Structure diagram
      - Implementation view
        
        Component diagram
        
        Composite Structure diagram
      - Behavioral view
        
        Sequence diagram
        
        Communication diagram
        
        State diagram
        
        Activity diagram
        
        Interaction overview diagram
        
        Timing diagram
      - Environment view
        
        Deployment diagram
      - Use Case view
        
        Use Case diagram
- - - - Classes
      - Their attributes
      - Operations/methods
      - Relationships among objects
  - - - Encapsulates attributes and operations
        
        Attributes have types
        
        Operations have signature
    - - The name of the class appears in first partrition
    - - Shown in the second partrition
      - Attribute type show after colon
      - Attribute map onto member variables in code
    - - Shown in third partrition
        
        Services the class provides
      - Return type of method shown after colon the end of method signature
      - Return type of method params shown after colon followed by params name
    - - Conceptual
        
        Represents the concept in the domain
      - Specification
        
        Focus on the interfaces of Abstract Data Type in software
      - Implementation
        
        Describe how classes will implement their interfaces
    - - Inheritance
        
        a taxonomic relationship between a more general classifier and a more specific classifier
        
        Specific classifier inherits features of general classifier
        
        Represent an 'is-a' relationship
      - Association
        
        structural link between two classes
      - Aggregation
        
        Special type of association
        
        "Part of" relationship
      - Composition
        
        Special type of aggregation
        
        Parts are destroyed when whole is destroyed
        
        Part cannot stand by itself
      - Dependency
        
        An object use an object of another class
        
        Special type of association
        
        One changes the other will follow (not entities around)
      - Realization
        
        Relationship between the blueprint class
        
        Relationship between the interface and the implementing class