Categorization of real-time software components for code size estimation

Abstract

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.

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

“…On the other hand, Lind and Heldal [4][37] [38] found a significant correlation between software code size of components in Bytes and functional size in CFP. They developed a linear model to estimate the amount of memory required in Electronic Control Units (ECU) in cars from CFP before the software is available.…”

CompSize: A Model-Based and Automated Approach to Size Estimation of Embedded Software Components

“…The purpose is to assess whether the students have identified the majority of the data movements, and to make sure that the timing data is relevant. A scatter plot comparing the CFP values obtained in the case study and our previous CFP values from [25], is shown in Fig. 11.…”

“…2. Other factors necessary for categorization of components within GM and Saab are identified in [27]. Table 1 summarizes the complete mapping between the main COSMIC concepts and corresponding UML concepts.…”

“…The manual measurements and estimations obtained in our previous work [25] according to Fig. 8 are replicated according to the complete process described in Fig.…”

A Model-Based and Automated Approach to Size Estimation of Embedded Software Components

“…In our previous work, we have estimated the Code Size based on CFP (COSMIC Function Points) within 15% accuracy [23], [24], [25], [26], [27], [28]. Our results were obtained using software implementations developed by the automotive companies Saab and GM (General Motors).…”