This is a Software Design Metric Dashboard (Diamond) Report, it is one of reports that Balanced Scorecard Designer can generate for Software Design KPI. With this software you can also design your own scorecards, KPIs and metrics.

Software Design Balanced Scorecard

Report includes: 2 day(s), from 19.01.2009 to 20.01.2009

Name

Start value

End value

Dynamic

Contains

Software Design Balanced Scorecard

49,46 %

42,65 %

-6,81 %

Quality Perspective	(55,6%, 6,25%)
Exception Handling and Operations Perspective	(29,4%, -24,12%)
Logical Size and Complexity Perspective	(48,4%, -4,73%)
Design Efforts Perspective	(27,7%, -12,2%)

Graph for Software Design Balanced Scorecard

Data for Software Design Balanced Scorecard

Dates	Value
19.01.2009	49,46
20.01.2009	42,65

Quality Perspective

Name

Start value

End value

Dynamic

Parent

Contains

Quality Perspective

49,39 %

55,64 %

+ 6,25%

Software Design Balanced Scorecard

Indicators

Compatibility Index

Security and fault-bearing Ratio

Reliability Claim Meeting

Other quality enhancing features *

* - Information for this metric is limited in sample report Description This is to ensure that the resultant software has enough number of attributes to boast off.

Graph for Quality Perspective

Data for Quality Perspective

Dates	Value	Weight
19.01.2009	49,39	3
20.01.2009	55,64	3

Compatibility Index

	Name	Start value	End value	Dynamic	Measure units	Optimization method	Parent
	Compatibility Index	0,9535	0,941	-0,0125	#	Maximize	Quality Perspective

Description This shows whether the software gels well with the other components for interoperability. Sometimes, the issue 'whether it can be accommodated with the older versions' is an important consideration. This makes it important to pay the deserving attention to this subject.

Graph for Compatibility Index

Data for Compatibility Index

Dates	Weight	Min	Max	Value
19.01.2009	3	0,75	1	0,9535
20.01.2009	3	0,75	1	0,941

Security and fault-bearing Ratio

	Name	Start value	End value	Dynamic	Measure units	Optimization method	Parent
	Security and fault-bearing Ratio	0,9454	0,9584	+ 0,013	#	Maximize	Quality Perspective

Description This parameter can be had by examining the extent to which the software can withstand the intrusions by viruses and recover on itself.

Graph for Security and fault-bearing Ratio

Data for Security and fault-bearing Ratio

Dates	Weight	Min	Max	Value
19.01.2009	2	0,8	1	0,9454
20.01.2009	2	0,8	1	0,9584

Reliability Claim Meeting

	Name	Start value	End value	Dynamic	Measure units	Optimization method	Parent
	Reliability Claim Meeting	86,18	85,76	-0,42	%	Maximize	Quality Perspective

Description Reliability refers to the capability of the software of performing 'a specific function' under 'given conditions' for 'stated period of time'.

Graph for Reliability Claim Meeting

Data for Reliability Claim Meeting

Dates	Weight	Min	Max	Value
19.01.2009	3	80	100	86,18
20.01.2009	3	80	100	85,76

Exception Handling and Operations Perspective

Name

Start value

End value

Dynamic

Parent

Contains

Exception Handling and Operations Perspective

53,53 %

29,41 %

-24,12%

Software Design Balanced Scorecard

Indicators

Exception Failure Fraction

Number of run-time exceptions

Number of manually created exceptions

Number of Operations *

* - Information for this metric is limited in sample report Description This group of KPIs is to gauge the software's potency of handling 'exception failures'. The designers must take care of this requirement while proceeding with the task.

Graph for Exception Handling and Operations Perspective

Data for Exception Handling and Operations Perspective

Dates	Value	Weight
19.01.2009	53,53	2
20.01.2009	29,41	2

Exception Failure Fraction

	Name	Start value	End value	Dynamic	Measure units	Optimization method	Parent
	Exception Failure Fraction	27,6	27,675	+ 0,075	%	Minimize	Exception Handling and Operations Perspective

Description There are basically two identified causes for system failures- errors that relate to logics in the code and exception failures. The latter, which occur due to unexpected surroundings constitute a major portion, so should be treated well enough. The value of this metric can be obtained by dividing the 'number of instances when exception failure occurs' to 'total number of failures'.

Graph for Exception Failure Fraction

Data for Exception Failure Fraction

Dates	Weight	Min	Max	Value
19.01.2009	3	0	75	27,6
20.01.2009	3	0	75	27,675

Number of run-time exceptions

	Name	Start value	End value	Dynamic	Measure units	Optimization method	Parent
	Number of run-time exceptions	8,961	4,055	-4,906	#	Maximize	Exception Handling and Operations Perspective

Description Some of the problematic cases, which the software must be able to combat are- division by zero, array creation with negative index, out-of-bound array index and null reference's invalid use.

Graph for Number of run-time exceptions

