Requirements elicitation and elicitation technique selection: Model for two knowledge-intensive software development processes

Proceedings of the 36th Annual Hawaii International Conference on System Sciences, HICSS 2003

Volumn , Issue , 2003, Pages

  Hickey, A M ^a   Davis, A M ^a  

^a UNIVERSITY OF COLORADO   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

REQUIREMENTS ENGINEERING; SOFTWARE DESIGN; SOFTWARE ENGINEERING;

ELICITATION METHODS; ELICITATION TECHNIQUES; KNOWLEDGE INTENSIVE PROCESS; META-PROCESS; REQUIREMENTS ELICITATION; SOFTWARE DEVELOPMENT PROCESS;

KNOWLEDGE MANAGEMENT;

EID: 84969581187     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/HICSS.2003.1174229     Document Type: Conference Paper

References (52)

1. Gottesdeiner, E., Requirements by Collaboration, Addison-Wesley, 2002.
2. Standish Group, "The Chaos Report," www.standishgroup.com, 1995.
3. Hofmann, H., and F. Lehner, "Requirements Engineering as a Success Factor in Software Projects," IEEE Software, 18, 4 (July/Aug 2001), pp. 58-66.
4. Gause, D., and G. Weinberg, Are Your Lights On?, Dorset House, 1990.
5. Jackson, M., Problem Frames, Addison-Wesley, 2001.
6. Wood, J., and D. Silver, Joint Application Development, Wiley, 1995.
7. Davis, A., "A Taxonomy for the Early Stages of the Software Development Life Cycle," Journal of Systems and Software, 8, 4 (September 1988), pp. 297-311.
8. Davis, A., Software Requirements: Objects, Functions and States, Prentice Hall, 1993.
9. Goguen, J., and C. Linde, "Software Requirements Analysis and Specification in Europe: An Overview," First International Symposium on Requirements Engineering, IEEE Computer Society Press, 1993, pp. 152-164.
10. Kotonya, G., and I. Sommerville, Requirements Engineering, Wiley, 1998.
11. Lauesen, S., Software Requirements: Styles and Techniques, Addison-Wesley, 2002.
12. Leffingwell, D., and D. Widrig, Managing Software Requirements, Addison-Wesley, 2000.
13. Macaulay, L., Requirements Engineering, Springer, 1996.
14. Maiden, N., and G. Rugg, "ACRE: Selecting Methods for Requirements Acquisition," Software Engineering Journal, 11, 5 (May, 1996), pp. 183-192.
15. Wiegers, K., Software Requirements, Microsoft Press, 1999.
16. Royce, W., "Managing the Development of Large Software Systems," WESCON '70, 1970;
17. reprinted in IEEE 9th International Conference on Software Engineering, IEEE Computer Society Press, 1987.
18. Siddiqi, J., and M. Shekaran, "Requirements Engineering: The Emerging Wisdom," IEEE Software, 13, 2 (March 1996), pp. 15-19.
19. Hickey, A., "Integrated Scenario and Process Modeling Support for Collaborative Requirements Elicitation," University of Arizona Department of Management Information Systems PhD Dissertation, 1999.
20. Graham, I., Requirements Engineering and Rapid Development, Addison-Wesley, 1998.
21. Zave, P., "Classification of Research Efforts in Requirements Engineering," ACM Computing Surveys, 29, 4 (April 1997), pp. 315-321.
22. Jarke, M., and K. Pohl, "Requirements Engineering in 2001: (Virtually) Managing a Changing Reality," Software Engineering Journal, 9, 6 (June 1994), pp. 257-266.
23. Pohl, K., Process-Centered Requirements Engineering, Wiley, 1996.
24. Thayer, R., and M. Dorfman, Standards, Guidelines, and Examples on System and Software Requirements Engineering, IEEE Computer Society Press, 1994.
25. Loucopoulos, P., and V. Karakostas, System Requirements Engineering, McGraw Hill, 1995.
26. Playle, G., and C. Schroeder, "Software Requirements Elicitation: Problems, Tools, and Techniques," Crosstalk, 9, 12 (December 1996), pp. 19-24.
27. Gaska, M., and D. Gause, "An Approach for Cross-Discipline Requirements Engineering Process Patterns," Third International Conference on Requirements Engineering, IEEE Computer Society, 1998, pp. 182-189.
28. Robertson, S., and J. Robertson, Mastering the Requirements Process, Addison-Wesley, 1999.
29. Hsia, P., et al., "Formal Approach to Scenario Analysis," IEEE Software, 11, 2 (March 1994), pp. 33-41.
30. Holbrook, H., "A Scenario-Based Methodology for Conducting Requirements Elicitation," ACM SIGSOFT Software Engineering Notes, (January 1990), pp. 95-104.
31. Sutcliffe, A., and M. Ryan, "Experience with SCRAM, a Scenario Requirements Analysis Method," Third International Conference on Requirements Engineering, IEEE Computer Society Press, 1998, pp. 164-171.
32. Sommerville, I., et al., "Viewpoints for Requirements Elicitation: A Practical Approach," Third International Conference on Requirements Engineering, IEEE Computer Society Press, 1998, pp. 74-81.
33. Browne, G., and M. Rogich, "An Empirical Investigation of User Requirements Elicitation: Comparing the Effectiveness of Prompting Techniques," Journal of Management Information Systems, 17, 4 (Spring 2001), pp. 223-249.
34. Gause, D., and G. Weinberg, Exploring Requirements: Quality Before Design, Dorset House, 1989.
35. Pressman, R., Adaptable Software Model, Preparing for Software Requirements Elicitation, http://www.rspa.com/checklists/reqelicit.html.
36. Maciaszek, L., Requirements Analysis and System Design, Addison-Wesley, 2001.
37. Dean, D., et al., "Enabling the Effective Involvement of Multiple Users: Methods and Tools for Collaborative Software Engineering," Journal of Management Information Systems, 14, 3 (Winter 1997-98), pp. 179-222.
38. Davis, A., and A. Hickey, "Requirements Researchers: Do We Practice What We Preach," Requirements Engineering Journal, 2002.
39. Glass, R., "Searching for the Holy Grail of Software Engineering," Communications of the ACM, 45, 5 (May 2002), pp. 15-16.
40. Yadav, S., et al., "Comparison of Analysis Techniques for Information Requirements Determination," Communications of the ACM, 31, 9 (September 1988).
41. Alexander, L., and A. Davis, "Criteria for the Selection of a Software Process Model," Fifteenth IEEE COMPSAC, 1991, IEEE Computer Society Press, pp. 521-528.
42. Jorgensen, P., The Use of MM-Paths in Constructive Software Development, Arizona State University, Department of Computer Science PhD Thesis, 1985.
43. Juristo, N., and A. Moreno, Basics of Software Engineering Experimentation, Kluwer Academic, 2001.
44. Scharer, S., "Pinpointing Requirements," Datamation, April 1981, pp. 139-154.
45. Preece, A., et al., "Better Knowledge Management through Knowledge Engineering," IEEE Intelligent Systems, (Jan/Feb 2001), pp. 36-42.
46. Alavi, M., and D. Leidner, "Review: Knowledge Management and Knowledge Management Systems: Conceptual-Foundations and Research Issues," MIS Quarterly, 25, 1 (March 2001), pp. 107-136.
47. Alavi, M., and D. Leidner, "Knowledge Management Systems: Issues, Challenges, and Benefits," Communications of the Association for Information Systems, 1, 7 (Feb. 1999).
48. Liebowitz, J., Knowledge Management: Learning from Knowledge Engineering, CRC Press, 2001.
49. Rook, F., and J. Croghan, "The Knowledge Acquisition Activity Matrix: A Systems Engineering Conceptual Framework," IEEE Transactions on Systems, Man, and Cybernetics, 19, 3, (May/June 1989), pp. 586-597.
50. Forsythe, D., and B. Buchanan, "Knowledge Acquisition for Expert Systems: Some Pitfalls and Suggestions," IEEE Transactions on Systems, Man, and Cybernetics, 19, 3 (May/June 1989), pp. 435-442.
51. Byrd, T., et al., "A Synthesis of Research on Requirements Analysis and Knowledge Acquisition Techniques," MIS Quarterly, 16, 1 (March 1992), pp. 117-138.
52. Shaw, M., and B. Gaines, "Requirements Acquisition," Software Engineering Journal, May 1996, pp. 149-165.