SECTION A
(2 × 10 = 20 Marks)
a) Explain the primary objectives of Software Project Management
The primary objective of Software Project Management is to ensure that software projects are completed within the specified time, cost, and quality constraints. It focuses on effective planning, resource utilization, risk control, and continuous monitoring so that customer requirements are met and project goals are achieved efficiently.
b) Discuss different types of project plans
Project plans are formal documents that guide the execution of a project. These include the project management plan, quality plan, risk management plan, configuration management plan, and communication plan. Each plan addresses a specific aspect of the project and collectively ensures systematic project execution.
c) Explain the purpose of network diagrams in project scheduling
Network diagrams are used to represent project activities and their dependencies graphically. They help project managers identify the sequence of activities, estimate project duration, and analyze critical paths, thereby enabling effective scheduling and control.
d) Explain the role of the critical path in CPM
The critical path represents the longest sequence of dependent activities in a project. It determines the minimum project completion time, and any delay in critical path activities directly affects the project schedule. Therefore, it plays a crucial role in schedule management.
e) Define SPI
Schedule Performance Index is a measure used in Earned Value Analysis to assess schedule efficiency. It is calculated as the ratio of earned value to planned value and indicates whether the project is ahead of or behind schedule.
f) Explain Schedule Variance
Schedule Variance represents the difference between earned value and planned value. A positive variance indicates that the project is ahead of schedule, while a negative variance indicates schedule delay.
g) Define Software Quality Assurance
Software Quality Assurance is a systematic process that ensures software development follows defined standards, procedures, and processes. It focuses on preventing defects rather than detecting them after development.
h) Explain Program verification
Program verification is the process of checking whether a software program correctly implements its specified requirements. It involves reviewing code, testing logic, and validating outputs to ensure correctness and reliability.
i) Discuss change request management
Change request management is the process of handling modifications to project requirements or scope. It involves evaluating the impact of changes on cost, schedule, and quality before approval to ensure controlled project evolution.
j) Define Risk
Risk is an uncertain event or condition that may have a positive or negative impact on project objectives. In software projects, risks commonly affect cost, schedule, scope, and quality.
SECTION B
(Attempt any three – answers provided for all)
2(a) Software Project Management Plan (SPMP)
A Software Project Management Plan is a comprehensive document that defines how a software project will be planned, executed, monitored, and controlled. It includes sections such as project scope, organization, scheduling, risk management, quality assurance, configuration management, and communication. Each section ensures clarity, coordination, and effective control throughout the project lifecycle.
2(b) Work Breakdown Structure (WBS)
A Work Breakdown Structure is a hierarchical decomposition of project work into manageable components. It helps in estimating cost, scheduling activities, assigning responsibilities, and tracking progress. WBS can be product-based, phase-based, or task-based. The WBS dictionary provides detailed descriptions of each work element, including scope, deliverables, and responsibilities.
2(c) Error Tracking and Cost Variance
Error tracking involves identifying, recording, and resolving defects throughout the software lifecycle. Cost variance measures the difference between actual cost and earned value, helping managers identify budget overruns or savings and take corrective actions.
2(d) Testing objectives and levels of testing
Testing aims to detect defects, verify functionality, and ensure software quality. Levels of testing include unit testing, integration testing, system testing, and acceptance testing, each validating the software at different stages of development.
2(e) Types of risks in software projects
Software projects face technical risks, schedule risks, cost risks, personnel risks, and external risks. Effective risk identification and mitigation strategies are essential to minimize project failure.
SECTION C
3(a) Software Project Management and SPM framework
Software Project Management is the discipline of planning, organizing, and controlling software development activities. The SPM framework includes project planning, scheduling, monitoring, quality management, risk management, and configuration management to ensure successful project delivery.
3(b) Objectives of software project planning
Software project planning aims to define scope, estimate resources, schedule activities, manage risks, and establish quality goals. It is critical because poor planning leads to cost overruns, delays, and project failure.
4(a) Project life cycle vs product life cycle
The project life cycle includes initiation, planning, execution, monitoring, and closure, while the product life cycle covers concept, development, deployment, maintenance, and retirement. Projects focus on delivery, whereas products focus on long-term value.
4(b) Milestone charts and Gantt charts
Milestone charts represent key events in a project, while Gantt charts display activities against time. Both tools help project managers monitor progress and identify schedule deviations.
5(a) Earned Value Analysis (EVA)
Earned Value represents the value of work completed at a given time. EVA integrates cost and schedule performance using metrics such as EV, PV, and AC, providing early warning signals for project issues.
5(b) Software reviews
Software reviews are systematic examinations of project artifacts to detect defects early. Types include walkthroughs, inspections, technical reviews, and management reviews.
6(a) Software quality attributes
Software quality attributes include reliability, usability, efficiency, maintainability, and portability. These attributes directly influence user satisfaction, performance, and long-term success of the software product.
6(b) SEI Capability Maturity Model
The SEI Capability Maturity Model describes five maturity levels ranging from initial to optimizing. It provides a framework for improving software processes and organizational capability.
7(a) Risk management in software projects
Risk management involves identifying, analyzing, prioritizing, and mitigating risks. Early risk management reduces uncertainty, improves decision-making, and increases the likelihood of project success.
7(b) CASE tools
CASE tools support software development and project management by automating design, coding, testing, documentation, and configuration management. They improve productivity, consistency, and quality.
