RAGHU ENGINEERING COLLEGE

Autonomous
(Approved by AICTE, New Delhi, Accredited by NBA (CIV, ECE, MECH, CSE), NAAC with ‘A+’ grade
& Permanently Affiliated to JNTU-GV Vizianagaram)
Dakamarri, Bheemunipatnam Mandal, Visakhapatnam Dist. – 531 162 (A.P.)
Ph: +91-8922-248001, 248002 Fax: + 91-8922-248011
e-mail: principal@[Link] website: [Link]

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

ACADEMIC YEAR : 2025-2026 REGULATION: AR20
th
YEAR & SEMESTER: IV Year CSE sem-1 (2022 Admitted Batch)
NAME OF THE COURSE: SPM [PE-III] COURSE CODE: 20CS7331
SOFTWARE PROJECT MANAGEMENT
UNIT-II Syllabus
SW Project evaluation & Planning: Tools and techniques, funds flow analysis,
cost-benefit analysis, risk evaluation, project portfolio management, benefit
management, Gathering requirements, Identification of project scope, step wise
project planning, case study.
Software project estimation: Software effort estimation techniques, cost
estimation, effect of schedule compression, Capers Jone’s estimation.

Q(1)Discuss various tools and techniques used in software project evaluation

and planning.
Explain how Gantt charts, PERT/CPM, SWOT analysis, and work
breakdown structures (WBS) assist in effective project planning. Illustrate
your answer with relevant examples.
A: Software Project Evaluation and Planning is a critical phase in the software
development life cycle that determines the feasibility, risks, cost, schedule, and
scope of a project before its execution. Several tools and techniques are used to
ensure that planning is effective, efficient, and aligned with business goals. These
tools help in visualizing, analyzing, and managing different aspects of the project.

Here are some key tools and techniques commonly used in software project
evaluation and planning:
1. Gantt Charts
Definition:
A Gantt chart is a visual project management tool that displays project activities
against time. It shows start and end dates of each task and helps track project
progress.
Purpose:
 Scheduling tasks and milestones
 Monitoring project progress
  Identifying task dependencies and critical paths
Example:
In a software project to develop a mobile application, a Gantt chart might include
tasks like:
 Requirement gathering (Jan 1–Jan 10)
 UI Design (Jan 11–Jan 20)
 Coding (Jan 21–Feb 10)
 Testing (Feb 11–Feb 20)

By viewing the chart, a project manager can easily monitor whether tasks are being
completed on time or not.
2. PERT (Program Evaluation Review Technique) / CPM (Critical Path
Method)
Definition:
PERT and CPM are network-based scheduling techniques used to model project
activities and determine the minimum time needed to complete the project.

 PERT is used when time estimates are uncertain (uses optimistic,

pessimistic, and most likely estimates).
  CPM is used for projects with known activity durations.

Purpose:
 Identify the critical path (longest duration path) which directly affects
project completion time
 Estimate earliest and latest start/finish times
 Analyze task dependencies
Example:
Consider a software module development project where:
 Task A (Requirements) – 5 days
 Task B (Design) – 4 days (starts after A)
 Task C (Development) – 10 days (starts after B)
 Task D (Testing) – 6 days (starts after C)
CPM analysis will help identify the total project duration (25 days) and show that
any delay in critical tasks will delay the entire project.

3. SWOT Analysis (Strengths, Weaknesses, Opportunities, Threats)

Definition:
SWOT is a strategic planning tool used to analyze the internal and external
environment of a project or organization.
Purpose:
 Evaluate project viability
 Understand internal capabilities and external challenges
 Inform risk mitigation and strategic alignment
Example:
In a startup software project:
 Strengths: Skilled team, agile methodology
 Weaknesses: Limited budget, no in-house testers
 Opportunities: Growing demand for mobile apps
 Threats: Competitors with more resources, changing technology
This analysis guides project decisions such as whether to outsource testing or seek
investment.

4. Work Breakdown Structure (WBS)

Definition:
A WBS is a hierarchical decomposition of the total scope of a project into
manageable sections called work packages.
Purpose:
 Define and organize project scope
 Assign responsibilities
 Estimate cost and time more accurately
 Facilitate tracking and control
Example:
In a software development project:
 Level 1: Mobile App Development
 Level 2.1: Planning
 Level 2.2: Design
 Level 2.2.1: UI Design
Level 2.2.2: UX Flow
 Level 2.3: Development
 Level 2.4: Testing
 Level 2.5: Deployment
Each work package can be assigned to a team member with a defined deliverable
and timeline.
Conclusion
Each of these tools and techniques offers unique benefits in project evaluation and
planning:
 Gantt Charts provide visual time tracking and progress monitoring.
 PERT/CPM help in identifying critical activities and optimizing schedules.
 SWOT Analysis enables strategic insight into project feasibility.
  WBS facilitates scope definition and resource allocation.
By combining these tools, project managers can improve decision-making,
enhance planning accuracy, reduce risk, and increase the likelihood of successful
project delivery.

Q (2) Describe the process of funds flow analysis in software project planning.
Explain how funds flow analysis helps in identifying the financial health of a
project, budgeting, and financial decision-making. Support your answer with
a sample flow diagram.
A: Funds Flow Analysis in Software Project Planning
1. Introduction to Funds Flow Analysis
Funds Flow Analysis is a vital financial planning tool used in software project
management to understand how funds are generated and utilized during a project’s
lifecycle. It helps project managers and stakeholders analyze the movement of
funds (inflows and outflows) to evaluate the financial health, budget adequacy, and
make informed financial decisions.

2. Process of Funds Flow Analysis

The steps involved in performing a funds flow analysis are:
Step 1: Identify Sources of Funds (Inflows)
Sources of funds may include:
 Capital investment
 Internal funding from the organization
 Government grants
 Revenue from clients (milestone-based payments)
 Loans or lines of credit
Step 2: Identify Application of Funds (Outflows)
 These include all expenditures:
 Salaries of developers and project staff
 Purchase of hardware/software tools
 Infrastructure cost (servers, office space)
 Outsourcing and consultancy
 Overheads (utilities, administration)
 Training and development
Step 3: Prepare Funds Flow Statement
Create a statement that matches sources against their application to understand net
funds available or deficit.
Step 4: Analyze the Flow
 Compare planned vs. actual cash movement at regular intervals to:
  Monitor overspending
 Predict future shortages
 Reallocate funds if necessary
Step 5: Decision-making
Based on the analysis:
 Adjust budgets
 Request additional funding
 Reduce scope or reschedule project activities

3. Importance of Funds flow Analysis

Aspect Description
Budgeting Ensures funds are allocated to high-priority tasks.
Cash Flow Management Prevents cash shortages by timely forecasting.
Financial Health Monitoring Detects inefficiencies or overruns early.
Investor Confidence Helps justify funding requests with clear projections.
Risk Mitigation Identifies financial bottlenecks early in the process.

4. Sample Funds Flow Diagram

