Class hierarchy based metric for object-oriented design

There is no software metrics based on object-oriented programming languages (OOPLs) developed to help object-oriented software development. A graph-theoretical complexity metric to measure object-oriented software complexity is described. It shows that inheritance has a close relation with the object-oriented software complexity, and reveals that misuse of repeated (multiple) inheritance will increase software complexity and be prone to implicit software errors. An algorithm to support this software metric is presented. Its time complexity is O(n/sup 3/). >

Using Z to specify object-oriented software complexity measures

Software metrics is a necessary step for software reliability and quality, and software metrics of traditional procedure-oriented programming are fairly mature and have various methodologies and tools available for use. Object-oriented programming has recently became popular. However, traditional procedure-oriented software metrics are not appropriate for the development of object-oriented software. Some research into object-oriented software metrics has been proposed, but these articles focus on only one metric that measures a specific characteristic of the object-oriented software. The authors propose a new metric methodology, the data scope complexity, for object-oriented software based on the data scope of a program. The data scope complexity can show complexities of multiple features of object-oriented programming at the same time. They also quantify and compare object-oriented programming with procedure-oriented programming.

Object-oriented software metrics are important in software engineering field for measurement of the software quality, size estimation, complexity and effort. Object oriented software development is the most popular and best practice in software development. Object oriented software metrics can be used for measuring extend of object orientedness of a program. These quantities are important information indicators, that can be helpful for a software developer in take decisions for designing good software. It is proven that the software metrics provide quantitative information about the structure of the code, which can be used to determine the reliability of software. The design of the software is highly recommended to be object oriented in the software development environment. Software metrics specific to programs that have object oriented design can be used to measure the quality of the software like inheritance, assessing the effects of coupling, the complexity of the code, size aspects, etc, of the software developed in such an environment. Software measurement is a way for assessing the quality of software. Many attributes can define quality of a software, internal (size, complexity) as well as external (reliability)[14]. Often internal attributes are contributing factors to external attributes. Reliability as a term means the degree to which a component, product or system executes specified functions for a specific period of time under specified conditions. Software reliability is the software being trustworthy of the specifications. The aim of the work is to model the relationship between reliability of object oriented software to the object oriented design metrics and predict reliability of software.

The role of design pattern in the form of software metric and internal code architecture for object-oriented design plays a critical role in software en-gineering in terms of production cost efficiency. This paper discusses about code reusability that is a frequently exercised cost saving methodology in IT produc-tion. After reviewing existing literatures towards study on software metrics, we found that very few studies are witnessed to incline towards code reusability. Hence, we developed a simple analytical model that establishes relationship between the design components of standard software metric and code reusability using case studies of three software projects (Customer Relationship Management project, Supply Chain Management project, and Enterprise Relationship Management project). We also testify our proposal using stochastic based Markov model to find that proposed system can extract significant information of maximized values of code reusability with increasing level of uncertainties of software project methodologies.

The role of the design pattern in the form of software metric and internal code architecture for object-oriented design plays a critical role in software engineering regarding production cost efficiency. This paper discusses code reusability that is a frequently exercised cost saving methodology in IT production. After reviewing existing literature towards a study on software metrics, we found that very few studies are witnessed to incline towards code reusability. Hence, we developed a simple analytical model that establishes a relationship between the design components of standard software metric and code reusability using case studies of three software projects (Customer Relationship Management project, Supply Chain Management project, and Enterprise Relationship Management project). We also testify our proposal using stochastic based Markov model to find that proposed system can extract significant information of maximized values of code reusability with increasing level of uncertainties of software project methodologies.

Software metrics serve as a significant issue to improve software quality. It is an important research of software engineering. In line with the methodologies of object-oriented analysis and design widely developed, many software metrics techniques have been proposed. However, not many focus on the metrics evaluation of an inheritance hierarchy. In this paper, we propose a novel concept named unit repeated inheritance (URI) in Z notation to realize object-oriented software metrics. The approach describes an inheritance level technique (ILT) method as a guide to measure the software complexity of an inheritance hierarchy. The measures of inheritance metrics are formed based on the proposed mechanism. Also, we use Lex and Yacc to construct a windowing tool which is used in conjunction with a conventional C++ programming environment to assist a programmer to analyze and measure his/her C++ programs.

Object-oriented finite element analysis and programming in VC++

