C857: Software Quality Assurance, Top
Exam Questions & Answers, 100%
Accurate. VERIFIED.
Why should we conduct peer reviews? - ✔✔-- detect defects
- remove defects
- determine product progress
- identify potential improvements
- uniform and predictable quality of work
- cross-training
- reduce costs
- reduce development time
- reduce testing cost and time
Reasons for management reviews? - ✔✔-- track progress
- identify inconsistencies
- monitor risks
- evaluate effectiveness of management
- corrective action
- project control
- change project scope
Principal Processes for achieving objective: Progress Check or Evaluation - ✔✔-- Management/Technical
Review
Principal Processes for achieving objective: Verification - ✔✔-- inspection/walkthrough test
,Principal Processes for achieving objective: Validation - ✔✔-- test
- simulation
- emulation
Principal Processes for achieving objective: Compliance Confirmation - ✔✔-- audit
What are the three types of manager reviews? - ✔✔-- project manager reviews
- milestone reviews
- senior management oversight reviews
Peer Review Types - ✔✔-- buddy checks
- circulation reviews
- inspections
- walkthroughs
- structured walkthroughs
Buddy Check - ✔✔-- INFORMAL verification technique
- "life-cycle work" product is examined by author and one other person
- the author walks the "buddy" through the life-cycle work and describes what is intended in each
section
- most importantly the buddy decides on the "fit" to the described intent by the author
- objectives:
-- improve work
-- consider alternative approaches
-- exchange techniques
-- point out problems
-- give a different perspective
-- mentoring
, Circulation Review - ✔✔-- can be formal OR informal
- useful when reviewers are geographically separated
- useful when looking for a large cross section of reviewers
- time is not a constraint
- objectives:
-- improve work
-- consider alternatives
-- point out problems
-- gain consensus from large set of reviewers
-- gain input from valuable contributors who cannot be present for a face-to-face review
Technical Review - ✔✔-- a FORMAL team evaluation
- identifies any discrepancies from specifications and standards
- determines suitability of use
- provides recommendations
- objective is to make sure life-cycle work conforms to specifications
- confirms that work is being done according to plan
Inspection - ✔✔-- Formal verification technique
- work is examined by a group of peers for the explicit purpose of finding defects
- led by a moderator; the author is NOT allowed to be the moderator
- written action on ALL defects is mandatory
- defect data is used to improve the product, the process, and the effectiveness of the inspection
process
- managers are NOT permitted to attend
- collects engineering data
- does NOT examine alternatives
- verifies work satisfies both specs and preceding work products
- verifies work conforms to standards
Exam Questions & Answers, 100%
Accurate. VERIFIED.
Why should we conduct peer reviews? - ✔✔-- detect defects
- remove defects
- determine product progress
- identify potential improvements
- uniform and predictable quality of work
- cross-training
- reduce costs
- reduce development time
- reduce testing cost and time
Reasons for management reviews? - ✔✔-- track progress
- identify inconsistencies
- monitor risks
- evaluate effectiveness of management
- corrective action
- project control
- change project scope
Principal Processes for achieving objective: Progress Check or Evaluation - ✔✔-- Management/Technical
Review
Principal Processes for achieving objective: Verification - ✔✔-- inspection/walkthrough test
,Principal Processes for achieving objective: Validation - ✔✔-- test
- simulation
- emulation
Principal Processes for achieving objective: Compliance Confirmation - ✔✔-- audit
What are the three types of manager reviews? - ✔✔-- project manager reviews
- milestone reviews
- senior management oversight reviews
Peer Review Types - ✔✔-- buddy checks
- circulation reviews
- inspections
- walkthroughs
- structured walkthroughs
Buddy Check - ✔✔-- INFORMAL verification technique
- "life-cycle work" product is examined by author and one other person
- the author walks the "buddy" through the life-cycle work and describes what is intended in each
section
- most importantly the buddy decides on the "fit" to the described intent by the author
- objectives:
-- improve work
-- consider alternative approaches
-- exchange techniques
-- point out problems
-- give a different perspective
-- mentoring
, Circulation Review - ✔✔-- can be formal OR informal
- useful when reviewers are geographically separated
- useful when looking for a large cross section of reviewers
- time is not a constraint
- objectives:
-- improve work
-- consider alternatives
-- point out problems
-- gain consensus from large set of reviewers
-- gain input from valuable contributors who cannot be present for a face-to-face review
Technical Review - ✔✔-- a FORMAL team evaluation
- identifies any discrepancies from specifications and standards
- determines suitability of use
- provides recommendations
- objective is to make sure life-cycle work conforms to specifications
- confirms that work is being done according to plan
Inspection - ✔✔-- Formal verification technique
- work is examined by a group of peers for the explicit purpose of finding defects
- led by a moderator; the author is NOT allowed to be the moderator
- written action on ALL defects is mandatory
- defect data is used to improve the product, the process, and the effectiveness of the inspection
process
- managers are NOT permitted to attend
- collects engineering data
- does NOT examine alternatives
- verifies work satisfies both specs and preceding work products
- verifies work conforms to standards
