(SEM -VII) THEORY EXAMINATION 2018-19 SOFTWARE PROJECT MANAGEMENT

SECTION – A

(Attempt all questions in brief – 2 × 10 = 20 marks)

(a) Difference between Task and Activity

A task is a small unit of work that needs to be completed as part of a project, whereas an activity is a group of related tasks performed to achieve a specific project objective. Activities are broader in nature and are often broken down into tasks for better planning and control.

(b) Define Project and Management

A project is a temporary effort undertaken to create a unique product, service, or result within a defined time and budget. Management is the process of planning, organizing, directing, and controlling resources to achieve specific goals efficiently and effectively.

(c) Risk Assessment Activities

Risk assessment activities involve identifying possible risks in a project, analyzing their likelihood and impact, and prioritizing them. These activities help project managers prepare mitigation plans to reduce the effect of risks on cost, schedule, and quality.

(d) How Software Projects Differ from Other Engineering Projects

Software projects differ because software is intangible, highly flexible, and continuously evolving. Unlike traditional engineering projects, software development involves frequent requirement changes, higher uncertainty, and strong dependence on human skills rather than physical materials.

(e) Difference between Test Plan and Test Cases

A test plan is a high-level document that defines the testing strategy, scope, objectives, resources, and schedule. Test cases are detailed step-by-step instructions used to verify specific software functionalities based on requirements.

(f) Understanding of Automation Testing

Automation testing uses tools and scripts to automatically execute test cases without manual intervention. It improves testing speed, accuracy, and repeatability, especially for regression and large-scale testing.

(g) Advantages of Pair Programming

Pair programming involves two programmers working together at one workstation. It improves code quality, reduces errors, enhances knowledge sharing, and promotes better team collaboration.

(h) Black Box Testing

Black box testing is a testing method where the internal structure of the software is not known to the tester. The focus is on validating inputs and outputs based on functional requirements.

(i) CPI and SPI

Cost Performance Index (CPI) measures cost efficiency by comparing earned value to actual cost. Schedule Performance Index (SPI) measures schedule efficiency by comparing earned value to planned value.

(j) Desk Checking

Desk checking is a manual process of reviewing source code or design documents to detect errors before execution. It helps find logical and syntactical mistakes early in development.

SECTION – B

(Attempt ANY THREE – 10 × 3 = 30 marks)

(a) Work Breakdown Structure (WBS) in Software Projects

A Work Breakdown Structure is a hierarchical decomposition of a software project into manageable components. It divides the project into phases, deliverables, and tasks, making planning, scheduling, cost estimation, and responsibility assignment easier. For example, a software project may be broken into requirement analysis, design, coding, testing, and maintenance.

(b) Characteristics of Good Software Metrics and Project Monitoring

Good software metrics should be simple, objective, measurable, and relevant to project goals. Metrics help in monitoring progress, quality, productivity, and cost. Project monitoring uses these metrics to compare actual performance with planned performance and take corrective actions when deviations occur.

(c) Software Configuration Management (SCM) Planning

SCM planning involves identifying configuration items, version control, change control, and configuration audits. SCM helps manage changes systematically, prevents inconsistencies, and ensures software integrity. Effective SCM improves traceability and team coordination.

(d) SEI-CMM Process Model

The SEI-CMM model defines five maturity levels: Initial, Repeatable, Defined, Managed, and Optimizing. Each level represents increasing process maturity. Key Process Areas guide organizations in improving software process quality and predictability.

SECTION – C

(Attempt ANY ONE – 10 marks)

(a) Software Project Scheduling and Estimation

Software project scheduling involves identifying tasks, estimating durations, assigning resources, and defining dependencies. Estimation techniques such as expert judgment, analogy, and algorithmic models help determine effort, cost, and time. Proper scheduling ensures timely delivery and efficient resource utilization.

(b) Risk Management Process in Software Projects

Risk management is a continuous process that includes risk identification, analysis, planning, monitoring, and control. It helps reduce uncertainties and increases the chances of project success by preparing proactive response strategies.

(c) Quality Management in Software Projects

Quality management ensures that the software meets customer requirements and standards. It includes quality planning, assurance, and control. Activities such as reviews, testing, and audits help maintain high software quality throughout the project lifecycle.