Author Topic: Metrics for Component Based Measurement Tools  (Read 1670 times)

0 Members and 1 Guest are viewing this topic.

IJSER Content Writer

  • Sr. Member
  • ****
  • Posts: 327
  • Karma: +0/-1
    • View Profile
Metrics for Component Based Measurement Tools
« on: August 20, 2011, 06:14:54 am »
Quote
Author : P. Edith Linda, V. Manju Bashini, S. Gomathi
International Journal of Scientific & Engineering Research, Volume 2, Issue 5, May-2011
ISSN 2229-5518
Download Full Paper : PDF

Abstract— The main aim of this paper is to integrate the different object oriented metric tools and make them available as a single add-on. The first part of this paper analyzed five different tools and they are migrated into one to make use of those tools in efficient manner.
Index Terms— Metrics, component, de-compiler, SLOC, LOC, NOS, NOP, Cyclomatic complexity

1   INTRODUCTION                                                                      
THE emerging Object oriented programming is most widely used by the programmers to develop the software. The object oriented programs are used in the IT world which is used for secured transactions and mainly convenient. Even though they are widely used, the complex and confusing structure may arise if the program is not properly measured and not properly structured. To overcome this problem many proposed varieties of metric tools to measure the criteria of Object oriented programming are used. Again the problem arises that some metric tools measure the particular criteria of the object oriented programs. In order to overcome the individuality of those tools, they should be migrated.

Component based measurement tool is the concept of migrating many tools available widely. The main aim is to search some important tools and making them as a single add-on to provide the user friendly environment.
Each individual tool will measure some parameter to measure the java program. But  a single tool will not measure all the parameters.
Thus there exist a need of collection of tools to measure the java programs which will satisfy all the parameters to be measured.
2     METRICS
Software metrics are used to measure the software quality to check whether it satisfies the        require-ments. Metrics are defined as “Quantifiable measures that could be used to measure      characteristics of a software system or the software development process.”  Software metrics are essential to plan, predict, monitor, control, evaluate, products and processes. The main goal of the software metrics is to reduce costs, Improve quality, Control/Monitor schedule, small testing effort, many reusable fragments, to better understand the quality of the product and the program.

3   METRICS CATEGORIZATION
Metrics can be categorized into three Kinds, measures and size.

Two kinds of software metrics they are Product metrics: quantify characteristics of the product being developed to measure the size, reliability and Process metrics: quantify characteristics of the process being used to develop the software to measure the efficiency of fault detection.

Types of Measures are Direct Measures (internal attributes): to measure the Cost, effort, LOC, speed, memory and Indirect Measures (external attributes): to measure the Functionality, quality, complexity, effi-ciency, reliability, maintainability.

Size-oriented metrics are LOC - Lines Of Code, KLOC - 1000 Lines Of Code, LOC – Statement Lines of Code (ignore whitespace).
   
4   COMPONENT
Components are the collections of many pre pro-grammed tools which is used as the add-on page which is to make use of those tools. There are various tools available to measure the Java source code. Those tools are developed and modeled based on the developer’s point of view. Some tools will measure some parameters to be measured in java program. Initially the tools which are used to measure the java object oriented programs are searched and analyzed individually to make it as a component. The component based tools will be executed separately but available in a same location and some tools will provide a chart for the results when the program is executed.
5   EVOLUTION OF COMPONENTS
In 1990’s, software systems for e-business transactions were built of components across multiple platforms, programming language and network protocols. No tools were available for detecting “bugs” or to measure the efficiencies in the programs (object oriented pro-grams). Initially the errors are printed using the output statement and the number of lines [1] , number of packages and most important concepts of object oriented programs with the critical programs
Those programs which are used to measure the OOPS programs seem to be critical and they are imple-mented with the large number of coding.  In 1997, Inter-metrics, a software engineering company , proposed to develop a debugging tool for Component- based software systems. It only identifies the errors and yields the error free program.
But finding the error won’t give the remedy. Thus the problem to find the efficiency of the program is solved with the help of the component based tools which efficiently provides the charts for the results and measures the program.
The main advantage of component based tool is that the user can select their own tool to measure their program according to their needs. In this, the user can also see the links from where the tools are available, that is the user can also download or know more about the tool from the direct link.
The collection of more tools which will provide more flexibility and choice to the user or the pro-grammer and he can know more about tools. Those tools will display an error if the program is not correct.
Some tools will also provide the charts and warning message if the program is not structured and programmed in a proper format based on the mea-surement criteria.

Read More: Click here...