Unit-I: Introduction to Software Project Management (SPM)

1. Introduction to Software Project Management (SPM)

Definition of a Software Project (SP): A software project is a complex endeavor to develop
software systems or applications, involving various activities such as planning, coding, testing,
and deployment.
SP Vs. Other Types of Projects:
Invisibility: Unlike physical projects, software cannot be seen or touched.
Complexity: Software projects often involve complex algorithms and integrations.
Conformity: Software must conform to a vast range of external interfaces and user
requirements.
Flexibility: Software projects need to be adaptable to changing requirements and
technologies.
Activities Covered by SPM: Planning, scheduling, resource allocation, monitoring and control,
risk management, quality assurance, and project closure.

2. Software Project Categories

Compulsory vs. Voluntary Users:
Compulsory Users: Users required to use the software, such as employees in an
organization.
Voluntary Users: Users who choose to use the software, like customers in the market.
Information System vs. Embedded Systems:
Information System: Systems that manage and process data (e.g., databases, ERP).
Embedded Systems: Software integrated into hardware devices (e.g., automotive control
systems).
Objectives vs. Products:
Objective-Driven: Projects focused on achieving specific goals.
Product-Driven: Projects focused on developing a particular product.

3. Project Scheduling and Planning

Project Scheduling: Establishing timelines for project tasks and milestones.
Defining a Task Set and Task Network:
Task Set: A comprehensive list of all tasks required to complete the project.
Task Network: A visual representation of task dependencies and sequences.
Scheduling: Allocating time and resources to tasks to ensure timely project completion.
Earned Value Analysis Indicators:
 Planned Value (PV): The budgeted cost for work scheduled.
Earned Value (EV): The budgeted cost for work performed.
Actual Cost (AC): The actual cost incurred for work performed.

4. Project Elements
Scope: The boundaries and deliverables of the project.
Time: The schedule for project tasks and milestones.
Cost: The budget and financial resources for the project.
Quality: The standards and criteria for project deliverables.
Human Resources: The team members and their roles.
Communication: The flow of information within the project.
Risk: Potential issues that could impact the project.
Procurement: Acquiring necessary resources and services.
Stakeholders: Individuals or groups with an interest in the project.

5. Work Breakdown Structure (WBS)

Definition: A hierarchical decomposition of the total scope of work to accomplish project
objectives.
Characteristics:
Breaks down project into smaller, manageable components.
Ensures all aspects of the project are covered.
Facilitates resource allocation and scheduling.
Issues:
Can be time-consuming to create.
Requires thorough understanding of project scope.
Advantages:
Clarifies project scope and deliverables.
Improves project planning and control.
Enhances communication and accountability.
Limitations:
Can become overly complex for large projects.
May require frequent updates as project evolves.

6. Selecting a Project
Criteria: Feasibility, alignment with strategic goals, resource availability, potential risks, and
expected benefits.
 Process: Evaluate project proposals, conduct feasibility studies, prioritize projects, and obtain
stakeholder approval.

7. Identifying Project Scope and Objectives

Scope: Defines what is included and excluded in the project.
Objectives: Specific, measurable goals that the project aims to achieve.

8. Identifying Project Infrastructure

Resources: Human, financial, and technical resources needed.
Tools: Software, hardware, and methodologies required.
Environment: Physical and virtual environments necessary for project execution.

9. Analyzing Project Characteristics

Size: Scale of the project in terms of resources and duration.
Complexity: Level of difficulty and intricacy involved.
Dependencies: Interdependencies between tasks and external factors.
Risks: Potential challenges and uncertainties.

10. Identifying Project Products and Activities

Products: Tangible deliverables produced by the project.
Activities: Tasks and actions required to create project deliverables.

Unit-II: Project Estimation and Evaluation

1. Software Project Estimation
Definition: The process of predicting the effort, time, and cost required to complete a software
project.
Techniques: Expert judgment, analogy-based estimation, parametric models, and bottom-up
estimation.

2. Decomposition Techniques
Definition: Breaking down the project into smaller, manageable components for estimation.
Steps:
Understand the Scope: Clearly define what needs to be done.
Determine Software Size: Measure size using lines of code (LOC) or function points.
 Break Down SDLC Activities: Divide the software development life cycle (SDLC) into
