C857 Software Quality Assurance, Overview

C857 Software Quality Assurance, Overview
(Answers on top of the questions)


Less costly
Finding and fixing bugs early in the development process rather than finding and fixing
bugs all at once near the end of a project is more or less costly?

[Best Practices, Lesson 1: Process Improvement]
Having clearly defined goals for every milestone
What key best practice bring the development process together in order to meet the
deliverable deadline?

[Best Practices, Lesson 1: Process Improvement]
Process improvement
What can help software development build and retain product and service quality?

[Best Practices, Lesson 1: Process Improvement]
A measurable business result
What can be achieved with a process improvement initiative based on the CMMI?

[Best Practices, Lesson 1: Process Improvement]
More costly
Studies have shown that the defects found and fixed in the requirements phase are
more likely to be what?

[Best Practices, Lesson 1: Process Improvement]
Peer review
Which type of review is considered a walkthrough?

[Best Practices, Lesson 1: Process Improvement]
System validation
Which is a key principle of testing?

[Best Practices, Lesson 1: Process Improvement]
Acceptance testing
Which test type will satisfy the final validation and verification criteria?

[Best Practices, Lesson 1: Process Improvement]
As early as possible

,When is the appropriate time to include people responsible for quality in the
development cycle?

[Best Practices, Lesson 1: Process Improvement]
Giving the team the opportunity to voice their concerns and advocate for their own
priorities
What is the benefit of building a discrete list of defects and ranking them in order of
importance?

[Best Practices, Lesson 2: Bug Management]
A matrix of impacts versus severity
What is a visual definition of how you will prioritize bugs as they are discovered?

[Best Practices, Lesson 2: Bug Management]
A bug base
What is a system for keeping track of every bug logged in a database system called?

[Best Practices, Lesson 2: Bug Management]
A test case management system
What is the best way to document and keep track of test cases?

[Best Practices, Lesson 2: Bug Management]
A bug model
What is based on historical data and planned activities and predicts how many bugs will
be found during the project?

[Best Practices, Lesson 2: Bug Management]
A screenshot
Which element of a bug record will provide the programmer with a visual representation
of the problem?

[Best Practices, Lesson 2: Bug Management]
It will help deliver compliant business-enabling systems
How is a solid IT-QA relationship fundamental to business success?

[Best Practices, Lesson 2: Bug Management]
You are confident that you do not want anything to change in the code
When is a good time to start automation testing?

[Best Practices, Lesson 3: Code Quality]
Optimizing your process and making testing more efficient
What is the intent of test automation?

[Best Practices, Lesson 3: Code Quality]
Program developer

, Who should create automated unit tests?

[Best Practices, Lesson 3: Code Quality]
Eliminating the need for human participation
What could be considered the ultimate goal of automated testing?

[Best Practices, Lesson 3: Code Quality]
A white-box tester
When the testing is focused on how the application behaves at a code level, who should
create the tests?

[Best Practices, Lesson 3: Code Quality]
Code-level tools
What can a developer employ to identify and resolve code quality issues?

[Best Practices, Lesson 3: Code Quality]
Testing
What is the process of executing a program with the intent of finding errors?

[Lesson 2, Testing Fundamentals: The Psychology and Economics of Software Testing]
Discovery of a new error
What makes a test run successful?

[Lesson 2, Testing Fundamentals: The Psychology and Economics of Software Testing]
Finding and removing errors
What does it mean to raise the reliability of a program?

[Lesson 2, Testing Fundamentals: The Psychology and Economics of Software Testing]
A program's intended purpose and user
What must a black-box tester focus on?

[Lesson 2, Testing Fundamentals: The Psychology and Economics of Software Testing]
Usability issues
In addition to finding errors, what else would a black-box tester look for when testing a
program?

[Lesson 2, Testing Fundamentals: The Psychology and Economics of Software Testing]
Black-box tester
Which type of tester is not concerned about the internal behavior and structure of a
program?

[Lesson 2, Testing Fundamentals: The Psychology and Economics of Software Testing]
White-box tester
Which type of tester focuses exclusively on validating the interactions and behaviors
that result in functionality?