Below is a simple visual representation of funds flow in a software project:
+----------------------+
| Sources of Funds |
+----------------------+
| |
+-----------+ +------------+
| |
+----------------+ +------------------+
| Client Payments| | Internal Funding |
+----------------+ +------------------+
| |
+-----------+---------------+
|
+--------------------+
| Project Account |
+--------------------+
|
+----------+-----------+
| |
+---------------+ +-----------------+
| Salaries/HR | | Infrastructure |
+---------------+ +-----------------+
| |
+---------------+ +-----------------+
| Licenses/Tools| | Misc. Overheads |
+---------------+ +-----------------+

5. Example Scenario
Assume a software project has the following:
 Total inflow: ₹20,00,000 (client milestone payments + internal funding)
 Outflows:
Salaries:₹10,00,000
Tools and licenses:₹3,00,000
Infrastructure:₹2,50,000
Miscellaneous:₹1,50,000
Total Outflows =₹17, 00,000
Net Funds Available = ₹20,00,000 – ₹17,00,000 = ₹3,00,000
This ₹3, 00,000 can be:
 Used as contingency reserve
 Reallocated to speed up delivery
 Invested in employee training

6. Conclusion
Funds Flow Analysis enables effective resource planning, budget control, and
financial stability in software projects. By tracking the movement of funds and
analyzing trends, project managers can ensure timely completion without financial
bottlenecks, ultimately improving the project's success rate.

Q(3)Explain cost-benefit analysis and its role in software project selection and
prioritization.
Provide a detailed explanation of different types of costs and benefits
involved, and discuss how ROI, NPV, and payback period are calculated and
interpreted.
A: Cost-Benefit Analysis (CBA) is a systematic approach to estimate the strengths
and weaknesses of alternatives used to determine options that provide the best
approach to achieve benefits while preserving savings.
In software project planning, CBA helps to:

 Select the most economically viable project,

 Determine the priority of various projects in a portfolio,
 Justify the investment to stakeholders and management.

Types of Costs in Software Projects

1. Development Costs:
 Salaries for developers, testers, designers, project managers
 Cost of tools, IDEs, cloud servers, third-party APIs
2. Operational Costs: Hosting costs, license renewals, system maintenance, IT
support
3. Training Costs: Training for users, onboarding team members
4. Opportunity Costs: Cost of not choosing another alternative
5. Hidden Costs: Delay costs, cost of poor quality or rework

Types of Benefits
Tangible Benefits:
 Increased revenue from the software
 Reduced processing time, lower manpower cost
 Cost savings from automation
Intangible Benefits:
 Improved customer satisfaction
 Enhanced brand reputation
 Employee morale and productivity

Financial Metrics Used

1. ROI (Return on Investment):
ROI= (Net Profit/total investment) x100

2. NPV (Net Present Value)

NPV=∑(Rt/(1+i)t)=C0
Where:
𝑅t= Net cash inflow during the period t
i = Discount rate (interest rate)
t = Time period
C0= Initial investment
If NPV > 0 → Project is profitable
3. Payback Period:
Payback Period=Time taken to recover the initial investment from net cash flows

Real-Time Example: HR Management Software for a Mid-Sized Company

� Project Goal:
Automate HR functions like attendance, payroll, and leave management.

Estimated Project Costs:

| Item | Cost (INR) |
| ----------------------------- | ---------- |
| Developer Salaries (6 months) | ₹12, 00,000 |
| Software Tools & Licenses | ₹1, 00,000 |
| Server & Hosting (1 year) | ₹50,000 |
| Training for HR staff | ₹50,000 |
| **Total Initial Investment** | ₹14, 00,000 |

Estimated Benefits:
| Benefit | Annual Value (INR) |
| ---------------------------- | ------------------ |
| Reduced HR manpower cost | ₹5,00,000 |
| Faster processing saves time | ₹2,00,000 |
| Error reduction | ₹1,00,000 |
| **Total Annual Benefits** | ₹8,00,000 |

ROI Calculation:
ROI=(8,00,000-14,00,00)/14,00,000 X100=-42.8%(in Year 1)
ROI improves in later years as software costs reduce.

NPV Calculation:
Assume a discount rate of 10%, benefits expected for 5 years.
NPV=(8,00,000)/(1+0.1)1+8,00,000/(1+0.1)2+……..+8,00,000/(1+0.1)5)-14,00,000
NPV≈Rs30,38,000-Rs14,00,000=Rs16,38,000Profitable project

Payback Period:
Cumulative benefits:
Year 1: ₹8,00,000
Year 2: ₹16,00,000 (crosses investment)
So, Payback Period = ~1.75 years
Role in Software Project Selection
1. Comparative Evaluation: Between multiple project proposals, the one with
higher ROI and NPV is prioritized.
2. Risk Mitigation: Low payback periods are less risky.
3. Budget Justification: Managers use CBA to secure approvals and allocate
funds.

Summary Table
Metric Value Interpretation
ROI (Year 1) -42.8% Initial loss, not uncommon
ROI (Over 5 yrs) Positive (>100%) Profitable long-term
NPV ₹16,38,000 Good investment
Payback Period 1.75 years Recovers quickly

Conclusion:
Cost-Benefit Analysis is crucial for selecting and prioritizing software projects. By
evaluating the financial feasibility through ROI, NPV, and payback period,
companies can make data-driven decisions to maximize value and minimize risk.

Q(4) What is risk evaluation in software project management?

Elaborate on different types of risks, their impact, and probability. Describe
techniques such as risk matrix, Monte Carlo simulation, and sensitivity
analysis with suitable examples.
A: Risk evaluation is the process of identifying, analyzing, and prioritizing risks
that may impact the success of a software project. It helps project managers decide
which risks to mitigate, which to monitor, and which to accept.

Key Concepts:
 Risk: An uncertain event or condition that, if it occurs, can impact one or
more project objectives.
 Risk Exposure = Probability × Impact
 Risk Evaluation helps in determining:
The likelihood of a risk occurring
The impact if the risk does occur
The overall priority of that risk
Types of Risks in Software Projects:

Risk Type Description Example

Technical Failure of technology, Incompatibility with a new
Risk complexity, unproven tools database system
Budget overruns due to Underestimating server hosting
Cost Risk
inaccurate estimates costs
Developer resignation mid-
Schedule Risk Delays in project milestones
sprint
Operational Inefficiencies in process or
Lack of skilled testers
Risk people-related issues
Product may not achieve market Product not aligned with user
Business Risk
success needs
Outside the project team's Vendor delay or change in
External Risk
control government policy
Data breaches, lack of API vulnerability exploited by
Security Risk
encryption attackers

Impact and Probability Classification

 Probability: Likelihood the risk will occur (e.g., Low, Medium, High or 0–1
scale)
 Impact: Degree to which risk will affect objectives (Cost, Time, Quality)
| Probability | Impact | Risk Exposure |
| ----------- | ----------------- | ------------- |
| High (0.9) | High (₹500,000) | ₹450,000 |
| Low (0.2) | Medium (₹300,000) | ₹60,000 |
Risk Evaluation Techniques
1. Risk Matrix (Heat Map)
Description: A 2D grid plotting Probability vs. Impact. Used to visualize and
prioritize risks.
Low Impact Medium Impact High Impact
High Probability Moderate Risk High Risk Extreme Risk
Medium Low Risk Moderate Risk High Risk
Probability
Low Probability Low Risk Low Risk Moderate Risk
Example:
Risk: Delay in UI module
Probability: Medium
Impact: High
→ Falls in High Risk zone → Needs mitigation plan.
2. Monte Carlo Simulation
Description: A statistical technique that simulates different outcomes of a project
by running multiple scenarios (often thousands) using random variables.
Example:
Task duration estimates:
 Best case: 10 days
 Most likely: 15 days
 Worst case: 25 days
