Introduction
Building software is not just about writing code. A large system involves many people, months of effort, tight budgets, and shifting requirements. Software Project Management (SPM) is the discipline of planning, organizing, staffing, directing and controlling a software project so that it is delivered on time, within budget, and to the required quality. Software metrics are the measurements we use to make those management decisions objective rather than guesswork — how big is the software, how much effort will it take, how complex is the code, how good is the quality.
For BCS, Bank IT, and IT-officer exams this topic is a reliable source of marks because it is calculative and definition-heavy: examiners love COCOMO effort formulas, Function Point counting, cyclomatic complexity, the 4 P's, and Critical Path / PERT questions. Master the formulas and you can score the numeric MCQs that many candidates leave blank.
Learning objectives
- Define software project management and explain the 4 P's (People, Product, Process, Project).
- Distinguish size-oriented, function-oriented, and object-oriented metrics and know process vs product vs project metrics.
- Estimate software size using Lines of Code (LOC) and Function Points (FP) and convert between them.
- Apply the COCOMO model (Basic, Intermediate, Detailed) to compute effort, development time, and staffing.
- Measure code complexity with McCabe's cyclomatic complexity and understand Halstead metrics.
- Build a project schedule and find the critical path using PERT/CPM, and read a Gantt chart.
- Understand risk management (RMMM) and quality metrics like defect density and DRE.