1) What is project evaluation? Explain its benefits.

Project evaluation is a critical process within project management that assesses the feasibility and
worth of a proposed project, typically at its initial stages. It involves determining whether the project
is viable and if its anticipated benefits justify the costs of its implementation and operation.

Project evaluation encompasses several key activities to ensure a thorough assessment:

• Technical Assessment: This involves evaluating whether the required functionalities of the
proposed system can be achieved using current, affordable technologies. It also considers how the
project aligns with existing organizational policies, such as hardware/software infrastructure
standards, which limit the technical solutions that can be adopted.

• Cost-Benefit Analysis: This is a fundamental part of project evaluation, comprising two main steps:

◦ Identifying all costs and benefits: This includes quantifying development costs (e.g., staff
salaries), setup costs (e.g., new hardware, file conversion, training), and operational costs (e.g.,
system maintenance). Benefits are also identified and, where possible, assigned a financial value
(e.g., increased profits, cost savings). For non-profit organizations, benefits might be quantified
without a direct financial value (e.g., improved diagnosis in a medical system).

◦ Expressing costs and benefits in common units (money): All identified costs and benefits are
converted into monetary terms to allow for direct comparison and calculation of net benefit.

• Cash Flow Forecasting: It is crucial to produce a forecast that indicates when expenditure and
income will occur over the project's life. This helps ensure the organization can fund development
expenses and understand the timing of returns. Typically, products generate negative cash flow
during development and positive cash flow during operation.

Benefits of Project Evaluation:

Project evaluation offers numerous advantages that contribute significantly to successful project
outcomes and organizational efficiency:

• Feasibility and Business Case Validation: It ensures that a project is indeed worth starting and has
a valid business case, confirming that its benefits will exceed its costs. This prevents investment in
non-viable projects.

• Informed Decision-Making and Project Selection: When an organization has multiple potential
projects but limited resources, project evaluation provides a systematic way to compare and decide
which projects to select and prioritize. This ensures that the most valuable projects receive the
necessary resources.

• Optimized Resource Allocation: By assessing project requirements and potential outcomes,

evaluation helps in determining the most effective ways to allocate limited resources, such as staff
time and finances. It informs when resources should be made available and assesses the efficacy of
additional spending.

• Detailed Costing and Budget Control: After an initial evaluation, more detailed and accurate
estimates of costs and their timing can be obtained. This provides a clearer financial roadmap,
against which future project progress can be monitored.
• Motivation and Accountability: Establishing clear targets and benchmarks during evaluation
provides motivation for staff and a clear standard against which their achievements can be
measured. This enhances accountability throughout the project lifecycle.

• Enhanced Coordination and Communication: For large projects involving multiple teams, the
project plan derived from evaluation acts as an effective vehicle for communication and
coordination, particularly when staff need to be transferred between projects or work concurrently.

Conclusion: In essence, project evaluation is indispensable for strategic decision-making in any

organization. It provides a robust framework for assessing a project’s viability, aligning it with
organizational objectives, optimizing resource use, and setting realistic financial and performance
expectations, thereby laying a solid foundation for project success.

FeDi ReCo MoCo"

 Fe → Feasibility

 Di → Decision

 Re → Resources

 Co → Costing

 Mo → Motivation

 Co → Communication

--------------------------------------------------------------------------------

2) What is project evaluation? Explain its importance.

Project evaluation is the process of critically assessing a proposed project to determine its viability
and justification, primarily by weighing its potential benefits against its anticipated costs. It acts as a
fundamental gatekeeping mechanism, ensuring that only worthwhile initiatives proceed.

The importance of project evaluation cannot be overstated, particularly in the context of complex
and resource-intensive undertakings like software projects. Its significance stems from several crucial
aspects:

• Ensuring Business Viability (Business Case): A primary importance of project evaluation is to

establish and validate the business case for a project. This means confirming that the value of
benefits derived from the project's outcomes will exceed the costs incurred during its development,
implementation, and operation. Without rigorous evaluation, organizations risk investing significant
capital and effort into projects that may never yield a positive return, leading to financial losses and
wasted resources.

