A cost oriented profiler (COP) mechanism that analyzes the behavior of input application source code with regard to the software total cost of ownership (TCO). The cost analysis tool provided by the mechanism analyzes the behavior of the source code and generates a cost report with indications as to the portions of the source code that have the most impact on the TCO of the application. Based on simulations and by comparing multiple versions of the source code, the COP mechanism determines if a particular change to the source code will increase or decrease software TCO. Behavior analysis, including static and dynamic analysis of the source code, is used to generate one or more code recommendations to reduce the TCO.

System and method of cost oriented software profiling

We may not be able to make you love reading, but software measurement and estimation a practical approach will lead you to love reading starting from now. Book is the window to open the new world. The world that you want is in the better stage and level. World will always guide you to even the prestige stage of the life. You know, this is some of how reading will give you the kindness. In this case, more books you read more knowledge you know, but it can mean also the bore is full.

Software Measurement and Estimation: A Practical Approach

To obtain the functional size of software and reduce measurement variance caused by the interpretations of individual measurers, a number of measurement procedureshave been designed based on measurement methods approved as international standards. To date, most of these procedures have targeted Management Information Systems software, while only a few were designed for real-time and reactiveembedded software. In this paper, we propose a functional size measurement (FSM) procedure for real-time embedded software, based on the COSMIC method, version 3.0.1 (ISO 19761), and with requirements documented using the Simulinkmodel. The design of this FSM procedure is based on the mapping of key concepts in both Simulink and COSMIC, and the identification of the mapping rules for extracting the information stored in the Simulink files that is required formeasurement. This procedure therefore provides the foundation for automating the measurement of software requirements documented using Simulink. The backgroundstudy for this procedure was conducted at Renault SAS using ECU (Electronic Control Unit) functional requirements expressed with the Simulink tool.

Design of a Functional Size Measurement Procedure for Real-Time Embedded Software Requirements Expressed using the Simulink Model

Background: Source code size in terms of SLOC (source lines of code) is the input of many parametric software effort estimation models. However, it is unavailable at the early phase of software development. Objective: We investigate the accuracy of early SLOC estimation approaches for an object-oriented system using the information collected from its UML class diagram available at the early software development phase. Method: We use different modeling techniques to build the prediction models for investigating the accuracy of six types of metrics to estimate SLOC. The used techniques include linear models, non-linear models, rule/tree-based models, and instance-based models. The investigated metrics are class diagram metrics, predictive object points, object-oriented project size metric, fast&&serious class points, objective class points, and object-oriented function points. Results: Based on 100 open-source Java systems, we find that the prediction model built using object-oriented project size metric and ordinary least square regression with a logarithmic transformation achieves the highest accuracy (mean MMRE=0.19 and mean Pred(25)=0.74). Conclusion: We should use object-oriented project size metric and ordinary least square regression with a logarithmic transformation to build a simple, accurate, and comprehensible SLOC estimation model.

Source code size estimation approaches for object-oriented systems from UML class diagrams: A comparative study

This paper investigates the use of the COSMIC functional size measurement method for mobile applications. Some proposals have been recently introduced to size mobile applications in terms of COSMIC. In this work we empirically analyse whether the COSMIC functional size of mobile applications can be exploited to estimate the size of the final applications in terms of lines of code and number of bytes of the source code and byte code. To this end, we take into account a total of 7 different code size measures collected from 13 Android applications. The results of the empirical study show that the COSMIC functional size is strongly correlated to all the size measures taken into account and that it can be also used to predict the mobile application size in terms of bytes with a high accuracy.

/pdf/investigating-functional-and-code-size-measures-for-mobile-4z5mvxwe10.pdf

Investigating Functional and Code Size Measures for Mobile Applications

Various measures and methods have been developed to measure the sizes of different software entities produced throughout the software life cycle. Understanding the nature of the relationship between the sizes of these products has become significant due to various reasons. One major reason is the ability to predict the size of the later phase products by using the sizes of early life cycle products. For example, we need to predict the Source Lines of Code (SLOC) from Function Points (FP) since SLOC is being used as the main input for most of the estimation models when this measure is not available yet. SLOC/FP ratios have been used by the industry for such purposes even though the assumed linear relationship has not been validated yet. Similarly, FP has recently started to be used to predict the Bytes of code for estimating the amount of spare memory needed in systems. In this paper, we aim to investigate further the nature of the relationship between the software functional size and the code size by conducting a series of empirical studies.

