Comparison Study and Review on Object-Oriented Metrics

The best elucidations to software development problems are regularly touted as object-oriented processes. The popularity of object-oriented design metrics is essential in software engineering for measuring the software complexity, estimating size, quality and project efforts. There are various approaches through which we can find the software cost estimation and predicates on various kinds of deliverable items. Object-oriented metrics assures to reduce cost and the maintenance effort by serving as early predictors to estimate software faults. Such an early quantification augments the quality of the final software. This paper reviews object-oriented metrics. A comparison table is maintained via which we can analyze the difference between all the object-oriented metrics effectively

A Review of Metrics for Object-Oriented Design

The ever-evolving body of empirical results do confirmation on the theoretical perspective the validity of OOD metrics whose validity is determined by them demonstrating that [1] they measure what they purport to measure. Quite often OOD metrics have been used as indicators of both the internal and external behaviors in the software development process. Software metrics especially for Object Oriented Systems literature often describe complex models with the focus to help predict various properties of software products and processes by measuring other properties. Usually designers are met with challenges to work with these measures especially when and how to use them. The very process of collecting these measurements leads to a better organization of the software process and a better understanding of what designers do as long as they confine to measurements that are meaningful. To this end therefore, the initiation of these metrics during the initial software development process is important. This paper elicits an understanding of the OOD metrics used in OOS development

A Review of Metrics for Object-Oriented Design

The ever-evolving body of empirical results do confirmation on the theoretical perspective the validity of OOD metrics whose validity is determined by them demonstrating that [1] they measure what they purport to measure. Quite often OOD metrics have been used as indicators of both the internal and external behaviors in the software development process. Software metrics especially for Object Oriented Systems literature often describe complex models with the focus to help predict various properties of software products and processes by measuring other properties. Usually designers are met with challenges to work with these measures especially when and how to use them. The very process of collecting these measurements leads to a better organization of the software process and a better understanding of what designers do as long as they confine to measurements that are meaningful. To this end therefore, the initiation of these metrics during the initial software development process is important. This paper elicits an understanding of the OOD metrics used in OOS development

Generalization Index: Defining a metric for the detection of smells in UML Class Diagrams in Eclipse Modeling Framework in Eclipse

In the field of Software Engineering, while designing the software design and maintaining the source code quality, a lot of good and bad practices come into being. With the continuous evolutions in the field of modeling in software development processes, Model Driven Software Development (MDSD), focuses towards the quality of software models. Unified Modeling Language (UML) is a graphical notation for expressing object-oriented designs. With its emergence as a modeling standard and being widely accepted by most software development organizations, in this research paper we focus on UML Class Diagrams. Metrics are mathematical models used for measuring. In software engineering, metrics are utilized for measuring quality aspects of software models. A manual model review is very time consuming and prone to errors, so it becomes essential to automate the tasks as effectively as possible. The Eclipse plug-in EMF Metrics supports specification and calculation of metrics wrt. specific EMF based models. A new definition technique for EMF quality assurance can be defined using Java, an OCL query or Henshin Pattern. In this paper we propose an algorithm for the calculation a new metric named Generalization Index Metric (GIX) for Java Code

A metrics paradigm for object-oriented analysis and design.

