An operational model for structuring the requirements generation process

Requirements Engineering

Volumn 10, Issue 1, 2005, Pages 45-62

  Arthur, James D ^a   Gröner, Markus K ^a  

^a State University   (United States)

Author keywords

Customer intent; Requirements engineering; Requirements generation; Requirements identification; Software engineering; Software methodology

Indexed keywords

CUSTOMER SATISFACTION; MATHEMATICAL MODELS; QUALITY ASSURANCE; SOFTWARE ENGINEERING;

CUSTOMER INTENT; REQUIREMENTS ANALYSIS; REQUIREMENTS GENERATION; REQUIREMENTS IDENTIFICATION; SOFTWARE METHODOLOGY;

REQUIREMENTS ENGINEERING;

EID: 13644249478     PISSN: 09473602     EISSN: 1432010X     Source Type: Journal    
DOI: 10.1007/s00766-004-0196-2     Document Type: Article

References (31)

1. Royce WW (1970) Managing the development of large software systems: concepts and techniques. In: Proceedings of the Western electronic show and convention (WesCon), Los Angeles, California, August 1970, pp 1-9 (Reprinted in: Proceedings of the 9th international conference on software engineering, Monterey, California, March 1987, pp 328-338)
2. Boehm BW (1988) A spiral model of software development and enhancement. IEEE Comput 21(5):61-72
3. Agresti WW (1986) New paradigms for software development. In: IEEE tutorial series. IEEE Computer Society Press, Los Angeles
4. Connel JL, Shafer LB (1989) Structured rapid prototyping: An evolutionary approach to software development. Yourdon Press, Prentice Hall Building, Englewood Cliffs
5. Bravo E (1993) The hazards of leaving out the users. In: Schuler D, Namioka A (eds) Participatory design: Principles and practices. Lawrence Erlbaum Associates, Hillsdale, pp 3-11
6. Freedman DP, Weinberg GM (1990) Handbook of walkthroughs, inspections, and technical reviews: Evaluating programs, projects, and products, 3rd edn. Dorset House Publishing Company, New York
7. Greenbaum J (1993) A design of one's own: Towards participatory design in the United States. In: Schuler D, Namioka A (eds) Participatory design: Principles and practices. Lawrence Erlbaum Associates, Hillsdale, pp 27-37
8. Davis AM (1993) Software requirements: Objects, functions, and states. 2nd revised edn. Prentice-Hall, Englewood Cliffs
9. Davis AM (2003) The art of requirements triage. IEEE Comput 36(3):42-49
10. Herlea DE, Jonker CM, Treur J, Wijngaards NJE (2002) A compositional knowledge level process model of requirements engineering. Int J Softw Eng Know 12(1):41-75
11. Ambler SW (2002) Agile modeling: Effective practices for XP and RUP. Wiley, New York
12. Ambler SM (2002) An introduction to agile modeling (AM). White paper, Ronin International. http://www.ronin-intl.com/publications/ agileModeling.pdf
13. Boehm B, Egyed A, Kwan J, Port D, Shah A, Madachy R (1998) Using the WinWin spiral model: A case study. IEEE Computer 31 7 33-44
14. Bjerknes G, Tone Bratteteig (1995) User participation and democracy: A discussion of Scandinavian research on system development. Scand J Inf Syst 7(1):73-98
15. Wood J, Silver D (1995) Joint application development, 2nd edn. Wiley, New York
16. Mullery G (1979) CORE: A method for controlled requirements specifications. In: Proceedings of the 14th international conference on software engineering, Munich, Germany, pp 126-135
17. Richards D (2003) Merging individual conceptual models of requirements. Requirements Eng J 8(4):195-205
18. Easterbrook S, Nuseibeh B (1996) Using viewpoints for inconsistency management. Software Eng J 11(1):31-43
19. Finkelstein A, Gabbay D, Hunter A, Kramer J, Nuseibeh B (1994) Inconsistency handling in multi-perspective specifications. IEEE Trans Software Eng 20(8):569-578
20. Leite JCSP, Freeman PA (1991) Requirements validation through viewpoint resolution. IEEE Trans Software Eng 17(12):1253-1269
21. Sommerville I, Sawyer P, Viller S (1998) Viewpoints for requirements elicitation: A practical approach. In: Proceedings of the 3rd IEEE international conference on requirements engineering (ICRE '98), Colorado Springs, Colorado, April 1998, pp 74-81
22. Davis AM, Hickey AM (2002) Requirements researchers: Do we practice what we preach? Requirements Eng J 7(2):107-111
23. Fagan ME (1976) Design and code inspection to reduce errors in program development. IBM Syst J 15(3):182-211
24. Lewis RO (1992) Independent verification and validation: A life cycle engineering process for quality software. Wiley, New York
25. Ebenau RG, Strauss SH (1993) Software inspection process. McGraw-Hill, New York
26. Grudin J (1994) Groupware and social dynamics: Eight challenges for developers. Commun Assoc Comput Machinery (CACM) 37(1):92-105
27. Nunamaker JF, Dennis AR, Valacich JS, Vogel DR, George JF (1991) Electronic meeting systems to support group work. Commun Assoc Comput Machinery (CACM) 34(7):30-61
28. Groener MK, Arthur JD (2002) Confirming the effectiveness of the requirements generation model: An industry-based empirical study. In: Proceedings of the 12th annual Pacific Northwest software quality conference, Portland, Oregon, pp 221-230
29. Arthur JD, Groener MK, Hayhurst KJ, Holloway CM (1999) Evaluating the effectiveness of independent verification and validation. IEEE Comput 32(10):79-83
30. Laeusen S, Vinter O (2001) Preventing requirements defects: An experiment in process improvement. Requirements Eng J 6(1):37-50
31. Rogers RA, McCaugherty D, Martin F (2001) A Case study of IV&V return on investment (ROI). White paper, Titan Systems Corporation, Civil Government Services Group. http://titansystemscorp.com/groups/ cgsg/techpapers/IVV_roi_cse.pdf