Analyze the 'Scope Guidelines' and 'Budgeted Effort' components of the CMMI Project Management Framework. Discuss how requirements clarification can be managed, how baselines are established with sales and customers (including invitees), and how effort variation exceeding 25% triggers corrective administrative meetings. Provide a Python program simulating an effort variance validator that takes contracted and estimated actual efforts for multiple phases, flags variations over 25%, and automatically schedules a meeting with sales at a specific time.
Ch 05: Project Management Process Area
Examines project estimation models, milestone tracking, corrective action plans, vendor and subcontractor management, and risk mitigation in software quality assurance.
178 Questions178 MCQs0 Short Questions0 Long Questions
SEMESTER PASS
CS611 - Software Quality Engineering Examination Practice
Timed practice exam simulation for CS611 - Software Quality Engineering.
Showing 101 โ 110 of 178 Questions
Page 11 of 18
Perform a comprehensive audit analysis of 'Example 1 of CPI and SPI' from the course handouts. Explain the role of Planned Value (PV), Actual Value (AV), and Earned Value (EV) in this audit. Detail how the CPI and SPI values are calculated, interpret the project's financial and scheduling health, and discuss how such audits are used under CMMI to trigger corrective management actions. Provide a Python program that implements a robust EVM Audit calculator. The program should accept PV, AV, and EV, perform CPI and SPI calculations, flag budget and schedule overruns, and handle the mathematical verification of whether the project is truly ahead of or behind schedule (resolving any manual text typos).
Discuss the significance of Earned Value Management (EVM) in software quality engineering and process management under CMMI. Explain its primary purpose, how it represents work done, why it is represented graphically, and why it is not considered a traditional corporate financial tool. Additionally, provide a Python program simulating an EVM performance calculator that takes Planned Value (PV), Actual Value (AV), and Earned Value (EV) as inputs and prints whether the project is on track, over budget, or behind schedule.
Detail the mathematical equations, input metrics, and status interpretations for Earned Value Management (EVM) indices (SPI and CPI) as described in Module 05. Explain the operational meaning of values greater than, less than, or equal to 1 for both metrics. Provide a Python program simulating an EVM Audit engine. The script must accept lists of PV, AV, and EV values across multiple milestones, calculate the cumulative SPI and CPI, determine project status, and print a warning alert if remedial actions are required.
Provide an in-depth analysis of Project Planning under the CMMI Process Management Process Area. Detail the role of development estimations, explain why estimations are fundamentally different from timelines (illustrating with the concept that '200 hours does not mean 5 weeks'), and outline the seven core artifacts of the Project Management Framework. Additionally, write a Python program that simulates a Project Planning Scheduler. The program should accept a total effort estimation in man-hours, the number of allocated developers, their daily working hours capacity, and any calendar blockers (e.g. holidays or leaves) to compute and display the actual calendar timeline required to complete the project, illustrating the effort-to-calendar conversion.
Analyze the detailed project planning spreadsheet presented in Module 05, focusing on Task 1 (sorting filters), Task 2 (Deactivated users module), and Task 3 (Analytical report time filters). Explain how breakdown structure (sub-tasks), estimated hours, start/end dates, and comments help project managers track progress and maintain process discipline. Write a Python program that represents this project plan segment as an executable data structure, calculates the total estimated effort for Task 3's sub-tasks, and validates whether each sub-task has a documented schedule (start/end dates) or is missing execution schedules.
Detail the role and significance of 'Project Auditing' across each phase of the Project Management Process Area under CMMI. Explain what areas are evaluated, who provides the audit data, and how the results are used to take corrective actions. Analyze the schedule deviations in Project 1880's Milestone table, discussing why Phase 1 and Phase 2 are completed but experienced massive delays in their estimated end dates. Provide a Python program simulating an Audit Compliance Evaluator that reads a project's compliance across multiple dimensions (Scope, Budget, Roadmap, Demo Plan) and assigns a health status (Good, Satisfactory, Weak, Critically Deficient) based on the glossary rules from the handouts.
Discuss the transition from technical engineering process areas (Module 04) to the Process Management Process Area (Module 05). Specifically, explain the role of benchmarking in optimizing process reviews, and detail why a structured Project Management (PM) Framework is essential to avoid arbitrary software development. Provide a Python script that simulates a simple Benchmarking Registry where an organization retrieves, amends, and registers successful process models from literature or other companies.
Provide a detailed architectural analysis of Software Project Tracking and Control as described in Module 05. In your response:
1. Explain the role of project planning as a prerequisite to project tracking and control.
2. Discuss why administrative overhead (such as Project Management and Testing) must be added to pure technical development effort to obtain a realistic total effort estimation.
3. Describe how 'Total Man Days' is calculated and why this is a critical metric for schedule baselining.
4. Write a Python program that models a Project Planner and Tracker. The program should sum task efforts, append testing/management overhead, convert hours to man-days based on configurable workday shifts, and track task statuses (such as Pending, WIP, and Completed).
Analyze the mechanics of 'Project Tracking and Control' under CMMI. Explain why project planning is a mandatory prerequisite to project monitoring, discuss the role of daily standups (SCRUM) versus weekly status meetings in maintaining schedule alignment, and analyze the schedule variance for Project 1880 based on the contract start/end dates and the actual/estimated dates provided in the handouts. Provide a Python class representing a WeeklyStatusTracker that parses status report attributes, calculates starting delay in days, calculates ending slip in days, and outputs a diagnostic status warning.