Advertisement

Fundamentals

  • Miroslaw Staron
  • Wilhelm Meding
Chapter

Abstract

Measurement as a process is nothing new, nor specific to software engineers. As humans, we are used to measuring from other engineering disciplines. However, in software engineering, the science behind measurement—metrology—is relatively little-known, which results in low quality of measurement programs. In this chapter we describe the essence of metrology as a science, and we introduce the concepts from the most relevant standards in the area of measurement in general, and in software engineering in particular. We also show how the scientific view on metrology complements the industrial view on the same aspects.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. [Abr10]
    Alain Abran. Software metrics and software metrology. John Wiley & Sons, 2010.Google Scholar
  2. [BCH+95]
    Barry Boehm, Bradford Clark, Ellis Horowitz, Chris Westland, Ray Madachy, and Richard Selby. Cost models for future software life cycle processes: Cocomo 2.0. Annals of software engineering, 1(1):57–94, 1995.CrossRefGoogle Scholar
  3. [BEEM96]
    Lionel Briand, Khaled El Emam, and Sandro Morasca. On the application of measurement theory in software engineering. Empirical Software Engineering, 1(1):61–88, 1996.CrossRefGoogle Scholar
  4. [BMB96a]
    L.C. Briand, S. Morasca, and V.R. Basili. Property-based Software Engineering Measurement. IEEE Transactions on Software Engineering, 22(1):68–86, 1996.CrossRefGoogle Scholar
  5. [BMB96b]
    Lionel C Briand, Sandro Morasca, and Victor R Basili. Property-based software engineering measurement. Software Engineering, IEEE Transactions on, 22(1):68–86, 1996.Google Scholar
  6. [Boe99]
    Barry Boehm. Managing software productivity and reuse. Computer, 32(9):111–113, 1999.CrossRefGoogle Scholar
  7. [CMM02]
    CMMI Product Team. Capability Maturity Model Integration (CMMI), Version 1.1–Continuous Representation. 2002.Google Scholar
  8. [FP98]
    Norman E Fenton and Shari Lawrence Pfleeger. Software metrics: A rigorous and practical approach. PWS Publishing Co., 1998.Google Scholar
  9. [Int99]
    International Standards Organization. ISO/IEC 14598:1999–2001. Information Technology-Software Product Evaluation – Parts 1, 6, 1999.Google Scholar
  10. [Int08]
    International Standardization Organization/International Electrotechnical Commission and others. ISO/IEC 12207: 2008, systems and software engineering–Software life cycle processes. Geneva, Switzerland: ISO/IEC, 2008.Google Scholar
  11. [ISO16a]
    ISO/IEC. ISO/IEC 25000 - Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE). Technical report, 2016.Google Scholar
  12. [ISO16b]
    ISO/IEC. ISO/IEC 25023 - Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - Measurement of system and software product quality. Technical report, 2016.Google Scholar
  13. [OC01]
    International Standard Organization and International Electrotechnical Commission. ISO/IEC 9126, Software engineering, Product quality Part: 1 Quality model. Technical report, International Standard Organization/International Electrotechnical Commission, 2001.Google Scholar
  14. [OC07]
    International Standard Organization and International Electrotechnical Commission. Software and systems engineering, software measurement process. Technical report, ISO/IEC, 2007.Google Scholar
  15. [oWM93]
    International Bureau of Weights and Measures. International vocabulary of basic and general terms in metrology. International Organization for Standardization, Geneva, Switzerland, 2nd edition, 1993.Google Scholar
  16. [oWM05]
    International Bureau of Weights and Measures. General requirements for the competence of testing and calibration laboratories. International Organization for Standardization, Geneva, Switzerland, 1st edition, 2005.Google Scholar
  17. [RS05]
    Hugh Robinson and Helen Sharp. Organisational culture and XP: three case studies. 2005.Google Scholar
  18. [RSB+13]
    Rakesh Rana, Miroslaw Staron, Claire Berger, Jorgen Hansson, Martin Nilsson, and Fredrik Torner. Evaluating long-term predictive power of standard reliability growth models on automotive systems. In Software Reliability Engineering (ISSRE), 2013 IEEE 24th International Symposium on, pages 228–237. IEEE, 2013.Google Scholar
  19. [SDR17]
    Miroslaw Staron, Darko Durisic, and Rakesh Rana. Improving measurement certainty by using calibration to find systematic measurement error – a case of lines-of-code measure. In Software Engineering: Challenges and Solutions, pages 119–132. Springer, 2017.Google Scholar
  20. [SHF+13]
    Miroslaw Staron, Jorgen Hansson, Robert Feldt, Anders Henriksson, Wilhelm Meding, Sven Nilsson, and Christoffer Hoglund. Measuring and visualizing code stability – A case study at three companies. In Software Measurement and the 2013 Eighth International Conference on Software Process and Product Measurement (IWSM-MENSURA), 2013 Joint Conference of the 23rd International Workshop on, pages 191–200. IEEE, 2013.Google Scholar
  21. [SM09]
    Miroslaw Staron and Wilhelm Meding. Using models to develop measurement systems: A method and its industrial use. 5891:212–226, 2009.Google Scholar
  22. [SM11]
    Miroslaw Staron and Wilhelm Meding. Factors determining long-term success of a measurement program: An industrial case study. e-Informatica Software Engineering Journal, pages 7–23, 2011.Google Scholar
  23. [SMH+13]
    Miroslaw Staron, Wilhelm Meding, Jörgen Hansson, Christoffer Höglund, Kent Niesel, and Vilhelm Bergmann. Dashboards for continuous monitoring of quality for software product under development. System Qualities and Software Architecture (SQSA), 2013.Google Scholar
  24. [SMH+14]
    Miroslaw Staron, Wilhelm Meding, Jörgen Hansson, Christoffer Höglund, Kent Niesel, and Vilhelm Bergmann. Dashboards for continuous monitoring of quality for software product under development. System Qualities and Software Architecture (SQSA), 2014.Google Scholar
  25. [SMN08]
    Miroslaw Staron, Wilhelm Meding, and Christer Nilsson. A framework for developing measurement systems and its industrial evaluation. Information and Software Technology, 51(4):721–737, 2008.CrossRefGoogle Scholar
  26. [SMP12]
    Miroslaw Staron, Wilhelm Meding, and Klas Palm. Release readiness indicator for mature agile and lean software development projects. In Agile Processes in Software Engineering and Extreme Programming, pages 93–107. Springer, 2012.Google Scholar
  27. [Sta12]
    Miroslaw Staron. Critical role of measures in decision processes: Managerial and technical measures in the context of large software development organizations. Information and Software Technology, 54(8):887–899, 2012.CrossRefGoogle Scholar
  28. [TC06]
    James J Thomas and Kristin A Cook. A visual analytics agenda. Computer Graphics and Applications, IEEE, 26(1):10–13, 2006.Google Scholar
  29. [TZ92]
    Jianhui Tian and Marvin V Zelkowitz. A formal program complexity model and its application. Journal of Systems and Software, 17(3):253–266, 1992.CrossRefGoogle Scholar
  30. [Wey88]
    Elaine J. Weyuker. Evaluating software complexity measures. Software Engineering, IEEE Transactions on, 14(9):1357–1365, 1988.MathSciNetCrossRefGoogle Scholar
  31. [Zus98]
    Horst Zuse. A framework of software measurement. Walter de Gruyter, 1998.Google Scholar

Copyright information

© Springer International Publishing AG, part of Springer Nature 2018

Authors and Affiliations

  • Miroslaw Staron
    • 1
  • Wilhelm Meding
    • 2
  1. 1.Department of Computer Science and EngineeringUniversity of GothenburgGothenburgSweden
  2. 2.Ericsson ABGothenburgSweden

Personalised recommendations