Monte Carlo simulates thousands of combinations of such estimates to produce a
probability distribution of project completion dates.
Useful in:
 Cost estimation
 Schedule prediction
 Budget forecasting
3. Sensitivity Analysis
Description: Identifies which variables (risks) have the biggest impact on the
project outcome. Also called the “What-if” analysis
Example:
In a web app project-Cost estimate is affected by:
 Server usage
 Licensing cost
 Developer productivity
Sensitivity analysis reveals:
Developer productivity has the highest impact on total cost → Requires focus.
Real-Time Example – E-commerce Mobile App Development
Risks Identified:
Risk Probability Impact (INR) Risk Exposure
Payment Gateway Integration Delay 0.4 ₹3,00,000 ₹1,20,000
Developer Resignation 0.2 ₹5,00,000 ₹1,00,000
App Rejection by App Store 0.1 ₹7,00,000 ₹70,000
Action Based on Evaluation:
 Payment Integration Delay → Mitigate: Use parallel APIs
 Developer Resignation → Plan backup resource
 App Store Rejection → Improve compliance early
Monte Carlo Outcome:
Shows 80% chance that app will be completed within 5 months and 20% chance it
will overrun.
Conclusion:
Risk evaluation helps reduce uncertainty and prepare for potential failures. By
using tools like the Risk Matrix, Monte Carlo Simulation, and Sensitivity Analysis,
project managers can:
 Prioritize high-risk elements
 Allocate resources wisely
 Make better strategic decisions

Q(5)Discuss the concept of project portfolio management.

How does portfolio management contribute to strategic alignment of software
projects? Explain the selection criteria for project portfolios and the role of
balancing risk and value.
A: Project Portfolio Management (PPM) is the centralized management of multiple
projects, programs, or initiatives that are aligned with the strategic objectives of an
organization.

Instead of treating projects individually, PPM views them as part of a portfolio to

optimize resource usage, manage risks, and maximize overall business value.

Goals of PPM:
 Align projects with strategic goals
 Maximize ROI and value delivery
 Optimize use of resources, time, and budget
 Balance risks across all projects
 Eliminate or defer low-value or conflicting projects

How Does Portfolio Management Contribute to Strategic Alignment?

Aspect Role in Strategic Alignment
Vision & Goals Ensures only those projects that support business vision are
Match approved
Prioritization Ranks projects based on how well they support key
initiatives
Resource Prevents wastage on low-priority or redundant projects
Optimization
Feedback Loop Periodic evaluation of project performance and relevance
Project Selection Criteria in Portfolio Management
To decide which projects enter the portfolio, the organization evaluates:
Criterion Description
Strategic Fit Does it align with company goals (e.g., customer
retention)?
ROI & Financial What are the expected returns, profits, cost savings?
Value
Risk Level What technical, financial, or schedule risks are involved?
Resource Demand Are the right people and tools available?
Urgency & Timing Is the project time-sensitive?
Dependencies Is it linked to other ongoing projects?

Balancing Risk and Value in a Portfolio

PPM aims to balance:
 High-Value, High-Risk Projects (e.g., new product development)
 Low-Value, Low-Risk Projects (e.g., small internal automations)
 Quick Wins (high value, low risk)
 Strategic Long-Term Bets

This balance ensures that not all resources are tied to risky ventures, while also not
missing out on innovation and long-term rewards.

Real-Time Example: IT Company Portfolio – Software Projects

Company Goal: “Improve customer engagement and operational efficiency."
Portfolio Includes 4 Projects:
Project Description Strategic Goal ROI Risk
Name Estimate Level
1. CRM Enhance current Customer High Low
System customer database satisfaction
Upgrade tool
2. AI Chatbot Launch chatbot to 24/7 customer Very High High
App automate support engagement
3. Internal HR Digitalize leave, Operational Medium Low
Portal payroll, onboarding efficiency
4. Data Real-time analytics Market-driven High Medium
Analytics for product feedback improvements
Tool
Portfolio Analysis:
1. CRM Upgrade: Low risk, reliable ROI → Quick win
2. AI Chatbot: Aligns with innovation, but high risk → Needs close monitoring
3. HR Portal: Supports internal efficiency → Moderate value, low risk → Support
project
4. Analytics Tool: Enables data-driven decisions → Strategic value

Portfolio Manager’s Actions:

 Approve all 4, but stagger resource allocation.
 Assign best team to AI Chatbot to mitigate risk.
 Monitor performance KPIs monthly.
 Review portfolio quarterly to retire, pivot, or scale projects.

Conclusion:
Project Portfolio Management helps companies:
 Choose the right projects,
 Ensure all projects are strategically aligned,
 Achieve optimal balance between risk and return,
 Use resources efficiently, and Drive long-term success.

Q(6)Define benefit management and discuss its importance in software

project success.
Explain the lifecycle of benefits management, including identification,
planning, realization, and measurement of benefits. Use a real-world software
project as a case study.
A: Benefit Management is the process of identifying, planning, measuring, and
realizing the value or advantages that a project is expected to deliver. In software
project management, it's about ensuring that the business outcomes promised by
the software are actually achieved and sustained.

Why is Benefit Management Important?

Benefit Importance
Ensures ROI Aligns project outcomes with business goals and
financial returns
Guides Decision-Making Helps stakeholders justify investment
Improves Accountability Each benefit is tracked and measured
Supports Continuous Lessons learned feed future projects
Improvement
A project may be delivered on time and within budget, but if it fails to deliver
business benefits, it is not a success.

Lifecycle of Benefits Management

1. Identification
 What benefits will this project deliver?
 Involves understanding stakeholder needs and organizational strategy.
Example:
 Increase customer retention
 Reduce manual work
 Improve decision-making with real-time data
2. Planning
 Map each benefit to project activities and define when and how it will be
achieved.
 Assign owners for each benefit.
 Define metrics for measuring success.
Example:
 Benefit: Reduce manual HR work
 Owner: HR Manager
 Metric: Number of automated tasks post-launch
3. Realization
 During and after project execution, ensure that benefits are actually
delivered.
 Involves training, change management, stakeholder engagement.
Example:
 HR staff starts using the new automated payroll system.
 Manual errors drop by 80%.
4. Measurement and Review
 Track benefits metrics against the plan.
 Determine if expected value is being realized.
 Take corrective actions or scale benefits.
Example:
 After 3 months: Time saved = 120 hours/month
 HR satisfaction score = 90%
 ROI achieved earlier than expected
Case Study: Real-World Example – Payroll Automation Software for a Mid-
sized Company
Objective: Reduce HR workload and improve payroll accuracy.

1. Benefit Identification
Identified Benefit Description
Time-saving Reduce manual payroll calculations
Error reduction Minimize payment errors and penalties
Cost savings Reduce overtime due to processing delays
Employee satisfaction On-time, error-free salaries

