Analyze the role of Defect Prevention with a specific focus on 'Education and Training' under high-maturity software quality engineering frameworks. Explain the core assumptions of defect prevention, how the 'people factor' acts as a major driver for software defects, and why a continuous learning culture is necessary to handle rapid changes. Write a Python script to model a 'DeveloperTrainingTracker' class that monitors developer training, records skill levels in specific technologies, checks if they are certified to work on a feature, and calculates potential risk exposure based on untrained developer hours.
Ch 07: Software Requirements
Covers ambiguity detection, requirements validation techniques, IEEE SRS standards, verifiable acceptance criteria, and maintaining bidirectional requirement-to-test matrices.
111 Questions111 MCQs0 Short Questions0 Long Questions
SEMESTER PASS
CS611 - Software Quality Engineering Examination Practice
Timed practice exam simulation for CS611 - Software Quality Engineering.
Showing 61 โ 70 of 111 Questions
Page 7 of 12
Explain the relationship between Software Quality Assurance (QA) and defects as outlined in Module 07 of the course handouts. Detail the three-tier defect classification scheme (Defect Prevention, Defect Detection, and Defect Containment) and discuss how these strategies work in unison to protect critical system functionality. Write a Python program representing a 'DefectAuditTracker' that registers software defects, tracks their detection phase, calculates the containment ratio (proportion of bugs captured by SQA versus escaping to production), and audits if any defects have compromised critical functions.
Analyze software testing as a dynamic fault detection methodology as presented in Module 07. Contrast testing with static inspections, discuss when formal testing begins, and explain how executing the product helps ensure its stability. Write a Python class 'FaultDetectionEngine' that simulates a testing cycle, registers test cases with expected outputs, executes code blocks to capture actual outputs, identifies mismatches (bugs), and calculates a test pass-rate metric.
Analyze the database CSV log export failure detailed in Module 07 as a case study in Software Quality Economics. Explain how missing SRS constraints impact SQA coverage, the high cost/reputational damage of production hot-fixes, and the mechanics of the chunking workaround. Write a Python class 'ChunkedCSVExporter' that simulates this system, mimicking database log generation, enforcing a chunk boundary of 500,000 rows, exporting separate data files, and merging them into a final consolidated report.
Provide a thorough analysis of the economics and collateral impact of post-release defects in software product development as detailed in Module 07. Compare the financial cost of post-release defects to pre-release/in-development bugs, explaining why multiple product installations compound this cost. Discuss the negative non-financial consequences on supplier organizations. Finally, write a Python class `DefectCostCalculator` that compares the cost of fixing a pre-release defect versus a post-release defect across $N$ client installations, factoring in deployment overhead and calculating reputational risk damage.
Analyze the relationship between Quality Assurance and defects under CMMI as detailed in Module 07. Explain the 'last resort' principle for critical functionalities and detail the first two tiers of the defect classification scheme: Defect Prevention and Defect Detection (correcting original grammatical typos like 'Default Detection'). Write a Python class 'DefectShieldEngine' that models these strategies, processes software tasks, filters out root causes of potential defects, executes reviews to detect bugs, and guarantees that critical features remain unharmed by defects.
Analyze the competing processes of defect injection and defect removal as detailed in Module 07, Section 07.15. Explain why defect prevention mechanisms cannot guarantee a 100% defect-free product, and discuss how a vigorous defect reduction strategy must be structured to mitigate this. Finally, write a Python program representing a 'QualityGateSimulator' that registers software tasks, models a defect prevention filter, simulates active defect reduction activities (like code walkthroughs and testing reviews) to catch remaining bugs, and evaluates the escape rate of errors.
Analyze the role of Domain Knowledge in requirements engineering and SQA as detailed in Module 07. Explain why software developers are classified as 'pure technical resources' rather than domain specialists, and how domain-specific terminologies vary across industries. Using the Property Tax calculation scenario (covered area, constructed area, floors, property type, category, and off-road/on-road rates), discuss why a domain specialist is indispensable for deriving formulas. Write a Python program modeling a 'PropertyTaxCalculator' class that accepts these properties, applies specific law rules as derived by a domain specialist, and handles validation exceptions when invalid technical data is supplied.
Analyze the concepts of 'Defect Containment' and 'Pre-Release (Dormant) Defects' as presented in Module 07 of the course handouts. Discuss how the cash register scenario (cash + credit card + gift voucher payment) serves as a classic example of a dormant defect, and explain how a QA team should design their test strategy to minimize such occurrences. Finally, write a Python class 'DormantDefectSimulator' that represents a transactional system, contains a hidden dormant bug triggered only under a rare multi-instrument payment combination, simulates a testing run that fails to catch it under standard test cases, and demonstrates the bug being triggered in production.
Discuss software inspections as a static QA methodology for direct fault detection and removal. Analyze the social media login conflict scenario described in Module 07 of the handouts to explain how peer reviews and code walkthroughs act as 'another eye' to solve complex shared codebase bugs. Write a Python class 'CodeInspectionAuditor' that simulates this exact scenario, representing a shared codebase, modeling how an inspected 'plugin' changes a shared state, and demonstrating how a static code review catches and resolves this state conflict before dynamic QA testing begins.