Please enable JavaScript.

Coggle requires JavaScript to display documents.

Static techniques - Coggle Diagram

- - - - focus on technical content
      - defects found by experts (architects, chief designers, key users)
      - assess, establish consistency, ensure tech concepts are used correctly, inform participants of the tech content
    - - is led by the authors, guiding the participants through the document to archive a common understanding and to gather feedback
    - - not documented (no record)
      - start right away to discussion (no log phase)
      - review a document or code
      - a two-person team or more
  - - - take care of any review training requested
      - decides on the execution of reviews
  - - - ensure the information was record or collected is correct and stored for future analysis
      - ensure that the author has taken action on all known defects
    - - author indicates where changes are made
      - author will improve the document under review step by step (not every defects)
    - - Focus on logging defects
      - consists of
        
        decision phase
        
        a decision on the document by all participants based on formal exit criteria (e.g. the average number of critical/major defects found per page)
        
        complies with the exit criteria
        
        leave the review process
        
        follow-up
        
        exceeds a certain level
        
        review again
        
        need to be reworked
        
        discussion phase
        
        logging phase
        
        Spelling defects are noted into document and given to author at the end of meeting
        
        Severity classes (propose by whom indentify the defect)
        
        Minor
        
        Major
        
        Critical
        
        Log as many defects as possible within a certain timeframe
    - - Record issues using a logging form
      - work individually on document using related documents, procedures, rules and checklists
    - - short introduction of above content
    - - assign roles tp focus on
        
        usage (e.g. for testability or maintainability)
        
        related documents (e.g. interfaces between software functions)
        
        compliance to standards (e.g. internal consistency, naming conventions, templates)
        
        higer-level documents (e.g. does the design comply to reqs)
      - decide which part of the document to review
      - the author requests for review to moderator
        
        The moderator schedule for the review
        
        (e.g. in inspections) performs an entry check, definds exit criteria
- - - - performed on requirements, design or code without executing software
      - ideally performed before the other types of formal review
      - As reviews, static analysis finds defects rather than failures
      - unrelated to dynamic properties such as test coverage
  - - - Ex: naming conventions, indentation, spacing,...
      - Without using tool, very hard to check manually
    - - Ex: comment frequency, depth of nesting, cyclomatic number, number of lines of code
      - Code metrics show we know when code is becoming bigger, how difficulty to understand and maintain code
    - - control flow structure
      - data flow structure
      - data structure