2. Benefit Planning
Benefit Owner Metric Timeline
Time-saving HR Hours saved per payroll 1 month post-
Manager cycle deployment
Error QA Lead % drop in salary errors 3 months
reduction
Cost savings Finance INR saved per quarter 6 months

3. Benefit Realization
 Software launched after 4 months.
 After first month:
Time per payroll run dropped from 18 hours to 5 hours
Errors decreased by 70%
HR team reported higher confidence and satisfaction
4. Benefit Measurement
Metric Before After 3 Months Result
Time per payroll 18 hours 4.5 hours 75% time saved
Salary errors 12/month 3/month 75% error reduction
Cost per cycle ₹40,000 ₹25,000 ₹15,000 saved
Company decided to extend automation to leave management and employee
onboarding modules.
Summary Table
Phase Focus Area Key Activities
Identification Define what to Engage stakeholders, list
achieve tangible/intangible benefits
Planning Map benefits to Assign owners, define KPIs
project steps
Realization Deliver benefits Execute project, enable adoption
Measurement Track and validate Review, audit, and improve
benefits

Conclusion: Benefit Management ensures that software projects go beyond

delivery to generate real business value. By following the benefit lifecycle,
organizations can:
 Improve ROI,
 Align projects with business goals,
 Make future projects more effective.

Q(7)Explain the techniques used in gathering requirements during the initial

stages of a software project.
Discuss interviews, questionnaires, observation, prototyping, and Joint
Application Development (JAD), including advantages and limitations of
each.
A: Techniques for Gathering Requirements in Software Projects
Gathering accurate and complete requirements is critical for the success of a
software project. It sets the foundation for design, development, and testing.

1. Interviews
Description: A structured or unstructured conversation between the analyst and
stakeholders (users, clients, managers) to extract detailed information about needs,
expectations, and constraints.
Example:
Project: Building an Online Appointment System for a Hospital
The analyst interviews doctors, receptionists, and patients to understand:
 Appointment booking process
 Data confidentiality needs
 Time-slot preferences
Advantages:
 Provides in-depth, qualitative information
 Builds trust and clarity
 Allows clarification of ambiguous points
Limitations:
 Time-consuming
 Depends heavily on communication skills
 May miss unspoken or undocumented workflows

2. Questionnaires/Surveys
Description: A set of structured questions distributed to a large audience to collect
responses about software needs, preferences, and expectations.
Example:
Project: Developing an E-learning Platform
Sent to 1,000 students and 50 teachers across institutions
Questions include:
 Preferred video formats
 Use of mobile vs desktop
 Features like quiz, live class, forum

Advantages:
 Reaches a large number of stakeholders
 Useful for quantitative analysis
 Cost-effective
Limitations:
 Lacks depth
 Misinterpretation of questions
 Low response rate may bias results

3. Observation
Description: The analyst observes users in their actual work environment to
understand processes, bottlenecks, and pain points that users might not express
verbally.
Example: Project: Creating a Warehouse Inventory Management System
 Analyst observes how workers scan items, record quantities, and manage
stock
 Notes inefficiencies in manual barcode entry and misplacement of items
Advantages:
 Reveals real-world workflows and undocumented tasks
  Identifies pain points users may not mention
Limitations:
 Observer bias may affect findings
 May not capture exceptions or rare cases
 Users may alter behavior when observed

4. Prototyping
Description: Building a working mock-up or partial model of the system (UI,
features) and refining it based on user feedback. Used in iterative and Agile
models.
Example: Project: Food Delivery Mobile App
Developer creates UI screens for:
 Home page
 Restaurant list
 Checkout page
 Shown to users to gather feedback before full development
Advantages:
 Helps visualize the system early
 Encourages early user feedback
 Reduces risk of wrong development
Limitations:
 Users may assume prototype is the final product
 Focus may shift from requirements to UI
 Requires extra time and tools

5. Joint Application Development (JAD)

Description: A collaborative workshop where developers, users, and managers
come together for multiple sessions to define requirements and design
collaboratively
Example: Project: Enterprise Resource Planning (ERP) System for a
Manufacturing Company
JAD session includes:
 Production managers
 Finance heads
 IT developers
 Business analysts
Discuss workflows like procurement, invoicing, inventory, and payroll
Advantages:
 Promotes shared understanding and consensus
  Faster decision-making and validation
 Saves time compared to many individual interviews
Limitations:
 Scheduling all stakeholders is difficult
 Dominant voices may influence outcomes
 Needs facilitators and structured planning

Summary Table
Technique Used When… Advantages Limitations Real-World
Example
Interviews In-depth, Deep Time- Online
personal understanding, consuming, Appointment
insights needed clarification subjective System
Questionnaires Input from Quick, Less context, E-learning
large group scalable, low lower Platform
needed cost response rate
Observation Real user Sees unspoken Observer Inventory
workflow issues bias, System
understanding behavior
needed changes
Prototyping Early UI/UX Visual, quick Confused Food Delivery
feedback is feedback expectations App
needed
JAD Complex Shared vision, Needs good ERP for
system with team alignment facilitation Manufacturing
multiple
stakeholders

Conclusion: Using a mix of requirement gathering techniques ensures that the

software project:
 Accurately reflects user needs,
 Avoids rework and misunderstandings,
 Increases stakeholder satisfaction.
The right technique(s) depend on project size, audience type, time constraints, and
stakeholder availability.
Q(8)Describe the process of identifying project scope and preparing a scope
statement.
Include the role of stakeholders, scope creep, and tools like context diagrams
and use-case diagrams. Explain how scope definition influences project
success.
A: Identifying Project Scope & Preparing Scope Statement
Project Scope: Project scope refers to the boundaries and deliverables of a software
project — what is included and what is excluded. It defines what the project will
deliver, how, and under what constraints.
Why is Scope Identification Important?
 Sets clear project expectations
 Helps in resource allocation
 Prevents misunderstandings
 Guides schedule, budget, and design decisions
 Prevents scope creep
A. Process of Identifying Project Scope
Step-by-step process used in IT companies:
Step 1: Requirement Gathering with Stakeholders
Stakeholders: Clients, end-users, project sponsors, developers, QA team,
legal/compliance officers.
Goal: Identify and understand what the client really wants.
Real-World Example: Project: Building a Mobile Banking App
 Stakeholders include bank executives, customers, compliance officers
 Analysts gather requirements:
View balance, fund transfer, UPI, mini-statement
Exclude features like credit card management for phase-1

Step 2: Define Project Boundaries (In-Scope and Out-of-Scope)

In-Scope Features Out-of-Scope (Phase-1) In-Scope Features
Login, Balance Check, Loan management, Credit Login, Balance Check,
UPI card UPI
Mini-statement, Profile Chatbot customer support Mini-statement, Profile

Step 3: Use Diagrams to Model the Scope

1. Context Diagram: Shows the system in context with external entities like users,
third-party APIs, banks, etc.
Example: Mobile Banking App
External entities: Users, Payment Gateway, Bank Server, SMS Gateway
System: Banking App (central block)

2. Use-Case Diagram: Visualizes user interactions (actors and system use-cases)

