Module Three Flashcards
What are Static Testing Benefits
1) Early defect detection and correction
2) identify defects not easily found by dynamic testing
3) Prevent design or code defects
4) increase development productivity
5) reduced development time and costs
6) testing time and cost reductions
7) Reduce total cost of quality over software lifetime
8) Improved communication within team
What are static testing defects
1) Requirement defects Design defects code defects deviation from standards incorrect interface specifications security vulnerabilities problem with test coverage insufficient maintainability
What is the review process
Reviews vary from informal to formal
the formality of a review process is related to a variety of factors and the focus of the review depends on its objectives.
What is work product planning
Defining the scope estimating effort and timeframe identifying review characteristics selecting people to participate in review define entry and exit criteria checking entry criteria is met.
What is work product - initiate review
Distributing the work product
explaining the scope, objectives, process roles to participants
answering any participants questions
What is work product review - individual review
Reviewing all or part of work product
noting potential defects, recommendations or questions
What is work product review - issue communication and analysis
Communicating potential defects
analysing potential defects
evaluating/documenting quality characteristics
evaluating the review findings against exit criteria
what is work product review - fixing and reporting
creating defect reports finding defects communicating defects reporting and updating status of defects gathering metrics checking exit criteria are met
What are the roles and responsibilities
Author Management Facilitator or moderator Review leader Reviewers Scribe or recorder
What is the purpose of a review
Uncover defects.
What is the review type - Informal review
Main Purpose: Detecting potentials defects
Also referred to as buddy check, pairing or pair review
Main Characteristics are
- Not based on formal process
- May not involve a review meeting
- may be performed by a colleague of the author
- results may be documented
- caries in usefulness
- use of checklists is optional
- commonly used in agile development
What is the review type - Walkthrough
Main Purpose: Find defects, improve software product, consider alternatives, evaluate conformance to standards and specs
Main characteristics are
- Individual prep before review is optional
review meeting is typically led by author
scribe is mandatory
checklists is optional
- may take the form of scenarios
-potential defect logs and review products may be produced
- may vary in practice from quite informal to very formal
What is the review type - Technical Review
Main purpose: Gaining consensus, detecting potential defects
Main characteristics are
- Reviewers should be technical peers of the author
-individual prep before the review meeting is required
-review meeting is optional ideally led by trained facilitator
- scribe is mandatory ideally not the author
- checkslists optional
-potential defect logs and review products may be produced
What is the review type - Inspection
Main Purpose: Detecting potential defects, evaluating quality and building confidence, preventing defects through author learning and root cause analysis
Main Characteristics:
- Follows a defined process with formal documented outputs
-uses clearly defined roles and may also include a reader
-Individual prep before is required
-reviewers are peers of the author
-specified entry and exit criteria are used
-scribe is mandatory
-led by trained facilitator not the author
-author cannot act as the review leader, reader or scribe
What is the Ad Hoc Review Technique
- Reviewers provided with little guidance on w to review
- Typically read work product sequentially raising issue as found
- commonly sued technique needing little preparation
- highly dependent on skills of reviewer
