Please enable JavaScript.

Coggle requires JavaScript to display documents.

DUM (Diagrams (ERD (Keys (Super key (Candidate key (Primary key)), Primary…

- - - - generalization (inheritance)
        
        customer - genral (parent), returning (child), new( child)
      - Primary - initiates the use of the system - LEFT (customer)
      - Secondary - reactory RIGHT (bank for ex)
    - - Oval shape - within the subject/system , verbs/actions
      - Relationships
        
        Types
        
        Generalization - INHERITANCE - generalized UC/ parent- very general (make payment) - speicalized UCs (from chšecking, from savings) - STRAIGHT LINE POINTING TO GENERAL UC
        
        Extend - HAPPENS SOMETIMES- DOTTED LINE WITH ARROW FROM EXTENDED TOWARDS BASE UC ( When the BASE UC is executed, EXTEND UC caN BE SET OFF, BUT DOESNT HAVE TO BE), if statements, for Verify password--> Display error (if wrong password)
        
        Include - HAPPENS EVERYTIME- DOTTED LINE WITH ARROW FROM BASE TO INCLUDED (when UC isnt directly set off by actor, but another UC) - Ex - Log in --> Verify password) Everytime the Base Uc ( log in) is executed, Included (verify) is set off, BASE UC isnt completed without INCLUDED UC
        
        Associations ( general use of UC by actor)
      - Each UC has to be used by at least one actor
  - - - Flow objects
        
        Event
        
        Start event
        
        End Event
        
        Activity
        
        Atomic
        
        Non-atomic
        
        Gateaway
        
        control the flow of the map
        
        deciding points
        
        single direction
        
        Paralel activities
        
        Synchronisation
      - Connecting objects
        
        Sequence flow
        
        Message Flow
        
        Association
      - Basic elements = Swimlanes
        
        Pool
        
        Lane
      - Artifacts
        
        Data Object
        
        Group
        
        Annotation (provides details )
    - - B2B processes - external
      - Business processes- internal
  - - - Context Diagram - is a special case of a data flow diagram, containing a single process representing the whole system
        
        Terminators
        
        Data received
        
        Data produced
        
        Data stored
        
        System boundry
      - Event List
        
        textual list of stimuli coming from the
        environment that must be responded by the system
    - - shows what kinds of information will be input to and output from the system, where the data will come from and go to, and where the data will be stored
      - does not show information about the timing of processes, or information about whether processes will operate in sequence or in parallel
      - DFD Data Flow Diagram
        
        Processes - models a part of the system that transforms specific inputs to outputs
        
        Data flows - models a way for data transfer from one part of the system to another
        
        Data stores -models a static collection of data that are shared by two or more processes operating in different time
        
        Terminators -represents an external entity communicating with the system
      - Data modelling
  - - - Identifiable - entities can be distinguished by their identity
      - Needed - have significant role in the system
      - Described by attributes shared by all entities of the same type
    - - Primary keys
      - Foreign keys
      - Composite key (2 PK combined)
      - Super key
        
        Candidate key
        
        Primary key
- - - - Internal work
      - External work