Example Use-Cases:
 Login
 Transfer Funds
 Check Balance
 View Mini-Statement
 Actors: Customer, Bank Admin

Step 4: Prepare the Scope Statement

A formal document that outlines:
Element Description
Project Purpose Why the project is being done
Deliverables Features/modules to be delivered
In-Scope Items Functional features and supported platforms
Out-of-Scope Items Features not to be developed now
Assumptions Platform dependencies, version control, third-party APIs
Constraints Budget, timeline, technology stack
Approval Stakeholder sign-off to prevent disputes later
The scope statement becomes a reference throughout the project lifecycle.

B. Role of Stakeholders in Scope Definition

Stakeholder Role in Scope Identification
Client/Customer Defines business goals and must-haves
Project Manager Facilitates scope meetings, maintains scope control
Business Analyst Documents requirements, prepares scope documents
Developers/Testers Evaluate feasibility and technical constraints
Legal/Compliance Ensures regulatory features are included or excluded

C. Scope Creep: A Major Risk

Scope Creep: Uncontrolled expansion of project scope without time, cost, or
resource adjustments
Example:
During the mobile banking app project, the client asks to add credit card
integration midway without extending the timeline.
Effects of Scope Creep:
 Missed deadlines
 Budget overrun
 Team burnout
 Poor-quality software
 Project failure
Prevention:
 Well-defined scope statement
 Proper change control process
 Stakeholder approval for all changes

D. How Scope Definition Influences Project Success

Impact Area Effect of Clear Scope Definition
Timeline Prevents delays due to unplanned additions
Budget Keeps cost under control
Quality Allows proper testing and acceptance
Stakeholder Trust Builds confidence and reduces last-minute disagreements
Team Focus Keeps developers aligned with agreed goals

Real-Time Case: Scope Definition for E-commerce Web Platform

Goal: Build an online store for a clothing brand.

Scope Statement Summary:

Section Content
In-Scope User login, product catalog, cart, checkout, order tracking
Out-of- Seller dashboard, recommendation engine, chatbot
Scope
Stakeholders Client (store owner), customers, IT vendor team, marketing
manager
Constraints Completion within 4 months, on WordPress WooCommerce
Assumptions Client will provide product images and shipping info
Outcome:
 Project delivered on time, with no scope creep
 Later additions moved to Phase-2 roadmap
 Clear boundaries avoided confusion between client and development team

Summary of the Process

Step Description
1. Identify Requirements Collaborate with stakeholders to gather needs
2. Define Boundaries Clarify what is and isn't included
3. Use Diagrams Context & Use-case diagrams to visualize boundaries
4. Prepare Scope Statement Formal doc with scope details, constraints, sign-off
5. Manage Scope Creep Use change control and approval workflows
Conclusion: A clearly defined project scope is essential to:
 Deliver projects on time and within budget
 Avoid conflicts with stakeholders
 Provide a roadmap for project teams
 Tools like context diagrams, use-case diagrams, and a well-written scope
statement help visualize and solidify this understanding.

Q (9) Outline and explain the step-wise project planning process proposed by
software engineering standards.
Describe each step such as feasibility assessment, risk management, resource
allocation, scheduling, and monitoring, with appropriate tools and techniques.
A: Step-Wise Software Project Planning Process
According to software engineering standards, effective project planning involves a
systematic series of steps to define, manage, and track a software project from
conception to delivery.
Real-World Example:
Let’s consider a real-time project:
Project: Developing a Cloud-Based Library Management System (CLMS)
Client: A network of universities wants a centralized system for issuing, returning,
searching books, and managing inventory.
Step 1: Feasibility Assessment
Objective: Evaluate whether the project is technically, economically, and
operationally viable.
Techniques:
 Cost-Benefit Analysis (CBA)
  SWOT Analysis
 Technical Feasibility Reports
Tools:
 Microsoft Excel for ROI and CBA
 SWOT templates for strategy
Example (CLMS):
 Technical Feasibility: Assessing compatibility with cloud infra (e.g., AWS
or Azure)
 Economic Feasibility: Project cost ₹20 lakhs, with estimated savings of ₹10
lakhs/year
 Operational Feasibility: Stakeholders from 20 universities agree to centralize
data

Step 2: Risk Management Planning

Objective: Identify potential project risks and prepare mitigation strategies.
Techniques:
 Risk Matrix (Probability × Impact)
 Monte Carlo Simulation
 Sensitivity Analysis
Tools:
 MS Excel Risk Matrix
 RiskyProject or @RISK for simulations
� Example (CLMS):
Risk Probability Impact Mitigation Strategy
(INR)
Server downtime Medium ₹2,00,000 Use AWS failover &
redundancy
User resistance High ₹1,00,000 Conduct training & feedback
sessions
Data migration Low ₹3,00,000 Perform pilot migration &
failure backups

Step 3: Resource Allocation

Objective: Assign human, technical, and financial resources to each activity or
phase.
Techniques:
 Resource Breakdown Structure (RBS)
  Effort Estimation Models: COCOMO II, Function Point Analysis
 Skill Matrix Analysis
Tools:
Trello, Jira, or MS Project
Resource calendars in Google Workspace or Office 365
Example (CLMS):
Role No. of People Tasks Assigned
Frontend Devs 2 [Link] UI for book search & login
Backend Devs 2 APIs for issue/return, search, reports
QA Engineers 1 Test planning and automation
Cloud Architect 1 AWS setup and integration

Step 4: Scheduling
Objective: Break project tasks into timelines with milestones and deadlines.
Techniques:
 Work Breakdown Structure (WBS)
 Gantt Charts
 Critical Path Method (CPM)
Tools:
 Microsoft Project
 Gantt Project
 Asana or ClickUp
 Lucidchart (for WBS)
Example (CLMS):
Task Duration Start Date End Date
Requirement Gathering 2 weeks July 1 July 14
UI/UX Design 3 weeks July 15 Aug 5
Backend & API Development 4 weeks Aug 6 Sept 2
Testing & UAT 2 weeks Sept 3 Sept 17
Deployment & Training 1 week Sept 18 Sept 24
Milestone: MVP delivery on Sept 2

Step 5: Monitoring & Control Plan

Objective: Continuously track project performance, adjust as needed, and report to
stakeholders.
Techniques:
 Earned Value Management (EVM)
 Burndown Charts
 Progress Reports & Dashboards
Tools:
 Jira is a popular project management and issue tracking tool developed by
Atlassian. It's widely used by software development teams, IT teams, and
businesses to manage projects, track issues, and improve collaboration.
 GitLab is a web-based DevOps platform that provides a comprehensive set
of tools for software development, version control, and collaboration. It
allows developers to manage their codebase, track changes, and collaborate
with team members. (issue tracking)
 Power BI is a business analytics service by Microsoft that allows users to
create interactive visualizations and business intelligence reports using data
from various sources.
 Tableau (dashboards) is business intelligence and data visualization tool that
helps users connect to various data sources, create interactive dashboards,
and share insights with others.
 Slack is a popular communication and collaboration platform designed for
teams. It offers real-time messaging, file sharing, and integrations with
various tools and services.
 Microsoft Teams is a communication and collaboration platform that
