Please enable JavaScript.

Coggle requires JavaScript to display documents.

PB007 - Coggle Diagram

- - - - use case d
    - - class d
    - - sequnce d
    - - activity d, state d
  - - - timing
      - security
      - reliabilty constraints
- - - - not clear outcome
      - keep interest of customers
      - difficult to collaborate
      - losing vision
      - Contracts
      - documentation
      - priorities = multiple stakeholders
      - large systems
      - simplicity = extra work
    - - SCRUM
      - User story
      - stand-up
      - Backlog
        
        product backog
        
        tasks to be done
        
        sprint backlog
        
        what will be done in the next sprint from product backlog
    - - iterative design process
      - effective communication and stakeholder engagement
      - aiming for quality and reliable software
      - short development cycle allowing regular delivery of software
      - Kanban
      - Scrum
        
        ceremonies
        
        sprint
        
        planning
        
        daily scrum
        
        sprint review
        
        sprint retrospective
      - Extreme programming
        
        iterative, frequent small releases
        
        pair programming
        
        TDD
      - Feauture drivind development
        
        model - feature-lists-plan-design-build by feature
        
        long-term complex projects
      - TDD
  - - - Objective setting
      - Risk assesment and reduction
      - Development and validation
      - planning
- - - - Process v.
      - Development vies
      - Logical view
      - Physical view
      - Use cases and scenarios view
  - - - postman
      - no calling waterfall
      - without logic
      - multiple ways to interact
      - unknown future
      - presentation in different wazs
      - complexe code
    - - supports icremental development
      - requirements falling down
      - isolated - teams
      - replacement of entire layers
      - separation between layers is difficult
      - bad performance
    - - big data shared
      - single.point of failure
      - antipattern
    - - distribution of data
      - stand-alone service providing servers
    - - transformations to output
      - batch, transaction based
- - - - Prevent
      - Detect
      - Repair
      - keep track
      - define quality issues
  - - - validation testing
      - defect testing
  - - - charasteric error checking
      - uder-definied error ch.
      - assertion ch.
      - weak typing, security checking
  - - - unit
        
        object class testing
      - component
      - system/integration
      - TDD
        
        Code coverage
        
        regression testing
        
        simplified debugging
        
        system documnetation
      - regression t.
    - - guideline-based
      - partition
    - - misuse
      - misuderstanding
      - timing errors
  - - - stress t
      - profile of use
    - - simulations
      - what system should do
    - - riger team
      - tool-based
      - experience-based
- - - - iterative approach
      - incremental delivery
- - - - in small = analysis
      - in large = design
      - advantages
        
        planning, communication, analysis, documentation, reuse
    - - System context
      - Interaction model
  - - - Structured
        
        Hierarchical graphical texhniques
        
        structuring to smaller parts
        
        Notations
        
        Context diagram
        
        DFD
        
        ERD
        
        STD
      - Objected-oriented
        
        interacting objects
        
        object = class + state + behaviour
        
        Various models
        
        all objects have
        
        identity
        
        state
        
        behaviour
- - - - Stakeholders
        
        end-user
        
        managers
        
        maintenance engineers
        
        somain experts, etc.
      - WHAT system should do?
      - Techniques
        
        Questionnaires
        
        Interviews
        
        Workshops
        
        Ethnography
    - - MoSCoW
      - RUP Attributes
        
        Status, Benefit, Effort, Risk, Stability, Terget Release
    - - Natural language
      - Structured language
      - Graphical notation
      - Mathematical functions
    - - Checking criterias
      - Validation
      - Techniques
        
        Requirements reviews
        
        Prototyping
        
        A/B testing
  - - - Product R.
      - Organisational R.
      - External R.
- - - - Fault avoidance
      - Fault detection
        
        monitoring and event processing
        
        Acceptance test
        
        ping/echo
        
        Heartbeat
      - Fault tolerance
        
        redundancy
        
        diversity
        
        can continue after failure
        
        tactics
        
        exception handling
        
        checkpoint/rollback
        
        Recovery capabilities
        
        active redundancy
        
        passive redundancy
        
        voting
        
        N-version programming
        
        Protection systems
  - - - Platform-level
      - Application-level
      - Record-level
    - - security policy
      - single-point of failure
      - Fail securely
      - balance security/usability
      - log user actions
      - redundancy and diversity
      - accesses
      - recoverability
      - deployment
      - validate everything
    - - Resistance
      - Recognition
      - Recovery
    - - Performance tactics
        
        Concurrency
        
        REsources
        
        increase resources
      - Modifiability tactics
        
        Runtime registration
        
        Configuration files
        
        Polymorphism
        
        Component replacement
        
        adherence to protocols
        
        ripple effect
        
        hide infromation
      - Usability tactics
        
        separate the UI
        
        maintain a model of the taks
        
        maintain a model of the user
        
        maintain a model of the system
- - - - Volume
      - Variety
      - Variability
      - Velocity
      - Veracity
    - - organised collection of data
      - SQL
        
        analytical
        
        relational
        
        2D tables
        
        PostgreSQL, MySQL
      - DBMS
      - NoSQL
        
        key-value
        
        dictionary, hash table
        
        Shopping cart. catching, multi-player games
        
        graph
        
        nodes & edges
        
        social networks, fraud detection, recommendation engines
        
        Column Based
        
        IoT, Security analytics, stock market, bioinformatics
        
        enormous, structured, volatile data
        
        not the same columns
        
        Document
        
        XML, JSON, YAML
        
        documents differs in structure
        
        User profiles, real-time big data, content management
    - - caption
      - maintenance
      - usage
      - publication
      - archiving
      - purging/destruction
  - - - Entity
        
        identifiable
        
        needed
        
        described by attributes
- - - - release
      - Deployment
        
        local
        
        Development
        
        Stagigng
        
        production
    - - shared repository
    - - Phase-out
      - Evolution
      - servicing
- - - - templates
      - abstract enough to reuse
      - Observer pattern
    - - Single responsibility
        
        one reason to change
      - Open/Closed
        
        open for extension, closed for modification
      - Liskov substituion
        
        subtype
      - Interface segregation
      - Dependency inversion
        
        decoupling
    - - for performance
        
        Reduce resources for individual algorithms
        
        Reduce number of processed computations
        
        control use of resources
    - - observer
      - facade
      - adapter
      - flyweigh
      - singleton
    - - limit visibility of information
      - check all inputs
      - Handler for exceptions
      - minimalize error-prone constructs
      - Restart capabilities
      - array bounds
      - timeouts - calling external components
      - name constatans properly