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 Manage