0% found this document useful (0 votes)
47 views8 pages

Metrics Assignment

metrics

Uploaded by

damesamuel3
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
47 views8 pages

Metrics Assignment

metrics

Uploaded by

damesamuel3
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

COLLEGE OF ENGINEERING AND TECHNOLOGY

DEPARTMENT OF SOFTWARE ENGINEERING


Individual Assignment of Software Metrics
Course Title: Software Metrics

Name Id_No
Dame Samuel Abdisa Nsr/2225/20

Instructor: Mr.Hachalu Mulgeta.


Submission Date: December 15, 2024

i
1. Explain different types of metrics.
Metrics are quantifiable measures used to track and assess the status, quality, or performance of
processes, projects, or systems. They can vary depending on the domain (e.g., business, software
development, or healthcare), but broadly, metrics can be classified into the following categories:

1. Business Metrics

 Definition: These measure the health and performance of an organization.


 Examples:
o Revenue: Total income generated by the business.
o Customer Acquisition Cost (CAC): Cost to acquire a new customer.
o Net Promoter Score (NPS): Customer loyalty and satisfaction.
o Market Share: Percentage of the market that uses a company's products/services.

2. Performance Metrics

 Definition: These assess the effectiveness and efficiency of a process or system.


 Examples:
o Productivity: Output per unit of input (e.g., hours worked).
o Throughput: Amount of work completed in a given time.
o First Response Time (FRT): Time taken to respond to customer inquiries.

3. Software Development Metrics

 Definition: These track the performance and quality of software development processes.
 Examples:
o Code Quality Metrics:
 Cyclomatic Complexity: Measures the complexity of code.
 Code Coverage: Percentage of code covered by automated tests.
o Team Productivity Metrics:
 Velocity: Amount of work completed per sprint.
 Burndown Chart: Work remaining in a sprint.
o Operational Metrics:
 Mean Time to Failure (MTTF): Average time before software fails.
 Mean Time to Recovery (MTTR): Time taken to recover from a failure.

4. Financial Metrics

1
 Definition: These measure the financial performance of an organization.
 Examples:
o Profit Margin: Net income as a percentage of revenue.
o Return on Investment (ROI): Gain/loss generated relative to the investment
cost.
o Operating Expenses (OPEX): Costs associated with business operations.

5. Marketing Metrics

 Definition: These measure the performance of marketing campaigns.


 Examples:
o Conversion Rate: Percentage of users who take a desired action (e.g., signing
up).
o Click-Through Rate (CTR): Ratio of clicks to impressions for ads.
o Customer Lifetime Value (CLV): Total revenue expected from a customer over
their relationship with the business.

6. Health and Safety Metrics

 Definition: These assess workplace or community health and safety.


 Examples:
o Injury Rate: Number of injuries per 1,000 workers.
o Incident Severity Rate: Impact of safety incidents

7. Educational Metrics

 Definition: These measure learning outcomes and institutional performance.


 Examples:
o Graduation Rate: Percentage of students completing a program.
o Average Test Scores: Performance on standardized tests.

8. Environmental Metrics

 Definition: These measure the impact on the environment.


 Examples:
o Carbon Footprint: Total greenhouse gases emitted.
o Energy Efficiency: Output per unit of energy used.

9. Customer Service Metrics

 Definition: These measure the quality and effectiveness of customer support.


 Examples:
o Customer Satisfaction Score (CSAT): Level of satisfaction with service.
o Resolution Time: Average time to resolve customer issues.

10. Project Management Metrics

2
 Definition: These track the progress and success of projects.
 Examples:
o On-Time Delivery Rate: Percentage of tasks completed on schedule.
o Budget Variance: Difference between actual and planned budget.
o Scope Creep: Measure of unplanned changes in project scope.

2. What are Current Research in Software Metrics.


Current research in software metrics is quite diverse and covers various aspects of software
development and maintenance. Here are some key areas of focus:

1. Transparency in Software Engineering: Researchers are exploring metrics to evaluate


and improve transparency in the software development life cycle. This includes
measuring how open and clear the development process is, which can impact
communication, maintainability, and productivity1.
2. Evaluation of New Development Methods and Paradigms: There is ongoing research
into how different development methods and paradigms can be measured for
effectiveness and efficiency. This includes evaluating agile methodologies, DevOps
practices, and other modern approaches to software development.
3. Quality and Management Improvement Programs: Metrics are being developed to
assess and improve the quality and management of software projects. This includes tools
and techniques for measuring software quality, productivity, and overall project
performance.
4. Tool-Supporting Initiatives: Research is being conducted on tools that support software
measurement and metrics. These tools help automate the collection and analysis of
software metrics, making it easier for teams to track and improve their performance.
5. Object-Oriented Software Metrics: There is a focus on developing metrics specifically
for object-oriented software development. This includes measuring the complexity,
maintainability, and quality of object-oriented code.
6. Evaluation of Java Applications: Researchers are looking into metrics for evaluating
the efficiency and maintainability of Java applications. This includes studying how Java
applications perform and how they can be improved.
7. Compliance with Privacy Laws: Metrics are being developed to assess the compliance
of software systems with privacy laws and regulations. This is particularly important for
applications that handle sensitive user data.
8. Neural-Fuzzy Techniques for Software Quality Models: Some research is exploring
the use of neural-fuzzy techniques combined with genetic algorithms to create software
quality models. These models aim to predict and improve software quality more
accurately.

