Advertisement

Framework for Quantitatively Evaluating the Quality Requirements of Software System

  • Yuki Terawaki
Part of the Lecture Notes in Computer Science book series (LNCS, volume 8016)

Abstract

Quality requirements (QR) are a description which indicates how well the software’s behavior is to be executed. It is widely recognized that quality requirements are vital for the success of software systems. Therefore, to define the quality requirements and to check the quality attributes carefully is necessary for bringing good- quality software and ensuring quality of the service. This paper proposes a framework that measures the quality attributes in the requirements document such as SRS. The effectiveness of this framework was briefly described, we discuss approach was to enrich the representative quality corpora.

Keywords

Requirements Engineering Quality Requirements Non-Functional Requirements text-mining 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Wiegers, K.E.: Software Requirements. Microsft Press (2003)Google Scholar
  2. 2.
    Chung, L., Nixon, B.A., Yu, E., Mylopoulos, J.: Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers (2000)Google Scholar
  3. 3.
    Berntsson Svensson, R., Gorschek, T., Regnell, B., Torkar, R., Shahrokni, A., Feldt, R.: Quality Requirements in Industrial Practice – an extended interview study at eleven companies. IEEE Transaction on Software Engineering (2011) (in print)Google Scholar
  4. 4.
    Borg, A., Yong, A., Carlshamre, P., Sandahl, K.: The Bad Conscience of Requirements Engineering: An Investigation in Real-world Treatment of Non-functional Requirements. In: Third Conference on Software Engineering Research and Practice in Sweden (SERPS 2003), Lund, Sweden (2003)Google Scholar
  5. 5.
    Chung, L., do Prado Leite, J.C.S.: On Non-Functional Requirements in software engineering. In: Borgida, A.T., Chaudhri, V.K., Giorgini, P., Yu, E.S. (eds.) Conceptual Modeling: Foundations and Applications. LNCS, vol. 5600, pp. 363–379. Springer, Heidelberg (2009)CrossRefGoogle Scholar
  6. 6.
    IEEE, Recommended practice for software requirements specifications, IEEE, Tech. Rep., IEEE Std830-1998 (1998)Google Scholar
  7. 7.
    Lauesen, S.: Software Requirements styles and Techniques. Addison-Wesley (2002)Google Scholar
  8. 8.
    Wilson, W.M., et al.: Automated Analysis of Requirement Specifications. In: Proceedings of the International Conference on Software Engineering ICSE 1997, pp. 161–171 (1997)Google Scholar
  9. 9.
    Fantechi, A., et al.: Application of Linguistic Techniques for Use Case Analysis. In: Proceedings of the IEEE Joint International Conference on Requirements Engineering, pp. 157–164 (2002)Google Scholar
  10. 10.
    Grimshaw, D., Drapper, G.W.: Non-functional requirements analysis: Deficiencies in structured methods. Information and Software Technology 43, 629–634 (2001)CrossRefGoogle Scholar
  11. 11.
    Johansson, E., Wesslen, A., Bratthall, L., Host, M.: The importance of quality requirements in software platform development –a survey. In: Proceedings of the 34th Annual Hawaii International Conference on System Sciences (2001)Google Scholar
  12. 12.
    Kaiya, H., Sato, T., Osada, A., Kitazawa, N., Kaijiri, K.: Toward quality requirements analysis based on domain specific quality spectrum. In: SAC 2008 Proceedings of the 2008 ACM Symposium on Applied Computing (2008)Google Scholar
  13. 13.
    Olsson, T., Sevenssion, R.B., Regnell, B.: Non-functional requirements metrics in practice – an empirical document analysis. In: Workshop on Measuring Requirements for Project and Product Success (2007) (a full version is to appear in the Information and Software Technology)Google Scholar
  14. 14.
    Kotonya, G., Sommerville, I.: Requirements Engineering: Processes and Techniques. John Wiley & Sons Ltd. (1997)Google Scholar
  15. 15.
    ISO/IEC, ISO/IEC 25010 Systems and software engineering- Systems and software Quality Requirements and Evaluation (SQuaRE) -System and software quality models (2011)Google Scholar
  16. 16.
    Sen (December 2010), http://ultimania.org/sen/
  17. 17.
  18. 18.
    日本語 WordNet (December 2010), http://nlpwww.nict.go.jp/wn-ja/index.en.html
  19. 19.
    Terawaki, Y., Tamai, T.: A Framework for Mining Quality Requirements in Software Requirements Specifications. In: The International Symposium on Requirements Engineering (RE) (submitted)Google Scholar
  20. 20.
    Fagan, M.: Design and Code Inspections to Reduce Errors in Program Development. IBM Systems Journal 15(3), 182–211 (1976)CrossRefGoogle Scholar
  21. 21.
    Takano, A.: Association computation for information access. In: Grieser, G., Tanaka, Y., Yamamoto, A. (eds.) DS 2003. LNCS (LNAI), vol. 2843, pp. 33–44. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  22. 22.
    Terawaki, Y.: Supporting of Requirements Elicitation for Ensuring Services of Information Systems Used for Education. In: Smith, M.J., Salvendy, G. (eds.) HCII 2011, Part I. LNCS, vol. 6771, pp. 58–65. Springer, Heidelberg (2011)CrossRefGoogle Scholar
  23. 23.
    Terawaki, Y., Tamai, T.: A practical approach to Quality Requirements Handling in Software Systems Development. In: The Eighth International Conference on Systems, ICONS 2013, pp. 160–163 (2013)Google Scholar
  24. 24.
    ISO/IEC, ISO/IEC 25030 Software engineering – Software product Quality Requirements and Evaluation (SQuaRE) – Quality requirements, 1 edn. (2007)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Yuki Terawaki
    • 1
  1. 1.Research Center for Computing and Multimedia StudiesHosei UniversityKoganeiJapan

Personalised recommendations