WGU C857 Software QA. Exam Questions and answers, 100% Accurate.

WGU C857 Software QA. Exam Questions and answers, 100% Accurate. CMMI (Capability Maturity Model Integration) - -If one were to take a high-level view of the this and its process areas without the interference of the staged or continuous representation that will be discussed later, it would not be hard to classify this as project management, quality management, and engineering all glued together by process management Reviews - -An evaluation of a life-cylce work product(s) or project status to determine if there are any deviations from planned results and to recommend improvement. Peer Reviews - -This kind of review may be thought of as human-based testing as opposed to computer-based testing Anomaly - -A [blank] is any condition that deviates from expectations based on requirements, specifications, design docs, standards, plans, etc. from someone's experiences. Often called defects. Project Manager Reviews - -Weekly project meeting that is called by the project manager. A minimum, the project manager and development staff are in attendance. Representatives from systems engineering, QA, CM, and testing should also be at attendance. Project Manager Reviews - -Items discussed at the weekly project meeting include tracking of the standard issues of technical activities, cost, and schedule performance against the plan. Staffing concerns may also be brought up. Resources planned for and consumed are reviewed. Risks are identified, prioritized, and contingency plans discussed. Necessary commitment changes are acknowledged, documented, and approved. Stakeholder involvement is discussed to ensure that the relevant stakeholders are involved at the time it was deemed necessary and the project is receiving the necessary results from their involvement. Corrective actions maybe necessary and all planning documents are updated as necessary. Milestone Reviews - -This review might signify the end of a phase or a major activity. It might be linked to customer involvement and even contract payments. Milestone Reviews - -These reviews normally address project and other engineering discipline risks. Action items from previous meetings are brought up to determine progress and closure and new action items are recorded, assigned, and reviewed as necessary. All decisions are documented with corresponding actions and resolutions. Buddy Check - -This type of review is examined by the author and one other person. The author walks this person through the life-cycle work product and describes what is intended in each section. That person then offers comments for improvement. Circulation Reviews - -This review takes on attributes of both buddy checks and walkthroughs. This is circulated to each reviewer who reviews it and either attaches comments, questions, recommendations directly on the lief-cycle work product or places them into a separate document. Inspections - -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. Inspections - -The author is not allowed to act as the moderator. Written action on all major defects is mandatory. Inspection Team - -Usually consists of four people. The first person is the moderator. The moderator cannot be the author of the program. The second team member is the programmer. The remaining are usually program designers and test specialist. Moderator duties - -1. Distributing materials for, and scheduling the inspection session. 2. Leading the session. 3. Recording all errors found. 4. Ensuring that the errors are subsequently corrected Inspection Agenda - -Two activities occur: 1. The programmer narrates the logic of the program. Other people raise questions which should determine if errors exist. 2. The program is analyzed with respect to checklists of historically common programming errors The moderator is responsible for ensuring that the discussions proceed along productive lines and that the participants focus their attention on finding errors, not correcting them. Walkthrough - -Normally led by the author. As this progresses errors, suggested changed, and improvement suggestions are noted and documented. Walkthrough - -Usually lasts for one to two hours and consists of 5 people. One of these people plays a role similar to that of the moderator, another is the secretary, and third is the role of a tester Peer Ratings - -A technique for evaluating anonymous programs in terms of their overall quality, maintainability, extensibility, usability, and clarity. Peer ratings - -Each participant is asked to select two of their programs to be reviewed: one of their finest work, one of poorer quality. Then these programs are distributed and reviewed. Then the evaluator rates the program from 1 to 10 from a set of questions. Bug Record - -This should provide a clear and complete information about a bug, including details about the environment and specific steps that the developer can use to reproduce the issue. Bug Record - -Contains several elements: 1. An accurate description of the problem. 2. The browser/os being used 3. steps to take to repeat the problem 4. What was expected vs. what actually happened. 5. Error messages if applicable .Black-box testing - -Your goal is to completely unconcerned about the internal behavior and structure of the program. Concentrate on finding circumstances in which the program does not behave according to its specifications