WGU - C857 - Software Quality Assurance (definitions) Latest 2022 100% Pass

Document Content and Description Below

WGU - C857 - Software Quality Assurance (definitions) Latest 2022 100% Pass CMMI -Answer- Capability Maturity Model Integration Capability Maturity Model Integration (CMMI) -Answer- a proven set... of global best practices that drives business performance through building and benchmarking key capabilities - project management, quality management, and engineering all glued together by process management review -Answer- an evaluation of a life-cycle work product or project status to determine if there are any deviations from planned results and to recommend improvement peer reviews -Answer- human-based testing rather than computer-based testing anomaly, defect -Answer- any condition that deviates from expectations based on requirements, specification, design documents, standards, plans, and so on, or from someone's experiences Project Manager Review -Answer- normally, a weekly project with the development staff called by the Project manager Milestone Review -Answer- Represent meaningful points in the project's schedule and are documented in the project management plan, tracked, and reviewed. Buddy Check -Answer- an informal verification technique in which the life-cycle work product is examined by the author and one other person Circulation Reviews -Answer- A review that takes on attributes of both a buddy check and a walkthrough; they can be informal or formal; the life-cycle product is passed around to each reviewer who review it and either attaches comments, questions, and recommendations directly on the life-cycle work product or places them into a separate document. Inspections -Answer- a formal verification technique in which life-cycle work products are examined in detail by a group of peers for the explicit purpose of detecting and identifying defects Inspection Team -Answer- Usually consists of four people: moderator, programmer, designer, test specialist Walkthrough -Answer- a less formal verification technique in which life-cycle work products are examined by a group of peers for the purpose of finding defects, omission, and contradictions; typically led by the author of the work Peer Ratings -Answer- a technique of evaluating anonymous programs in terms of their overall quality, maintainability, extensibility, usability, and clarity; the purpose of this techniques to provide programmer self-evaluation Bug Record -Answer- Provide clear and complete information about a bug, including details about the environment and specific steps that the developer can use to reproduce the issue Black-Box Testing -Answer- Testing without concern about the internal behavior and structure of the program, instead concentrating on finding circumstances in which the program does not behave according to its specifications Equivalence Partitioning (Equivalence Classes) -Answer- a testing technique in which a set of test conditions is divided into groups or sets that can be considered the same Boundary Value Analysis -Answer- A black box test design technique in which test cases are designed based on boundary values, those situations directly on, above, and beneath the edges of input and output equivalence classes. Cause-Effect Graphing -Answer- a black-box testing technique that aids in selecting, in a systematic way, a high-yield set of test cases and that has the benefit of pointing out incompleteness and ambiguities in the specification. Symbol for Identity function on Cause-Effect Graph -Answer- single path Symbol for NOT function on Cause-Effect Graph -Answer- zigzag path Symbol for OR function on Cause-Effect Graph -Answer- "V" Symbol for AND function on Cause-Effect Graph -Answer- inverted "V" Identity function -Answer- if (a = 1) { b = 1 } else { b = 0 } Not function -Answer- if (a = 1) { b = 0 } else { b = 1 } Or function -Answer- if (a or b or c = 1) { d = 1 } else { d = 0 } And function -Answer- if ( a and b = 1 ) { c = 1 } else { c = 0 } Error Guessing (process) -Answer- Enumerate a list of possible errors or error-prone situations and then write test cases based on the list Logic Coverage -Answer- Tests that exercise all decision point outcomes at least once, and ensure that all statements or entry points are executed at least once. Equivalence Partitioning -Answer- Defines condition or error classes to help reduce the number of finite tests Boundary value analysis -Answer- Tests each edge condition of an equivalence class (output and input) Cause-effect graphing -Answer- Produces Boolean graphical representations of potential test case results to aid in selecting efficient and complete test cases [Show More]

Last updated: 1 year ago

Preview 1 out of 8 pages