An Empirical Study on SW Metrics for Embedded System
One of the most important reasons to measure software projects is to increase visibility of the development process. High visibility enables the development team to estimate their project more accurately and to establish a reasonable project plan. It also provides a rationale for improving the software development process. We propose standard metrics needed for our organization to develop embedded systems and present the results of related data collection and measurement. To define software metrics, the GQM (Goal Question Metric) approach was used. This empirical study should benefit people on the SEPG (Software Engineering Process Group) of each software development division who drive to improve their software development process.
Unable to display preview. Download preview PDF.
- 1.Bassman, M.J., McGarry, F., Pajerski, R.: Software Measurement Guidebook Revision 1. Software Engineering Laboratory Series, vol. SEL-94-102. NASA Goddard Space Flight Center, Greenbelt, MD (1995)Google Scholar
- 2.COCOMO II Model Definition Manual, Available at: http://sunset.usc.edu/research/COCOMOII
- 3.Grady, R.B., Caswell, D.L.: Software Metrics: establishing a company-wide program. Prentice-Hall, Englewood Cliffs (1987)Google Scholar
- 5.Victor, R.B., Caldiera, G., Rombach, H.D.: The Goal Question Metric Approach. In: Marciniak, J.J. (ed.) Encyclopedia of Software Engineering, vol. 1, pp. 528–532. John Wiley & Sons, Chichester (1994)Google Scholar
- 6.Humphrey, W.S.: A Discipline for Software Engineering. Addison Wesley, Reading (1995)Google Scholar
- 7.Florac, W.A., Park, R.E., Carleton, A.D.: Practical Software Measurement: Measuring for Process Management and Improvement, CMU/SEI-97- HB-003 (1997)Google Scholar