• Strategic Alignment: Evaluation is crucial for ensuring that individual projects are aligned with the
organization's broader strategic objectives. Often, a single project might not yield immediate direct
financial benefits on its own, but it could be a vital component of a larger programme of projects
designed to achieve a strategic goal, such as establishing a new IT infrastructure. Project evaluation
helps managers decide which projects best contribute to these strategic aims.

• Optimizing Resource Allocation: Resources, whether financial capital, skilled personnel, or

equipment, are always limited. Project evaluation allows managers to prioritize project
proposals and make informed decisions on how to share these limited resources effectively. It helps
prevent "too many projects are started given the resources available,"* Foundation for Planning and
Control: Project evaluation provides the initial high-level estimates for crucial parameters such as
effort, duration, and cost. These early estimates, though broad, serve as the baseline for all
subsequent detailed planning and monitoring activities. Without a solid initial evaluation, detailed
planning would lack direction and control would be difficult to establish, making it challenging to
keep the project on target.

• Achieving Stakeholder Consensus and Clear Objectives: Evaluation helps in articulating clear and
shared project objectives among diverse stakeholders, who may initially have differing or even
conflicting interests. By identifying what the project must achieve for success and establishing
practical measures of effectiveness, evaluation fosters a common understanding and commitment
among all parties involved.

Conclusion: In summary, project evaluation is not merely a formality but a foundational activity that
dictates a project's destiny. Its importance lies in providing the necessary insights for strategic
alignment, prudent resource management, proactive risk handling, and establishing clear,
measurable objectives, all of which are essential for navigating the complexities of modern project
delivery and ensuring long-term organizational success.

FeDi ReCo MoCo"

 Fe → Feasibility

 Di → Decision

 Re → Resources

 Co → Costing

 Mo → Motivation

 Co → Communication

--------------------------------------------------------------------------------

3) Describe at least three cost-benefits evaluation techniques.

Cost-benefit evaluation techniques are methods used to compare projects based on their
anticipated cash flows, helping organizations make informed decisions about which projects to invest
in. These techniques provide a structured way to analyze the financial viability and attractiveness of
competing project proposals. Here are three prominent techniques:

1. Net Profit (or Total Profitability)

◦ Definition: The net profit of a project is the straightforward difference between the total income
generated and the total costs incurred over the entire expected lifetime of the project. It represents
the absolute financial gain (or loss) a project is expected to yield.
 ◦ Explanation: This is the simplest financial metric. To calculate it, all projected revenues from the
project are summed, and all projected expenditures (development, setup, operational, and
decommissioning costs) are subtracted. For instance, if Project A has total income of £1,000,000 and
total costs of £950,000, its net profit is £50,000.

◦ Example (Conceptual): Consider Project 2 in Table 2.1. If it shows the greatest net profit, a simple
analysis based on this criterion would rank it highest.

◦ Limitations: The main drawback of net profit is that it takes no account of the timing of cash
flows. Money received sooner is inherently more valuable due to its potential for reinvestment (time
value of money), but net profit treats all income equally regardless of when it is received. It also
doesn't consider the initial investment size relative to the profit, meaning a project requiring massive
investment for a slightly higher profit might be preferred over a project with lower investment but
better return.

2. Return on Investment (ROI) / Accounting Rate of Return (ARR)

◦ Definition: Return on Investment (ROI) provides a way of comparing a project's net profitability
directly to the investment required, expressed as a percentage. It quantifies the efficiency of an
investment.

◦ Explanation: The common formula for ROI is: ROI = (Average Annual Profit / Total Investment) ×
100.

▪ Average Annual Profit is calculated by dividing the total net profit over the project's life by the
number of years.

▪ Total Investment typically refers to the initial capital outlay or the total capital invested in the
project.

◦ Example: For Project 1 (as described in Table 2.1 and calculation in source):

▪ Net Profit: £50,000 over 5 years.

▪ Total Investment: £100,000.

▪ Average Annual Profit: £50,000 / 5 = £10,000.

▪ ROI = (£10,000 / £100,000) × 100 = 10%.

◦ Advantages: ROI is simple to calculate and understand, making it a popular metric for comparing
the relative profitability of different projects.