integrates with Microsoft 365 and other tools. It enables teams to chat, meet,
and work together in a shared workspace for communication
Example (CLMS):
 Weekly status reports sent to university IT heads
 Jira board shows completed vs. pending stories
 Burndown Chart tracks sprint-wise task completion

Step 6: Scope, Quality, and Communication Planning

1. Scope Planning:
 Prepare Scope Statement
 Use Context Diagrams, Use-Case Diagrams
2. Quality Planning:
 Define metrics: defect density, response time
 Use tools: Selenium, JMeter, SonarQube
3. Communication Planning:
 Stakeholder communication plan (status updates, meetings, feedback loops)
  Summary of Step-Wise Planning Process
Step Key Output/Deliverables Tools &
Techniques
Feasibility Assessment CBA, SWOT Report, Feasibility Excel, SWOT tools
Report
Risk Management Risk Register, Mitigation Plans Risk Matrix, Monte
Carlo
Resource Allocation Resource Plan, Staffing Plan RBS, COCOMO,
Gantt charts
Scheduling Project Schedule, Milestones, MS Project, Jira,
WBS GanttProject
Monitoring & Control Status Reports, Dashboards, Power BI, Jira,
EVM Metrics GitHub
Scope/Quality/Comms Scope Statement, QA Strategy, UML, Context
Plan Communication Guidelines Diagrams,
SonarQube
Conclusion: A well-structured planning process, aligned with software
engineering standards, ensures that a project:
 Starts with realistic goals
 Handles uncertainty effectively
 Allocates resources wisely
 Delivers value on time and within budget
 Avoids failure due to scope creep or unmanaged risks

Q(10)Present a case study of a software project from initiation to planning

phase.
Include requirement gathering, scope definition, risk identification, budget
estimation, and planning steps. Evaluate what went right and what could have
been improved.
A: Case Study: Cloud-Based School Management System (SMS)

Objective: To develop a centralized cloud-based School Management System that

digitizes student records, fee management, attendance, timetable scheduling, and
parent communication for a group of 10 schools.
Phase 1: Project Initiation
Activities:
 Client Consultation: Series of meetings with the school board
 Business Need: Reduce paperwork, increase parental transparency, improve
administrative reporting
 Initial Proposal Submitted to IT Steering Committee
Key Stakeholders:
 School Principals
 IT Manager
 Parents' Representative
 Development Team (Vendor)

Phase 2: Requirement Gathering

Techniques Used:
 Interviews: Conducted with teachers, administrative staff, parents
 Questionnaires: Distributed to over 300 parents
 Observation: Analyst visited 3 schools to observe attendance and record
systems
 Prototyping: Wireframes for dashboards, report cards, and fee interfaces
shown to stakeholders
Functional Requirements Identified:
 Student admission module
 Timetable creation
 Online fee collection
 Attendance tracking with notifications
 Parent login for viewing records
Non-Functional Requirements:
 Mobile-friendly
 Data encryption for privacy
 99.9% uptime for hosted services

Phase 3: Scope Definition Scope Statement:

In-Scope Out-of-Scope (Phase 1)
Web-based portal Mobile App (planned for Phase 2)
Fee, attendance, timetable modules Alumni management
Role-based dashboards Advanced analytics/reporting
  Assumptions: School will provide internet connectivity and existing student
data
 Constraints: Must be live before new academic year (4-month deadline)

Phase 4: Risk Identification

Risk Description Probability Impact Mitigation Strategy
Data migration from old Medium High Pilot migration + Data
systems fails backup
Staff resistance to new tech High Medium Conduct training
workshops
Internet downtime in rural Medium Medium Enable offline sync
schools capability
Payment gateway issues for Low High Partner with verified,
fee module secure provider
A risk register and risk matrix were created and shared.

Phase 5: Budget Estimation

Cost Components:
 Development: ₹8,00,000
 Cloud Hosting & Security: ₹2,00,000
 Training & Support: ₹1,00,000
 Contingency (10%): ₹1,10,000
 Total Estimated Budget: ₹12,10,000
Technique Used:
Bottom-Up Estimation based on:
 Module complexity
 Developer rates
 Training days
 Licensing & hosting

Phase 6: Project Planning Activities

Tools Used:
Work Breakdown Structure (WBS):
 Modules broken into tasks
 Assigned to developers & QA
Scheduling:
 Created Gantt chart with dependencies
  4 development sprints of 3 weeks each
Resource Allocation:
 2 Backend Developers ([Link])
 1 Frontend Developer (React)
 1 QA Tester
 1 Project Manager
Milestones:
Milestone Date
Requirements finalized Jan 20, 2025
UI/UX design completed Feb 5, 2025
MVP ready for review March 15, 2025
Pilot launched in 2 schools April 10, 2025
Full rollout May 15, 2025

Evaluation: What Went Right?

Positive Outcome Explanation
Strong stakeholder involvement Led to accurate and complete requirements
Early prototyping Helped validate UI expectations early
Realistic budget No overruns due to clear estimations
Training planned early Reduced resistance from school staff

What Could Have Been Improved?

Issue Recommendation
Initial data quality from schools was poor Could have included data audit step
earlier
Scope expanded with minor feature Enforce stricter change control policy
requests
Some schools had poor infrastructure Plan for offline-first support
Project manager had to wear multiple Assign a dedicated business analyst
hats
Conclusion: This case study illustrates a best-practice-based planning process,
where detailed requirement gathering, scope control, and risk planning enabled the
successful launch of a critical educational platform. Minor improvements could
further enhance outcomes in future phases.
Q(11)Compare and contrast various software effort estimation techniques.
Discuss expert judgment, analogy-based estimation, parametric models like
COCOMO, and machine learning-based estimation methods. Provide
advantages, disadvantages, and when each is best used.
A: Software Effort Estimation Techniques – Detailed Comparison
Effort estimation helps determine the amount of work, time, and resources required
to complete a software project. It plays a key role in budgeting, scheduling, and
project planning.
1. Expert Judgment
Definition: Relies on the experience and intuition of experts who estimate effort
based on past similar projects.
Example: A senior developer estimates that building a user registration module
will take 5 days based on prior experience.
Advantages:
 Quick and low cost
 Leverages domain-specific insights
 Works well for small or unclear projects
Disadvantages:
 Highly subjective
 Not scalable or repeatable
 Biased by overconfidence or pessimism
Best Used:
 Early phases of project planning
 Small projects or startups without historical data
 When time is limited

2. Analogy-Based Estimation
Definition: Estimates are made by comparing the current project or module to a
similar past project, adjusting based on complexity, team size, tools, and
environment.
Example: "The e-commerce cart module we built last year took 80 hours. This one
is 25% more complex, so it may take ~100 hours."
Advantages:
 More objective than pure judgment
 Helps estimate effort when reusable history exists
 Easy to explain to stakeholders
Disadvantages:
 Accuracy depends on quality of past project data
  May not account for new technologies or tools
 Requires proper documentation of previous efforts
Best Used:
 In companies with rich project history
 When building similar applications (e.g., new CRM, second e-commerce
portal)

3. Parametric Estimation (e.g., COCOMO Model)

