Skip to main content
Log in

Requirements honesty

  • Viewpoints
  • Published:
Requirements Engineering Aims and scope Submit manuscript

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

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Fig. 1.

References

  1. Beck K (1999) Embracing change with extreme programming. IEEE Comput 32(10):70–77

    Article  Google Scholar 

  2. McCormick M (2001) Programming extremism. Commun ACM 44(6):109–111

    Article  Google Scholar 

  3. Paulk MC (2001) Extreme programming from a CMM perspective. In: XP universe, Raleigh, NC, July 2001

  4. Robertson S, Robertson J (2002) Extending requirements: a practical workshop. Seminar offered by Atlantic System Guild. Description available at www.systemsguild.com/GuildeSite/Robs/erw.html. Cited Jun 2002

    Google Scholar 

  5. do Prado Leite JCS (2001) Extreme requirements. In: Jornadas de Ingeniería de Requisitos Aplicada, Sevilla, Spain, June 2001

  6. Booch G (2001) Developing the future. Commun ACM 44(3):119–121

    Article  Google Scholar 

  7. Müller MM, Padberg F (2002) Extreme programming from an engineering economics viewpoint. In: 4th international workshop economics-driven software engineering research, EDSER, Orlando, FL, May 2002

  8. Roman G-C (1985) A taxonomy of current issues in requirements engineering. IEEE Comput 18(4):14–22

    Google Scholar 

  9. Nuseibeh B, Easterbrook S (2000) Requirements engineering: a roadmap. In: Finkelstein ACW (ed) The future of software engineering, Limerick, Ireland, June 2000. IEEE Computer Society Press, Los Alamitos, CA (companion vol to Proceedings of the 22nd international conference on software engineering, ICSE'00)

  10. van Lamsweerde A (2000) Requirements engineering in the year 00: a research perspective. In: 22nd international conference on software engineering, ICSE'00, Limerick, Ireland, June 2000. IEEE Computer Society Press, Los Alamitos, CA

  11. Naur P, Randell B (eds) (1969) Software engineering: report of a conference sponsored by NATO Scientific Committee, Garmish, Germany, October 1968. Brussels, Scientific Affairs Division, NATO. www.cs.ncl.ac.uk/people/brian.randell/home.formal/ NATO/ index.html. Cited Jun 2002

    Google Scholar 

  12. Randell B, Buxton JN (eds) (1970) Software engineering techniques: report of a conference sponsored by the NATO Scientific Committee, Rome, Italy, October 1969. Brussels, Scientific Affairs Division, NATO. www.cs.ncl.ac.uk/people/brian.randell/home.formal/ NATO/ index.html. Cited Jun 2002

    Google Scholar 

  13. Davis AM (1992) Operational prototyping: a new development approach. IEEE Softw Sept:70–78

    Article  Google Scholar 

  14. Özcan MB, Siddiqi J (1996) Interchanging specifications and implementations in evolutionary prototyping. Softw Pract Exper 26(9):999–1023

    Article  Google Scholar 

  15. Muller MJ, Wildman DM, White EA (1993) Taxonomy of PD practices: a brief practitioner's guide. Commun ACM 36(4):26–28

    Google Scholar 

  16. Carmel E, Whitaker RD, George JF (1993) PD and joint application design: a transatlantic comparison. Commun ACM 36(4):40–48

    Article  Google Scholar 

  17. XP.org (2002) Extreme programming: a gentle introduction. http://www.extremeprogramming.org. Cited Jun 2002

  18. van Deursen A (2001) Customer involvement in extreme programming. ACM SIGSOFT Softw Eng Notes 26(6):70–73

    Google Scholar 

  19. Goguen JA, Linde C (1993) Techniques for requirements elicitation. In: 1st IEEE international symposium on requirements engineering, RE'93, San Diego, CA. IEEE Computer Society Press, pp 152–164

  20. Green EL (2002) FUD 101. http://badtux.org/eric/editorial/fud101.html. Cited Jun 2002

  21. Meyer P (1998) Killer applications. Bus Econ Rev 44(2). research.moore.sc.edu/research/bereview/be44_2/ killapp.html. Cited Jun 2002

  22. Balasubramaniam JP-H, Baskerville H, Levine L (2001) How internet software companies negotiate quality. IEEE Comput 43(5):51–57

    Google Scholar 

  23. Collison DJ (2000) Corporate propaganda: its implication for accounting and accountability. Discussion papers series, University of Dundee, Accountancy and Business Finance Department. http://www.dundee.ac.uk/accountancy/papers/010.doc. Cited Jun 2002

  24. Ulrich P (1994) Facing public interest. the ethical challenge to business policy and corporate communication. In: Topics of the 7th European business ethics conference, St Gallen, September 1994. Institute for Business Ethics. http://www.iwe.unisg.ch/org/iwe/web.nsf. Cited Jun 2002

  25. Chomsky N (1997) Market democracy in a neoliberal order: doctrines and reality. Davie Lecture, University of Cape Town, May 1997. http://www.bigeye.com/chomsky.htm. Cited Jun 2002

  26. Karlsson E-A, Andersson L-G, Leion P. Daily build and feature development in large distributed projects. In: 22nd international conference on software engineering, ICSE'00, Limerick, Ireland, June 2000

  27. Deming WE (1982) Quality, productivity, and competitive position. MIT, Cambridge, MA

  28. Juran JM (1992) Juran on quality by design: the new steps for planning quality into goods and services, rev edn. Free Press, New York

    Google Scholar 

  29. Weinberg GM (1998) Psychology of computer programming (Silver Anniversary edn). Dorset House, New York (An adaptation of chap 4 on egoless programming is published in IEEE Softw 16(1):118–120, 1999)

    Google Scholar 

  30. Williams LA, Kessler RR (2000) All I really need to know about pair programming I learned in kindergarten. Commun ACM 43(5):109–114

    Article  Google Scholar 

  31. Williams L, Upchurch RL (2001) In support of student pair-programming. In: SIGCSE conference on computer science education, Charlotte, NC, February 2001

  32. Tomayko JE (2002) A comparison of pair programming for software defect reduction: extreme programming web page, Carnegie Mellon. xpdata.distance.cmu.edu/ papers/ index.html. Cited Nov 2002

    Google Scholar 

  33. Müller MM, Tichy WF (2001) Case study: extreme programming in a university environment. In: 23rd international conference on software engineering, ICSE'01, Toronto, May 2001, pp 537–544

  34. Müller MM, Hagner O (2002) Experiment about test-first programming. In: Conference on empirical assessment in software engineering, EASE'02, Keele University, UK, 8–10 April 2002

  35. Dubois E, Yu E, Petit M (1998) From early to late formal requirements: a process-control case study. In: 9th international workshop on software specification and design, Ise-Shima (Isobe), Japan, April 1998. IEEE Computer Society Press, pp 34–42

  36. Weidenhaupt K, Pohl K, Jarke M, Haumer P (1998) Scenarios in system development: current practice. IEEE Softw Mar/Apr:34–45

  37. Sutcliffe AG, Maiden NAM, Minocha S, Manuel D (1998) Supporting scenario-based requirements engineering. IEEE Trans Softw Eng 24(12):1072–1088

    Article  Google Scholar 

  38. Berry DM (2002) The inevitable pain of software development, including of extreme programming, caused by requirements volatility. In: International workshop on time-constrained requirements, TCRE'02, Essen, Germany, September 2002

Download references

Acknowledgements

I am grateful to the constructive comments and suggestions that I received from the anonymous reviewers. Particularly, I would like to thank Daniel Berry for his invaluable help and encouragement. They all pointed out errors and made very interesting points that helped me to improve the content and presentation of the paper.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Francisco A. C. Pinheiro.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Pinheiro, F.A.C. Requirements honesty. Requirements Eng 8, 183–192 (2003). https://doi.org/10.1007/s00766-003-0165-1

Download citation

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00766-003-0165-1

Keywords

Navigation