Requirements engineering: Setting the context

Engineering and Managing Software Requirements

Volumn , Issue , 2005, Pages 1-15

  Aurum, Aybüke ^a   Wohlin, Claes ^b  

^a UNIVERSITY OF NEW SOUTH WALES   (Australia)

^b BLEKINGE INSTITUTE OF TECHNOLOGY   (Sweden)

Author keywords

Business requirements; Product requirements; Project requirements; Requirements management; Requirements taxonomy; Stakeholders

Indexed keywords

EID: 84895382020     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/3-540-28244-0_1     Document Type: Chapter

References (41)

1. Anthony RN (1965) Planning and control systems: A framework for analysis. Harvard University, Boston, USA.
2. Aurum A, Wohlin C (2003) The fundamental nature of requirements engineering activities as decision making process. Journal on Information and Software Technology, 45(14): 945-954.
3. Babbie E (1990) Survey research methods. Wadsworth, ISBN 0-524-12672-3.
4. Berry DM, Lawrence B (1998) Requirements engineering. IEEE Software 25(2): 26-29.
5. Boehm BW, (1988) A spiral model of software development and enhancement, Computer, May, 21(5): 61-72.
6. Boehm BW, Papaccio PN (1988) Understanding and controlling software costs. IEEE transactions on software engineering, 14 (10): 1462-1477.
7. Boehm BW, Grünbacher P, Brigges RO (2001) Developing groupware for requirements negotiation: lessons learned. IEEE, Software, May/June, pp. 46-55.
8. Boehm BW (2003) Value-based software engineering. ACM SIGSOFT, Software engineering notes, March, 28(2): 1-12.
9. BSC'04 (2004) The challenges of complex IT projects. The report of a working group from the Royal academy of engineering and the British computer society. ISBN 1- 903496-15-2. Access on 20th October 2004. http://www.bcs.org/ BCS/News/PositionsAndResponses/Positions/complexity.htm.
10. Chaos'94 (1995) The Standish group. Access on 4th October 2004. http://standishgroup.com/sample-research/.
11. Chaos'98 (1999) A recipe for success. The Standish group report. Access on 4th October 2004 http://www.standishgroup.com/sample-research.
12. Chao'01 (2002) Extreme chaos. The Standish group report. Accessed on 4th October 2004 http://www.standishgroup.com/sample-research.
13. Chatzoglou PD (1997) Factors affecting completion of the requirements capture stage of projects with different characteristics. Information and Software Technology, 39 (9): 627-640.
14. Curtis B, Krasner H, Iscoe N (1988) A field study of the software design process for large systems. Communications of the ACM 31(11):1268-1287.
15. Davis A (1990) System testing: Implications of requirements specifications. Information and Software Technology, 32 (6): 407-414.
16. Edwards J, Coutts I, McLeod S (2000) Support for system evolution through separating business and technology issues in a banking system. In: Proceedings of international conference on software Maintenance, 11-14 October, pp. 271-276.
17. El Emam K, Madhavji NH (1995) A field study of requirements engineering practices in information systems development. In: Proceedings of 2nd international symposium on requirements engineering, York, England, IEEE CS Press, pp.68-80.
18. European Software Institute (1996) European user survey analysis. Report USV-EUR 2.1, ESPITI project, January.
19. Faulk SR, Harmon RR, Raffo DM (2000) Value-base software engineering: A valuedriven approach to product-line engineering. In: Proceedings of 1st international conference on software product-line engineering, Colorado, August 28, 2000.
20. Hall T, Beecham S, Rainer A (2002) Requirements problems in twelve companies: an empirical analysis. IEE proceedings software, 149 (5): 153-160.
21. Hofmann HF, Lehner F (2001) Requirements engineering as a success factor in software projects. IEEE Software, 18 (4): 58-66.
22. Houdek F, Pohl K (2000): Analyzing requirements engineering processes: A case study. In: Proceedings of the 11th international workshop on database and expert systems applications, Greenwich, UK, 6-8 September, pp.983-987.
23. Hunter A, Nuseibeh B (1997) Analyzing inconsistent specifications. In: Proceedings of 3rd international symposium on requirements engineering, RE'07, Annapolis, Md, pp.78-86.
24. IEEE-STD 610.12-1990, Standard Glossary of Software Engineering Terminology, 1990, Institute of Electrical and Electronics Engineers.
25. Kotonya G, Sommerville I (1998) Requirements engineering - processes and techniques, John Wiley & Sons UK.
26. Lauesen, S (2002) Software requirements: styles and techniques, Addison-Wesley, London, UK.
27. Loucopoulos P, Karakostas V (1995): System requirements engineering. McGraw-Hill Book company Europe.
28. Lowe D, Eklund J (2001) Development issues in specification of web systems. In: Proceedings of 6th Australian workshop on requirements engineering, 22-23 November, University of New South Wales, Sydney, Australia, pp. 4-13.
29. Lubars M, Potts C, Richter C (1993) A review of the state of the practice in requirements modelling. In: Proceedings of the IEEE international symposium on requirements engineering, IEEE Computer Society, San Diego, USA, pp. 2-14.
30. Macaulay LA (1996) Requirements engineering. Springer-Verlag, New York, London.
31. Madhavji NH, Holtje D, Hong W, Bruckhaus T (1994) Elicit: A method for eliciting process models. In: Proceedings of CAS conference, Toronto, Canada, 31 October-3 November, pp.11-122.
32. Martin S, Aurum A, Jeffery R, Paech B (2002) Requirements engineering process models in practice. In: Proceedings of 7th Australian workshop on requirements engineering, AWRE'02, 2-3 December, Melbourne, pp. 41-47.
33. Menzies T, Easterbrook S, Nuseibeh B, Waugh S (1999) An empirical investigation of multiple viewpoint reasoning in requirements engineering. In: Proceedings of IEEE international symposium on requirements engineering, 7-11 June, pp.100-109.
34. Miller E (2002) For survival, start thinking lifecycle management. Computer-aided engineering, 21 (1): 15-18.
35. Nguyen L, Swatman P (2003) Managing the requirements engineering process. Requirements engineering, 8 (1): 55-68.
36. Pouloudi A, Whitley EA (1997) Stakeholder identification in inter-organizational systems: Gaining insights for drug use management systems. European journal of information systems, 6: 1-14.
37. Sommerville I (2001) Software engineering. Pearson Education Ltd, UK.
38. Tveito A, Hasvold P (2002) Requirements in the medical domain: Experiences and prescriptions. IEEE Software, Nov-Dec, pp.66-69.
39. van Lamsweerde A (2000) Requirements engineering in the year 00: A research perspective. In: Proceedings of 22nd International conference on software engineering, pp.5-19.
40. Wohlin C, Runeson P, Höst M, Ohlsson MC, Regnell B, Wesslén A (2000) Experimentation in software engineering - An introduction. Kluwer Academic Publishers, Boston, MA, USA.
41. Yin RK (1994) Case study research design and methods. Sage Publications, Beverly Hills, California, USA.