Advertisement

A Process-Oriented Approach for the Optimal Satisficing of Non-Functional Requirements

  • Christopher Burgess
  • Aneesh Krishna
Part of the Lecture Notes in Computer Science book series (LNCS, volume 5543)

Abstract

In an ever more competitive world, the need for software systems to meet specific quality characteristics becomes increasingly apparent. These quality characteristics, or non-functional requirements, are often contradictory and ambiguous, making them difficult to manage during software development processes. This paper presents a modification of the NFR framework that facilitates the automated discovery of optimal system designs for the satisfaction of non-functional requirements. Just as with the NFR framework, this method can be used at any stage during the software development process in order to aid design decisions. The proposed method introduces the capacity to incorporate both qualitative and quantitative non-functional requirements, as well as the potential to include various cost factors into the optimisation process.

Keywords

Requirements engineering non-functional requirements NFR framework softgoal interdependency ruleset graphs 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Basili, V.R., Musa, J.D.: The Future Engineering of Software: A Management Perspective. IEEE Computer 24(9), 90–96 (1991)CrossRefGoogle Scholar
  2. 2.
    Chung, L.: Representing and Using Non-Functional Requirements: A Process Oriented Approach. Ph.D. Thesis, Dept. of Comp. Sci., Univ. of Toronto (1993)Google Scholar
  3. 3.
    Chung, L., Nixon, B.A.: Dealing with Non-Functional Requirements: Three Experimental Studies of a Process-Oriented Approach. In: 17th IEEE International Conference on Software Engineering, Seattle, pp. 25–37 (1995)Google Scholar
  4. 4.
    Chung, L., Nixon, B.A., Yu, E.: Using Quality Requirements to Systematically Develop Quality Software. In: Proc. 4th International Conference on Software Quality, McLean, VA, USA (1994)Google Scholar
  5. 5.
    Chung, L., Nixon, B.A., Yu, E., Mylopoulos, J.: Non-Functional Requirements in Software Engineering. Kluwer Academic Publishing, Dordrecht (2000)CrossRefzbMATHGoogle Scholar
  6. 6.
    Glinz, M.: On Non-Functional Requirements. In: 15th IEEE International Requirements Engineering Conference (2007)Google Scholar
  7. 7.
    Linger, R.C.: Cleanroom Software Engineering for Zero-Defect Software. In: Proc. 15th International Conference on Software Engineering, Baltimore, MD, USA, pp. 2–13 (1993)Google Scholar
  8. 8.
    Schneider, G.M., Martin, J., Tsai, W.T.: An Experimental Study of Fault Detection in User Requirements Documents. ACM Transactions on Software Engineering and Methodology 1(2), 188–204 (1992)CrossRefGoogle Scholar
  9. 9.
    Simon, H.A.: The Sciences of the Artificial, 2nd edn. MIT Press, Cambridge (1981)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Christopher Burgess
    • 1
  • Aneesh Krishna
    • 1
  1. 1.School of Computer Science and Software EngineeringUniversity of WollongongAustralia

Personalised recommendations