For several years, the software industry has been affected by a problem called the software crisis. Many software developers have worked hard to determine remedies for this crisis. The crisis deals with products being produced over costs, behind schedule, with low quality, and not meeting customer satisfaction. Processes are being used which waste resources and build low quality products. In dealing with the software crisis, software practitioners have used many tools, methodologies, and metrics to help produce better products, save resources, and increase productivity. Metrics are meaningful measures used to determine how well software is being produced, where weaknesses are in products, processes, or resources, and indicate where to make improvements. Today, the most popular methodology is the Object-Oriented (00) methodology. Users of this methodology want to prove that it helps resolve the software crisis. There is a belief that 00 systems are developed earlier, easier to understand and maintain, and contain reusable components. However, without metrics, the effectiveness of the 00 approach cannot be proven. Metrics must be used to show if the process or resources being used is responsible for the success or failure of software development, if management of the process is responsible, if the complexity or size of the product being produced is responsible, or if a lack of communication or misunderstandings of requirements is responsible. There are many, many reasons why metrics are used and can be seen in this Thesis. Many metrics are being used for traditional software development methodologies that deal with processes, products, and resources. However, there is no metric paradigm for the 00 development methodology. But, there is a small set of metrics proposed for 00 programming. We provide a 00 metric paradigm that contains metrics grouped into nine categories. We grouped the metrics into categories to make the selection of a particular· metric easier. These nine metrics fit nicely into the 00 methodology. The metrics can be used to measure processes, products, and resources. We provide a size estimation method that helps determine progress, costs, quality, effort, complexity, and schedule. The metrics can be used to prove the effectiveness of the 00 methodology and indicate areas for further improvement

Methods of labor economy increasing in educational organization

The urgency of problem under investigation due to fact that increasing demand of the information technology infrastructure development in current conditions of educational institutions functioning, including formation of the information-educational environment point of view. Offered organizational and economic model of constructing processes for software development is based on agile project management, regarded as an object-oriented tool for optimizing labor economics. The purpose of article is in model for labor economy processes optimization as a part of software development based on agile project management methodology in departments associated with development of information technologies in educational organization. The leading method to the problem study is in measurement of labor economics key indicators, including specific metrics of technical expert’s human capital growth. As an experimental base of research are considered educational organizations, at different times, using classical approach for software development and agile project management. The article presents research results of educational organizations departments engaged in project activities for development of information technologies, which are in the development of software products using classical approach for software development and agile project management. Article submissions may be useful to create a culture for constructing labor economics and human capital system based on sustainable growth in departments of educational institutions working in the field of information technology. © 2016 Dorozhkin et al

Modeling the object-oriented software process: OPEN and the unified process

A short introduction to software process modeling is presented, particularly object-oriented modeling. Two major industrial process models are discussed: the OPEN model and the Unified Process model. In more detail, the quality assurance in the Unified Process tool (formally called Objectory) is reviewed

Next generation software environments : principles, problems, and research directions

The past decade has seen a burgeoning of research and development in software environments. Conferences have been devoted to the topic of practical environments, journal papers produced, and commercial systems sold. Given all the activity, one might expect a great deal of consensus on issues, approaches, and techniques. This is not the case, however. Indeed, the term "environment" is still used in a variety of conflicting ways. Nevertheless substantial progress has been made and we are at least nearing consensus on many critical issues.The purpose of this paper is to characterize environments, describe several important principles that have emerged in the last decade or so, note current open problems, and describe some approaches to these problems, with particular emphasis on the activities of one large-scale research program, the Arcadia project. Consideration is also given to two related topics: empirical evaluation and technology transition. That is, how can environments and their constituents be evaluated, and how can new developments be moved effectively into the production sector

Software Process Assessment (SPA)

NASA's environment mirrors the changes taking place in the nation at large, i.e. workers are being asked to do more work with fewer resources. For software developers at NASA's Goddard Space Flight Center (GSFC), the effects of this change are that we must continue to produce quality code that is maintainable and reusable, but we must learn to produce it more efficiently and less expensively. To accomplish this goal, the Data Systems Technology Division (DSTD) at GSFC is trying a variety of both proven and state-of-the-art techniques for software development (e.g., object-oriented design, prototyping, designing for reuse, etc.). In order to evaluate the effectiveness of these techniques, the Software Process Assessment (SPA) program was initiated. SPA was begun under the assumption that the effects of different software development processes, techniques, and tools, on the resulting product must be evaluated in an objective manner in order to assess any benefits that may have accrued. SPA involves the collection and analysis of software product and process data. These data include metrics such as effort, code changes, size, complexity, and code readability. This paper describes the SPA data collection and analysis methodology and presents examples of benefits realized thus far by DSTD's software developers and managers