Cocomo II as productivity measurement: a case study at KBC.

Software productivity is generally measured as the ratio of size over effort, whereby several techniques exist to measure the size. In this paper, we propose the innovative approach to use an estimation model as productivity measurement. This approach is applied in a case-study at the ICT-department of a bank and insurance company. The estimation model, in this case Cocomo II, is used as the norm to judge about productivity of application development projects. This research report describes on the one hand the set-up process of the measurement environment and on the other hand the measurement results. To gain insight in the measurement data, we developed a report which makes it possible to identify productivity improvement areas in the development process of the case-study company.

Calibration and Validation of the COCOMO II.1997.0 Cost/Schedule Estimating Model to the Space and Missile Systems Center Database

The goal of this study was to determine the accuracy of COCOMO II.1997.0, a software cost and schedule estimating model, using Magnitude of Relative Error, Mean Magnitude of Relative Error, Relative Root Mean Square, and a 25 percent Prediction Level. Effort estimates were completed using the model in default and in calibrated mode. Calibration was accomplished by dividing four stratified data sets into two random validation and calibration data sets using five times resampling. The accuracy results were poor; the best having an accuracy of only .3332 within 40 percent of the time in calibrated mode. It was found that homogeneous data is the key to producing the best results, and the model typically underestimates. The second part of this thesis was to try and improve upon the default mode estimates. This was accomplished by regressing the model estimates to the actual effort. Each original regression equation was transformed and tested for normality, equal variance, and significance. Overall, the results were promising; regression improved the accuracy in three of the four cases, the best having an accuracy of .2059 within 75 percent of the time

Evaluation of Personnel Parameters in Software Cost Estimating Models

Software capabilities have steadily increased over the last half century. The Department of Defense has seized this increased capability and used it to advance the warfighter\u27s weapon systems However, this dependence on software capabilities has come with enormous cost. The risks of software development must be understood to develop an accurate cost estimate

System Qualities Ontology, Tradespace and Affordability (SQOTA) Project Phase 5

Motivation and Context: One of the key elements of the SERC's research strategy is transforming the practice of systems engineering and associated management practices- "SE and Management Transformation (SEMT)." The Grand Challenge goal for SEMT is to transform the DoD community 's current systems engineering and management methods, processes, and tools (MPTs) and practices away from sequential, single stovepipe system, hardware-first ,document-driven, point- solution, acquisition-oriented approaches; and toward concurrent, portfolio and enterprise-oriented, hardware-software-human engineered, model-driven, set-based, full life cycle approaches.This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08-D-0171 and HQ0034-13-D-0004 (TO 0060).This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08-D-0171 and HQ0034-13-D-0004 (TO 0060)

Cost-benefit analysis for software process improvement

Justification of investments to improve software development processes and technol- ogy continues to be a significant challenge for software management. Managers interested in improving quality, cost, and cycle-time of their products have a large set of methods, tools, and techniques from which to choose. The implementation of one or more of these potential improvements can require considerable time and cost. Decision makers must be able to understand the benefits from each proposed improvement and decide which improvements to implement. While a variety of approaches exist for evaluating the costs and benefits of a few specific improvements such as inspections or systematic reuse, there is no general model for evaluating software process improvements. The result of this research is a practical, useful framework to assist practitioners in evaluating potential process improvements. This general framework can accommodate a variety of methods for estimating the cost-benefit effects of a process change. To illustrate this framework a set of cost-benefit templates for Emerald and Cleanroom technologies were developed and validated. Methods for evaluating effects range from constants and simple equations to bayesian decision models and dynamic process simulations. A prototype tool was developed to assist in performing cost-benefit analysis of software process improvements

Tradespace and Affordability – Phase 1

