This is a Software Design Balanced Scorecard Report, it is one of reports that Balanced Scorecard Designer can generate for Software Design scorecard. With this software you can also design your own KPIs, Balanced Scorecards and metrics.


Software Design Balanced Scorecard

Report includes: 1 month(s) 49 day(s), from 23.12.2008 to 10.02.2009

  Name Start value End value Dynamic Contains
Root Software Design Balanced Scorecard  50,74 % 40,26 % -10,48 %
Quality Perspective(44,9%, -10,82%Down)
Exception Handling and Operations Perspective(30%, -29,47%Down)
Logical Size and Complexity Perspective(34,6%, -2,78%Down)
Design Efforts Perspective(52%, -2,56%Down)

Graph for Software Design Balanced Scorecard

Graph for Software Design Balanced Scorecard

Data for Software Design Balanced Scorecard

DatesValue
23.12.200850,74
30.12.200846,35
06.01.200948,2
13.01.200957,34
20.01.200946,03
27.01.200951,49
03.02.200948,41
10.02.200940,26


Quality Perspective

  Name Start value End value Dynamic Parent Contains
Root Quality Perspective  55,69 % 44,87 % -10,82% 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

Graph for Quality Perspective

Data for Quality Perspective

DatesValueWeight
23.12.200855,693
30.12.200843,333
06.01.200965,483
13.01.2009653
20.01.200955,543
27.01.200959,953
03.02.200922,693
10.02.200944,873


Compatibility Index

  Name Start value End value Dynamic Measure units Optimization method Parent
Root Compatibility Index  0,94675 0,931 -0,0157 # 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

Graph for Compatibility Index

Data for Compatibility Index

DatesWeightMinMaxValue
23.12.200830,7510,94675
30.12.200830,7510,772
06.01.200930,7510,981
13.01.200930,7510,99025
20.01.200930,7510,9525
27.01.200930,7510,86025
03.02.200930,7510,78625
10.02.200930,7510,931


Security and fault-bearing Ratio

  Name Start value End value Dynamic Measure units Optimization method Parent
Root Security and fault-bearing Ratio  0,9454 0,804 -0,141 # 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

Graph for Security and fault-bearing Ratio

Data for Security and fault-bearing Ratio

DatesWeightMinMaxValue
23.12.200820,810,9454
30.12.200820,810,9216
06.01.200920,810,8324
13.01.200920,810,8316
20.01.200920,810,9682
27.01.200920,810,9786
03.02.200920,810,8468
10.02.200920,810,804


Reliability Claim Meeting

  Name Start value End value Dynamic Measure units Optimization method Parent
Root Reliability Claim Meeting   80,04 91,22 + 11,18 % 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

Graph for Reliability Claim Meeting

Data for Reliability Claim Meeting

DatesWeightMinMaxValue
23.12.200838010080,04
30.12.200838010093,5
06.01.200938010091,64
13.01.200938010095,78
20.01.200938010084,68
27.01.200938010098,6
03.02.200938010083,6
10.02.200938010091,22


Exception Handling and Operations Perspective

  Name Start value End value Dynamic Parent Contains
Root Exception Handling and Operations Perspective  59,45 % 29,98 % -29,47% 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

Graph for Exception Handling and Operations Perspective

Data for Exception Handling and Operations Perspective

DatesValueWeight
23.12.200859,452
30.12.200847,522
06.01.200940,572
13.01.200960,242
20.01.200948,892
27.01.200931,292
03.02.200965,452
10.02.200929,982


Exception Failure Fraction

  Name Start value End value Dynamic Measure units Optimization method Parent
Root Exception Failure Fraction  5,1 68,775 + 63,68 % 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

Graph for Exception Failure Fraction

Data for Exception Failure Fraction

DatesWeightMinMaxValue
23.12.200830755,1
30.12.2008307523,925
06.01.2009307561,425
13.01.2009307517,775
20.01.2009307546,05
27.01.2009307554,3
03.02.2009307545
10.02.2009307568,775


Number of run-time exceptions

  Name Start value End value Dynamic Measure units Optimization method Parent
Root Number of run-time exceptions  13,13 4,924 -8,206 # 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

Graph for Number of run-time exceptions

Data for Number of run-time exceptions

DatesWeightMinMaxValue
23.12.2008241513,13
30.12.2008241510,182
06.01.200924154,154
13.01.200924155,661
20.01.200924155,727
27.01.2009241510,941
03.02.2009241511,59
10.02.200924154,924


Number of manually created exceptions

  Name Start value End value Dynamic Measure units Optimization method Parent