Definition: Uses mathematical models to estimate effort based on inputs like size
(LOC or Function Points), complexity, and cost drivers.
Example: The COCOMO II model estimates effort using:
Effort = A × (Size) ^B × EAF
Where:
Size = Kilo Lines of Code (KLOC)
EAF = Effort Adjustment Factor
A and B are empirically derived constants
Advantages:
 Provides quantitative, repeatable results
 Based on empirical data
 Helpful for large projects
Disadvantages:
 Requires accurate size estimation early
 Not suitable for agile or small teams
 Needs calibration for better accuracy
Best Used:
 Large and well-defined projects
 Organizations using formal planning and cost models
 When you have function points, LOC, or UCP data

4. Machine Learning-Based Estimation

Definition: Uses historical data and machine learning (ML) models (e.g.,
regression, decision trees, neural networks) to predict effort based on patterns in
past projects.
Example: A model trained on 500 past projects can estimate that a 20-feature app
with 3 senior developers will take 10 sprints.
Advantages:
 Adaptive: Improves over time with more data
 Can capture complex, non-linear relationships
 Handles multiple variables (team skills, tools, features)
Disadvantages:
 Needs large, clean, high-quality historical data
 Requires technical expertise to build/train models
 Less interpretable than traditional models
Best Used:
 Enterprises with huge project datasets
 Repeated product development with measurable metrics
 Organizations moving toward AI-driven estimation

Comparative Summary Table

Technique Pros Cons Best Use Case
Expert Quick, simple, Subjective, not Small teams, early rough
Judgment no tools needed scalable estimates
Analogy- Based on real Needs detailed Similar app/module
Based past data project history development
COCOMO Repeatable, Requires size Waterfall, large
(Parametric) data-driven estimation and government/enterprise
calibration projects
ML-Based Smart, Needs lots of Big tech, agile product
Estimation adaptive, multi- data, complex development
variable

Real-World Example Scenario

Project: Development of a Mobile Health Tracker App
Estimation Application Example
Technique
Expert Judgment Tech lead estimates 4 weeks based on a past wellness app
development
Analogy-Based Compared to past fitness app → Adjusted +15% effort for new
biometric integration
COCOMO Model Used UCP = 35, Effort = 2.94 × (35)^1.1 = ~120 person-hours
ML Model ML predicts 5.2 weeks based on inputs: team skill, APIs used,
platform complexity, feature count

Conclusion: There is no one-size-fits-all technique. The best effort estimation

method depends on:
  Project size and clarity
 Data availability
 Team experience
 Organizational maturity

A hybrid approach often works best:

Use expert judgment + analogy, validate with parametric models, and refine with
machine learning over time.

Q(12)Explain the process and challenges involved in software cost estimation.

Include direct vs. indirect costs, fixed vs. variable costs, and internal vs.
external costs. Describe cost drivers and how uncertainty affects estimation.
A: Software cost estimation is the process of predicting the amount of effort, time,
and money required to develop a software system. Accurate cost estimation is
crucial for budgeting, planning, pricing, and risk management.

Process of Software Cost Estimation

1. Requirement Analysis:
 Understand functional and non-functional requirements.
 Identify scope and complexity.
 Example: In a mobile banking app, requirements include account access,
fund transfer, UPI integration, etc.

2. Selection of Estimation Technique:

 Expert Judgment
 Analogy-Based Estimation
 Parametric Models (e.g., COCOMO)
 Machine Learning Models
3. Identify Cost Elements:
 Direct vs. Indirect Costs
 Fixed vs. Variable Costs
 Internal vs. External Costs
4. Apply Estimation Models:
 Use historical data, models like COCOMO II, or story points (Agile).
 Adjust using cost drivers and risk factors.
5. Review and Revise Estimates:
 Iteratively refine based on team feedback and requirement changes.
Types of Software Costs
Cost Type Description Example
Direct Costs Costs directly tied to project Salaries of developers, software
tools
Indirect Costs Overhead or support costs Office rent, HR, admin staff
Fixed Costs Do not vary with project size Server purchase, license costs
Variable Change with project scale Developer hours, support staff
Costs
Internal Costs Incurred using in-house In-house QA team salaries
resources
External Outsourced or third-party Cloud hosting, contractor fees
Costs services

Cost Drivers in Software Estimation

Cost drivers are attributes that significantly influence the effort and cost of
software development.
Examples of COCOMO II Cost Drivers:
 Product Factors: Required reliability, complexity, reusability.
 Platform Factors: Execution time constraints, platform volatility.
 Personnel Factors: Team capability, experience, familiarity with tools.
 Project Factors: Development process maturity, team cohesion.

Challenges in Software Cost Estimation

1. Unclear Requirements: Early-stage estimates are highly uncertain due to
changing or ambiguous requirements.
2. Rapid Technology Change: New platforms or tools may emerge, affecting
timelines and costs.
3. Human Factors: Developer experience and productivity vary widely.
4. Scope Creep: Gradual expansion of requirements leads to cost escalation.
5. Historical Data Availability: Lack of comparable past projects reduces
estimation accuracy.
6. Integration & Testing Complexity: Estimating time for debugging,
performance tuning is difficult.

Live Example: Mobile Food Delivery App (ZestEats)

Project Summary:
A startup, ZestEats, is building a food delivery app like “Swiggy/Zomato” with
GPS tracking, payment gateway, customer reviews, and restaurant dashboards.

Estimation Steps:
1. Requirement Analysis:
 Customer App, Restaurant Portal, Delivery App, Admin Dashboard
 Non-functional requirements: 99.9% uptime, secure transactions.
2. Identified Costs:
Type Cost Item Estimated Cost
Direct Developer Salaries ₹12,00,000
Indirect Office Rent, Utilities ₹2,00,000
Fixed AWS Server Setup, SSL ₹1,00,000
Variable Additional Support Staff (on-demand) ₹1,50,000
Internal UI/UX team ₹3,00,000
External Payment Gateway, Maps API ₹2,50,000
3. Cost Drivers:
 High product complexity (multiple modules).
 Medium team experience (start-up team).
 High reliability & security requirements.
4. Estimation Technique:
 Used a hybrid: COCOMO II for back-end effort and Agile story-point
estimation for front-end.
 Estimated 9 months timeline, ₹22-24 lakhs budget.
5. Uncertainty Factors:
 Risk of feature changes based on user testing.
 External dependency on API cost changes.
 New regulatory compliance like digital tax collection

Summary Table
Category Factors
Techniques Used COCOMO II, Agile Points
Cost Types Direct, Indirect, Fixed, Variable, Internal, External
Cost Drivers Product complexity, team experience, platform stability
Challenges Scope creep, unclear requirements, integration issues
Live Example ZestEats food delivery app
Category Factors
Conclusion: Software cost estimation is a blend of technical modeling and
managerial judgment. While models like COCOMO and Agile help in
quantification, the real challenge lies in managing uncertainty, dynamic
requirements, and external dependencies. A well-planned estimation approach not
only forecasts budgets but also enhances stakeholder confidence and project
success.

Q(13)Discuss the impact of schedule compression on software project cost,

