According to Module 09 of the course handouts, what is the primary software artifact to be tested, and how are test cases typically derived?
A.The primary artifact is the Software Requirements Specification (SRS) document, and test cases are derived from the project's Gantt chart timelines.
B.The primary artifact is the software program or code written in different programming languages, and test cases are derived from use cases.
C.The primary artifact is the database schema backup file, and test cases are derived from SQL transaction rollback logs.
D.The primary artifact is the software release note, and test cases are derived from third-party CMMI compliance checklist sheets.
According to Module 09, how is software testing described in layman's terms and what concrete perspective does it provide on the software product?
A.It is a static walkthrough of code styles that provides a qualitative assessment of developer expertise.
B.It is all about comparing the actual and the desired behavior of the product, providing a concrete and objective view of the quality of the product.
C.It is a version-control baseline review that evaluates the capability maturity level of SCM systems.
D.It is a risk management framework focused on rewriting business contracts to establish post-deployment SLAs.
According to Module 09 of the course handouts, what is the core objective of the 'Test Planning & Preparation' activity?
A.To run automated regression test suites and measure product execution speeds in milliseconds.
B.To set the goals for testing, select the best and appropriate testing strategy/methodology, and prepare specific test cases and the general test procedure.
C.To merge codebase revisions using SCM tools and assign administrative rights to the support team.
D.To conduct first-party compliance audits on developer documentation and baseline configuration manifests.
Sourced from Module 09 of the course handouts, which of the following best contrasts the definitions and roles of 'test cases' and 'use cases' during SQA activities?
A.Use cases are compiled executable files designed to find syntax errors, whereas test cases are UML diagrams used by project managers to measure SPI.
B.Use cases describe all the steps the final user will perform to complete a task, serving as inputs for test cases, while a test case is a document that describes the testing activities, pre/post-conditions, expected behavior, and results.
C.Test cases are written by the client to describe business goals, whereas use cases are written by SCM managers to coordinate code branching.
D.Use cases track project billing and invoicing milestones, whereas test cases map code execution times in milliseconds to prevent database latency.
Based on Section 09.8 of the course handouts, what techniques should be used to explore the physical possibilities of entering values into an arithmetic software input field?
A.Using the mouse, keyboard, typing, and pasting values to explore input interaction possibilities.
B.Writing unit tests to verify database connectivity parameters.
C.Employing SCM baseline versioning tools to automatically merge input modules.
D.Utilizing statistical process boundaries (SPI and CPI) to measure user typing speed.
As Chunk 198 through 206 transitions from Black Box to White Box Testing, what is the primary distinction regarding internal code visibility?
A.Black Box testing evaluates statistical CPI margins, while White Box testing focuses on external user interface aesthetics.
B.Black Box testing treats the system as an opaque box where internal code is unknown, whereas White Box testing focuses on verifying internal implementations like code, data structures, and statement paths.
C.Black Box testing requires a certified Lead Auditor, while White Box testing is completely automated by SCM compilers.
D.There is no distinction; both methodologies are executed only after software is deployed to production.
According to Module 09 of the course handouts, what is the primary aim of 'White Box Testing' and how is it achieved?
A.It is a functional testing approach achieved by executing ad-hoc manual scripts to observe differences between expected and actual performance without code visibility.
B.It is a configuration management technique that uses SCM versioning repositories like Git to track user permissions.
C.It is a structural testing strategy achieved by executing and observing software behaviors to verify correct internal implementations such as code statements, data structures, blocks, and interconnections.
D.It is an external auditing mechanism led by a certified lead auditor to establish SLA boundaries with the client.
According to Module 09 of the course handouts, what does the 'Analysis & Follow-up' activity in software testing involve?
A.Writing release notes and distributing billing invoices to the finance department.
B.Analyzing results to determine if a failure has been observed, and if so, taking and monitoring corrective actions to ensure removal and reproduction of defects.
C.Unilaterally reclassifying defects as 'not a bug' without stakeholder consent.
D.Modifying the project plan's scheduled deadlines and negotiating new SLAs.
Based on Module 09, Section 09.10, how do debugging tools assist a tester during statement-level code coverage testing?
A.They automate the transition of tickets through the CMMI Maturity Level 5 defect lifecycle.
B.They compile high-level requirements into UML use cases to generate automated test cases.
C.They allow the tester to see if all or specific statements have been executed and whether they give the desired output, identifying errors along with their locations.
D.They calculate the Cost Performance Index (CPI) of individual lines of code to prevent budget overruns.
According to Module 09 of the course handouts, which of the following defines 'Software Testing' and its core purpose?
A.It is a project management practice of negotiating SLAs with clients to ensure a zero-bug delivery.
B.It is the process of executing the software product with the intention to ensure that it is giving the desired outcomes, satisfying all requirements/business needs, and finding bugs so they can be corrected.
C.It is a configuration management process that monitors the number of developers check-ins on shared repositories.
D.It is a static walkthrough of SRS documents led by a certified lead auditor to remove toxic requirements.