Root Number of manually created exceptions  3,371 6,206 + 2,835 # 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

Graph for Number of manually created exceptions

Data for Number of manually created exceptions

DatesWeightMinMaxValue
23.12.200823103,371
30.12.200823107,235
06.01.200923108,124
13.01.200923107,487
20.01.200923109,447
27.01.200923104,106
03.02.200923106,619
10.02.200923106,206


Logical Size and Complexity Perspective

  Name Start value End value Dynamic Parent Contains
Root Logical Size and Complexity Perspective  37,42 % 34,64 % -2,78% 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

Graph for Logical Size and Complexity Perspective

Data for Logical Size and Complexity Perspective

DatesValueWeight
23.12.200837,423
30.12.200844,113
06.01.200943,793
13.01.200939,43
20.01.200932,513
27.01.200955,263
03.02.200958,493
10.02.200934,643


SLOC measure

  Name Start value End value Dynamic Measure units Optimization method Parent
Root SLOC measure  85700001,43 40600005,94 -4,51E007 # 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

Graph for SLOC measure

Data for SLOC measure

DatesWeightMinMaxValue
23.12.200821010000000085700001,43
30.12.200821010000000026200007,38
06.01.200921010000000014200008,58
13.01.200921010000000097200000,28
20.01.200921010000000031400006,86
27.01.200921010000000051400004,86
03.02.200921010000000075400002,46
10.02.200921010000000040600005,94


Average development time

  Name Start value End value Dynamic Measure units Optimization method Parent
Root Average development time  43,3 3,2 -40,1 % 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

Graph for Average development time

Data for Average development time

DatesWeightMinMaxValue
23.12.20083010043,3
30.12.20083010016,4
06.01.20093010080,9
13.01.20093010040
20.01.20093010045,3
27.01.20093010076,3
03.02.20093010061,7
10.02.2009301003,2


Cyclomatic Complexity

  Name Start value End value Dynamic Measure units Optimization method Parent
Root Cyclomatic Complexity  14,5 73,2 + 58,7 % 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

Graph for Cyclomatic Complexity

Data for Cyclomatic Complexity

DatesWeightMinMaxValue
23.12.20083010014,5
30.12.20083010085,5
06.01.2009301003,8
13.01.2009301002,8
20.01.2009301007,8
27.01.20093010070,1
03.02.20093010028,2
10.02.20093010073,2


Design Efforts Perspective

  Name Start value End value Dynamic Parent Contains
Root Design Efforts Perspective  54,6 % 52,04 % -2,56% 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

Graph for Design Efforts Perspective

Data for Design Efforts Perspective

DatesValueWeight
23.12.200854,62
30.12.200853,082
06.01.200936,522
13.01.200969,842
20.01.200949,22
27.01.200953,342
03.02.200954,822
10.02.200952,042


Study

  Name Start value End value Dynamic Measure units Optimization method Parent
Root Study  3,156 3,364 + 0,208 % Maximize Design Efforts Perspective
Description This KPI indicates the quantitative value of the attempts put for doing the pre-design study.

Graph for Study

Graph for Study

Data for Study

DatesWeightMinMaxValue
23.12.20082263,156
30.12.20082263,864
06.01.20092262,036
13.01.20092264,476
20.01.20092264,244
27.01.20092265,792
03.02.20092264,64
10.02.20092263,364


Create

  Name Start value End value Dynamic Measure units Optimization method Parent
Root Create  60,14 52,88 -7,26 % Maximize Design Efforts Perspective
Description This is to know the portion of efforts that go into creation of design.

Graph for Create

Graph for Create

Data for Create

DatesWeightMinMaxValue
23.12.20082506560,14
30.12.20082506564,7
06.01.20092506561,4
13.01.20092506562,72
20.01.20092506562,3
27.01.20092506559,465
03.02.20092506551,62
10.02.20092506552,88


Review

  Name Start value End value Dynamic Measure units Optimization method Parent
Root Review  5,788 5,572 -0,216 % Maximize Design Efforts Perspective
Description Review too, is an important piece of designing puzzle.

Graph for Review

Graph for Review

Data for Review

DatesWeightMinMaxValue
23.12.200824105,788
30.12.200824106,328
06.01.200924108,11
13.01.200924108,536
20.01.200924104,678
27.01.200924106,91
03.02.200924106,838
10.02.200924105,572
Created by: AKS-Labs
Report created with Balanced Scorecard Designer at 15.01.2009 17:37:57

Copyright © 2000-2012 AKS-Labs. All rights reserved.