Software Measurement @ Siemens – A Practical Approach Allows Best Practice Sharing of Various Organizations

  • Sebastian Schunk
Part of the Lecture Notes in Computer Science book series (LNCS, volume 5338)


The Siemens Measurement System for Software-based Systems (SMS) was set up in 2004 (see Keynote of F. Paulisch at the Metrikon 2006) and until now information of more than 440 projects has been collected. The active contribution of almost all software developing organizations within Siemens to the company-wide Measurement System provides a good data base to compare and analyze performance data such as “Budget Deviation” and the various success-critical influencing factors such as review practices, “Team Size” or “Unplanned Team Changes” between various organizations. This way, areas of interest can be objectively identified, where organizations could benefit from Best Practice Sharing.


Measurement System Benefits Success Factors Statistical Analyses Organization-wide Best Practice Sharing 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Boehm, B.: Software Cost Estimation with COCOMO II. Prentice Hall, Englewood Cliffs (2000)Google Scholar
  2. 2.
    Paulisch, F.: Establishing a Common Measurement System, In: Applied Software Measurement. In: Proceedings of the International Workshop on Software Metrics and DASMA Software Metrik Kongress, pp. 1–3 (2006)Google Scholar
  3. 3.
    El Emam, K., Card, D. (co-eds.): ISO/IEC Standard 15939: Software Measurement Process, International Organization for Standardization (2002)Google Scholar
  4. 4.
    Crissis, M., Konrad, M., Schrum, C.: Capability Maturity Model – Integration. Addison Wesley, Reading (2003)Google Scholar
  5. 5.
    Briand, L., Differding, C., Rombach, D.: Practical Guidelines for Measurement-Based Process Improvement (Goal Question Metric paradigm), Technical Report (ISERN-96-05) (1996)Google Scholar
  6. 6.
    Ebert, C., Dumke, R., Bundschuh, M., Schmietendorf, A.: Best Practices in Software Measurement. Springer, Heidelberg (2005)zbMATHGoogle Scholar
  7. 7.
    McGarry, J., Card, D., et al.: Practical Software Measurement. Addison Wesley, Reading (2002)Google Scholar
  8. 8.
    Goethert, B., Bailey, E.K., Busby, M.B.: Software Effort & Schedule Measurement. SEI, Carnegie Mellon University (1992)Google Scholar
  9. 9.
    Grady, R.B.: Practical Software Metrics for Project Management and Process Improvement. PTR Prentice-Hall, Englewood Cliffs (1992)Google Scholar
  10. 10.
    Herbsleb, J.D., Grinter, R.E.: Conceptual simplicity meets organizational complexity: case study of a corporate metrics program. In: Proceedings of the 20th international conference on Software engineering, Kyoto, Japan (1998)Google Scholar
  11. 11.
    Pfleeger, S.L., Jeffery, R., Curtis, B., Kitchenham, B.: Status report on software measurement. Software, IEEE 14(2) (March/April 1997)Google Scholar
  12. 12.
    Wiegers, K.E.: Software Metrics: Ten Traps to Avoid. Software Development magazine (October 1997) Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2008

Authors and Affiliations

  • Sebastian Schunk
    • 1
  1. 1.Siemens AG, Corporate Technology, CT SE SWIMunichGermany

Personalised recommendations