Ch 06: Support Process Area

Analyze the relationship between Software Requirement Engineering and Software Quality Engineering based on the Cavendish Software Chaos Report and the motivation for software requirements. Explain how a client's low prioritization of requirements documentation impacts a development team's ability to deliver high-quality software, how this is connected to the 87% project failure rate mentioned in the report, and write a Python script that models a Requirements Ambiguity Simulator to compute how uncertainty cascades from requirements down to coding and SQA verification phases.

Analyze the 'Verifiable' attribute of software requirements as detailed in Module 06. Explain why untestable requirements are not verifiable, the role of the Quality Assurance team as the gatekeeper for closing requirements, and the specific words that should be avoided. Write a Python program that simulates a 'RequirementsVerifiabilityChecker' to parse requirements, flag prohibited words (such as 'must', 'shall', 'etc.', 'minimum', 'maximum'), check if they specify numeric values where appropriate, and generate a quality compliance report.

Analyze 'Completeness' and 'Feasibility' as vital attributes of software requirements as detailed in Module 06. Explain the consequences of incomplete requirements on system development and customer satisfaction. Discuss the open questions and suggestions of the 'Status Message' completeness example and the role of developer input in determining feasibility. Finally, write a Python program representing a 'RequirementsAttributeValidator' that parses requirement objects, checks for incomplete indicators (such as undefined fields or lack of display target), verifies developer feasibility approval, and generates a compliance audit report.

Explain the significance of the 'Traceable' attribute in Software Requirements and Software Quality Engineering under high-maturity CMMI standards. Differentiate clearly between forward and backward integration with appropriate examples. Discuss the real-time project failure example documented in Module 06 and analyze how non-traceable requirements lead to project failures during Root-Cause Analysis (RCA). Provide a Python script representing a 'RequirementsTraceabilityMatrix' (RTM) class that tracks requirements, checks for forward and backward link compliance, detects undocumented features, and generates an SQA Traceability Audit Report.

Analyze the critical role of Software Requirements in preventing project failures under CMMI and Software Quality Engineering. Focus on the issues of 'Missing Requirements' and 'Client Non-Involvement' as detailed in Module 06. Describe how these issues propagate through the subsequent phases of the Software Development Life Cycle (SDLC) and increase the cost of fixing errors. Provide a Python program that simulates a Requirements Validation and Risk Assessment System. The program must accept a list of requirements, check for missing or vague descriptors, evaluate the risk level based on client involvement, and calculate an overall project risk score.

Analyze the significance of 'Correctness' and 'Coherency' as core quality attributes of software requirements under CMMI and Software Quality Engineering. Explain how open-ended terms (like 'etc.' or 'assumed') and inconsistent technical vocabulary lead to 'toxic requirements' that cause project failures. Provide a Python program representing a 'RequirementsCoherencyAuditor' that parses various requirement statements, detects conflicts between requirements, flags inconsistent technical terms, and checks length boundaries.

Provide a comprehensive analysis of the 'Feasible' attribute of software requirements as detailed in Module 06. Explain the operational definitions of feasibility, the specific issues identified with 'simultaneous' computer actions and 'zero bug' expectations, and the necessity of developer-level technical input during requirements engineering. Write a Python program simulating a Feasibility Verification Engine. The program must parse requirement strings, identify unfeasible words (e.g., 'simultaneously', 'zero bug', 'instantaneous'), and check if there is developer feasibility approval before allowing the requirement to be baselined.

Discuss the relationship between Software Requirements and Software Quality Assurance (SQA) under high-maturity CMMI standards as documented in Module 06. Explain why SQA is considered the 'internal customer' and the significance of having QA resources review requirements before finalizing them. Provide a Python program that simulates a 'RequirementsQAReviewEngine' that registers software requirements, audits if SQA has reviewed and mapped them to test cases, and flags any non-reviewed requirements to prevent premature development baselining.

Explain how Use Cases act as the primary connector between different phases of the Software Development Life Cycle (SDLC) under SQA and CMMI frameworks. Discuss the structural components of the Use Case template (such as Pre-conditions, Post-conditions, and Normal Course of Events) and their importance. Write a Python program representing a Use Case Parser and Validation Engine that checks if a Use Case object contains all mandatory template fields and tests it using the 'Sign In' use case from the handouts.

Analyze the role of Software Quality Assurance (SQA) as the 'internal customer' and the significance of 'Release Notes' in release and build management under CMMI. Explain who writes and owns the release notes, what contents they must include, and why SQA's approval is the ultimate gate for distributing both the software and its documentation. Write a Python script to model a 'BuildReleaseAuditor' class that validates if a software build is fully tested, compiles its release notes dynamically (features, benchmarks, known issues), and flags compliance errors if unauthorized distribution is attempted.