response for a class (RFC)
So-called software metrics, which quantify different properties of software products and processes, are used to measure software products. When measuring software, an object-oriented metric takes into account the grouping of data structures and the methods applicable to them to form an object, its relationships to other objects and the general structural features of object-oriented programming.
The metric after Response for a Class (RFC) is to be classified into the group of the measures, which make software measurable on class level. Further object-oriented software metrics are Weighted Methods for Class(WMC), Coupling Between Objects( CBO), Depth of Inheritance Tree( DIT), Lack of Cohesion in Methods( LCOM) and Number of Children ( NOC).
RFCdefinition: RFC is the number of all possible methods to be executed.
All possible direct and indirect method calls that can be reached via associations are evaluated.
The class diagram shown defines the static parts of a system of classes with their associations and methods.
Example class diagram: RFC(A)=4 and RFC(B)=2 and RFC(C)=1, RFC(F)=0.
Application: Mainly in connection with the testability and maintainability of software. This is based on the consideration that a class is to be understood and treated the more complex, the larger the number of its methods as well as couplings with other classes is. The complexity entails then also a higher expenditure - a increased degree of difficulty - with changes. The value for Response for a Class (RFC) also specifies the maximum number of possible calls to methods and thus specifically defines the number of test cases.