phases and tasks.
Compare and Consider Estimates: Ensure there is no vast divergence in estimates, check
scope and data.
Reconcile Estimates: Address discrepancies and finalize estimates.

3. Empirical Estimation Models

Definition: Use historical data and statistical techniques to estimate project parameters.
COCOMO Model:
Constructive Cost Model (COCOMO): Estimates effort and cost based on project size and
complexity.
Types: Basic, Intermediate, and Detailed.
Formula: E = a × (KLOC)b × M , where E is effort, KLOC is thousands of lines of
code, a and b are constants, and M is a multiplier based on project attributes.

4. Estimation for Object-Oriented Projects

Factors:
Class Count: Number of classes in the system.
Object Complexity: Complexity of the interactions between objects.
Inheritance Levels: Depth of the inheritance tree.
Reuse: Amount of reused code or components.
Estimation Process: Adjust traditional estimation techniques to account for the unique aspects of
object-oriented development.

5. Estimation for Agile Development

Techniques:
User Story Points: Measure the complexity of user stories.
Velocity Tracking: Measure the team's productivity over iterations.
Iterative Planning: Regularly update estimates based on progress and new information.

6. Estimation for Web Engineering Projects

Considerations:
Page Complexity: Complexity and functionality of web pages.
Content Volume: Amount of content and data processing required.
User Interaction: Level of interactivity and user interface complexity.
 Estimation Techniques: Use a combination of function points, story points, and expert judgment
tailored to web-specific factors.

7. Cost Benefit Analysis

Definition: A financial evaluation to compare the benefits and costs of a project.
Steps:
Identify Costs: Include all direct, indirect, and opportunity costs.
Identify Benefits: Quantify financial and non-financial benefits.
Compare: Assess whether benefits outweigh costs.

8. Cash Flow Forecasting

Definition: Predicting the inflow and outflow of cash to ensure project financial viability.
Process: Estimate future cash receipts and payments, and create a cash flow statement.

9. Cost Benefit Evaluation Techniques

Methods:
Payback Period: Time required to recover the initial investment.
Discounted Cash Flow (DCF): Present value of future cash flows.
Net Present Value (NPV): Difference between the present value of benefits and costs.
Internal Rate of Return (IRR): Discount rate that makes NPV zero.

10. Risk Evaluation

Definition: Assessing the potential risks that could impact the project.
Steps: Identify risks, analyze their impact and probability, and prioritize them.

11. Selection of an Appropriate Project Report

Criteria: Should effectively communicate project status, progress, risks, and issues to
stakeholders.
Types: Status reports, progress reports, risk reports, and final project reports.

12. Choice of Process Model

Factors: Project requirements, complexity, risk tolerance, stakeholder preferences.
Models:
Waterfall: Sequential phases with clear milestones.
Spiral: Iterative cycles focusing on risk management.
Agile: Iterative and incremental development with flexibility.
 RAD (Rapid Application Development): Focus on quick development and user feedback.

13. Structured Methods

Definition: Formalized approaches and methodologies for systematic project management.
Examples: SSADM (Structured Systems Analysis and Design Method), V-Model.

14. Rapid Application Development (RAD)

Focus: Quick development through iterative prototyping and user feedback.
Phases: Requirements planning, user design, construction, and cutover.

15. Waterfall
Approach: Linear and sequential.
Phases: Requirements, design, implementation, testing, deployment, maintenance.

16. Spiral Models

Approach: Combines iterative development with systematic risk management.
Phases: Planning, risk analysis, engineering, evaluation.

17. Prototyping Delivery

Definition: Developing functional prototypes to gather user feedback and refine requirements.
Process: Build prototype, user evaluation, refine based on feedback, iterate until final product.

18. Albrecht Function Point Analysis

Definition: Measuring software size based on functional components like inputs, outputs, and
data files.
Process: Identify and count function points, use them to estimate effort and cost.

Unit-III: Activity Planning and Risk Management

1. Activity Planning
Objectives of Activity Planning:
Ensure all tasks are identified and allocated.
Establish a timeline for project completion.
Allocate resources effectively.
Identify dependencies and critical path.
 Project Schedule:
A timeline that outlines when tasks and milestones should be completed.
Helps manage time and ensure timely project delivery.
Projects and Activities:
Projects: Large endeavors with defined objectives.
Activities: Smaller tasks that contribute to project completion.
Sequencing and Scheduling Activities:
Sequencing: Determining the order of activities.
Scheduling: Allocating time and resources to activities.