One of the key elements of the SERC’s research strategy is transforming the practice of systems engineering – “SE Transformation.” The Grand Challenge goal for SE Transformation is to transform the DoD community’s current systems engineering and management methods, processes, and tools (MPTs) and practices away from sequential, single stovepipe system, hardware-first, outside-in, document-driven, point-solution, acquisition-oriented approaches; and toward concurrent, portfolio and enterprise-oriented, hardware-software-human engineered, balanced outside-in and inside-out, model-driven, set-based, full life cycle approaches.This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08- D-0171 (Task Order 0031, RT 046).This material is based upon work supported, in whole or in part, by the U.S. Department of Defense through the Office of the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) under Contract H98230-08- D-0171 (Task Order 0031, RT 046)

Penerapan Penghitungan Workflow Complexity Effort Multiplier pada Metode Constructive Cost Model II (COCOMO II)

Constructive Cost Model II (COCOMO II) adalah salah satu metode untuk mengukur effort estimation pada pengembangan software yang sudah diaplikasikan secara luas. Model estimasi COCOMO telah diaplikasikan dalam banyak proyek pengembangan software. Dalam pengaplikasiannya, Constructive Cost Model II (COCOMO) II memiliki banyak komponen effort multiplier untuk dapat mengukur pembobotan setiap komponennya. Terdapat 17 jenis komponen effort multiplier pada Constructive Cost Model II (COCOMO) II yang dimana pada setiap komponen memiliki memiliki pembobotan effort multiplier yang berbeda pada setiap tingkatan ratings level. Namun sampai saat ini belum ada komponen pada effort multiplier di Constructive Cost Model II (COCOMO) II yang melakukan pembobotan berdasarkan kompleksitas workflow dalam sebuah pengembangan software Berdasarkan belum adanya metode yang diaplikasikan untuk melakukan analisa kompleksitas sebuah perangkat lunak, maka untuk mencapai tujuan dilakukannya sebuah penelitian dengan menggunakan metode workflow complexity yang ditambahkan ke dalam komponen effort multiplier di Constructive Cost Model (COCOMO) II yang melibatkan pembobotan terhadap tingkat kompleksitas workflow untuk menghasilkan cost model dengan hasil deviasi yang lebih akurat. ============== Constructive Cost Model II (COCOMO II) is one method to measure effort estimation on widely applied software development. The COCOMO estimation model has been applied in many software development projects. In its application, Constructive Cost Model II (COCOMO II) has many components of multiplier effort to be able to measure the weighting of each component. There are 17 types of effort multiplier component in Constructive Cost Model II (COCOMO) II which in each component has different weight multiplier at each level of rating level. However, until now there has been no component on the effort multiplier in Constructive Cost Model II (COCOMO II) which performs weighting based on workflow complexity in a software development Based on the absence of a method applied to analyze the complexity of a software, to achieve the objective of a study using workflow complexity method added to the component multiplier in the Constructive Cost Model (COCOMO II) which involves weighting the level of workflow complexity to produce cost model with more accurate deviation result

Estimating the effort in the early stages of software development.

Estimates of the costs involved in the development of a software product and the likely risk are two of the main components associated with the evaluation of software projects and their approval for development. They are essential before the development starts, since the investment early in software development determines the overall cost of the system. When making these estimates, however, the unknown obscures the known and high uncertainty is embedded in the process. This is the essence of the estimator's dilemma and the concerns of this thesis. This thesis offers an Effort Estimation Model (EEM), a support system to assist the process of project evaluation early in the development, when the project is about to start. The estimates are based on preliminary data and on the judgement of the estimators. They are developed for the early stages of software building in which the requirements are defined and the gross design of the software product is specified. From these estimates only coarse estimates of the total development effort are feasible. These coarse estimates are updated when uncertainty is reduced. The basic element common to all frameworks for software building is the activity. Thus the EEM uses a knowledge-base which includes decomposition of the software development process into the activity level. Components which contribute to the effort associated with the activities implemented early in the development process are identified. They are the size metrics used by the EEM. The data incorporated in the knowledge-base for each activity, and the rules for the assessment of the complexity and risk perceived in the development, allow the estimation process to take place. They form the infrastructure for a 'process model' for effort estimating. The process of estimating the effort and of developing the software are linked. Assumptions taken throughout the process are recorded and assist in understanding deviations between estimates and actual effort and enable the incorporation of a feedback mechanism into the process of software development. These estimates support the decision process associated with the overall management of software development, they facilitate management involvement and are thus considered as critical success factors for the management of software projects

