According to Module 10 of the course handouts, changes in software products are continuous facts of software development. What are the two primary drivers for these changes, and whose responsibility is it to manage them in complete detail?
A.Error removal and product refinement; it is the responsibility of SCM.
B.Staff turnover and code compilation warnings; it is the responsibility of SQA.
C.Client billing delays and hardware obsolescence; it is the responsibility of Finance.
D.UML design modeling and use case diagramming; it is the responsibility of EPG.
According to Module 10, Section 10.19 of the course handouts, into which four severity levels are bugs/defects classified for all units/features in a sanity test report?
A.Low, Average, High, and Catastrophic
B.Critical, Major, Medium, and Cosmetic
C.Functional, Structural, Static, and Dynamic
D.Compile-Time, Run-Time, Logical, and Semantic
According to the course handouts in Section 10.21, if a software feature consists of multiple underlying units, what specific type of testing is required to perform Feature Level Testing effectively?
A.Static syntax analysis to check warning messages on uncalled methods.
B.Integration testing to test the feature by verifying the interfaces and interconnections between its multiple units.
C.Ad-hoc exploratory testing performed exclusively by business analysts before SCM merges the code.
D.Unit testing of each block independently without compiling or merging them into a unified build.
Based on Module 10, Section 10.13 of the course handouts, which of the following options correctly outlines the differences in budget, requirements source, and lifespan between project-based and product-based testing?
A.Project testing utilizes the organization's own budget with requirements from market standards, whereas product testing is a one-time activity.
B.Project testing is a one-time activity that ends upon delivery to the client and uses client budget/requirements; product testing is an ongoing activity using the organization's own budget based on market standards.
C.Both project and product testing are one-time activities that end immediately when the QA team finishes regression testing.
D.Project testing requirements are regularly updated as per release, whereas product testing requirements are specific under a single static environment.
In the regression testing scenario described in Module 10, Section 10.27 of the handouts, which specific features are added or updated in Release 1.1 compared to Release 1.0, and what must regression testing verify?
A.Feature 4 is updated to 'Payment with Discount Card using PayPal also', and Feature 5 ('Discount Card') is added; regression testing must verify that these additions do not impact the already developed features of Release 1.0 (Login, Product Listing, Shopping Cart).
B.Feature 1 is updated to support biometric login, and Feature 2 is updated to support CSV logs; regression testing must verify database index limits.
C.Feature 3 is replaced entirely with an external off-the-shelf payment gateway; regression testing must verify network bandwidth.
D.No new features are added; Release 1.1 only consists of unit-level calculations for the database capacity.
According to Module 10 of the course handouts, which team is responsible for coordinating software release activities, and what is the sequence of handoffs for the codebase?
A.Coordinated by the SQA team, handed over to the development team, and then passed to the customer.
B.Coordinated by the SCM team, handed over to QA, and then passed to the customer.
C.Coordinated by the Engineering Process Group (EPG), handed over to the Lead Auditor, and then passed to the customer.
D.Coordinated by the Sales team, handed over to the Product Manager, and then passed to the developer.
According to Module 10, Section 10.21 of the course handouts, which of the following statements best defines 'Feature Level Testing' and explains its relationship with underlying units?
A.Feature level testing is a white-box testing technique where developers inspect compiler warnings on isolated mathematical statements to calculate cyclomatic complexity.
B.Feature level testing is aimed at making sure that software and its features work properly to meet all intended specifications; it evaluates each function, which may consist of multiple units, to see if it is working as required.
C.Feature level testing represents the final stage of performance load testing where concurrent client requests are simulated on an unmerged repository.
D.Feature level testing is a cost-benefit calculation model used to predict schedule variance (SV) during project planning phases.
Based on Module 10, Section 10.36 of the course handouts, what is the primary objective of defect correction during the pre-production software development phase?
A.To guarantee a completely 100% bug-free codebase that is mathematically proven to never crash.
B.To fix and ship in-scope bugs to ensure maximum compliance with the agreed requirements.
C.To ignore all minor and cosmetic bugs to ensure that the project schedule performance index (SPI) remains above 1.5.
D.To deliver features exclusively as paid wishlist items directly to the client without executing any SQA reviews.
Based on Module 10, Section 10.32 of the course handouts, what is the primary quality engineering purpose of including test results and information about the testing procedure inside the distributed Release Notes?
A.To allow developers to copy the test procedures and bypass writing local unit test algorithms.
B.To increase client or end-user confidence in the quality and stability of the product.
C.To satisfy SCM version control check-ins so that the code branches can be automatically merged.
D.To replace formal third-party CMMI audits with customer self-verification checklists.
According to the comparative regression scenario described in Module 10, Sections 10.26 and 10.27 of the course handouts, what must regression testing specifically ensure during the transition from Release 1.0 to Release 1.1?
A.That all unit testing modules are rewritten in Java to improve the stability of the compiler class.
B.That the newly added or updated features—specifically the discount card and the PayPal payment option—do not impact or break the already developed and tested features.
C.That the database capacity is immediately increased by 500,000 rows to accommodate social media logins.
D.That the EPG lead auditor manually signs off on all technical design specifications before SCM merges the branches.
