Please enable JavaScript.

Coggle requires JavaScript to display documents.

Validation, Aluno: Alexandre Nadolni Bonacim - Coggle Diagram

- - - - randomly selected
    - - based on requirements specification
    - - based on internal structure, execute all branches
    - - derived from model
    - - profile of SUT, misses rare events
    - - usually model-based
    - - analyze source code to generate data
    - - fault injection
    - - Function coverage
      - Statement coverage
      - Branch coverage
      - Condition coverage
      - Fault coverage
  - - - Regression testing
      - New-function testing
    - - Why do we perform the test?
      - How to choose the test cases?
      - How much testing is sufficient?
      - What is that we execute?
      - Where do we perform the observation?
      - When is it in the product lifecycle that we perform the test?
- - - - Effective and precise communication
      - Familiar concepts. Precise yet abstract
      - Simple mechanical analysis can lead to detection of inconsistencies
      - Reviews at early-stages are more effective
      - Difficulty to express vague ideas helps to reveal problem domains that need further investigation
    - - Rigid formalism that is cumbersome
    - - Intermediate level of abstraction