Ch 06: Support Process Area

Briefly describe the summary and primary actors of the 'Register new patient' Use Case (Use Case ID 7) as documented in Module 06.

Are software requirements the same as requirements in other engineering domains? Describe the key reasons for your answer.

Explain the difference between working on 'what the client needs' versus 'what the developers want' based on the 'Necessary' attribute in Module 06. Highlight the 'social media login' example to illustrate your explanation.

Briefly compare how 'Software Requirements' differ from requirements in other traditional domains (such as the construction industry) as explained in Module 06 of the course handouts.

Explain why it is very difficult to identify whether a requirement is feasible or non-feasible without technical input from developers, and outline the CMMI recommendations to address this challenge.

Discuss the relationship between requirements traceability, functional specifications, and project success under CMMI guidelines. Specifically, analyze the real-time Root-Cause Analysis (RCA) of the project failure described in Module 06 where a key developer spent a major part of their time on a non-traceable requirement. Explain how functional requirements are formally captured using Use Cases and what technical elements they drive. Finally, write a Python program that simulates a simple 'Requirements Auditing System' that checks if developer-logged tasks map back to verified Use Case IDs, and flags any non-traceable work (gold-plating) that could lead to project delay.

Detail the requirements engineering challenges and effort-wise budget distributions discussed in Module 06. In your response: 1. Explain the three requirements-related issues (Wrong, Changing, and Out of Scope requirements) and why they occur. 2. Discuss the difference between typical and ideal budget allocations for the requirements phase, explaining why requirements gathering is often treated as an overhead and how neglecting it affects project success. 3. Write a Python program simulating an SDLC Budget Estimator that calculates the requirements phase allocation from a total budget, classifies whether it is 'Standard' (10%) or 'Ideal' (20%), and provides a CMMI risk analysis warning of potential downstream risks based on the selection.

Explain why requirements engineering is classified as a communicational activity rather than a technical one under CMMI and Software Quality Engineering. Discuss the challenges associated with managing diverse stakeholder points of view, and analyze the specific impediments of gathering specifications from non-technical clients. Provide a Python class 'RequirementStakeholderCommunicator' that stores various stakeholder priorities, identifies conflicting interests, and models a negotiation mechanism to reach a 'win/win' compromise.

Analyze 'Necessity' as a key quality attribute of software requirements under CMMI and Software Quality Engineering. Discuss how developer over-engineering and gold-plating can lead to project failure and customer rejection of demos, using the social media login case study from the handouts. Provide a Python program that simulates a 'RequirementsPrioritizer' that validates whether a project's implemented features align with the customer's high-business-value baseline needs, and flags any developer gold-plating.

Do you agree that correctness-centric activities are the basics of quality assurance? [Yes/No]. Enlist any two objectives of Quality Assurance, and write a Python function 'evaluate_qa_objectives' that takes a list of verified objectives and returns a pass status if the core SQA objectives are met.