Requirements Statements Content Goodness and Complexity Measurement

##plugins.themes.academic_pro.article.sidebar##

Published Mar 1, 2013
https://doi.org/10.47164/ijngc.v4i1.46
Download
pdf
Statistic

Downloads

Download data is not yet available.

Metrics

Metrics Loading ...
Volume 4, Issue 1, March 2013

##plugins.themes.academic_pro.article.main##

Chao Y. Din
NuWave Solutions, LLC, Virginia, USA
David Rine
George Mason University, Virginia, USA

Abstract

In software development projects where written requirements are produced, a requirements document summarizes the results of the requirements analysis and becomes the basis for subsequent software development. In many cases, the quality of the requirements documents dictates the success of the software development. The need for determining the quality of requirements documents is particularly acute when the target applications are large, complicated, and mission critical. The goal of this research is to develop quality indicators to indicate the quality of requirements statements in a requirements document. To achieve the goal, the goodness properties of the requirements statements are adopted to represent the quality of requirements statements. A suite of complexity metrics of requirements statements is proposed as the quality indicators and is developed based upon research of noun phrase (NP) chunks. A two phased empirical case study is performed to evaluate the usage of the proposed metrics. By focusing upon the complexity metrics based on NP chunks, the research aided in development of complexity indicators of low quality requirements statements of requirements documents.

##plugins.themes.academic_pro.article.details##

How to Cite
Chao Y. Din, & David Rine. (2013). Requirements Statements Content Goodness and Complexity Measurement. International Journal of Next-Generation Computing, 4(1), 62–87. https://doi.org/10.47164/ijngc.v4i1.46
Crossref
Scopus
Google Scholar
Europe PMC

