Software Project Management

This Engineering360 topic introduces SPM for B.Tech SE papers. You outline manager responsibilities, state the COCOMO effort form, and explain why estimation uncertainty and risk registers matter.

COCOMO basic: (organic/semi-detached/embedded constants differ)
schedule $months \approx c \times (Effort)^d$ (model-specific exponents)
earned value idea: compare planned vs completed work for progress

Symbol and sign-convention guide for the equations listed under Key relations & formulas.

Keep SI units consistent end-to-end (do not mix mm with m, or N with kN, in one substitution).

Symbol guide:
• Use symbols exactly as defined in your prescribed text for this unit.

Sign convention: lock the textbook’s positive sense (force, moment, rotation, heat, or flow) before substituting. A correct symbolic setup still earns method marks in most Indian university papers even if arithmetic slips.

Write relations with symbols exactly as in Software Engineering — Roger Pressman before substituting numbers.

Building software is a project: finite goal, constraints, and resources. Managers break work down, estimate size/effort, schedule dependencies, assign people, and track progress against plans. COCOMO-style models relate effort to delivered size with mode-dependent constants; they are starting points, not truths, until historical data calibrates them. Risk management lists threats (staff loss, requirement churn, technical unknowns) with mitigation. Without SPM, even good engineers deliver late or incomplete systems.

State assumptions explicitly before using any relation for software project management — steady state, uniform properties, linear elastic material, ideal gas, incompressible flow, etc., as applicable.

Wrong assumptions invalidate the entire solution even when the formula is correct. In Software Engineering viva and GATE descriptive questions, listing valid assumptions often earns separate marks.

1. Read the question and list given data with SI units (common in Software Engineering papers).
2. Draw a neat labelled diagram where applicable — examiners in Indian universities award diagram marks even when arithmetic slips.
3. Identify which relation from this topic applies to software project management.
4. Use equation 1: .
5. Use equation 2: schedule $months \approx c \times (Effort)^d$.
6. Substitute values, compute, and verify units and sign (direction).
7. State conclusion in one line — e.g. safe/unsafe, stable/unstable, feasible/infeasible.

Software Project Management appears in product teams and IT services. In Indian it software curricula this topic is tested because it connects theory to SDLC, requirements, design, quality, and maintenance.

GATE and semester exams often combine software project management with earlier units — revise prerequisites before attempting mixed problems.

Industry interview panels sometimes ask: "Where did you use software project management?" — answer with a lab, mini-project, or plant visit example if possible.

• Memorising COCOMO constants without knowing Effort = a(KLOC)^b structure
• Treating estimates as guarantees
• Ignoring people and risk factors when discussing schedule slips

Before attempting software project management problems, confirm you can:

1. SPM covers estimation, scheduling, risk, people, and monitoring
2. COCOMO estimates effort from size; accuracy needs calibrated data
3. Project manager plans and tracks; does not replace technical ownership

Revise the solved examples in Software Engineering — Roger Pressman and one previous-year GATE or university paper for this unit.