quality, and risk.
Provide examples of schedule compression techniques such as crashing and
fast tracking, and analyze their effect on the project triangle (cost-time-scope).
A: Schedule compression is a project management technique used to shorten the
project timeline without reducing its scope. It is usually implemented when a
project is behind schedule or when the client demands early delivery.

There are two major schedule compression techniques:

 Crashing
 Fast Tracking

These techniques impact the Project Management Triangle (also known as the Iron
Triangle):
 Time
 Cost
 Scope (or Quality)

Why Use Schedule Compression?

 Meet early delivery deadlines.
 Avoid project penalties.
 Seize market opportunities (e.g., launching before a competitor).
 Align with client requirements or funding windows.

Schedule Compression Techniques

1. Crashing
 Definition: Adding extra resources to critical path activities to complete
them faster.
 Example: Assigning more developers to the module handling payment
integration.
  Impact:
[Link]: Reduced.
[Link]: Increased due to overtime pay, hiring, or contract work.
[Link]: Moderate (resource coordination).
[Link]: Might suffer if resources are unfamiliar with the project.

2. Fast Tracking
 Definition: Performing tasks in parallel that were originally scheduled in
sequence.
 Example: Starting UI testing before completing back-end integration.
 Impact:
[Link]: Reduced.
[Link]: May stay the same initially.
[Link]: High due to rework from dependency issues.
[Link]: May suffer due to overlapping work and confusion.

Impact on the Project Triangle

Factor Normal Project After Compression (Crashing or Fast
Tracking)
Time Baseline (e.g., 8 Shortened (e.g., 6 months)
months)
Cost Budgeted (e.g., ₹20 Higher (e.g., ₹25 lakhs)
lakhs)
Scope Full Scope Usually unchanged, but quality risk increases
Quality Stable May decrease due to rework or errors

Risks and Challenges with Schedule Compression

Area Risks
Human Resources Burnout due to overtime, lack of skilled replacements
Communication Misalignment in fast-tracked activities
Quality Assurance Compressed testing cycles lead to undetected bugs
Project Scope creep due to incomplete planning
Management
Budget Overruns due to emergency contracting or resource
shortages
Real-World Example: CRM Software Development
Scenario: A company developing a CRM platform is asked by the client to launch
2 months earlier due to a new market opportunity.
Actions Taken:
Crashing: Hired 3 contract developers to speed up dashboard and analytics
modules.
Fast Tracking: Started user training before completing performance testing.
Outcome:
Factor Result
Time Project delivered on time (6 instead of 8 months)
Cost Increased by 18% due to contract labor and rework
Quality Multiple minor bugs post-launch; had to issue 2 hotfixes
Risk High coordination effort between fast-tracked teams

When to Use Schedule Compression

Use Case Recommendation
Strict deadline but flexible budget Use Crashing
Tasks can safely overlap without conflict Use Fast Tracking
Fixed cost and fixed scope � Avoid both – may risk failure
Project already behind schedule Use with caution, assess risk first
Use Case Recommendation

Conclusion:
Schedule compression is a powerful technique, but it comes at a cost of increased
risk, cost, and potential quality compromise. Project managers must carefully
weigh these trade-offs when accelerating delivery.
Both crashing and fast tracking are effective but require:
 Careful planning
 Strong communication
 Thorough risk management
Balance is key—a compressed schedule should not come at the expense of project
failure.
Q(14)Who is Capers Jones and what are his contributions to software
estimation?
Discuss Capers Jones’s estimation models, including Function Point Analysis,
and explain how his work has influenced modern software project estimation
practices.
A: Capers Jones is a renowned software engineering expert, particularly known for
his work in software cost estimation, productivity measurement, and quality
assurance. He is the founder and chairman of Software Productivity Research
(SPR) and has authored many influential books like:
 Applied Software Measurement
 Estimating Software Costs
 The Economics of Software Quality

Jones's work has influenced industry best practices for software cost, effort, and
quality estimation, especially through his advocacy and refinement of Function
Point Analysis (FPA).

Capers Jones’s Major Contributions

1. Function Point Analysis (FPA)

 A structured technique to measure the functional size of a software
application based on user requirements.
 It quantifies: [Link] [Link] [Link] interactions [Link] external interfaces
 Purpose: Estimating size before coding begins, unlike LOC (Lines of
Code), which is available only post-development.
2. Software Estimation Models
 Developed estimation models using historical data and statistical analysis.
 Emphasized:
[Link] defect prediction
[Link] estimation based on project domain and team productivity
[Link] analysis associated with scope and schedule changes
3. Software Productivity Metrics
 Proposed standardized metrics to compare productivity across teams,
domains, and organizations
4. Benchmarking Tools
 Tools from SPR helped in benchmarking project costs, schedule, and defect
rates.
Function Point Analysis (FPA) Explained
Function Component Description
External Inputs (EI) Data entering the system (e.g., login request)
External Outputs (EO) Processed data sent out (e.g., sales report)
External Inquiries (EQ) User-initiated requests without updates (e.g., account
balance)
Internal Logical Files User-maintained files (e.g., customer database)
(ILF)
External Interface Files Files used but not maintained (e.g., supplier data from
(EIF) another system)
Each of these components is assigned a complexity weight, and the sum gives the
Unadjusted Function Point Count. This is adjusted using 14 General System
Characteristics (GSCs) like performance, reusability, and security to get the final
Function Point (FP) count.

Live Example: Library Management System (LMS)

Scenario: A university is developing an online library management system with
features like:
 Book search
 Online issue/return
 Admin portal
 Notifications to students
Estimation using Function Points
Function Examples Estimated Weight FP
Type Count (Avg) Contribution
EI Login, Register, Issue 5 4 20
Book
EO Overdue Reports, 4 5 20
Book Issue Receipts
EQ Search Book, View 3 4 12
History
ILF Book Catalog, Student 2 7 14
Database
EIF University ID 1 5 5
Database
Unadjusted Function Points = 20 + 20 + 12 + 14 + 5 = 71 FP

Let’s assume an adjustment factor of 1.1 after applying the 14 GSCs:

Adjusted Function Points = 71 × 1.1 = 78.1 ≈ 78 FP

Estimating Cost & Effort (based on Jones’s Data)

 Average productivity rate (for medium complexity systems): 10 Function
Points per person-month
 So, Effort = 78 / 10 = ~8 person-months
 If cost per person-month = ₹1,00,000
Total Cost Estimate = ₹8, 00,000

Impact of Capers Jones's Work on Modern Estimation Practices

Area Influence
Pre-code Enabled early estimation through Function Points, improving
Estimation budget control
Productivity Standardized benchmarks (FPs/month) across industries
Metrics
Quality Used FP to predict likely defects, test cases, and maintenance
Prediction needs
Tool Integration Many estimation tools (like SEER-SEM, SLIM, and IBM
Rational) use or extend his concepts
Process Maturity His models complement CMMI, ISO, and Agile estimation
practices

Conclusion:
Capers Jones has revolutionized software estimation by promoting function-based
over code-based sizing, advocating for predictive analytics in software quality, and
building data-driven benchmarking tools.
His Function Point Analysis provides:
 A structured, repeatable method for estimating effort and cost.
 The ability to plan early and accurately, especially for fixed-scope projects
 A foundation for integrating estimation into Agile, DevOps, and hybrid
models