24-03-2012, 04:18 PM
Coupling-based Structural metrics.
[attachment=18923]
INTRODUCTION
1.1.Objective:
The main objective of this Project is to measure the quality of modularization of object-oriented projects by Coupling-based Structural metrics.
Goal is to analyses or measure how the code is framed for the particular software and Applying Software metrics to show the result.
1.2.Methodology
Much work has been done during the last several years on automatic approaches for code reorganization. Fundamental to any attempt at code reorganization is the division of the software into modules, publication of the API (Application Programming Interface) for the modules, and then requiring that the modules access each other’s resources only through the published interfaces.
Modularization
In this context "module" is considered to be a responsibility assignment rather than a subprogram. The modularizations include the design decisions which must be made before the work on independent modules can begin. Quite different decisions are included for each alternative, but in all cases the intention is to describe all "system level" decisions (i.e. decisions which affect more than one module).
Analysis of Existing System:
In the existing system large number of coding are divided into only two modules, so each module contains large number of coding. So in the existing system performance analysis takes more time as well as not more accurate.
Some of the earliest contributions to software metrics deal with the measurement of code complexity and maintainability . From the standpoint of code modularization, some of the earliest software metrics are based on the notions of coupling and cohesion . Low intermodule coupling, high intramodule cohesion, and low complexity have always been deemed to be important attributes of any modularized software. The above-mentioned early developments in software metrics naturally led several researchers to question their theoretical validity. Theoretical validation implies conformance to a set of agreed-upon principles and these principles are usually stated in the form of a theoretical framework.
Process of Proposed System:
Modern software engineering dictates that a large body of software be organized into a set of modules. A module captures a set of design decisions
which are hidden from other modules and the interaction among the modules should primarily be through module interfaces. In software engineering parlance, a module groups a set of functions or subprograms and data structures and often implements one or more business concepts. This grouping may take place on the basis of similarity of purpose or on the basis of commonality of goal
In the Proposed system we considered the leaf nodes of the directory hierarchy of the original source code to be the most fine-grained functional modules. All the files (and functions within) inside a leaf level directory were considered to belong to a single module. In this manner, all leaf level directories formed the module set for the software. After that we apply Coupling-based Structural Metrics as follows
[attachment=18923]
INTRODUCTION
1.1.Objective:
The main objective of this Project is to measure the quality of modularization of object-oriented projects by Coupling-based Structural metrics.
Goal is to analyses or measure how the code is framed for the particular software and Applying Software metrics to show the result.
1.2.Methodology
Much work has been done during the last several years on automatic approaches for code reorganization. Fundamental to any attempt at code reorganization is the division of the software into modules, publication of the API (Application Programming Interface) for the modules, and then requiring that the modules access each other’s resources only through the published interfaces.
Modularization
In this context "module" is considered to be a responsibility assignment rather than a subprogram. The modularizations include the design decisions which must be made before the work on independent modules can begin. Quite different decisions are included for each alternative, but in all cases the intention is to describe all "system level" decisions (i.e. decisions which affect more than one module).
Analysis of Existing System:
In the existing system large number of coding are divided into only two modules, so each module contains large number of coding. So in the existing system performance analysis takes more time as well as not more accurate.
Some of the earliest contributions to software metrics deal with the measurement of code complexity and maintainability . From the standpoint of code modularization, some of the earliest software metrics are based on the notions of coupling and cohesion . Low intermodule coupling, high intramodule cohesion, and low complexity have always been deemed to be important attributes of any modularized software. The above-mentioned early developments in software metrics naturally led several researchers to question their theoretical validity. Theoretical validation implies conformance to a set of agreed-upon principles and these principles are usually stated in the form of a theoretical framework.
Process of Proposed System:
Modern software engineering dictates that a large body of software be organized into a set of modules. A module captures a set of design decisions
which are hidden from other modules and the interaction among the modules should primarily be through module interfaces. In software engineering parlance, a module groups a set of functions or subprograms and data structures and often implements one or more business concepts. This grouping may take place on the basis of similarity of purpose or on the basis of commonality of goal
In the Proposed system we considered the leaf nodes of the directory hierarchy of the original source code to be the most fine-grained functional modules. All the files (and functions within) inside a leaf level directory were considered to belong to a single module. In this manner, all leaf level directories formed the module set for the software. After that we apply Coupling-based Structural Metrics as follows