From Algorithms to Software - A Practical Approach to Model-Driven Design

Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement

2010

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.

“…The UML Component Diagram is modeled in the Rhapsody tool [16], as part of the system architecture development activities within GM. This is described further in [7].…”

Section: Software Components and Requirement Specificationsmentioning

confidence: 92%

Section: Factors Affecting the Linear Relationshipmentioning

confidence: 98%

See 1 more Smart Citation

Categorization of real-time software components for code size estimation

Lind¹,

Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement

2010

“…The UML Component Diagram is modeled in the Rhapsody tool [11], as part of the system architecture development activities within Saab and GM. This is described further in [5].…”

Section: Definition and Planningmentioning

confidence: 99%

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

Lind¹,

IEICE Trans. Inf. & Syst.

2012

SUMMARYAccurate 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.

“…The UML Component Diagram is modeled in the Rhapsody tool [11], as part of the system architecture development activities within Saab and GM. This is described further in [4].…”

Section: Definition and Planningmentioning

confidence: 99%

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

Lind¹,

Model Driven Engineering Languages and Systems

2011

Abstract. 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.