Software development and correction estimation in the automotive domain

Während der letzten Jahrzehnte hat sich Software in alle Lebensbereiche ausgebreitet. Die kontinuierlich steigenden Kundenanforderungen ließen auch die Komplexität steigen, bei gleichbleibender Produktqualität. Analysedaten und diverse Beispiele entstammen der Automobildomäne, die einen sicherheitskritischen Bereich darstellt, in dem Produkte mit speziellen Qualitätsanforderungen entwickelt werden. Qualitätsanforderungen müssen von diversen Prozessen und Standards bedient werden, bei gleichzeitiger Einhaltung enger Endtermine. Die Komplexität der Software und der Safety-Aspekt beeinflussen die Fehlerquote der Produkte stark. Viele Anforderungen werden während der Entwicklung hinzugefügt oder verändert und führen zu permanenten Änderungen in der Software und einer weiteren Steigerung der Komplexität. Änderungen müssen analysiert und getestet werden, um die Qualität des entstehenden Produktes zu gewährleisten. Die Vorhersage von Defekten und Änderungen in der Software sind ein wichtiger Anteil des Software Engineering. Die industrielle Software-Entwicklung muss ihr Ziel innerhalb diverser Grenzen erreichen, ganz wichtig ist das Budget, wobei sich Änderungen an Projektparametern negativ auf das geplante Budget auswirken können. Solche Änderungen werden in zwei Klassen eingeteilt, durch Kunden verursachte neue oder veränderte Anforderungen, und die Korrekturen, die durch Systemverbesserungen oder Fehlerbehebungen entstehen, beide Klassen für das Projekt-Budget relevant. Die Aufwände für die neuen Kundenanforderungen können dem Budget einfach aufgeschlagen werden. Die Korrekturen verursachen ebenfalls große Aufwände, die zu einem negativen Budget führen können, was eine große Herausforderung für das Projektmanagement wie auch die automatisierte Schätzung der Aufwände über die gesamte Projektlaufzeit darstellt.Over the past decades, software has spread to most areas of our lives. The complexity increased due to steadily increasing customer demands and, at the same time, the high quality of the products had to be kept. The data for the analyses and many of the examples are taken out of the automotive software development domain. The automotive domain is a safety-critical area where products are developed with specific quality requirements. These quality requirements have to be met by many processes and by satisfying several standards within stipulated deadlines during the development lifecycle. The complexity of the software and the safety aspect have a strong influence on the product defect ratio. Many requirements will be added and adjusted during the development lifecycle leading to continuous changes in the software and increased complexity. All these changes need to be analyzed and tested to ensure the quality of the product. Predicting software defects and changes is a significant part of software engineering. Industrial software development has to achieve its target within several boundaries. One of the important boundaries for an industrial project is the budget, where changes of any project parameters can easily lead to negative effects in the planned budget. Such changes are classified into two types, the changes pushed by the customer as new requirements or changed requirements, and the correction changes in the project because of improvements of the system and identified bugs with their fixes. This classification is important to control the project budget. The effort for the realization of new customer changes can be estimated and added to the budget. The correction changes also cause huge efforts, which can lead to a negative budget in the project which is a big challenge for the project management, the automated calculation of effort estimations for the complete development life-cycle. This thesis offers a new model to improve the effort estimation from multiple perspectives. This model also integrates follow-up-defects in later process phases. Thus, the defect cost flow is part of the model and enables the management defects and follow-up defects which could spread throughout the development phases. The newly developed model was successfully evaluated in the automotive domain. The overall accuracy of the effort estimations was improved by 80%

Proceedings of the 19th Annual Software Engineering Workshop

The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of applications software. The goals of the SEL are: (1) to understand the software development process in the GSFC environment; (2) to measure the effects of various methodologies, tools, and models on this process; and (3) to identify and then to apply successful development practices. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that include this document