Software Maturity Performance

Avatar July 5th, 2013 Posted by Zohar Peretz( ) KPI, Software Lifecycle Management, Test Management

IEEE talks about changes made in the software, over 3 dimensions,  to measure the maturity of the software, here in this post we wish to present the relation between test being performed (regardless to their results) vs. the defect discovery during the same period.

 

Test Metrics can be used to measure test coverage prior to software delivery. It provides a measure of the percentage of the software tested at any point during testing.

It is calculated as follows:
Functional Test Coverage = FE/FT
Where,
FE –  is the number of test requirements that are covered by test cases that were executed against the software
FT –  is the total number of test requirements

Software Maturity Metric

Software Maturity Index is that which can be used to determine the readiness for release of a software system. This index is especially useful for assessing release readiness when changes, additions, or deletions are made to existing software systems. It also provides a historical index of the impact of changes. It is calculated as follows:
SMI = Mt – ( Fa + Fc + Fd)/Mt

Where:

SMI is the Software Maturity Index value
Mt is the number of software functions/modules in the current release
Fc is the number of functions/modules that contain changes from the previous release
Fa is the number of functions/modules that contain additions to the previous release
Fd is the number of functions/modules that are deleted from the previous release
Reliability Metrics

Looking at the image below you will find that some of the above calculation can also be reflected in simple presentation of the execution of tests being performed at ALL software releases regardless to the module add/change/delete and at the same time looking at the trend of defects discovery.

Looking at the first period of the software lifecycle you can identify that the number of tests being executed reflects directly on the defect discovery during the same period of time. That is vs. the more advanced period where the software is getting more matured, even those there is dramatic increase in the testing effort, still the defect discovery is not showing the same performance as on the first period.

 

QPack Analytics™ report based on OBIEE technology 

Software_Maturity_Test_Run_vs_Defect_Discovery_Rate

 

 


About the author, Zohar Peretz

Zohar has 18 years of experience in leading software development products, at leading software companies and startups. Using his vast experience in software development, Zohar has identified the need for a holistic solution for R&D departments, and together with Rami and a small development team, they established Orcanos ALM in 2005.

Since then, Orcanos software has evolved to other domains such as quality control and specific industries, such as medical device.

Zohar holds a BA degree in Industrial Engineering.

Tags: , , ,
Orcanos

Contact

8 Tozeret Ha'aretz Street
Tel Aviv, Israel
+972-3-5372561
info@orcanos.com

Copyright © Orcanos, All rights reserved. | Privacy policy | Terms of use