According to Section 09.17 of the course handouts, what is a 'Test Checklist' and how does it relate to functional testing?
A.It is a formal statistical analysis tool used to track CPI and SPI metrics across different departments during the CMMI Level 4 process reviews.
B.It consists of standard steps to list down all activities and tasks to be performed before the test and during the test to ensure readiness, and is not a kind of functional testing.
C.It is a dynamic black-box test suite that automatically checks server memory limits and database capacity.
D.It is a list of UML use cases designed to be executed only by a certified lead auditor to establish SLA boundaries.
According to Module 09 of the course handouts, how is 'Inspection' defined and who typically leads this SQA activity?
A.It is an informal review activity led by the author of the code to explain logic branches to senior programmers.
B.It is a formal type of static testing normally led by a trained facilitator or moderator who is not the author of the code.
C.It is a dynamic testing technique led by a certified third-party auditor to evaluate CPU compile-time efficiency.
D.It is an automated configuration management script executed by the SCM team to resolve merge conflicts.
According to Module 09 of the course handouts, what is the primary focus when performing an inspection on source code, and what are typical questions asked?
A.Setting CMMI Level 5 quantitative billing goals and analyzing statistical process boundaries.
B.Evaluating user login sessions and creating SQL transaction logs in production databases.
C.Removing redundant or unwanted code at max, verifying compiler warnings, unneeded procedures, reusable library calls, consistent style, and symbolic constants usage.
D.Automating the compilation of UML models using SCM triggers to bypass manual quality assurance reviews completely.
According to Module 09 of the course handouts, what is the primary purpose of a 'Test Checklist' in Software Quality Engineering?
A.It consists of standard steps to list down all activities and tasks to be performed before and during the test to ensure readiness for formal QA tests.
B.It is a dynamic white-box testing technique used to verify statement coverage in arithmetic compilers.
C.It is an automated software configuration management (SCM) process used to compile database index triggers.
D.It is a project scheduling tool used to calculate SPI and CPI budget variances.
Sourced from Module 09 of the course handouts, why is Functional Testing often referred to as 'abstract level testing'?
A.Because it tests abstract object-oriented classes and interfaces before their concrete instantiation.
B.Because it just ensures that the software is giving the desired output to the end-user, without making programming or coding a matter of question.
C.Because it is performed solely on wireframes and prototypes before any source code is written.
D.Because it evaluates abstract mathematical models of software performance under extreme stress conditions.
Based on Module 09 of the course handouts, which of the following best contrasts the formal processes of 'Reviews' and 'Inspections' as static testing methods?
A.Reviews are dynamic tests that execute compiled code, while Inspections are manual code rewrites done by SCM administrators.
B.Reviews are informal, require no formal planning or resource utilization, and are led by the author, whereas Inspections are formal, led by a trained facilitator who is not the author, well-documented, and log all defects.
C.Reviews require external CMMI level 5 audit certification, whereas Inspections are simple peer-to-peer Skype team calls.
D.There is no difference; Reviews and Inspections are identical interchangeable processes conducted after product shipment.
Why is Structural Testing described as 'concrete testing from a code viewpoint' in Module 09 of the course handouts?
A.Because it focuses on concrete physical product packaging and hard-copy user guides prior to shipment.
B.Because code is executed and tested directly at the statement level, module level, or sub-system level.
C.Because it completely abstracts away the programming syntax to focus on subjective user-friendliness traits.
D.Because it compiles high-level UML use cases into relational databases using automated SCM baseline configurations.
Contrast the primary testing objectives of Functional Testing and Structural Testing as presented in Module 09 of the course handouts. Which of the following statements is true?
A.Functional testing is concerned with verifying external requirements conformance (external behavior), while structural testing focuses on internal programming, statements, and data structures.
B.Functional testing evaluates statement and path coverage, while structural testing is an abstract-level verification of customer expectations.
C.Functional testing is conducted exclusively by SCM configuration teams, whereas structural testing is performed by certified CMMI lead auditors.
D.There is no difference; functional and structural testing are interchangeable black-box testing methodologies.
According to the code inspection guidelines in Section 09.16 of the course handouts, why should symbolic constants be used instead of 'magic numbers' or hardcoded string constants?
A.To ensure that values are named meaningfully, which improves readability and simplifies code modification during maintenance.
B.Because magic numbers will trigger immediate division-by-zero crashes on compile servers.
C.Because symbolic constants are required to successfully register a project under CMMI Maturity Level 1.
D.Because compilers automatically delete file paths that contain hardcoded integer sequences.
According to Module 07, Section Q and Module 09, Section B of the course handouts, testing is conducted at which level of the Software Development Life Cycle (SDLC)?
A.Only the production deployment level to capture runtime system faults.
B.Only the post-release client-site maintenance level to generate hot-fixes.
C.Only the initial requirements gathering level to draft checklists.
D.Different levels of the SDLC, such as unit, integration, and system levels, to detect faults.