3
3. What is LOC, its features and Find LOC for the following simple
code
void main()

int fN, sN, tN;

cout << "Enter the 2 integers: ";

cin >> fN >> sN;

// sum of two numbers in stored in variable sum

sum = fN + sN;

// Prints sum

cout << fN << " + " << sN << " = " << sum;

return 0;

What is LOC?

LOC (Lines of Code) is a software metric used to measure the size of a program by counting the
number of lines in the source code. It helps in estimating the complexity and effort required for
development, maintenance, and testing.

Features of LOC

1. Simplicity: Easy to calculate; just count the lines.


2. Size Measurement: Provides a rough estimate of the size of the software project.
3. Productivity Assessment: Can be used to measure developer productivity over time.
4. Maintenance Estimation: Helps in assessing the potential effort for future maintenance.
5. Comparison: Useful for comparing different projects or codebases.

Finding LOC for the Given Code

LOC Calculation

 Counted Lines: Lines containing actual code and comments


 Blank Lines: Not counted

4
 Comment Lines: Counted

The total lines are:

 Lines of Code: 9 (Lines 1 to 11, excluding blank lines)


 Comment Lines: 2 (Lines 6 and 8)

Total LOC = 11 lines (including comments and code).

4. Look at the following simple code


1. for ( i = 0; i < 10; i++ )

2. {

3. if ( g1 == 1

4. && g2 == 0 )

5. {

6. printf("who cares!\n");

7. }

8. }

What if I wrote it like this?! and which tools you use to run this?

for(i=0;i<10,i++) if(g1==1&&g2==0) printf(“who cares!\n);

Original Code:

for (i = 0; i < 10; i++)

if (g1 == 1 && g2 == 0)

printf("who cares!\n");

5
Modified Code:

for(i = 0; i < 10, i++) if(g1 == 1 && g2 == 0) printf("who cares!\n");

Issues in the Modified Code:

1. Syntax Error in the printf Statement:


o The double quote (") for "who cares!\n" is mismatched. It should be replaced with
" at the end.
o Corrected version:

printf("who cares!\n");

2. Incorrect Separator in for Loop:

 A comma , is used instead of a semicolon ; between i < 10 and i++.

Corrected version:

for(i = 0; i < 10; i++) ...

Fully Corrected Version:

for (i = 0; i < 10; i++)

if (g1 == 1 && g2 == 0)

printf("who cares!\n");

This is a valid and compact C code. The curly braces ({}) around the if block are optional for
single statements.

Tools to Run the Code:

You can use any C compiler or IDE. Here are some common tools:

1. Command Line Compilers:


o GCC (GNU Compiler Collection):
2. Integrated Development Environments (IDEs):

 Code::Blocks
 Dev- C++
 Eclipse CDT
 CLion
 Visual Studio

6
5. What are some basics of KPIs (key performance indicators) for a
Project Management Office?.
A Project Management Office (PMO) plays a pivotal role in standardizing project management
practices and ensuring projects align with organizational objectives. To evaluate the effectiveness
of a PMO, it's essential to monitor specific Key Performance Indicators (KPIs). Here are some
fundamental KPIs commonly tracked:

Percentage of Projects Aligned to Strategy: This KPI measures the proportion of active
projects that directly support the organization's strategic goals. A higher percentage indicates
better alignment between project outcomes and business objectives.

On-Time Project Completion Rate: This metric assesses the percentage of projects
completed by their scheduled deadlines. It reflects the PMO's efficiency in time management and
scheduling.

Budget Variance: This KPI compares the planned budget to the actual expenditure of
projects. A minimal variance suggests effective financial oversight and resource allocation.

Resource Utilization: This metric evaluates how effectively the PMO deploys its resources,
including personnel and equipment. Optimal utilization ensures that resources are neither
underused nor overextended.

Customer Satisfaction Index: This KPI gauges stakeholder satisfaction with project
outcomes, providing insights into the quality and effectiveness of project deliverables.

Scope Creep Rate: This metric measures the frequency and extent of unauthorized changes to
the project scope, indicating the PMO's ability to manage project boundaries and requirements.

Return on Investment (ROI): This KPI calculates the financial return generated from
projects relative to their costs, reflecting the overall value delivered by the PMO.

You might also like