Ch 01: Software Quality Engineering Discipline

Explain the three main usability assessments (learnability, understandability, and usability/operability) of the ISO-9126 framework as described in Module 01, Section H of the handouts. Then, write a Python function 'evaluate_usability_survey' that takes a list of user survey responses (each being a dictionary of score ratings from 1 to 5 for learnability, understandability, and ease of use) and returns whether the software meets a target usability threshold of 4.0 out of 5.0.

Describe the relationship between software performance and system resource consumption under the ISO-9126 'Efficiency' characteristic, using the UI load-time example from Module 01, Section I of the handouts. Then, write a Python function 'evaluate_efficiency_performance' that takes system response time (in seconds), memory usage (in MB), and limits, and returns a status dict indicating if the performance is efficient.

Describe the main quality expectations of a 'Producer' as detailed in Module 01, Section D of the handouts, and explain why technical choices like languages or methodologies impact their work. Then, write a Python function 'validate_producer_conformance' that checks if a software release meets its contract specifications.

Enlist and briefly define the four subcomponents of the ISO-9126 'Maintainability' quality characteristic as described in Module 01, Section J of the handouts. Then, write a Python function 'evaluate_module_maintainability' that takes metrics for a module (e.g., complexity, comment density, test coverage) and returns whether the module is acceptable or a 'high technical debt risk' based on standard SQA thresholds.

Explain the dual-focus of 'Portability' as defined in Module 01, Section K of the handouts, including how requirement adaptation relates to portability. Then, write a Python function 'evaluate_portability_risk' that takes a dictionary of target platform versions and their test statuses (Pass/Fail) and returns a risk report indicating whether any feature fails on a specific OS version.

Explain the distinction between a 'Fault' and a 'Failure' as described in Module 01, Sections R and T of the course handouts, using the arithmetic subtraction sign example to illustrate your explanation. Then, write a Python function 'check_addition_failure' that takes 'value1', 'value2', and an 'actual_output' from a program, and returns whether a failure has occurred (when compared against expected addition) along with a diagnostic status.

Explain how functionality is evaluated as a totality of essential functions, citing the sales order processing system example from Module 01, Section F of the handouts. Provide a Python function 'evaluate_functionality_coverage' that takes a set of required essential features (e.g., 'record_sales', 'price', 'quantity', 'tax', 'shipping', 'inventory') and actual implemented features, returning whether the essential functionality is satisfied and its coverage percentage.

Explain how transcription errors can lead to catastrophic bugs in critical systems, citing the Mariner I space probe example from Module 01, Section Q of the handouts. Then, write a Python function 'simulate_trajectory_calculation' that demonstrates the difference between the correct formula on paper and the improperly transcribed code, highlighting how the transcription fault causes a deviation in the trajectory output.

Explain the distinction between an 'Error' and a 'Defect' as detailed in Module 01, Sections L and N of the handouts. Then, write a Python function 'parse_defect_log' that registers a list of system anomalies, filters out those occurring at the production site (which are classified as 'Defects'), and counts those caught before shipment (classified as 'Bugs/Errors').

Explain how the macro-level defect filtration funnel operates across different phases of the software development life cycle as described in Module 01, Section V of the handouts, and contrast it with late-stage testing. Then, write a Python function 'filter_defects' that simulates this sequential filtering process by taking an initial bug count and reduction efficiencies (as floats between 0 and 1) for the four filters, and returns a summary of defects caught at each phase, remaining escaped bugs, and whether the system met a 99.9% bug-free standard.