References

  1. Abney, S., and Abney, S.(1991). Parsing By Chunks In R. Berwick, S. Abney, and C. Tenny, editors, Principle- Based Parsing. Kluwer Academic Publishers, 1991.
  2. Basili, V. R. (1980). Qualitative Software Complexity Models: A Summary, Tutorial on Models and Methods for Software Management and Engineering. 1980.
  3. Briand, L. C., Daly, J. W., Wust, and J. K. (1999). A Uni ed Framework for Coupling Measurement in Object-Oriented Systems. IEEE Transactions on Software Engineering, 25:91 121, 1999
  4. Cant, S., Jeffery, D. R, Henderson-Sellers, and B (1995). A conceptual model of cognitive complexity of elements of the programming process. Information and Software Technology, 37(7):351 362, 1995.
  5. Card, D. N., and Glass, R. L. (1990). Measuring Software Design Quality Prentice-Hall, 1990.
  6. Darcy, D. P., and Kemerer, C. F. (2002). Software Complexity: Toward a Uni ed Theory of Coupling and Cohesion. not working here, 8, February 8 2002
  7. DeMarco, T. (1982). Controlling Software Projects. Yourdon Press, Englewood Cli s, NJ, 1982.
  8. Din, C. Y. (2008). Requirements Content Goodness and Complexity Measurement Based On NP Chunks. PhD thesis, George Mason University, Fairfax, VA, 2007, Reprinted by VDM Verlag Dr. Muller, 2008
  9. Din, C. Y., and Rine, D. C.(2008). Requirements Content Goodness and Complexity Measurement Based On NP Chunks. Proceedings, Complexity and Intelligence of the Arti cial Systems: Bio-inspired Computational Methods and Computational Methods Applied in Medicine, WMSCI 2008 Conference.
  10. Din, C. Y., and Rine, D. C.(2012). Requirements Metrics for Requirements Statements Stored in a Database. Proceedings of the 2012 International Conference on Software Engineering Research and Practice, SERP'12, July 16-19, 2012, pp. 1-7.
  11. Dunsmore, H. E.(1984). Software Metrics: An Overview of an Evolving Methodology. Information Processing and Management, 20(1-2):183 192, 1984.
  12. Evangelist, W.(1983). Software Complexity Metric Sensitivity to Program Structuring Rules. Journal of Systems and Software, 3(3):231 243, 1983.
  13. Fagan, M.(1986). Advances in Software Inspections. IEEE Transactions in Software Engineering, 12, 7: 744-751 July 1986.
  14. Fenton, N. E., Neil, and Neil, M. (1999). A Critique of Software Defect Prediction Models. IEEE Transactions on Software Engineering, 25:675 689, 1999.
  15. Fenton, N. E., and Neil, M.. Software metrics: roadmap. In Proceedings of the International Conference on Software Engineering (ICSE), pages 357 370, 2000.
  16. Fenton, N. E., and Pleeger, L. (1997). Software Metri cs: A Rigorous and Practical Approach. International Thomson Computer Press, Boston, MA, 1997. 2nd ed.
  17. Garson, G. D. (2006). Public Information Technology and E-Governance: Managing the Virtual State. Jones & Bartlett Pub., January 2006.
  18. Graesser, A. C., McNamara, D. S., Louwerse, M. M., and Cai, Z. (2004). Coh-Metrix: Analysis of Text on Cohesion and Language. Behavioral Research Methods, Instruments, and Computers, 36(2):193 202, 2004.
  19. Henderson-Sellers, B. (1996). Object-Oriented Metrics textendash Measures of Complexity. Prentice Hall PTR, New Jersey, 1996.
  20. Kemerer, C. F. (1998). Progress, Obstacles, and Opportunities in Software Engineering Economics. Communi- cations of ACM, 41:63 66, 1998.
  21. Kitchenham, B. A., Pleeger, S. L, Fenton, and N. E (1995). Towards a Framework for Software Measurement Validation. IEEE Transactions on Software Engineering, 21:929 943, 1995.
  22. Klemola, T. (2000). A Cognitive Model for Complexity Metrics. volume 13, June 13 2000.
  23. Lee, S. (2003). Proxy Viewpoints Model-Based Requirements Discovery. PhD thesis, George Mason University, Fairfax, VA, 2003.
  24. Levitin, A. V. (1986). How to Measure Size, and How Not to. volume 10, pages 314 318, Chicago, Oct 8-10 1986. IEEE Computer Society Press.
  25. Li, H. F., and Cheung, W. K. (1987). An empirical study of software metrics. IEEE Transactions on Software Engineering, 13(6):697 708, 1987.
  26. McNamara, D. S. (2001). Reading both high and low coherence texts: E ects of text sequence and prior knowledge. Canadian Journal of Experimental Psychology, 55:51 62, 2001.
  27. McNamara, D. S., Kintsch, E, Songer, N. B, Kintsch, and W (1996). Are good texts always better? Text coherence, background knowledge, and levels of understanding in learning from text. Cognition and Instruction, 14:1 43, 1996.
  28. Pleeger, S. L.(1993). Lessons learned in building a corporate metrics program. IEEE Software, 10(3):67 74, 1993.
  29. Purao, S., and Vaishnavi, V. (2003). Product Metrics for Object-Oriented Systems. ACM Computing Surveys, 35(2):191 221, 2003.
  30. Ricker, M. (1995). Requirements Speci cation Understandability Evaluation with Cohesion, Context, and Cou- pling. PhD thesis, George Mason University, Fairfax, VA, 1995.
  31. Schneider, R. E. (2002). Process for building a more e ective set of requirement goodness properties. PhD thesis, George Mason University, Fairfax, VA, 2002.
  32. Schneider, R., and Buede, D. (2000). Properties of a High Quality Informal Requirements Document, In Proceedings of the Tenth Annual International Conference on Systems Engineering, INCOSE, July 16-20, 2000b, 377-384.
  33. Schneider, R., and Buede, D. (2000). Criteria for Selecting Properties of a High Quality Informal Requirements Document, In Proceedings of the International Conference on Systems Engineering, Mid-Atlantic Regional Conference, INCOSE-MARC, April 5-8, 2000a, 7.2-1 to 7.2-5.
  34. Sommerville, I. (2006). Software Engineering: update. Addison Wesley, 8 edition, 2006.
  35. Weyuker, E. (1988). Evaluating Software Complexity Measures. IEEE Transactions Software Engineering, 14(9):1357 1365, 1988.
  36. Wilson, W. M., Rosenberg, L. H, Hyatt, and L. E (1996). Automated Quality Analysis Of Natural Language Requirement Speci cations. In Fourteenth Annual Paci c Northwest Software Quality Conference, October 1996.
  37. Yin, R. K. (2003). Case study research. Sage Publications, Thousand Oaks, CA, 3 edition, 2003.
  38. Zuse, H. (1998). A Framework of Software Measurement. Walter de Gruyter, Berlin/New York, 1998.
  39. Begh, J. (2008). A New Standard for Quality Requirements. IEEE Software, March/April 2008 pp. 57-63.
  40. Chung, L., and Cesar, J. (2009). On Non-Functional Requirements in Software Engineering. Conceptual Modeling: Foundations and Applications, Lecture Notes in Computer Science, Volume 5600, 2009, pp 363- 379.
  41. Costello, R., and Liu, D. (1995). Metrics for requirements engineering. Journal of Systems and Software, Volume 29, Issue 1, April 1995, Pages 3963.
  42. Davis, A., Overmyer, S., Caruso, J., Dandashi, F., and Dinh, A. (1993). Identifying and measuring quality in a software requirements speci cation. In Proceedings Software Metrics Symposium, 1993, First International, 21-22 May 1993, pp.141 152.
  43. Farbey, B (1990). Software quality metrics: considerations about requirements and requirement speci cations. Information and Software Technology, Volume 32, Issue 1, JanuaryFebruary 1990, Pages 6064.
  44. Wnu, K., Regnell, B., and Berenbach, B. (2011). Scaling Up Requirements Engineering Exploring the Chal- lenges of Increasing Size and Complexity in Market-Driven Software Development. Requirements Engineering: Foundations for Software Quality, Lecture Notes in Computer Science Volume 6606, 2011, pp 54-59.