You are on page 1of 3

ASSIGNMENT#1

CRITICAL REVIEW
WRITING
SUBMITTED TO MA’AM
AQSA ALI
SUBMITTED BY
BITF16A501
CRITICAL REVIEW?
The summarization and evaluation of ideas and information in any article is called
Critical Review writing.

ARTICLE: “Software Quality Metrics for Object-Oriented Environments”

http://people.ucalgary.ca/~far/Lectures/SENG421/PDF/oocross.pdf

INTRODUCTION:
To evaluate software which are object orientation based software matrices are being
used for quality, maintenance and development. Here we are going to discuss about
the traditional structures and object orientation based structures. And which of the
new found matrices are good for object orientation based concepts.

MAIN:
Metrics based on object orientation include both the combination of data and
function as integrated and can be used in evaluation of different features attributes
like Efficiency, Understandability, Complexity, Reusability, and Maintainability. The
SATC found disagreement in software quality metrics. In object orientation system
traditional metrics are used in the methods that use the operations of a class. Two
metrics which are traditional are used one is cyclometic complexity in which quality
of an algorithm is tested which should be less than 10 which is a good quality
measure. The other traditional metrics is line count or size in which use of high lines
count will be reflecting like high risks of understandability maintainability and
reusability. The third metrics used is comments in which a formula is used to calculate
the percentage of the code which may be good if it’s up to 30%.

On the other hand object oriented metrics use the concepts of class coupling and
inheritance. The class metrics are used which are Methods Messages and Cohesion.
Method is defines in a class and operates upon an object. For understandability
reusability and Maintainability the count of methods is taken which tells the quality of
code. More the count more less the quality is. The second is Message response. The
greater the number of methods invoked from class through messages the greater is
the complexity since it will require a great effort to understand from tester’s point of
view. The third metrics is cohesion which is degree of the bounded methods or related
methods. Less or lack of the cohesion may result in bad quality and increasing
complexity. And efficiency and reusability can be measured by this metrics. The fourth
metrics is use of Coupling and if it is less than it will promote encapsulation and
modularity. So a good balance of coupling and cohesion is required for good quality
soft wares.

After the CLASS approach another way used in OOAD is the use of inheritance. It uses
two metrics one is DIT depth of inheritance tree and other is number of children NOC.
It evaluates efficiency and reuse. Deeper trees depth tells more complexity. Similarly
greater the NOC greater the reusability in a class and greater is the Inheritance. So this
metrics focus on evaluating Testing, Reusability, and Efficiency.

CRITIQUE:
The five attributes telling the product quality includes Efficiency, Reusability,
Complexity, Understandability and Maintainability. Depending on the Application
objectives and quality attributes the desired threshold values can be achieved. So we
will be focusing in future to develop good criteria for metrics developments to obtain
good quality codes and designs. This will be helping out a lot of complexities for
coders and developers in future world and greater results in achieving good quality
products.

You might also like