A software metric is a mapping on a set of software artifacts to the reals.   And a software metric tool typically implements software metrics for use in evaluating the quality of the parts of a software system.

A good overview of software metric tools is given by

R. Lincke, J. Lundberg and W Lowe, Software Technology Group, Vaxjo University, Sweden, 2008:

http://www.arisa.se/files/LLL-08.pdf

Perhaps you will find the following article interesting:

N. Joshi, P.  Singh, Role of software metrics on software quality, UREAT Int. J. of Research in Engineering & Advanced Technolgy 1(5), 2013:

http://www.ijreat.org/Papers%202013/Issue5/IJREATV1I5020.pdf

If you need available software for analyzing "the quality of fused image" you are not seeking for "quality metrics software". James listed good references about software metrics. As he mentioned, the main oal of software quality metrics is to measure the quality of parts of a software systems (product metrics) or the way engineers build these parts (process metrics).

It seems that you need software to measure the quality of "fused images", which is totally different from software metrics tools (which measure software).

There are many possible quality values for image fusion. I used in one work, for example, edge preservation value, "universal image quality index" based measures and different human perception based measures, mutual information combined with fusion symmetry etc. I attached a pdf-file for the references (see ref 7-11).

As you can see, the different measures give slightly different results and one should use multiple measures and use some voting scheme. In addition to calculated values people have also used panels to give gradings for the result image quality, as the quality sometimes is difficult to define and also depends on the purpose of the fusion result...

I hope this gives some direction...

Two main approaches; user centric and software intrinsic based.

Currently, many try to measure quality from developer point of view, but the overall quality lies in the eyes of software users.

Which one are you looking to measure?

There are many International Standard Organization (ISO) standard frameworks that can support software quality; however they are generally checking list guides. For example, the ISO 9000 family has been criticized not to be used for software quality (Stelzer et al. 1997). The ANSI/IEEE 730-2002 of Poston (1985) support quality assurance plans. Capability Maturity Model Integration (CMMI) of Ahern et al. (2008) is a process improvement training and certification program. So, these ISO standards are neither designed to address quality-in-use nor specific product characteristics.

Recently, the Software Product Quality Requirements and Evaluation (SQuaRE) ISO standards’ series has been derived from the blending of ISO/IEC 9126 and ISO/IEC 14598 series of standards. The purpose of the SQuaRE series of standards is to assist in developing and acquiring software products with the specification of quality requirements and evaluation. From the viewpoint of the stakeholders the quality requirements are specified, while the quality of the product is evaluated based on this specification. The evaluation is based on the chosen quality model, quality measurement and quality management process.

The ISO/IEC 25010:2011 standard (ISO 25010 hereafter), a part of the SQuaRE series, has two major dimensions; Quality-in-Use and Product Quality. The former specifies characteristics related to the human interaction with the system and the latter specifies characteristics intrinsic to the product. It also has one complementary data model (the ISO/IEC 25012).

Issa