◦ Limitations: Similar to net profit, ROI ignores the timing of cash flows. It also doesn't indicate the
absolute size of the return. A project with a lower ROI but significantly larger absolute profit might be
more attractive than one with a high ROI but very small returns.

3. Net Present Value (NPV)

◦ Definition: Net Present Value (NPV) is a sophisticated project evaluation technique that
explicitly takes into account both the profitability of a project and the timing of its cash flows. It is
based on the principle that money received today is worth more than the same amount of money
received in the future due to its earning potential (interest or investment).
 ◦ Explanation: NPV calculates the present value of all future cash inflows and outflows of a project,
discounted back to the present day using a specific discount rate (which reflects the cost of capital or
target rate of return). The discount factor used is 1 / (1 + r)^t, where 'r' is the discount rate and 't' is
the number of years from now. The NPV is the sum of these discounted cash flows. A positive NPV
indicates that the project is expected to be profitable, while a negative NPV suggests it is not.

◦ Example: For Project 1 (as described in Table 2.1 and calculation in source), assuming a 10%
discount rate:

▪ Year 0: -£100,000 (investment) * 1.0000 = -£100,000

▪ Year 1: +£10,000 * 0.9091 = £9,091

▪ Year 2: +£10,000 * 0.8264 = £8,264

▪ Year 3: +£10,000 * 0.7513 = £7,513

▪ Year 4: +£20,000 * 0.6830 = £13,660

▪ Year 5: +£100,000 * 0.6209 = £62,090

▪ Total NPV = £618.

◦ Advantages: NPV is widely considered a superior method because it incorporates the time value
of money, providing a more realistic assessment of a project's profitability. It also directly indicates
the absolute financial gain.

◦ Limitations: NPV is sensitive to the chosen discount rate, and determining the appropriate rate
can sometimes be subjective.

Conclusion: While net profit and ROI offer quick, easy-to-understand financial insights, their failure
to account for the time value of money makes them less robust for comprehensive decision-making.
Net Present Value (NPV), by contrast, provides a more sophisticated and generally preferred
assessment, as it considers both the magnitude and timing of cash flows, making it a powerful tool
for comparing and selecting projects for maximum financial benefit.

--------------------------------------------------------------------------------

4) Describe “Return on Investment” cost-benefits evaluation technique with example.

Return on Investment (ROI) is a financial metric used in project evaluation to assess the efficiency or
profitability of an investment. It provides a way of comparing the net profitability of a project to the
investment required, typically expressed as a percentage. In essence, ROI helps determine how much
return an organization gets relative to the cost of its investment.

Explanation:

The core idea behind ROI is to provide a standardized measure of financial return that allows for
straightforward comparison across different investment opportunities or projects. It answers the
question: "For every pound invested, how much profit is generated?"

The most common formula for calculating Return on Investment is:

ROI = (Average Annual Profit / Total Investment) × 100

Let's break down the components of this formula:

• Average Annual Profit: To calculate this, you first determine the total net profit over the entire
lifespan of the project. The total net profit is the total income generated by the project minus all
project-related costs (development, setup, operational, and potentially decommissioning costs). This
total net profit is then divided by the number of years the project is expected to generate returns to
get the average annual profit.

• Total Investment: This refers to the cumulative capital outlay required to initiate and complete the
project. It typically includes the initial expenses incurred at the beginning of the project, often at
"Year 0" in cash flow forecasts.

Advantages of ROI:

• Simplicity and Understandability: ROI is relatively easy to calculate and interpret, making it
accessible to a wide range of stakeholders, including those without deep financial expertise.

• Comparability: As a percentage, ROI allows for quick and direct comparison of the financial
attractiveness of diverse projects, regardless of their absolute cost or scale. This helps in ranking
projects when capital is limited.

Disadvantages of ROI:

• Ignores Time Value of Money: A significant weakness of ROI is its failure to account for the time
value of money. It treats a profit received five years from now as equal in value to a profit received
today, which is financially unsound because money received sooner can be reinvested to earn further
returns.

• Ignores Absolute Scale: ROI only provides a percentage return, not the actual monetary value of
the profit. A project with a very high ROI but a small initial investment might yield less absolute profit
than a project with a modest ROI but a much larger investment. For example, a 50% ROI on an
investment of £100 (resulting in £50 profit) is less impactful than a 10% ROI on an investment of
£1,000,000 (resulting in £100,000 profit).

