Ch 06: Support Process Area

279 Questions279 MCQs0 Short Questions0 Long Questions
๐ŸŽฏ Exam Practice Papers
SEMESTER PASS

CS611 - Software Quality Engineering Examination Practice

Timed practice exam simulation for CS611 - Software Quality Engineering.

๐Ÿ“˜ VU MID TERM EXAMLectures 1 to 22
โฑ๏ธ 60 Mins

Mid Term Examination

Covers syllabus of Lectures 1 to 22 with 30 high-yield MCQs in a timed exam environment.

๐Ÿ“30 MCQs
โฑ๏ธ60 Minutes
๐Ÿ“— VU FINAL TERM EXAMLectures 23 to 45
โฑ๏ธ 90 Mins

Final Term Examination

Comprehensive semester exam preparation with 45 MCQs covering Lectures 23 to 45 with complete course coverage.

๐Ÿ“45 MCQs
โฑ๏ธ90 Minutes
Showing 201 โ€“ 210 of 279 Questions
Page 21 of 28
Q201
โ“ MCQ๐Ÿ“˜ CS611๐Ÿ“‘ Lec 6๐Ÿท๏ธ 06.6. Software Requirement vs RequirementsMedium๐Ÿ”โญ๐Ÿ’ก๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Which of the following lists represents the seven distinct quality attributes of software requirements as defined in Software Quality Engineering?
  1. A.Correct, Coherent, Complete, Feasible, Necessary, Verifiable, Traceable
  2. B.Functionality, Reliability, Usability, Efficiency, Maintainability, Portability
  3. C.Defect Prevention, Defect Detection, Defect Containment, Inspection, Testing
  4. D.Ad-hoc, Reactive, Managed, Defined, Quantitatively Managed, Optimizing
Q202
โ“ MCQ๐Ÿ“˜ CS611๐Ÿ“‘ Lec 6๐Ÿท๏ธ 06.21. Functional RequirementsEasy๐Ÿ”โญ๐Ÿ’ก๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
What do functional requirements describe, and which artifact is commonly used to capture them?
  1. A.They describe the budget, cost-per-feature estimates, and timelines, captured using Gantt charts.
  2. B.They describe the internal technical coding standards, captured using the Technical Design Document.
  3. C.They define what the system should do and how it behaves under certain situations, captured using Use Cases.
  4. D.They specify hardware limitations and network configurations, captured using release notes.
Q203
๐Ÿง  Long Problem๐Ÿ“˜ CS611๐Ÿ“‘ Lec 6๐Ÿท๏ธ 06.3. Why Focus on RequirementsHardโญ๐Ÿ’ก๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Discuss how neglecting software requirement engineering affects downstream phases of the Software Development Life Cycle (SDLC). Support your explanation using statistics from the Cavendish Software Chaos Report and the effort-wise budget distribution of SDLC.
Q204
โ“ MCQ๐Ÿ“˜ CS611๐Ÿ“‘ Lec 6๐Ÿท๏ธ 06.7. CorrectMediumโญ๐Ÿ’ก๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Under the 'Correct' attribute of software requirements, what is the recommended length of a requirement statement, and which types of terms must be avoided?
  1. A.It must be 10 to 20 words, avoiding technical variables
  2. B.It should be in a single line and must not exceed 30 to 50 words, avoiding open-ended and subjective terms
  3. C.It should be a detailed paragraph of 100 to 200 words, avoiding code snippets
  4. D.It must be precisely 15 words, avoiding any uppercase characters
Q205
๐Ÿง  Long Problem๐Ÿ“˜ CS611๐Ÿ“‘ Lec 6๐Ÿท๏ธ 06.12. Example of CompletenessHardโญ๐Ÿ’ก๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Analyze the ambiguous client specification: 'The system should generate alerts quickly.' Detail the specific issues this introduces under the 'Complete' and 'Verifiable' attributes of software requirements. Explain why passing such specifications directly to development causes friction between SQA and developers, and write a compliant functional template representation.
Q206
๐Ÿง  Long Problem๐Ÿ“˜ CS611๐Ÿ“‘ Lec 6๐Ÿท๏ธ 06.32. Verifying RequirementsHardโญ๐Ÿ’ก๐ŸŒŸ๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
Define the concept of 'Requirement Verification' in Software Quality Engineering. Detail why it is classified as a structured, ongoing activity throughout the Software Development Life Cycle (SDLC) and how validation before development prevents project rework.
Q207
โ“ MCQ๐Ÿ“˜ CS611๐Ÿ“‘ Lec 6๐Ÿท๏ธ 06.33. People Expectation from Quality EngineeringEasy๐Ÿ”โญ๐Ÿ’ก๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
According to the software quality engineering handouts, what is a common yet unrealistic expectation that stakeholders often hold regarding software quality engineering, and what are its consequences?
  1. A.They expect quality engineering to automate all coding processes, which leads to compiler syntax errors.
  2. B.They expect the delivered software product to be completely defect-free (zero bugs), which leads to financial losses and loss of clients.
  3. C.They expect quality engineering to eliminate the need for any software requirements, which leads to missing project baselines.
  4. D.They expect that quality engineering will replace the database administration team, which leads to data security breaches.
Q208
๐Ÿ“ Short Q๐Ÿ“˜ CS611๐Ÿ“‘ Lec 6๐Ÿท๏ธ 06.3. Why Focus on RequirementsMediumโญ๐Ÿ’ก๐ŸŒŸ๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
In Software Requirement Engineering, define the problem of 'Missing Requirements' and explain how it typically occurs.
Q209
โ“ MCQ๐Ÿ“˜ CS611๐Ÿ“‘ Lec 6๐Ÿท๏ธ 06.5. Requirements DefinedEasyโญ๐Ÿ’ก๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
According to software quality engineering principles, why is software requirement engineering primarily classified as a communicational activity rather than a purely technical one?
  1. A.Because it requires developers to write complex socket communication protocols and network APIs.
  2. B.Because it involves multiple stakeholders with different concerns, and the core challenge is to negotiate and create a win/win situation.
  3. C.Because it is primarily focused on compilation syntax verification and database normalization.
  4. D.Because it deals with managing environment variables and deployment scripts across servers.
Q210
๐Ÿ“ Short Q๐Ÿ“˜ CS611๐Ÿ“‘ Lec 6๐Ÿท๏ธ 06.21. Functional RequirementsMediumโญ๐Ÿ’ก๐ŸŒŸ๐Ÿ“„๐ŸŽ“VU๐Ÿ›๏ธVU
What are functional requirements, and which modeling artifact is primarily used to capture and document them under standard software development life cycle methodologies?