Object-oriented structural and geometric analysis methods for truss structures are proposed. The methods are based on the iterative relaxation of nodal unbalanced forces by moving the nodes. The entities appeared in truss analysis are modeled as classes, and their class hierarchy is established. The knowledge about a truss node, a truss member, a material, and a sectional shape of the member are extracted and constructed as a knowledge base in an object-oriented manner. The object-oriented structural analysis is found to be valid for material and geometric nonlinearities, and the object-oriented geometric analysis where a kinematic problem is converted into a problem for a force equilibrium at the nodes is also found to be effective for determining the geometry of variable geometry trusses. The whole system is written in an object-oriented language, Smalltalk, and several results on structural and geometric analysis are presented. The speed of the computation is discussed along with the size of the structures and the over-relaxation factor. The extension of the knowledge base is also discussed.

13 - Software Design

Nowadays, software is expected to have an extended lifespan, which makes the evaluation of its complexity at the early stages critical in upcoming maintenance. Indeed, complexity is proportional to the evolution of software. Software metrics were introduced as tools that allow us to obtain an objective measurement of the complexity of software. Hence, enabling software engineering to assess and manage software complexity. Reducing software costs is one of the major concerns of software engineering which creates an increasing need for new methodologies and techniques to control those costs. Software complexity metrics can help us to do so. In this paper, we would investigate how those metrics can be used to reduce software costs. We would first analyze the most popular complexity metrics and distinguish their properties. Then, we will show how each of those metrics fit within the software life cycle. Finally, we will provide a detailed approach to use the complexity metrics to reduce software costs.

Software reuse, share and easy maintenance have long been an important issue in the image processing community. They are crucial to rapid system prototyping, technology transfer, share of software investment and easy system integration with other image processing software. Object-oriented design (OOD) offers excellent facilities for achieving these objectives through inheritance, dynamic binding and encapsulation. The authors present experiences in applying object-oriented design to two image processing examples. They demonstrate that the use of object-oriented software design can achieve efficiency in software reuse, maintenance and software integration.

Code smells are generally not considered as bugs; instead, they point out certain shortcomings in the software design or code. Identification of code smell is a necessary step for improving the software quality and reducing the maintenance effort. In this study, we introduce a bad smell prediction technique based on object-oriented software metrics that use Decision Tree (DT) and Random Forest (RF) machine learning algorithm. An open-source project, namely JHOTDRAW, was used as our dataset, for which values of object-oriented software metrics were calculated. Two feature selection methods-Random Forest Importance (RFI) and Information Gain (IG) were applied to extract the most relevant attributes for the prediction of code smells, namely, Feature envy, Dispersed coupling, refused parent bequest, and God class. The random-search algorithm was used to tune the parameters of Random Forest and Decision Tree. Results show that the best classification accuracy for Decision Tree was obtained at 99.13% for refused parent bequest code smells. Results also show that after using the Random Forest classifier, refused parent bequest smell was predicted with the best accuracy of 99.14%. Finally, in this research study, a set of code smell prediction rules were extracted using Decision Tree.

Object-oriented design and programming are big topics—entire books are devoted solely to the process of object-oriented design or to using object-oriented programming in various languages and on various programming platforms. My focus in this book isn’t to teach the basics of object-oriented design or programming but rather to show how you may apply them to the creation of distributed. NET applications.KeywordsApplication ServerBusiness LogicBusiness ObjectMobile ObjectLogical LayerThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Software reuse significantly reduce the costs of software production in the field of open-source software (OSS) development and lead to produce more reliable software systems. Software metrics have been proposed as indicators of software quality factors such as reusability. However, few empirical research papers have validated the relationship between components reusability and software metrics. This research aims to validate Chidamber and Kemerer (CK) metrics as predictors of software reusability. In order to achieve this goal, an empirical study is conducted to validate metrics in classifying two groups of components: library (reuse-prone) and non-library (less reuseprone). A nearest neighbor’s technique is used to classify library and application components using object-oriented software metrics. The approach is applied to a number of library and application systems available online. The conducted nearest neighbors models have produced acceptable classification. The results provide evidence of using metrics as surrogates of software reusability when models are evaluated using Fmeasure. CK metrics can be used to measure component reuse-proneness and can be used to differentiate between library and application components. A nearest neighbor’s technique can be used to identify the reuse-prone components in open-source application.