• Focus on Profitability over Liquidity: ROI doesn't provide insights into the cash flow patterns,
which are crucial for an organization's liquidity and ability to fund ongoing operations.

Example:

Let's use Project 1 from the source's Table 2.1 to illustrate the calculation of ROI, assuming a project
duration of 5 years:

• Project 1 Financial Data:

◦ Initial Investment (Year 0): -£100,000

◦ Annual Cash Flows (Income - Expenditure):

▪ Year 1: £10,000

▪ Year 2: £10,000

▪ Year 3: £10,000

▪ Year 4: £20,000

▪ Year 5: £100,000
• Step 1: Calculate Total Net Profit:

◦ Total Income = £10,000 + £10,000 + £10,000 + £20,000 + £100,000 = £150,000

◦ Total Costs (Investment) = £100,000

◦ Total Net Profit = Total Income - Total Costs = £150,000 - £100,000 = £50,000

• Step 2: Calculate Average Annual Profit:

◦ Project Duration = 5 years

◦ Average Annual Profit = Total Net Profit / Project Duration = £50,000 / 5 = £10,000 per year

• Step 3: Calculate ROI:

◦ ROI = (Average Annual Profit / Total Investment) × 100

◦ ROI = (£10,000 / £100,000) × 100 = 0.10 × 100 = 10%

Interpretation: An ROI of 10% for Project 1 means that, on average, for every £1 invested in this
project, the organization expects to receive £0.10 (or 10 pence) in annual profit over its 5-year life.
This figure can then be used to compare Project 1 against other potential investments or the
company's minimum acceptable rate of return.

Conclusion: While Return on Investment (ROI) is a simple and intuitive metric for assessing project
profitability and facilitating comparisons, its primary limitation is its disregard for the time value of
money and the absolute scale of profit. Therefore, for robust financial decision-making, it is often
best utilized in conjunction with other evaluation techniques like Net Present Value (NPV), which
explicitly account for the timing of cash flows.

--------------------------------------------------------------------------------

5) Explain GQM paradigm.

The provided source material does not contain any information about the GQM (Goal-Question-
Metric) paradigm. Therefore, based solely on the given excerpts, I cannot provide an explanation of
this concept.

--------------------------------------------------------------------------------

6) Enlist the techniques of process analysis and explain in brief.

Process analysis refers to the systematic examination and evaluation of the methods and procedures
used in software development to manage quality and improve efficiency. These techniques, often
referred to as process capability models, provide frameworks for organizations to understand, assess,
and enhance their development practices.

Here are some key techniques of process analysis:

1. SEI CMM (Software Engineering Institute Capability Maturity Model)

◦ Definition: SEI CMM is a reference model designed to appraise a software development

organization by classifying its development process into one of five maturity levels. It provides a
pathway for organizations to improve their processes incrementally.
 ◦ Explanation: The model operates on the premise that the maturity level of an organization's
process is indicative of its likely performance and the quality of the software it produces. CMM can
be used for:

▪ Capability Evaluation: Assessing a contractor's potential performance before awarding work.

▪ Process Assessment: Internal use by an organization to identify areas for improvement.

◦ Five Maturity Levels:

▪ Level 1: Initial: Processes are typically ad hoc, chaotic, and reactive, with success largely
dependent on individual heroics rather than structured procedures.

▪ Level 2: Repeatable: Basic project management processes are established to track cost,
schedule, and functionality. Organizations can repeat successes on similar projects due to
documented procedures for planning and control.

▪ Level 3: Defined: Processes are documented, standardized, and integrated into an

organizational standard process. There is a clear, consistent understanding of how work is performed.

▪ Level 4: Quantitatively Managed: Organizations at this level collect process and product
metrics, enabling quantitative management and control of processes. Performance is statistically
understood and managed.

▪ Level 5: Optimizing: Focus is on continuous process improvement through quantitative

feedback and the assimilation of innovative ideas and technologies. Lessons learned are
systematically incorporated to optimize processes.

◦ Purpose: Guides organizations to move from informal, inconsistent practices to disciplined,

