Software Metrics
(SWE2204)
By
Simon Kawuma(PhD)
Who am I
Name: Simon Kawuma
Designation: Lecturer
Office: Office 1, FCI Building
Department: Software Engineering
Contacts:
Email: [email protected]
Cell: 0702190961 or 0774253512
Website: http://must.ac.ug/simon-kawuma
Qualifications:
PhD in Software Engineering-MUST
2011-2013: MSc. Embedded Computing Systems, University of Southampton &
Norwegian University of Science and Technology
2006-2009: Bachelor of Computer, Mbarara University of Science & Technology
Research Interests:
Interests are in Embedded Computing Systems: Testing and Verification of
Embedded System Software, Computer Hardware Engineering, Signal Processing,
Medical Imaging, Modeling and Simulation , Empirical Software Engineering
[email protected]
Software Metrics
Software Metrics: What and Why ?
1. How to measure the size of a software?
2. How much will it cost to develop a software?
3. How many bugs can we expect?
4. When can we stop testing?
5. When can we release the software?
Software Metrics
Software Metrics: What and Why ?
6. What is the complexity of a module?
7. What is the module strength and coupling?
8. What is the reliability at the time of release?
9. Which test technique is more effective?
10. Are we testing hard or are we testing smart?
11. Do we have a strong program or a week test suite?
Pressman explained as “A measure provides a quantitative
indication of the extent, amount, dimension, capacity, or size of
some attribute of the product or process”.
Measurement is the act of determining a measure
Software
Metrics
The metric is a quantitative measure of the degree to which a
system, component, or process possesses a given
attribute.
Fenton defined measurement as “ it is the process by which
numbers or symbols are assigned to attributes of entities in the
real world in such a way as to describe them according to
clearly defined rules”.
Definition
Software metrics can be defined as “The
Software continuous application of measurement
based techniques to the software
Metrics development process and its products
to supply meaningful and timely
management information, together with
the use of those techniques to improve
that process and its products”.
Software Metrics
Areas of Applications
•The most established area of software metrics is cost and
size estimation techniques.
•The prediction of quality levels for software, often in terms
of reliability, is another area where software metrics have an
important role to play.
•The use of software metrics to provide quantitative checks
on software design is also a well established area.
Software
Metrics Developer Statement
Software development is to
Management view
Forget it, we will find
complex; it cannot be managed developers and managers who
like other parts of the will manage the development.
Problems During organization.
Implementation I am only six months late with the Fine, you are only out of a job
project
But you cannot put reliability Then we may not get the
constraints in the contract contract
Software Metrics
Categories of Metrics
i. Product metrics: describe the characteristics of the product such as size,
complexity, design features, performance, efficiency, reliability, portability, etc.
ii. Process metrics: describe the effectiveness and quality of the
processes that produce the software product.
Examples are:
• effort required in the process
• time to produce the product
• effectiveness of defect removal during development
• number of defects found during testing
• maturity of the process
Software Metrics
iii. Project metrics: describe the project characteristics and
execution. Examples are :
• number of software developers
• staffing pattern over the life cycle of the software
• cost and schedule
• productivity
Software Metrics