2. Network Planning Model

Definition: A visual representation of project activities and their dependencies.
Purpose: Helps identify the sequence of tasks, their dependencies, and the critical path.

3. Network Diagrams
Types:
CPM (Critical Path Method): Used to determine the longest path of dependent tasks.
Bar Charts (Gantt Charts): Visual representation of task timelines.
PERT (Program Evaluation and Review Technique): Focuses on task durations and
uncertainties.
Activity-on-Arrow (AOA):
Represents activities as arrows.
Nodes represent start and end points.
Activity-on-Node (AON):
Represents activities as nodes.
Arrows show dependencies between activities.

4. Critical Path Method (CPM)

Definition: A method to identify the longest sequence of tasks in a project.
Importance: Determines the minimum project duration.
Steps:
List all activities.
Determine dependencies.
Draw the network diagram.
Identify the longest path (critical path).
5. PERT (Program Evaluation and Review Technique)
Definition: A statistical tool used to analyze task durations with uncertainties.
Steps:
Define tasks and milestones.
Estimate three durations: optimistic, pessimistic, and most likely.
Calculate the expected duration using the formula:

O + 4M + P
Expected Time (TE) =
6
​

Construct the network diagram.

Analyze the critical path.

6. Activity-on-Arrow Network vs. Activity-on-Node Network

Feature Activity-on-Arrow (AOA) Activity-on-Node (AON)

Representation Activities as arrows Activities as nodes

Nodes Events/milestones Start/end of activities

Usage Traditional CPM and PERT Modern project management

Complexity Simpler for small projects Easier for complex projects

Flexibility Less flexible for changes More flexible for changes

7. Precedence Network
Definition: A diagram showing the sequence of project activities with nodes representing activities
and arrows representing dependencies.

8. Forward Pass vs. Backward Pass

Feature Forward Pass Backward Pass

Calculate earliest start and finish Calculate latest start and finish
Purpose
times times

Direction Left to right through the network Right to left through the network

Earliest Start Time

Start time of the first activity Calculate from latest finish times
(ES)
 Feature Forward Pass Backward Pass

Earliest Finish Time

ES + Duration Calculate from latest start times
(EF)

Identifies minimum project

Impact Identifies flexibility in scheduling
duration

9. Forward Pass
Definition: A technique to determine the earliest start (ES) and finish (EF) times for each activity
in a project.
Process:
Start with the first activity.
Calculate ES for each activity: ES
= EF of predecessor + 1.
Calculate EF: EF = ES + Duration − 1.
Continue to the end of the network.

10. Backward Pass

Definition: A technique to determine the latest start (LS) and finish (LF) times for each activity in a
project.
Process:
Start with the last activity.
Calculate LF for each activity: LF
= LS of successor − 1.
Calculate LS: LS = LF − Duration + 1.
Continue to the beginning of the network.

11. Critical Path

Definition: The longest path through the project network, determining the shortest time to
complete the project.
Importance: Any delay on the critical path delays the entire project.
Identification:
Use forward and backward pass calculations.
The path with zero slack/float is the critical path.

12. Risk and Risk Types

Definition: Potential events or conditions that can negatively impact a project.
Types:
 Technical Risks: Issues with technology, performance, or complexity.
Project Management Risks: Poor planning, scheduling, or resource allocation.
Organizational Risks: Changes in organizational structure or policies.
External Risks: Market changes, legal issues, or natural disasters.
Financial Risks: Budget overruns or funding issues.

13. Risk Breakdown Structure (RBS)

Definition: A hierarchical representation of project risks.
Purpose: Helps identify, categorize, and manage risks.
Levels: Broad categories (e.g., technical, management, external) broken down into specific risks.

14. Risk Management Process

Steps:
Risk Identification: Identify potential risks.
Risk Analysis: Assess the impact and probability of each risk.
Risk Prioritization: Rank risks based on severity.
Risk Response Planning: Develop strategies to mitigate, transfer, accept, or avoid risks.
Risk Monitoring and Control: Continuously monitor and manage risks throughout the
project lifecycle.

15. Evaluating Schedule Risk using PERT