quantitatively controlled, and continuously improving processes.

2. CMMI (Capability Maturity Model Integration)

◦ Definition: CMMI is an evolved and integrated version of the earlier CMMs, providing a more
comprehensive framework for process improvement across various disciplines, including software
engineering.

◦ Explanation: Developed to integrate the multiple CMMs that existed for different disciplines
(e.g., software, systems engineering), CMMI aims to reduce the cost and effort of implementing
process improvements. It defines Key Process Areas (KPAs) for each maturity level, outlining specific
practices an organization must implement. For example, Level 2 includes Requirements Management
and Project Planning, while Level 3 includes Organizational Process Focus and Integrated Project
Management. CMMI shares many core concepts with SEI CMM and provides a unified approach to
improving organizational capabilities.

3. ISO 15504 (Process Assessment)

◦ Definition: ISO/IEC 15504, also known as SPICE (Software Process Improvement and Capability
Determination), is an international standard for process assessment that aligns closely with CMMI.
It offers a standardized framework for assessing the capability of an organization's software
development processes.

◦ Explanation: ISO 15504 uses a process reference model (often based on ISO 12207, which
describes the main software development lifecycle processes like requirements analysis and
architectural design) as a benchmark. Assessors evaluate various process attributes (e.g., process
performance, process definition, process deployment, process control, process innovation) for each
process within an organization.

◦ Scoring: Processes are scored based on the degree to which these attributes are achieved, using
interpretations like "Not Achieved" (N), "Partially Achieved" (P), "Largely Achieved" (L), and "Fully
Achieved" (F). Achieving a higher level (e.g., Level 3) requires fulfilling the attributes of all preceding
levels (Levels 1 and 2).

◦ Purpose: Provides a consistent, globally recognized method for organizations to assess their
process strengths and weaknesses, enabling targeted improvements and benchmarking against
industry best practices.

Conclusion: Process analysis techniques like SEI CMM, CMMI, and ISO 15504 are vital for software
development organizations. They provide structured methodologies to evaluate the maturity and
effectiveness of their development processes, identify areas for improvement, and ultimately foster a
culture of continuous enhancement, leading to greater predictability, efficiency, and higher quality
software products.

Q3) b) Explain GQM paradigm. [5]

Answer:

GQM (Goal/Question/Metric) Paradigm is a goal-oriented approach for software measurement that

helps organizations define and interpret operational metrics.

Three Levels of GQM:

1. Conceptual Level (Goal):

• Definition: High-level objective that specifies what needs to be achieved
• Components: Purpose, Object, Issue, Viewpoint, Environment
• Example: "Improve the reliability of the billing system from the customer's perspective"

Goal Structure:
• Purpose: What do you want to achieve? (Improve, Control, Analyze, etc.)
• Object: What is being measured? (Product, Process, Resource)
• Issue: What quality aspect? (Reliability, Performance, Maintainability)
• Viewpoint: From whose perspective? (Developer, Manager, Customer)
• Environment: In what context? (Project phase, Organization type)

2. Operational Level (Question):

• Definition: Set of questions that characterize the goal and focus on specific aspects
• Purpose: Break down the goal into measurable components
• Examples:
- "What is the current system reliability?"
- "How many defects are discovered during testing?"
- "What is the user satisfaction level?"

3. Quantitative Level (Metric):

• Definition: Quantitative measures that answer the questions
• Types:
- Objective Metrics: Lines of code, defect count, response time
- Subjective Metrics: User satisfaction ratings, expert opinions
• Examples: Mean time between failures, defect density, customer satisfaction score

GQM Process Steps:

1. Planning Phase:
• Define measurement objectives
• Select projects and processes to measure
• Identify stakeholders and resources

2. Definition Phase:
• Define measurement goals clearly
• Develop questions and hypotheses
• Define metrics and data collection procedures
• Create measurement and analysis plans

3. Data Collection Phase:

• Implement data collection procedures
• Train personnel on measurement techniques
• Monitor data quality and consistency

4. Interpretation Phase:
• Analyze collected data in context of questions
• Evaluate achievement of goals
• Identify improvement opportunities
• Generate actionable insights