It may appear I have abandoned the idea of devising a product metric of my own, but I am still on the case. I have been exercising my Java skills over the last couple of weeks and now my little hocus-pocus Java application has grown. In this article you can find a drawing of the Metric Calculation pipeline. The application is basically calculates, collates, and exports custom metrics or measures devised during my seach for the new useful metric which I would like to introduce as part of my Master's thesis.

Below is a graphical representation of my application's modus operandi. I have avoided strict UML for I believe the simple ideas are best conveyed in a simple form. I do not expect anyone to pore through a UML diagram. Just  follow the arrows in the drawing below...

Topic

Object-Oriented Product Metrics

Introduction

The field of OO product metrics is attracting many researchers’ interest, as metrics provide a mechanism for assessing product quality. Measurement is a key element of any engineering process. Many researchers have dedicated much of their time and effort to devising a single comprehensive measure of software complexity. According to Fenton [FEN94], such measure is an “impossible holy grail”.
Assuming Fenton was right and that there really isn’t a single comprehensive measure, a number of “independent indicators of the quality of analysis and design models” [PRE05, p.467] could be devised in order to measure various software attributes. There’s a great quantity of software tools for measuring and analysing a variety of product metrics. According to Pressman, “hundreds of metrics have been proposed for computer software, but not all provide practical support to the software engineer” [PRE05, p.469].