Definition: Using PERT to evaluate the uncertainties in task durations and their impact on the
project schedule.
Steps:
Define task durations with optimistic, pessimistic, and most likely estimates.
Calculate the expected duration for each task.
Construct the PERT network diagram.
Identify the critical path and assess the probability of meeting deadlines using statistical
analysis.

Unit-IV: Resource Allocation and Monitoring & Control

1. Resource Allocation
Definition: The process of assigning and managing resources (people, equipment, money)
needed to complete project tasks.
Steps:
 Identify required resources.
Assign resources to specific tasks.
Optimize resource usage to prevent over-allocation or underutilization.

2. Monitoring the Control

Definition: The ongoing process of tracking project progress to ensure it stays on schedule and
within budget.
Activities:
Track performance against the project plan.
Identify variances.
Implement corrective actions to address issues.

3. The Nature of Resources

Types:
Human Resources: Project team members with specific skills.
Material Resources: Physical items needed for the project.
Financial Resources: Budget and funding required.
Informational Resources: Data and documentation needed for project tasks.
Characteristics:
Resources are limited and need efficient management.
Proper resource allocation is critical for project success.

4. Identifying Resource Requirements

Process:
Analyze project tasks and determine what resources are needed.
Estimate the quantity of each resource.
Identify specific skills and competencies required.

5. Visualizing Progress
Techniques:
Gantt Charts: Visual representation of the project schedule showing task durations and
dependencies.
Progress Reports: Regular updates on project status.
Burn-Down Charts: Track work remaining against time in Agile projects.
6. Project Tracking
Purpose: To ensure the project stays on track by monitoring progress, identifying issues, and
making necessary adjustments.
Methods:
Regular status meetings.
Performance metrics and key performance indicators (KPIs).
Project management software tools.

7. Status Reports
Content:
Overview of current project status.
Completed tasks and milestones.
Upcoming tasks and deadlines.
Issues and risks.
Budget and resource status.
Frequency: Typically generated on a weekly or monthly basis.

8. Milestone Analysis
Definition: The process of evaluating project milestones to assess progress and identify any
deviations from the plan.
Steps:
Define key milestones at the beginning of the project.
Track progress towards milestones.
Analyze any delays or deviations and take corrective actions.

9. Actual Versus Estimated Analysis of Effort and Schedule

Definition: Comparing the actual effort and schedule with the estimated values to assess project
performance.
Purpose: To identify variances and understand their causes.
Process:
Collect actual data on effort and time spent on tasks.
Compare with initial estimates.
Analyze differences and adjust future estimates or plans accordingly.

10. Defining Software Quality Attributes

Key Attributes:
 Functionality: The ability of the software to perform its intended functions.
Reliability: The consistency of the software's performance.
Usability: How easy it is for users to interact with the software.
Efficiency: The software's ability to use resources effectively.
Maintainability: Ease of making changes to the software.
Portability: The software's ability to operate in different environments.

11. ISO 9126

Definition: An international standard for software quality, defining six quality characteristics.
Characteristics:
Functionality: Suitability, accuracy, interoperability.
Reliability: Maturity, fault tolerance.
Usability: Understandability, learnability.
Efficiency: Time behavior, resource utilization.
Maintainability: Analyzability, changeability.
Portability: Adaptability, installability.

12. Software Quality Measures

Types:
Product Metrics: Measure characteristics of the software product (e.g., defect density, code
complexity).
Process Metrics: Measure the effectiveness of the development process (e.g., cycle time,
process adherence).
Project Metrics: Measure project management performance (e.g., schedule variance,
budget variance).

13. Project Closure Analysis

Definition: The final phase of a project, involving the formal completion and evaluation of the
project.
Activities:
Verify that all project deliverables are completed.
Obtain formal acceptance from stakeholders.
Conduct a post-project review.
Document lessons learned and best practices.
14. The Role of Closure Analysis
Purpose:
Ensure that all project objectives have been met.
Evaluate project performance and identify areas for improvement.
Provide closure for the project team and stakeholders.

15. Performing Closure Analysis

Steps:
Final Deliverable Verification: Ensure all deliverables meet requirements and are accepted
by the client.
Performance Evaluation: Assess project performance against initial goals and objectives.
Document Lessons Learned: Capture insights and lessons learned for future projects.
Formal Closure: Officially close the project and release resources.

By focusing on these detailed notes with highlighted keywords, you can efficiently cover the essential
aspects of Unit-IV for your exam. Good luck!