The Usage of Object Oriented Approach in Software Development Companies

Object orientation (00) has become a new buzzword for computer applications. Things are touted as being object oriented, with the implication that this is the "new" and "better" way to do things. As there are many approaches used to develop systems, therefore the software industry has to cope with the rapid technological evolution and the global market competition, in order to satisfy the growing user demands for quality, services and bandwidth. This project seeks a review of the status of the object-oriented approach among the software industry. Based on this, I will analyze the awareness of the object-oriented approach among software developers. In addition to this, the level of usage of the object-oriented approach in software development activities will also be examined. The results obtained will be statistically analyzed using SPSS (Statistical Package for Social Sciences), and discussed later in the light of the literature reviewe

Software Evolution Understanding: Automatic Extraction of Software Identifiers Map for Object-Oriented Software Systems

Software companies usually develop a set of product variants within the same family that share certain functions and differ in others. Variations across software variants occur to meet different customer requirements. Thus, software product variants evolve overtime to cope with new requirements. A software engineer who deals with this family may find it difficult to understand the evolution scenarios that have taken place over time. In addition, software identifier names are important resources to understand the evolution scenarios in this family. This paper introduces an automatic approach called Juana’s approach to detect the evolution scenario across two product variants at the source code level and identifies the common and unique software identifier names across software variants source code. Juana’s approach refers to common and unique identifier names as a software identifiers map and computes it by comparing software variants to each other. Juana considers all software identifier names such as package, class, attribute, and method. The novelty of this approach is that it exploits common and unique identifier names across the source code of software variants, to understand the evolution scenarios across software family in an efficient way. For validity, Juana was applied on ArgoUML and Mobile Media software variants. The results of this evaluation validate the relevance and the performance of the approach as all evolution scenarios were correctly detected via a software identifiers map

The dance of classes:a stochastic model for software structure evolution

In this study, we investigate software structure evolution and growth. We represent software structure by means of a generic macro-topology called Little House, which models the dependencies among classes of object-oriented software systems. We, then, define a stochastic model to predict the way software architectures evolve. The model estimates how the classes of object-oriented programs get connected one to another along the evolution of the systems. To define the model, we analyzed data from 81 versions of six Java based projects. We analyzed each pair of sequential versions, for each project, in order to depict a pattern of software structure evolution based on Little House. To evaluate the model, we performed two experiments: one with the data used to derive the model, and another with data of 35 releases, in total, of four open-source Java project. In both experiments, we found a very low rate of error for the application of the proposed model. The evaluation of the model suggests it is able to predict how a software structure will evolve

Software Metrics and Object-Oriented System Evolution

Object Oriented (OO) system design process can be quantitatively measured by metrics. Results from an empirical study of two OO systems that employed some of these metrics are discussed