What is the primary objective of 'Defect Containment' within the software quality engineering lifecycle?
A.To guarantee that a developed software product contains exactly zero dormant defects at shipment.
B.To reduce the chance of passing defects from one phase of the software development lifecycle to another.
C.To completely eliminate the need for subsequent software validation or system-level testing.
D.To increase the budget allocation for cosmetic graphic user interface modifications.
How easily can a software bug be traced by compiler tools during the development process?
A.Compiler tools can instantly and perfectly trace every logic bug to its exact root cause.
B.A bug is rarely traceable by a Compiler to its nearest place.
C.Compilers only trace bugs if they are located in third-party off-the-shelf components.
D.A bug is only traceable if it is recorded as a defect in production by the client.
Why are traditional software defect reduction techniques (such as testing and code inspections) alone insufficient for large and highly complex software systems?
A.Because they can only reduce the number of faults to a low level, leaving remaining faults that may still be triggered under rare conditions.
B.Because they inherently increase the rate of defect injection into downstream development phases.
C.Because they are only compatible with CMMI Maturity Level 1 ad hoc workflows.
D.Because they require open-budget projects and completely eliminate the need for requirements traceability.
In the C code example provided in the course handouts where the requirement is to add two numbers, the statement `ans = value1 - value2;` represents a ________, whereas the incorrect output printed to the screen represents a ________.
💻 c Snippet
ans = value1 - value2; // subtraction instead of addition
A.Bug, Defect
B.Error, Bug
C.Fault, Failure
D.Failure, Fault
Under the ISO-9126 standard, which quality characteristic is defined as a set of attributes related to the capability of software to maintain its level of performance under stated conditions for a stated period of time?
A.Usability
B.Efficiency
C.Reliability
D.Maintainability
What kind of structural model does the ISO-9126 standard establish for defining software quality?
A.A sequential list of programming languages and compiler requirements.
B.A hierarchical framework for quality definition, organized into quality characteristics.
C.An ad-hoc, process-free grading scheme managed exclusively by project heroes.
D.A budget-centered calculation spreadsheet tracking SPI and CPI variables.
How is the 'Reliability' characteristic defined in the ISO-9126 standard, and what information does it convey to stakeholders?
A.It represents the effort needed to make specified architectural modifications and software updates.
B.It defines the relationship between the level of software performance and the amount of server memory used.
C.It refers to the ease of use of any software function especially from the end-user viewpoint.
D.It refers to the capability of software to maintain its level of performance under stated conditions for a stated period of time.
What is the ISO-9126 Quality Framework as described in Module 01 of the course handouts?
A.A quantitative testing tool used to measure cost and schedule variations.
B.An international standard for software evaluation that provides a hierarchical framework for quality definition, organized into quality characteristics.
C.An organization-wide standard governing the selection of programming languages and compilers.
D.A CMMI-defined maturity level appraisal framework used by certified lead auditors.
According to the Software Quality Engineering handouts, what is a software 'Fault' defined as?
A.A human action or mistake committed by a programmer during code development.
B.An incorrect step, process, or data definition in a computer program that acts as a fundamental condition causing failures to occur.
C.The inability of a software system to perform its required functions within specified performance limits.
D.A deviation from customer requirements discovered after the software is shipped to the production site.
Where are software 'Defects' most commonly found or discovered in the software product lifecycle?
A.During the requirement gathering phase before any coding begins.
B.During unit testing and static analysis by the development team.
C.In the software after the software is shipped to the customer at the production site.
D.During design inspections and architecture walkthroughs.
