Skip to main content

Non-Functional Requirements Elicitation

  • Chapter
Perspectives on Software Requirements

Abstract

Software developers are constantly under pressure to deliver code on time and on budget. As a result, many projects focus on delivering functionalities at the expense of meeting non-functional requirements such as reliability, security, maintainability, portability, accuracy, among others. As software complexity grows and clients demand higher and higher quality software, non-functional properties can no longer be considered to be of secondary importance. Many systems fail or fall into disuse precisely because of inadequacies in these properties. These nonfunctional aspects have been treated as properties or attributes after the fact. While these properties have always been a concern among software engineering researchers, early work have tended to view them as properties or attributes of the finished software product to be evaluated and measured. Recent work offer the complementary view that they should be treated as requirements to be dealt with from the earliest stages of the software development process [6][7], and then throughout the entire life cycle.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

eBook
USD 16.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 109.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 109.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Boehm, B. Characteristics of Software Quality. North Holland Press, 1978.

    Google Scholar 

  2. Boehm, Barry and In, Hoh. Identifying Quality-Requirement Conflicts. IEEE Software 1996; 13(2): 25–35.

    Article  Google Scholar 

  3. Breitman, K. K, Leite J.C.S.P. and Finkelstein Anthony. The World’s Stage: A Survey on Requirements Engineering Using a Real-Life Case Study. Journal of the Brazilian Computer Society 1999; 6(1): 13–37.

    Article  Google Scholar 

  4. Chung L. Representing and Using Non-Functional Requirements: A Process Oriented Approach. Ph.D. Thesis, Dept. of Comp. Science, University of Toronto, June 1993. Also tech. Rep. DKBS-TR-91-1.

    Google Scholar 

  5. Chung, L., Nixon, B. Dealing with Non-Functional Requirements: Three Experimental Studies of a Process-Oriented Approach. Proceedings of 17th International Conference on Software Engineering; 1995 April 23–30; Seatle, Washington. ACM Press, 1995.

    Google Scholar 

  6. Chung, L., Nixon, B., Yu, E. and Mylopoulos, J. Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers, 2000.

    MATH  Google Scholar 

  7. Cysneiros, L.M. and Leite, J.C.S.P. Integrating Non-Functional Requirements into data model. Proceedings of RE’99, 4th International Symposium on Requirements Engineering; 1999 June 07–11; Limerick, Ireland. Los Alamitos, CA: IEEE Computer Society Press, 1999.

    Google Scholar 

  8. Cysneiros,L.M., Leite, J.C.S.P. and Neto, J.S.M. A Framework for Integrating Non-Functional Requirements into Conceptual Models. Requirements Engineering Journal 2001; 6(2):97–115.

    Article  MATH  Google Scholar 

  9. Cysneiros,L.M. and Leite, J.C.S.P. Using UML to Reflect Non-Functional Requirements. Proceedigns of the 11th CASCON, IBM; November 5–7 2001; Canada, Toronto.

    Google Scholar 

  10. Dardenne, A., van Lamsweerde A, Fickas, S. Goal Directed Requirements Acquisition. Science of Computer Programming 1993; 20: 3–50.

    Article  MATH  Google Scholar 

  11. Evaluation of Natural Language Processing Systems,http://www.issco.unige.ch/ewg95, 1995.

  12. Ebert, C. Dealing with Nonfunctional in Large Software Systems. Annals of Software Engineering 1997; 3: 367–395.

    Article  Google Scholar 

  13. Fenton, N.E. and Pfleeger, S.L. Software Metrics: A Rigorous and Practical Approach, 2nd ed. International Thomson Computer Press, 1997.

    Google Scholar 

  14. Finkelstein, A. and Dowell J. A comedy of Errors: The London Ambulance Service Case Study. Proceedings of IWSSD’96, Eighth International Workshop on Software Specification and Design; 1996 March 22–23; Paderborn, Germany. IEEE Computer Society Press.

    Google Scholar 

  15. Keller, S.E. et al. “Specifying Software Quality Requirements with Metrics”. In System and Software Requirements Engineering. Thayer, R.H.; Dorfman. M., eds. IEEE Computer Society Press, 1990; pp. 145–163.

    Google Scholar 

  16. Kirner T.G., Davis A.M. Nonfunctional Requirements of Real-Time Systems. Advances in Computers 1996; 42: 1–37.

    Article  Google Scholar 

  17. Lindstrom, D.R. Five Ways to Destroy a Development Project. IEEE Software 1993; 10(5): 55–58.

    Article  Google Scholar 

  18. Leite J.C.S.P. and Franco, A.P.M. A Strategy for Conceptual Model Acquisition. Proceedings of the First IEEE International Symposium on Requirements Engineering; 1993 January 4–6; San Diego, CA. Los Alamitos, CA: IEEE Computer Society, 1993.

    Google Scholar 

  19. Leite, J.C.S.P. et.al. Enhancing a Requirements Baseline with Scenarios. Requirements Engineering Journal 1997; 2(4): 184–198.

    Article  Google Scholar 

  20. Liu, L. and Yu E. Designing Web-Based Systems in Social Context: A Goal and Scenario Based Approach. Proceedings of CAiSE’02, 14th International Conference on Advanced Information Systems Engineering; 2002 May 27–31; Toronto, Canadá. LNCS 2348 Springer Verlag, 2002.

    Google Scholar 

  21. Liu, L., Yu, Eric, and Mylopoulos, J. Analyzing Security Requirements As Relationships among Strategic Actors. Proceedings of the 2nd Symposium on Requirements Engineering for Information Security; 2002 October 16; North Carolina.

    Google Scholar 

  22. Lyu, M.R., ed. Handbook of Software Reliability Engineering. McGraw-Hill, 1996.

    Google Scholar 

  23. Mylopoulos, J., Chung, L., and Nixon, B. Representing and Using Non-functional Requirements: A Process-Oriented Approach. IEEE Transactions on Software Engineering 1992; 18(6): 483–497.

    Article  Google Scholar 

  24. Neto, J.S.M. Integrando Requisitos Não Funcionais ao Modelo de Objetos. M.Sc. Dissertation, PUC-Rio, March 2000.

    Google Scholar 

  25. Rational et al, Object Constraint Language Specification,http://www.rational.com,1997.

  26. Yu, Eric. Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering. Proceedings of the 3rd International Symposium on Requirements Engineering; 1997 Januay 6–10; Annapolis, Maryland. Los Alamitos, CA, IEEE Computer Society Press, 1997.

    Google Scholar 

  27. Yu, E. and Cysneiros, L.M. Privacy in the Presence of Other Competing Requirements. Proceedings of 2nd Symposium on Requirements Engineering for Information Security; 2002 October; North Carolina.

    Google Scholar 

  28. VanLamsweerde, A. Goal-Oriented Requirements Engineering: A Guided Tour. Proceedings of the 5th IEEE International Symposium on Requirements Engineering; 2001 August 27–30; Toronto, Canada. Los Alamitos, CA: IEEE Computer Society Press, 2001.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2004 Springer Science+Business Media New York

About this chapter

Cite this chapter

Cysneiros, L.M., Yu, E. (2004). Non-Functional Requirements Elicitation. In: do Prado Leite, J.C.S., Doorn, J.H. (eds) Perspectives on Software Requirements. The Springer International Series in Engineering and Computer Science, vol 753. Springer, Boston, MA. https://doi.org/10.1007/978-1-4615-0465-8_6

Download citation

  • DOI: https://doi.org/10.1007/978-1-4615-0465-8_6

  • Publisher Name: Springer, Boston, MA

  • Print ISBN: 978-1-4613-5090-3

  • Online ISBN: 978-1-4615-0465-8

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics