Ch 01: Software Quality Engineering Discipline

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 191 – 200 of 279 Questions
Page 20 of 28
Q191
🧠 Long ProblemπŸ“˜ CS611πŸ“‘ Lec 1🏷️ 01.18. Example of FaultHardπŸ”β­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
Define a software 'Fault' and explain its relationship with 'Errors' and 'Failures'. Use the C code addition example from the handouts to illustrate how a fault is manifested in code.
πŸ’» c Snippet
#include
int main ()
{
    int value1, value2, ans;
    value1 = 5;
    value2 = 3;
    ans = value1 - value2;
    printf("The addition of 5 + 3 = %d.", ans);
    return 0;
}
Q192
🧠 Long ProblemπŸ“˜ CS611πŸ“‘ Lec 1🏷️ 01.20. Example of FailureHardπŸ”β­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
Provide a detailed comparison of 'Fault' and 'Failure' using the C program addition example from Module 01 of the course handouts, explaining how one leads to the other and how they are manifested in this scenario.
πŸ’» c Snippet
#include
int main ()
{
    int value1, value2, ans;
    value1 = 5;
    value2 = 3;
    ans = value1 - value2;
    printf("The addition of 5 + 3 = %d.", ans);
    return 0;
}
Q193
🧠 Long ProblemπŸ“˜ CS611πŸ“‘ Lec 1🏷️ 01.2. Roles and ResponsibilitiesHardπŸ”β­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
Identify the primary stakeholders in software development as defined in Module 01, and compare the software quality expectations of the 'Consumer' (including its sub-categories) against those of the 'Producer'.
Q194
🧠 Long ProblemπŸ“˜ CS611πŸ“‘ Lec 1🏷️ 01.16. Example of BugHardπŸ”β­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
Describe the historical event of the Mariner I space probe bug on July 28, 1962, explaining the root cause of the accident, its direct consequences, and the lesson it provides to Software Quality Engineering.
Q195
πŸ“ Short QπŸ“˜ CS611πŸ“‘ Lec 1🏷️ 01.11. What is ErrorMediumβ­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
Explain the relationship between the number of lines of code to be analyzed and the cost of fixing logical errors as described in Module 01, Section L of the course handouts. Then, write a Python function 'calculate_fixing_cost' that models this relationship by taking the number of lines of code ('loc') and a baseline cost per line, and returns the calculated cost, applying an exponential multiplier if the LOC exceeds a specific threshold.
πŸ’» python Snippet
def calculate_fixing_cost(loc, base_cost_per_line):
    pass
Q196
πŸ“ Short QπŸ“˜ CS611πŸ“‘ Lec 1🏷️ 01.22. Defect Detection or ReductionMediumβ­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
Explain Humphrey's (1995) concept of competing processes in software quality engineering, detailing why 100% prevention is unrealistic and how project constraints affect defect removal. Then, write a Python function 'simulate_defect_dynamics' that models defect injection, prevention efficiency, and subsequent removal, returning the net remaining bugs.
Q197
πŸ“ Short QπŸ“˜ CS611πŸ“‘ Lec 1🏷️ 01.15. What is BugMediumβ­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
Explain the distinction between a 'Defect' and a 'Bug' as described in Module 01, Sections N and P of the handouts. Then, write a Python function 'classify_anomaly' that takes an anomaly record (with fields 'name', 'found_in_production' boolean, and 'accepted_by_developers' boolean) and returns its SQA classification as 'BUG', 'DEFECT', or 'UNACCEPTED_ERROR'.
Q198
πŸ“ Short QπŸ“˜ CS611πŸ“‘ Lec 1🏷️ 01.23. Defect Removal or ContainmentMediumβ­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
Explain how Software Fault Tolerance breaks the causal relationship between faults and failures under rare conditions, as described in Module 01, Section X of the course handouts. Then, write a Python function 'tolerate_fault' that simulates a fault-tolerant system. The function should take a critical calculation block (as a callable), input values, and a fallback handler. If the critical block raises an exception (representing a rare triggered fault), it should catch the exception, invoke the fallback handler, and log a warning, thereby preventing system failure.
πŸ’» python Snippet
def critical_service(data):
    # Simulated rare fault condition
    if data.get("rare_trigger") == True:
        raise RuntimeError("Rare system-level fault triggered!")
    return data["value"] * 10
Q199
πŸ“ Short QπŸ“˜ CS611πŸ“‘ Lec 1🏷️ 01.20. Example of FailureMediumβ­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
Define 'Failure' and describe how a fault in the program code results in a failure in the output, referring to the example provided in Module 01, Sections T and U of the course handouts. Then, write a Python function 'check_system_failure' that evaluates whether a mathematical function's output complies with the expected specification, returning a diagnostic report.
Q200
πŸ“ Short QπŸ“˜ CS611πŸ“‘ Lec 1🏷️ 01.2. Roles and ResponsibilitiesMediumβ­πŸ’‘πŸŒŸπŸ“„πŸŽ“VUπŸ›οΈVU
Contrast the quality expectations of 'Users' and 'Customers' as stakeholders under the 'Consumer' category in Module 01, Section C of the handouts. Then, write a Python function 'evaluate_consumer_expectations' that takes a dictionary representing a software product's verified properties (e.g., {'meets_needs': True, 'reliable': True}) and evaluates whether both user expectations and customer expectations are satisfied based on budget.