Based on Module 01, Section N of the course handouts, where and when are 'Defects' most commonly found in the software lifecycle?
A.Inside the developer's local scratch workspace prior to SCM code integration.
B.In the software after the software is shipped to the customer at the production site.
C.During initial whiteboard requirement elicitation sessions with the client.
D.In the compiler's syntax warnings log before unit testing begins.
According to Module 01, Section B of the CS611 course handouts, how are stakeholders for software development categorized under Roles and Responsibilities, and why do they have different expectations?
A.They are divided into Consumers (further categorized into Users and Customers) and Producers, having different expectations based on their specific roles and operational interactions with the software.
B.They are divided into Lead Auditors, EPG members, and SCM coordinators, expecting standard metrics.
C.They are divided into Staging Admins, Database Managers, and Software Architects, expecting zero compile-time bugs.
D.They are divided into Contract Negotiators and Financial Executives, focusing solely on SPI.
According to Module 01, Sections S and U of the course handouts, in the example of a program designed to add two numbers (5 and 3) that prints the subtraction outcome instead, what is classified as the 'Fault' and what is classified as the 'Failure'?
💻 cpp Snippet
ans = value1 - value2; // Intended addition
A.The Fault is the client complaining about the wrong output, and the Failure is the programmer using a C++ compiler.
B.The Fault is the wrong subtraction sign '-' used instead of '+' in the code, and the Failure is the program outputting a value of 2 instead of 8.
C.The Fault is the local database being offline, and the Failure is a memory leak inside the printf statement.
D.The Fault is the presence of an Off-the-Shelf plugin, and the Failure is having an SPI score below 1.0.
Based on Module 01, Sections C and D of the course handouts, how do the quality expectations of "Consumers" (Users and Customers) fundamentally contrast with those of "Producers"?
A.Consumers focus on functional suitability, reliability, and cost-effectiveness of the solutions, whereas Producers focus on fulfilling contractual obligations, specification conformance, and technical design attributes like modifiability.
B.Consumers are only concerned with the programming language used, while Producers focus entirely on the purchase price of the product.
C.Consumers prioritize CMMI Maturity Level audits, while Producers prioritize daily standup meeting minutes.
D.There is no difference; both groups have identical definitions and metrics for assessing software quality under all circumstances.
According to Module 01, Section L of the course handouts, how is an "Error" formally defined, and what types of errors can it encompass in Software Quality Engineering?
A.Error is a human action that produces an incorrect result and/or the mistakes made by a programmer, usually representing syntax mistakes but potentially being both syntax and semantic errors.
B.Error is defined as a deviation from customer requirements discovered only after the software is shipped to the production site.
C.Error is the inability of a program to behave as expected within given performance requirements due to hardware bottlenecks.
D.Error refers to a structured list of testing checklists executed by the SCM team during the final stage of sanity testing.
Based on Module 01, Section X of the course handouts, why is 'tolerating' certain faults and containing failures necessary in large-scale software systems?
A.Nice software interfaces cannot process logical calculations without producing physical keyboard errors.
B.Because some faults are triggered under rare conditions that cannot be completely eradicated by testing alone, requiring that we break the causal relation between faults and failures.
C.Because software configuration management teams do not support version rollback operations in multi-platform environments.
D.Because CMMI Maturity Level 5 organizations do not perform any manual inspections or walkthroughs.
Based on Module 01, Section V of the course handouts, which of the following is true regarding the cost and impact of recurring software defects?
A.Recurring defects are highly economical since they are resolved using automated compilers during the coding phase.
B.Recurring defects are very costly by nature and represent a mere wastage of time and budget, whereas minimizing their count is a primary challenge.
C.Recurring defects do not affect user satisfaction if the system meets at least 50% of the customer requirements.
D.Recurring defects are automatically mitigated when an organization transitions from a physical keyboard to a touchscreen.
According to Module 01, Section V of the course handouts, how is 'Defect Prevention' formally defined, and what is its primary strategic objective in a software project?
A.A process of running automated load testing scripts on a weekly basis to identify server-side database bottlenecks.
B.A strategy to identify the root causes of defects and prevent them from recurring, thereby improving the process to avoid introducing defects in the first place.
C.An appraisal methodology designed to assign a numeric CMMI maturity level rating to an organization.
D.A post-release hotfix procedure used to patch critical software bugs reported by customers in the production environment.
According to Module 01, Section I of the course handouts, which system resources are primarily examined to evaluate the 'Efficiency' of a software solution when providing its required functionality?
A.The monetary cost of license keys and the billing hours of the SQA lead auditor.
B.The number of lines of source code and the count of tables in the database schema.
C.System resources such as the amount of disk space, memory, and network bandwidth used.
D.The number of physical keyboards and multi-touch touchscreen devices in the organization.
According to Module 01, Section N of the course handouts, how is a 'Defect' formally defined in Software Quality Engineering?
A.A human action or mistake made by a programmer during code development that results in a compilation failure.
B.The deviation from customer requirements, representing the departure of a quality characteristic from its specified value that results in a product not satisfying its normal usage requirements.
C.A temporary hardware or memory-handling delay that can be resolved by executing standard sanity test checklists.
D.The process of creating bidirectional traceability matrices to connect use cases with structural test runs.
