Paper - II (xii) — Software Engineering MCQ — 44 Practice Questions with Answers

Explanation

Black-box testing treats the software as a functional unit whose inputs and outputs are checked against the specification. Login cases based on valid, invalid and boundary conditions can be selected without seeing the code. White-box methods, by contrast, require structural knowledge such as paths, branches or statements.

Explanation

Verification asks whether work products conform to the specified requirements, design, or standards. Validation asks whether the built product is suitable for the user's intended purpose in its operational context. This distinction is why inspections, reviews, and tests can support verification, while acceptance-oriented checks often support validation.

Explanation

The context diagram is the top-level DFD view: it treats the system as a single process and identifies outside actors or systems that exchange data with it. That makes it useful during requirements analysis for fixing scope and interfaces before internal decomposition begins.

Explanation

Equivalence partitioning is a black-box test design technique. The tester groups possible inputs into valid and invalid classes and selects representative values from each class, using the specification rather than source-code paths. Mutation testing, path testing and inspection rely on different mechanisms.

Explanation

In a sequential SDLC, design translates requirements into architecture and detailed specifications. Therefore, the important preceding activity is to elicit, document, analyse and validate what the software must do, including constraints and acceptance expectations. Coding, regression testing and deployment-support documents are useful later, but they cannot safely substitute for a stable requirements baseline.