Abstract
Too many systems constructed by the software industry fail to meet users’ needs. Requirements elicitation is the set of activities performed to understand users’ needs for a system. Although most texts focus on a few elicitation techniques, there are numerous variations of these basic techniques. So, the question arises, how can an analyst understand all these techniques and their variations? Moreover, most experts today agree that the selection of an appropriate technique must be a function of the situation. But, a seemingly infinite number of situational characteristics exist. So, how can an analyst know which of these many situational characteristics should be taken into account when trying to select elicitation techniques? And, how does an analyst select a technique that makes sense given those situational characteristics?
The overarching goal of this research is to construct an information system to aid novice analysts in selecting the most effective requirements elicitation techniques for their project situation. Fundamental to the success of this endeavor is the creation of an ontology which: (1) sets the context for requirements elicitation and elicitation technique selection; (2) defines key characteristics of elicitation techniques that highlight their essential similarities and differences; and (3) identifies the important characteristics of a situation that should be considered when selecting an elicitation technique. This chapter describes the iterative ontology engineering approach used, summarizes the proposed requirements elicitation ontology, and demonstrates how the ontology will be used as a basis for an information system to assist analysts in selecting an appropriate elicitation technique. As a result, this chapter, rather than focusing on ontology research per se, focuses on the application of ontologies to improve the state of research and practice in one specific information systems discipline — requirements elicitation.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Alexander, L., and Davis, A., 1991, Criteria for the selection of a software process model, 15th IEEE COMPSAC, IEEE Computer Society, Los Alamitos, CA, pp. 521–528.
Bento, A., 1994, Systems analysis: A decision approach, Info. & Mgmt 27(8):185–193.
Boehm, B., Abts, C., Brown, A., Chulani, S., Clark, B., Horowitz, E., Madachy, R., Reifer, D., and Steece, B., 2000, Software Cost Estimation with COCOMO II, Prentice Hall, Upper Saddle River, NJ.
Burke, K., and Aytes, K., 1998, A longitudinal analysis of the effects of media richness on cohesive development and process satisfaction in computer-supported work, 31st Hawaii Int. Conf. on the System Sciences 1, IEEE Computer Society, Los Alamitos, CA,, pp. 135–144.
Byrd, T., Cossick, K., and Zmud, R., 1992, A synthesis of research on requirements analysis and knowledge acquisition techniques, MIS Quarterly 16(1):117–138.
Checkland, P., and Scholes, J., 1991, Soft Systems Methodology in Action, Wiley, Chichester, UK.
Conger, S., 1994, New Software Engineering, Wadsworth, Belmont, CA.
Coughlan, J., and Macredie, R., 2002, Effective communication in requirements elicitation: A comparison of methodologies, Req. Eng. 7(2):47–60.
Daft, R., and Lengel, R., 1986, Organizational information requirements, media richness and structural design, Mgmt Science 32(5):554–571.
Davis, A., 1993, Software Requirements: Objects, Functions and States, Prentice Hall, Upper Saddle River, NJ.
Davis, A., 2005, Just Enough Requirements Management, Dorset House, New York.
Dennis, A., and Haley Wixom, B., 2000, Systems Analysis and Design: An Applied Approach, Wiley, New York.
Dennis, A., and Valacich, J., 1999, Rethinking media richness: Towards a theory of media synchronicity, 32nd Hawaii Int. Conf. on System Sciences, IEEE Computer Society, Los Alamitos, CA.
Fensel, D., 2004, Ontologies: A Silver Bullet for Knowledge Management and Electronic Commerce, Springer, Berlin.
Gause, D., and Weinberg, J., 1989, Exploring Requirements: Quality Before Design, Dorset House, New York.
Glass, R., 2002, Searching for the holy grail of software engineering, Comm. of the ACM 45(5):15–16.
Goguen, J., and Linde, C., 1993, Software requirements analysis and specification in Europe: An overview, 1st Int. Symp. on Req. Eng., IEEE Computer Society, Los Alamitos, CA, pp. 152–164.
Gomez-Perez, A., Fernandez-Lopez, M., and Corcho, O., 2004, Ontological Engineering: With Examples from the Areas of Knowledge Management, e-Commerce, and the Semantic Web, Springer, London.
Gottesdiener, E., 2002, Requirements by Collaboration, Addison-Wesley, Reading, PA.
Gruber, T., 1993, A translational approach to portable ontologies, Knowledge Acq. 5(2):199–220.
Gruninger, M., and Lee, J., 2002, Ontology: Applications and design, Comm, of the ACM 45(2):39–41.
Hickey, A., and Davis, A., 2002, The role of requirements elicitation techniques in achieving software quality, Req. Eng.: Foundations for Software Quality WS, Essen, Germany.
Hickey, A., and Davis, A., 2003a, A tale of two ontologies: The basis for systems analysis technique selection, Americas Conf. on Info. Sys., Association for Information Systems, Atlanta.
Hickey, A., and Davis, A., 2003b, Elicitation technique selection: How do experts do it? 11th IEEE Int. Req. Eng. Conf., IEEE Computer Society, Los Alamitos, CA.
Hickey, A., and Davis, A., 2004, A Unified Model of Requirements Elicitation, J. of Mgmt Info. Sys. 20(4):65–84.
Hickey, A., Davis, A., and Kaiser, D., 2003, Requirements Elicitation Techniques: Analyzing the Gap Between Technology Availability and Technology Use, Comparative Tech. Transfer & Society 1(3):279–302.
Higgins, L., 2003, Principles of Marketing, www.principlesofmarketing.com.
Hoffer, J., George, J., and Valacich, J., 2002, Modern Systems Analysis and Design, 3rd ed., Prentice Hall, Upper Saddle River, NJ.
Hofmann, H., and Lehner, F., 2001, Requirements engineering as a success factor in software projects, IEEE Software 18(4):58–66.
Holsapple, C., and Joshi, K., 2002, A collaborative approach to ontology design, Comm. of the ACM 45(2):42–47
Juristo, N., and Moreno, A., 2001, Basics of Software Engineering Experimentation, Kluwer Academic, Boston.
Kishore, R., Sharman, R., and Ramesh, R., 2004a, Computational ontologies and information systems: I. Foundations, Comm. of the Assoc. for Info. Sys. 14:158–183.
Kishore, R., Sharman, R., and Ramesh, R., 2004b, Computational ontologies and information systems: II. Formal specification, Comm. of the Assoc. for Info. Sys. 14:184–205.
Kishore, R., Zhang, H., and Ramesh, R., 2004c, A helix-spindle model for ontological engineering, Comm. of the ACM 47(2):69–75.
Kotonya, G., and Sommerville, I., 1998, Requirements Engineering: Processes and Techniques, Wiley, Chichester, UK.
Lauesen, S., 2002, Software Requirements: Styles and Techniques, Addison-Wesley, Harlow, UK.
Leffingwell, D., and Widrig, D., 2000, Managing Software Requirements, Addison-Wesley, Reading, PA.
Liebowitz, J., 2001, Knowledge Management: Learning from Knowledge Engineering, CRC Press, Boca Raton, FL.
Macaulay, L., 1996, Requirements Engineering, Springer, London.
Maciaszek, L., 2001, Requirements Analysis and System Design, Addison-Wesley, Harlow, UK.
Maiden, N., and Rugg, G. 1996, ACRE: Selecting methods for requirements acquisition, Software Eng. J. 11(5):183–192.
Nunamaker, J., Dennis, A., Valacich, J., Vogel, D., and George, J., 1991, Electronic meeting systems to support group work, Comm. of the ACM 34(7):40–61.
Robertson, S., and Robertson, J., 1999, Mastering the Requirements Process, Addison-Wesley, Harlow, UK.
Romano, N., Nunamaker, J., Briggs, R., and Mittleman, D., 1999, Distributed GSS facilitation and participation: Field action research, 32nd Hawaii Int. Conf. on Sys. Sciences, IEEE Computer Society, Los Alamitos, CA.
Scharer, S., 1981, Pinpointing Requirements, Datamation (April):139–154.
Schewe, C., and Hiam, A., 1998, Portable MBA in Marketing, 2nd ed., Wiley, New York.
Standish Group, 1995, The Chaos Report, www.standishgroup.com.
Te’eni, D., Sagie, A., Schwartz, D., Zaidman, N., and Amichai, Y., 2001, The process of organizational communication: A model and field study, IEEE Trans. on Prof. Comm. 44(1):6–20.
Thayer, R., and Dorfman, M., 1994, Standards, Guidelines, and Examples on System and Software Requirements Engineering, IEEE Computer Society, Los Alamitos, CA.
Wiegers, K., 2003, Software Requirements, Microsoft, Redmond, WA.
Wood, J., and Silver, D., 1995, Joint Application Development, Wiley, New York.
Yeh, R., and Ng, P., 1990, Software requirements — A management perspective, in: Systems and Software Requirements Engineering, R. Thayer and M. Dorfman, eds., IEEE Computer Society, Los Alamitos, CA, pp. 450–461.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2007 Springer Science+Business Media, LLC
About this chapter
Cite this chapter
Hickey, A.M., Davis, A.M. (2007). An Ontological Approach to Requirements Elicitation Technique Selection. In: Sharman, R., Kishore, R., Ramesh, R. (eds) Ontologies. Integrated Series in Information Systems, vol 14. Springer, Boston, MA. https://doi.org/10.1007/978-0-387-37022-4_14
Download citation
DOI: https://doi.org/10.1007/978-0-387-37022-4_14
Publisher Name: Springer, Boston, MA
Print ISBN: 978-0-387-37019-4
Online ISBN: 978-0-387-37022-4
eBook Packages: Computer ScienceComputer Science (R0)