File: prn7.htmlref

package info (click to toggle)
cccc 1:3.1.4-4
  • links: PTS
  • area: main
  • in suites: wheezy
  • size: 3,956 kB
  • sloc: ansic: 33,244; cpp: 10,527; java: 622; makefile: 156; sh: 11
file content (199 lines) | stat: -rw-r--r-- 11,858 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
<HTML><HEAD><TITLE>
Report on software metrics
</TITLE>
</HEAD>
<BODY>
<TABLE BORDER WIDTH=100%>
<TR><TH COLSPAN=2>
CCCC Software Metrics Report
</TR>
<TR>
<TH><H4><A HREF="#projsum">Project Summary</A></H4></TH>
<TD>
Summary table of high level measures summed over all files processed in the current run.
</TR>
<TR>
<TH><H4><A HREF="#procsum">Procedural Metrics Summary</A></H4></TH>
<TD>
Table of procedural measures (i.e. lines of code, lines of comment, McCabe's cyclomatic complexity summed over each module.
</TR>
<TR>
<TH><H4><A HREF="#procdet">Procedural Metrics Detail</A></H4></TH>
<TD>
The same procedural metrics as in the procedural metrics summary, reported for individual functions, grouped by module.
</TR>
<TR>
<TH><H4><A HREF="#oodesign">Object Oriented Design</A></H4></TH>
<TD>
Table of four of the 6 metrics proposed by Chidamber and Kemerer in their various papers on 'a metrics suite for object oriented design'.
</TR>
<TR>
<TH><H4><A HREF="#structsum">Structural Metrics Summary</A></H4></TH>
<TD>
Structural metrics based on the relationships of each module with others.  Includes fan-out (i.e. number of other modules the current module uses), fan-in (number of other modules which use the current module), and the Information Flow measure suggested by Henry and Kafura, which combines these to give a measure of coupling for the module.
</TR>
<TR>
<TH><H4><A HREF="#structdet">Structural Metrics Detail</A></H4></TH>
<TD>
The names of the modules included as clients and suppliers in the counts for the Structural Metrics Summary.
</TR>
<TR>
<TH><H4><A HREF="#other">Other Extents</A></H4></TH>
<TD>
Lexical counts for parts of submitted source files which the analyser was unable to assign to a module. Each record in this table relates to either a part of the code which triggered a parse failure, or to the residual lexical counts relating to parts of a file not associated with a specific module.
</TR>
<TR>
<TH><H4><A HREF="#infocccc">About CCCC</A></H4></TH>
<TD>
A description of the CCCC program.
</TR>
</TR></TABLE>
<H1><A NAME="projsum">Project Summary</A></H1>
This table shows measures over the project as a whole.
<UL>
<LI>NOM = Number of modules<BR>
Number of non-trivial modules identified by the analyser.  Non-trivial modules include all classes, and any other module for which member functions are identified.
<LI>LOC = Lines of Code<BR>
Number of non-blank, non-comment lines of source code counted by the analyser.
<LI>COM = Lines of Comments<BR>
Number of lines of comment identified by the analyser
<LI>MVG = McCabe's Cyclomatic Complexity<BR>
A measure of the decision complexity of the functions which make up the program.The strict definition of this measure is that it is the number of linearly independent routes through a directed acyclic graph which maps the flow of control of a subprogram.  The analyser counts this by recording the number of distinct decision outcomes contained within each function, which yields a good approximation to the formally defined version of the measure.
<LI>L_C = Lines of code per line of comment<BR>
Indicates density of comments with respect to textual size of program
<LI>M_C = Cyclomatic Complexity per line of comment<BR>
Indicates density of comments with respect to logical complexity of program
<LI>IF4 = Information Flow measure<BR>
Measure of information flow between modules suggested by Henry and Kafura. The analyser makes an approximate count of this by counting inter-module couplings identified in the module interfaces.
</UL>
Two variants on the information flow measure IF4 are also presented, one (IF4v) calculated using only relationships in the visible part of the module interface, and the other (IF4c) calculated using only those relationships which imply that changes to the client must be recompiled of the supplier's definition changes.

<TABLE BORDER WIDTH=100%>
<TR>
<TH BGCOLOR="AQUA" WIDTH=70%>Metric</TH><TH BGCOLOR="AQUA" WIDTH=10%>Tag</TH><TH BGCOLOR="AQUA" WIDTH=10%>Overall</TH><TH BGCOLOR="AQUA" WIDTH=10%>Per Module</TH></TR>
<TR>
<TD>Number of modules</TD><TD>NOM</TD><TD ALIGN=RIGHT>     1</TD><TD>&nbsp;</TD></TR>
<TR>
<TD WIDTH=700%>Lines of Code</TD><TD WIDTH=120%>LOC</TD><TD ALIGN=RIGHT>    13</TD><TD ALIGN=RIGHT>13.000</TD></TR>
<TR>
<TD>McCabe's Cyclomatic Number</TD><TD>MVG</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT> 0.000</TD></TR>
<TR>
<TD>Lines of Comment</TD><TD>COM</TD><TD ALIGN=RIGHT>    34</TD><TD ALIGN=RIGHT>34.000</TD></TR>
<TR>
<TD>LOC/COM</TD><TD>L_C</TD><TD ALIGN=RIGHT>------</TD><TD>&nbsp;</TD></TR>
<TR>
<TD>MVG/COM</TD><TD>M_C</TD><TD ALIGN=RIGHT>------</TD><TD>&nbsp;</TD></TR>
<TR>
<TD>Information Flow measure ( &nbsp;inclusive&nbsp;)</TD><TD>IF4</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>   0.000</TD></TR>
<TR>
<TD>Information Flow measure ( &nbsp;visible&nbsp;)</TD><TD>IF4v</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>   0.000</TD></TR>
<TR>
<TD>Information Flow measure ( &nbsp;concrete&nbsp;)</TD><TD>IF4c</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>   0.000</TD></TR>
<TR>
<TD>Lines of Code rejected by parser</TD><TD>REJ</TD><TD ALIGN=RIGHT>     9</TD><TD>&nbsp;</TD></TR>
</TABLE>
<H1><A NAME="procsum">Procedural Metrics Summary</A></H1>
For descriptions of each of these metrics see the information preceding the project summary table.

The label cell for each row in this table provides a link to the functions table in the detailed report for the module in question
<TABLE BORDER WIDTH=100%>
<TR>
<TH BGCOLOR="AQUA">Module Name</TH><TH BGCOLOR="AQUA" WIDTH=8%>LOC</TH><TH BGCOLOR="AQUA" WIDTH=8%>MVG</TH><TH BGCOLOR="AQUA" WIDTH=8%>COM</TH><TH BGCOLOR="AQUA" WIDTH=8%>L_C</TH><TH BGCOLOR="AQUA" WIDTH=8%>M_C</TH></TR>
<TR>
<TD><A HREF="anonymous.html#procdet">
anonymous</A>
</TD><TD ALIGN=RIGHT>     4</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>     1</TD><TD ALIGN=RIGHT>------</TD><TD ALIGN=RIGHT>------</TD></TR>
</TABLE>
<H1><A NAME="procdet">Procedural Metrics Detail</A></H1>
<TABLE BORDER WIDTH=100%>
<TR>
<TD WIDTH=50%><A NAME="procdet"></A>
<A HREF="procsum">
anonymous</A>
<BR>
<BR>
</TD><TH BGCOLOR="AQUA" WIDTH=10%>LOC</TH><TH BGCOLOR="AQUA" WIDTH=10%>MVG</TH><TH BGCOLOR="AQUA" WIDTH=10%>COM</TH><TH BGCOLOR="AQUA" WIDTH=10%>L_C</TH><TH BGCOLOR="AQUA" WIDTH=10%>M_C</TH></TR>
<TR>
<TD>main( &nbsp;&nbsp;)<BR>
definition &nbsp;
<CODE><A HREF="cccc_src.html#prn7.c:        49">prn7.c:49</A></CODE><BR>
<BR>
</TD><TD ALIGN=RIGHT>     4</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>     1</TD><TD ALIGN=RIGHT>------</TD><TD ALIGN=RIGHT>------</TD></TR>
<TR><TD HEIGHT=12 COLSPAN=6></TD></TR>
</TABLE>
<H1><A NAME="oodesign">Object Oriented Design</A></H1>
<UL>
<LI>WMC = Weighted methods per class<BR>
The sum of a weighting function over the functions of the module.  Two different weighting functions are applied: WMC1 uses the nominal weight of 1 for each function, and hence measures the number of functions, WMCv uses a weighting function which is 1 for functions accessible to other modules, 0 for private functions.
<LI>DIT = Depth of inheritance tree<BR>
The length of the longest path of inheritance ending at the current module.  The deeper the inheritance tree for a module, the harder it may be to predict its behaviour.  On the other hand, increasing depth gives the potential of greater reuse by the current module of behaviour defined for ancestor classes.
<LI>NOC = Number of children<BR>
The number of modules which inherit directly from the current module.  Moderate values of this measure indicate scope for reuse, however high values may indicate an inappropriate abstraction in the design.
<LI>CBO = Coupling between objects<BR>
The number of other modules which are coupled to the current module either as a client or a supplier. Excessive coupling indicates weakness of module encapsulation and may inhibit reuse.
</UL>

The label cell for each row in this table provides a link to the module summary table in the detailed report for the module in question
<TABLE BORDER WIDTH=100%>
<TR>
<TH BGCOLOR="AQUA" WIDTH=50%>Module Name</TH><TH BGCOLOR="AQUA" WIDTH=10%>WMC1</TH><TH BGCOLOR="AQUA" WIDTH=10%>WMCv</TH><TH BGCOLOR="AQUA" WIDTH=10%>DIT</TH><TH BGCOLOR="AQUA" WIDTH=10%>NOC</TH><TH BGCOLOR="AQUA" WIDTH=10%>CBO</TH></TR>
<TR>
<TD><A HREF="anonymous.html#summary">
anonymous</A>
</TD><TD ALIGN=RIGHT>     1</TD><TD ALIGN=RIGHT>     1</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>     0</TD></TR>
</TABLE>
<H1><A NAME="structsum">Structural Metrics Summary</A></H1>
<UL>
<LI>FI = Fan-in<BR>
The number of other modules which pass information into the current module.
<LI>FO = Fan-out<BR>
The number of other modules into which the current module passes information
<LI>IF4 = Information Flow measure<BR>
A composite measure of structural complexity, calculated as the square of the product of the fan-in and fan-out of a single module.  Proposed by Henry and Kafura.
</UL>
Note that the fan-in and fan-out are calculated by examining the interface of each module.  As noted above, three variants of each each of these measures are presented: a count restricted to the part of the interface which is externally visible, a count which only includes relationships which imply the client module needs to be recompiled if the supplier's implementation changes, and an inclusive count

The label cell for each row in this table provides a link to the relationships table in the detailed report for the module in question

<TABLE BORDER WIDTH=100%>
<TR>
<TH BGCOLOR=AQUA ROWSPAN=2>Module Name</TH>
<TH BGCOLOR=AQUA COLSPAN=3>Fan-out</TH>
<TH BGCOLOR=AQUA COLSPAN=3>Fan-in</TH>
<TH BGCOLOR=AQUA COLSPAN=3>IF4</TH>
</TR>
<TH BGCOLOR="AQUA" WIDTH=7%>vis</TH><TH BGCOLOR="AQUA" WIDTH=7%>con</TH><TH BGCOLOR="AQUA" WIDTH=7%>inc</TH><TH BGCOLOR="AQUA" WIDTH=7%>vis</TH><TH BGCOLOR="AQUA" WIDTH=7%>con</TH><TH BGCOLOR="AQUA" WIDTH=7%>incl</TH><TH BGCOLOR="AQUA" WIDTH=7%>vis</TH><TH BGCOLOR="AQUA" WIDTH=7%>con</TH><TH BGCOLOR="AQUA" WIDTH=7%>inc</TH></TR>
<TR>
<TD><A HREF="anonymous.html#structdet">
anonymous</A>
</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>     0</TD><TD ALIGN=RIGHT>     0</TD></TR>
</TABLE>
<H1><A NAME="structdet">Structural Metrics Detail</A></H1>
<TABLE BORDER WIDTH=100%>
<TR>
<TH BGCOLOR="AQUA" WIDTH=20%>Module Name</TH><TH BGCOLOR="AQUA" WIDTH=40%>Clients</TH><TH BGCOLOR="AQUA" WIDTH=40%>Suppliers</TH></TR>
<TR>
<TD><A NAME="structdet"></A>
<A HREF="structsum">
anonymous</A>
</TD><TD WIDTH=50%>
&nbsp;
</TD>
<TD WIDTH=50%>
&nbsp;
</TD>
</TR>
</TABLE>
<H1><A NAME="other">Other Extents</A></H1>
<TABLE BORDER WIDTH=100%>
<TR>
<TH BGCOLOR="AQUA" WIDTH=25%>Location</TH><TH BGCOLOR="AQUA" WIDTH=45%>Text</TH><TH BGCOLOR="AQUA" WIDTH=10%>LOC</TH><TH BGCOLOR="AQUA" WIDTH=10%>COM</TH><TH BGCOLOR="AQUA" WIDTH=10%>MVG</TH></TR>
<TR><TD><CODE><A HREF="cccc_src.html#prn7.c:         1">prn7.c:1</A></CODE><BR>
</TD>
<TD>&lt;file scope items&gt;</TD><TD ALIGN=RIGHT>     9</TD><TD ALIGN=RIGHT>    33</TD><TD ALIGN=RIGHT>     0</TD></TR>
</TABLE>
<H1><A NAME="infocccc">About CCCC</A></H1>
<P>This report was generated by the program CCCC, which is FREELY REDISTRIBUTABLE but carries NO WARRANTY.
<P>CCCC was developed by Tim Littlefair. 
as part of a PhD research project. This project is now completed and descriptions of the findings can be accessed at <A HREF=http://www.chs.ecu.edu.au/~tlittlef>http://www.chs.ecu.edu.au/~tlittlef</A>. <P>User support for CCCC can be obtained by <A HREF=mailto:cccc-users@lists.sourceforge.net>mailing the list cccc-users@lists.sourceforge.net</A>.<P>Please also visit the CCCC development website at <A HREF=http://cccc.sourceforge.net>http://cccc.sourceforge.net</A>.
</BODY></HTML>