Software Metrics Overview
GN-z11Codes
Software metrics are ways to measure things in software development e.g size of code, quality of software, duration of the project, errors/bugs in the system, e.t.c.
Software metrics helps us:
Know if the software is good or bad.
Find and fix problems early.
Plan better.
Make smart decisions.
Software measurement principles
These are rules to follow when doing software measurements:
Know what you are measuring.
Use consistent tools and methods.
Measure things that matter.
Keep is simple and easy to understand.
Use results to improve.
Characteristics of software metrics:
Simple - Easy to understand.
Reliable - Gives correct results.
Relevant - Useful for the goal you want to achieve.
Measurable - Can be counted or calculated.
Comparable - Can be used to compare results overtime.
Types of software metrics:
Product metrics - These measure the actual software e.g lines of code (LOC)
Process metrics - These measure how the software was built e.g time taken to create login screen.
Project metrics - These measures the overall project e.g time, cost e.t.c.
Common software metrics with examples
| Metric | Meaning | Example |
| LOC (Lines of code) | Total number of code lines written | 6400 LOC |
| Cyclomatic complexity | How complexa program is depending on decision points (if, loops) | Value of 10 = complex |
| Defect density | Number of bugs per 1000 LOC | 16 bugs/1000 LOC |
| Code coverage | How much of the code has been tested | 70% |
| MTTR (mean time to repair) | Avarage time to fix bugs | 3 hours |
Benefits of using software metrics:
Better planning.
Better quality software.
Less bug.
Saves time & money.
Summary:
Software metrics helps us to measure & improve software.
Good metrics = better planning & better software.
3 types of metrics: product metrics, process metrics & project metrics.
Subscribe to my newsletter
Read articles from GN-z11Codes directly inside your inbox. Subscribe to the newsletter, and don't miss out.
Written by