SOFTWARE COMPONENT METRICS

Software Component Metrics



Software Component Metrics

Introduction

Formally, one speaks of the metric on a software unit to apply it for its better functioning. The result is the measure. Since the source code is typically divided into one or a plurality of individual files, the metric can be used depending on the type of the whole or parts of the source code. There are also metrics, such as the function point analysis that can be applied to the specification of this software to determine the costs for developing the software in advance. In the form of the numerical value, the measured value, the metric is a measure of a characteristic, a quality characteristic of the software. One can have a functional relationship represented or be derived from a checklist. Simple metrics point to the size of the source code in lines or characters, more complex metrics try to assess the comprehensibility of source code (Gui & Scott, pp.797-805, 2009). With a suitable number of different metrics can be assessed as consuming (i.e. labor and cost-intensive) the maintenance, development and subsequent testing of the software. From a newly developed program, not only certain functions are often required, but also quality characteristics such as maintainability, extensibility and understandability. Software metrics cannot establish a correct implementation of the evaluating functions, they can predetermine if needed, how much effort will prepare about the creation of the software and how many errors will occur (Ossher & Adviser-Lopes, 2013).

Discussion

The component-oriented programming (POC) is to use a modular approach to the architecture of an IT project, which ensures the software readability and better maintenance. Developers, instead of creating a monolithic executable, use reusable bricks.

The POC is not without similarities with OOP, as equivalent to using an object approach, not in the code, but at the general architecture of the software. The POC is particularly useful for teamwork and allows industrialize software development.

What is a Component

When we speak of components, it is simple files, usually containing the compiled code . In type systems Unix, for example, the components in the form of files with the extension . so (shared object). In type systems Microsoft Windows, it is the famous DLL (dynamic link library). There is also talk of modules, libraries or bookstores, abuse Translation (library being a false friend and meaningful library) (Gui & Scott, 2008).

It is possible to create components with most programming languages. However, in some cases, especially for interpreted languages or semi-compiled it is not possible to create "classic" components. For example, in python, the components are single files containing code (. py), while in Java, it is possible to create class libraries (. jar). Thus, only a program written in Java can be used as a component. Jar file (Abdellatief, Sultan & Jabar, 2012).

Component includes a number of features that can be called from an external program, or client. As component contains the compiled code, it is a priori not possible to know how they are implemented, unless you have the source ...