Data for Number of run-time exceptions

Dates	Weight	Min	Max	Value
19.01.2009	2	4	15	8,961
20.01.2009	2	4	15	4,055

Number of manually created exceptions

	Name	Start value	End value	Dynamic	Measure units	Optimization method	Parent
	Number of manually created exceptions	8,698	4,554	-4,144	#	Maximize	Exception Handling and Operations Perspective

Description These include errors like entering an invalid range for input variable, incorrect data formats etc.

Graph for Number of manually created exceptions

Data for Number of manually created exceptions

Dates	Weight	Min	Max	Value
19.01.2009	2	3	10	8,698
20.01.2009	2	3	10	4,554

Logical Size and Complexity Perspective

Name

Start value

End value

Dynamic

Parent

Contains

Logical Size and Complexity Perspective

53,15 %

48,42 %

-4,73%

Software Design Balanced Scorecard

Indicators

SLOC measure

Average development time

Cyclomatic Complexity

Blank Line Contribution *

* - Information for this metric is limited in sample report Description This class of indicators is to assess the size of the software, logically and not in physical terms.

Graph for Logical Size and Complexity Perspective

Data for Logical Size and Complexity Perspective

Dates	Value	Weight
19.01.2009	53,15	3
20.01.2009	48,42	3

SLOC measure

	Name	Start value	End value	Dynamic	Measure units	Optimization method	Parent
	SLOC measure	74000002,6	43100005,69	-3,09E007	#	Maximize	Logical Size and Complexity Perspective

Description Source Line of Codes (SLOC) gives the size of the program. The value is equal to number of lines that make up the text of program's source code. This reflects the programming productivity and efforts that go into making it.

Graph for SLOC measure

Data for SLOC measure

Dates	Weight	Min	Max	Value
19.01.2009	2	10	100000000	74000002,6
20.01.2009	2	10	100000000	43100005,69

Average development time

	Name	Start value	End value	Dynamic	Measure units	Optimization method	Parent
	Average development time	3	58,2	+ 55,2	%	Maximize	Logical Size and Complexity Perspective

Description This shows the efficiency of team in 'getting over with the assigned task'. The magnitude can be had using the relation- T = E/S (where S is the Strouds number (18); E is the amount of effort)

Graph for Average development time

Data for Average development time

Dates	Weight	Min	Max	Value
19.01.2009	3	0	100	3
20.01.2009	3	0	100	58,2

Cyclomatic Complexity

	Name	Start value	End value	Dynamic	Measure units	Optimization method	Parent
	Cyclomatic Complexity	95,5	14,2	-81,3	%	Maximize	Logical Size and Complexity Perspective

Description This measure was developed by Thomas McCabe to know the level of stability and confidence in a given program. The value is equal to the linearly independent paths in a program module. A program with lower value of this parameter shows that it can be easily understood and modified.

Graph for Cyclomatic Complexity

Data for Cyclomatic Complexity

Dates	Weight	Min	Max	Value
19.01.2009	3	0	100	95,5
20.01.2009	3	0	100	14,2

Design Efforts Perspective

Name

Start value

End value

Dynamic

Parent

Contains

Design Efforts Perspective

39,94 %

27,74 %

-12,2%

Software Design Balanced Scorecard

Indicators

Study

Create

Review

Testing *

Correction *

* - Information for this metric is limited in sample report Description This class of indicators is to know the fraction of total efforts that go into various steps of the design process, as whole.

Graph for Design Efforts Perspective

Data for Design Efforts Perspective

Dates	Value	Weight
19.01.2009	39,94	2
20.01.2009	27,74	2

Study

	Name	Start value	End value	Dynamic	Measure units	Optimization method	Parent
	Study	3,66	2,996	-0,664	%	Maximize	Design Efforts Perspective

Description This KPI indicates the quantitative value of the attempts put for doing the pre-design study.

Graph for Study

Data for Study

Dates	Weight	Min	Max	Value
19.01.2009	2	2	6	3,66
20.01.2009	2	2	6	2,996

Create

	Name	Start value	End value	Dynamic	Measure units	Optimization method	Parent
	Create	53,525	53,735	+ 0,21	%	Maximize	Design Efforts Perspective

Description This is to know the portion of efforts that go into creation of design.

Graph for Create

Data for Create

Dates	Weight	Min	Max	Value
19.01.2009	2	50	65	53,525
20.01.2009	2	50	65	53,735

Review

	Name	Start value	End value	Dynamic	Measure units	Optimization method	Parent
	Review	7,978	7,468	-0,51	%	Maximize	Design Efforts Perspective

Description Review too, is an important piece of designing puzzle.

Graph for Review

Data for Review

Dates	Weight	Min	Max	Value
19.01.2009	2	4	10	7,978
20.01.2009	2	4	10	7,468

Created by: AKS-Labs
Report created with Balanced Scorecard Designer at 15.01.2009 17:38:13