Software Quality Journal

, Volume 21, Issue 1, pp 3–22 | Cite as

Automated measurement of models of requirements

  • M. Monperrus
  • B. Baudry
  • J. Champeau
  • B. Hoeltzener
  • J. M. Jézéquel


On way to formalize system requirements is to express them using the object-oriented paradigm. In this case, the class model representing the structure of requirements is called a requirements metamodel, and requirements themselves are object-based models of natural language requirements. In this paper, we show that such object-oriented requirements are well suited to support a large class of requirements metrics. We define a requirements metamodel and use an automated measurement approach proposed in our previous work to specify requirements metrics. We show that it is possible to integrate 78 metrics from 11 different papers in the proposed framework. The software that computes the requirements metric values is fully generated from the specification of metrics.

Supplementary material

11219_2011_9163_MOESM1_ESM.pdf (24 kb)
Supplementary material 1 (PDF 24 kb)


  1. Basili, V. R., Caldiera, G., & Rombach, H. D. (1994). The goal question metric approach. In Encyclopedia of Software Engineering. Wiley.Google Scholar
  2. Baumert, J., & McWhinney, M. (1992). Software measures and the capability maturity model. Tech. rep., Software Engineering Institute, Carnegie Mellon University.Google Scholar
  3. Berenbach, B., & Borotto, G. (2006). Metrics for model driven requirements development. In Proceeding of the 28th international conference on software engineering (ICSE ’06) (pp. 445–451). ACM Press.Google Scholar
  4. Brottier, E., Baudry, B., Traon, Y. L., Touzet, D., & Nicolas, B. (2007). Producing a global requirement model from multiple requirement specifications. In Proceedings of the IEEE enterprise computing conference (EDOC’2007) (pp. 390–404).Google Scholar
  5. Brottier, E., Le Traon, Y., & Nicolas, B. (2010). Composing models at two modeling levels to capture heterogeneous concerns in requirements. In B. Baudry & E. Wohlstadter (Eds.), Software composition (Vol. 6144 of Lecture Notes in Computer Science, pp. 1–16). Berlin/Heidelberg: Springer.Google Scholar
  6. Budinsky, F., Steinberg, D., Merks, E., Ellersick, R., & Grose, T. J. (2004). Eclipse modeling framework. Boston: Addison-Wesley.Google Scholar
  7. Chen, X. (2010). Google Scholar’s dramatic coverage improvement five years after debut. Serials Review.Google Scholar
  8. Costello, R. J., & Liu, D. -B. (1995) Metrics for requirements engineering. Journal of Systems and Software, 29, 39–63.CrossRefGoogle Scholar
  9. Davis, A., Overmyer, S., Jordan, K., Caruso, J., Dandashi, F., Dinh, A., et al. (1993). Identifying and measuring quality in a software requirements specification. In Proceedings of the first international software metrics symposium. IEEE.Google Scholar
  10. Dhaussy, P., Pillain, P. -Y., Creff, S., Raji, A., Le Traon, Y., & Baudry, B. (2009) Evaluating context descriptions and property definition patterns for software formal validation. In A. Schürr & B. Selic (Eds.), Model driven engineering languages and systems (Vol. 5795 of Lecture Notes in Computer Science, pp. 438–452). Berlin/Heidelberg: Springer.Google Scholar
  11. Douglass, B. P. (2004) Computing model complexity. Borland: White paper, I-Logix.Google Scholar
  12. Dromey, R. (1996) Cornering the chimera. IEEE Software, 13(1), 33–43.CrossRefGoogle Scholar
  13. Gervasi, V., & Nuseibeh, B. (2002). Lightweight validation of natural language requirements. Software: Practice and Experience, 32(2), 113–133.MATHCrossRefGoogle Scholar
  14. Goknil, A. Kurtev, I., & van den Berg, K. (2008). A metamodeling approach for reasoning about requirements. In I. Schieferdecker & A. Hartman (Eds.), Model driven architecture-foundations and applications (Vol. 5095 of Lecture Notes in Computer Science, pp. 310–325). Berlin/Heidelberg: Springer.Google Scholar
  15. Hammer, T., Rosenberg, L., Huffman, L., Hyatt, L. et al. (1997). Requirements metrics—value added. In Proceedings of the 3rd IEEE international symposium on requirements engineering (RE’97) (p. 141.1). IEEE Computer Society.Google Scholar
  16. Henderson-Sellers, B., Zowghi, D., Klemola, T., & Parasuram, S. (2002). Sizing use cases: How to create a standard metrical approach. In Proceedings of the 8th international conference on object-oriented information systems (OOIS ’02) (pp. 409–421). Springer.Google Scholar
  17. IEEE. (1998). Recommended practice for software requirements specifications (IEEE 830). Tech. rep. IEEE.Google Scholar
  18. ISO/IEC. (2007). Software product quality requirements and evaluation (square) (ISO/IEC 25000). Tech. rep., ISO/IEC.Google Scholar
  19. Kolde, C. (2004). Basic metrics for requirements management. White paper, Borland.Google Scholar
  20. Loconsole, A. (2001). Measuring the requirements management key process area. In Proceedings of the 12th European software control and metrics conference (ESCOM’2001). Shaker Publishing.Google Scholar
  21. Lutowski, R. (2005). Software requirements: Encapsulation, quality, and reuse. Boston: Auerbach Publications.MATHCrossRefGoogle Scholar
  22. Marchesi, M. (1998). OOA metrics for the Unified Modeling Language. In Proceedings of the 2nd Euromicro conference on software maintenance and reengineering (CSMR’98) (p. 67). IEEE Computer Society.Google Scholar
  23. Medina Mora, M., & Denger, C. (2003). Requirements metrics: an initial literature survey on measurement approaches for requirements specifications. Tech. rep., Fraunhofer IESE .Google Scholar
  24. Modelware Project. (2006). D2.2 MDD engineering metrics definition. Tech. rep., Framework Programme Information Society Technologies.Google Scholar
  25. Moisiadis, F. (2002). The fundamentals of prioritising requirements. In Proceedings of the systems engineering, test and evaluation conference (SETE’2002). The Systems Engineering Society of Australia.Google Scholar
  26. Monperrus, M., Jézéquel, J. -M., Champeau, J., & Hoeltzener, B. (2008). A model-driven measurement approach. In Proceedings of the ACM/IEEE 11th international conference on model driven engineering languages and systems (MODELS’2008). Springer.Google Scholar
  27. Monperrus, M., Long, B., Champeau, J., Hoeltzener, B., Marchalot, G., & Jézéquel, J. -M. (2009). Model-driven architecture of a maritime surveillance system simulator. Systems Engineering Journal, 13.Google Scholar
  28. Monperrus, M., Jézéquel, J. -M., Baudry, B., Champeau, J., & Hoeltzener, B. (2010) Model-driven generative development of measurement software. Software and Systems Modeling (SoSyM).Google Scholar
  29. Nebut, C., Fleurey, F., Traon, Y. L., & Jézéquel, J. -M. (2003). Requirements by contracts allow automated system testing. In Proceedings of the 14th international symposium on software reliability engineering (ISSRE’03) (p. 85).Google Scholar
  30. Neuhaus, E., Neuhaus, C., Asher, A., & Wrede, C. (2006). The depth and breadth of Google Scholar: An empirical study. Libraries and the Academy, 6(2).Google Scholar
  31. OMG. (2004). UML 2.0 superstructure. Tech. rep., Object Management Group.Google Scholar
  32. OMG. (2010). Omg systems modeling language. Specification document 1.2, OMG.Google Scholar
  33. Paulk, M. C., Weber, C. V., Garcia, S. M., Chrissis, M. B., & Bush, M. (1993) Key practices of the capability maturity model. Tech. rep., Software Engineering Institute.Google Scholar
  34. Schmidt, D. C. (2006) Model-driven engineering. IEEE Computer, 39, 25–31.CrossRefGoogle Scholar
  35. Singh, Y., Sabharwal, S., & Sood, M. (2004) A systematic approach to measure the problem complexity of software requirement specifications of an information system. Information and Management Sciences, 15, 69–90.MATHGoogle Scholar
  36. Vicente-Chicote, C., Moros, B., & Álvarez, J. A. T. (2007). Remm-studio: An integrated model-driven environment for requirements specification, validation and formatting. Journal of Object Technology, 6(9), 437–454.CrossRefGoogle Scholar
  37. Young, R. R. (2006). Project requirements: A guide to best practices. Management Concepts.Google Scholar
  38. Zave, P. (1997). Classification of research efforts in requirements engineering. ACM Computing Surveys, 29(4), 315–321.CrossRefGoogle Scholar
  39. Zhang, H., & Babar, M. A. (2010). On searching relevant studies in software engineering. In Proceedings of the 14th international conference on evaluation and assessment in software engineering (EASE).Google Scholar

Copyright information

© Springer Science+Business Media, LLC 2011

Authors and Affiliations

  • M. Monperrus
    • 1
  • B. Baudry
    • 2
  • J. Champeau
    • 3
  • B. Hoeltzener
    • 3
  • J. M. Jézéquel
    • 2
    • 4
  1. 1.TU DarmstadtDarmstadtGermany
  2. 2.INRIARennesFrance
  3. 3.ENSIETABrestFrance
  4. 4.University of RennesRennesFrance

Personalised recommendations