/pdf/on-the-relationship-between-different-size-measures-in-the-12og1vzlkt.pdf

On the Relationship between Different Size Measures in the Software Life Cycle

To estimate software code size early in the development process is important for developing cost-efficient embedded systems. We have applied the COSMIC Functional Size Measurement (FSM) method for size estimation of embedded software components in the automotive industry. Correlational studies were conducted using data from two automotive companies. The studies show strong correlation between functional size and software code size, which is important for obtaining accurate estimation results. This paper presents the characteristics and results of our work, and aims to provide a practical framework for how to use COSMIC FSM for size estimation purposes. We investigate the results from our earlier correlational studies, and conduct further studies to identify such a framework. Based on these activities, we conclude that a clear purpose of the estimation process, a well-defined domain allowing categorization of software, consistent content and quality of requirements, and historical data from implemented software are key factors for size estimation of embedded software components.

A Practical Approach to Size Estimation of Embedded Software Components

For distributed networks which will be mass produced, such as computer systems in modern vehicles, it is crucial to find cost efficient hardware. A distributed network in a vehicle consists of several ECUs (Electronic Control Unit). In this paper we consider the amount of memory needed for these ECUs. They should contain enough memory to survive several software generations, without inducing unnecessary cost of too much memory. Our earlier work shows that UML Component Diagrams can be used to collect enough information for estimating memory size using a Functional Size Measurement method. This paper replicates our earlier experiment with more software components of a different type. We compare the results from the two experiments.

Estimation of Real-Time Software Code Size using COSMIC FSM

Accurate estimation of Software Code Size is important for developing cost-efficient embedded systems. The Code Size affects the amount of system resources needed, like ROM and RAM memory, and processing capacity. In our previous work, we have estimated the Code Size based on CFP (COSMIC Function Points) within 15% accuracy, with the purpose of deciding how much ROM memory to fit into products with high cost pressure. Our manual CFP measurement process would require 2,5 man years to estimate the ROM size required in a typical car. In this paper, we want to investigate how the manual effort involved in estimation of Code Size can be minimized. We define a UML Profile capturing all information needed for estimation of Code Size, and develop a tool for automated estimation of Code Size based on CFP. A case study will show how UML models save manual effort in a realistic case.

A model-based and automated approach to size estimation of embedded software components

Background: To estimate Software Code Size early in the development process is important both for Cost/Effort estimation and electronic hardware design reasons. The COSMIC FSM (Functional Size Measurement) method treats the intended software to be measured as a black box, and measures CFP (COSMIC Function Points) based only on data movement in and out of the software. Therefore, CFP can be measured on requirements defined early, and be used to estimate Code Size if there exists a strong correlation between CFP and Code Size. We have conducted four experiments in the automotive industry showing strong correlation between CFP and implemented Code Size in Bytes. All four experiments, of which two have not been published before, show equally strong correlation but the linear relationship is different between the experiments.Goal: This paper aims to identify the factors affecting the linear relationship. With these factors, we can categorize new requirements to be measured and select the proper linear relationship to convert CFP into Bytes, i.e. estimate Code Size.Method: We replicate our earlier experiments with software components of new types, and review the results from all our experiments. Potential factors affecting implemented Code Size are identified by performing open-ended interviews with domain experts.Results: We have in the automotive industry identified a set of factors that can be used to categorize the software components we want to measure; functionality type, quality constraints, and development methods and tools.Conclusions: COSMIC can produce accurate Code Size Estimates provided that sub-sets of cohesive and uniform requirements can be identified. Moreover, similar requirements must have been measured before to establish the linear relationship between CFP and Bytes. Finally, the sub-sets of requirements need to be able to categorize based on factors that affect the linear relationship. With this approach, even complex calculations can be measured, provided that they are proportional to the number of data movements.

Kenneth Lind

Papers

On the Relationship between Different Size Measures in the Software Life Cycle

A Practical Approach to Size Estimation of Embedded Software Components

Estimation of Real-Time Software Code Size using COSMIC FSM

A model-based and automated approach to size estimation of embedded software components

Categorization of real-time software components for code size estimation