The role of domain knowledge in requirements elicitation via interviews: an exploratory study
暂无分享,去创建一个
[1] Mark Lycett,et al. Communication issues in requirements elicitation: a content analysis of stakeholder experiences , 2003, Inf. Softw. Technol..
[2] Jennifer Wiley,et al. Effects of working memory capacity on mental set due to domain knowledge , 2007, Memory & cognition.
[3] Bashar Nuseibeh,et al. Requirements engineering: a roadmap , 2000, ICSE '00.
[4] Marianne LaFrance,et al. The Knowledge Acquisition Grid: A Method for Training Knowledge Engineers , 1987, Int. J. Man Mach. Stud..
[5] Daniel M. Berry. The importance of ignorance in requirements engineering: An earlier sighting and a revisitation , 2002, J. Syst. Softw..
[6] Glenn J. Browne,et al. An Empirical Investigation of User Requirements Elicitation: Comparing the Effectiveness of Prompting Techniques , 2001, J. Manag. Inf. Syst..
[7] Jeffrey Parsons,et al. An Experimental Evaluation of Property Precedence in Conceptual Modelling , 2004, APCCM.
[8] David A. Cook,et al. Experiences in the Adoption of Requirements Engineering Technologies , 1998 .
[9] Natalia Juristo Juzgado,et al. Effectiveness of Requirements Elicitation Techniques: Empirical Results Derived from a Systematic Review , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).
[10] George J. Spilich,et al. Acquisition of domain-related information in relation to high and low domain knowledge. , 1979 .
[11] A. Strauss. Basics Of Qualitative Research , 1992 .
[12] Venkataraman Ramesh,et al. Improving information requirements determination: a cognitive perspective , 2002, Inf. Manag..
[13] Ron Weber,et al. AIS Electronic Library (AISeL) , 2022 .
[14] Annie I. Antón,et al. The use of goals to surface requirements for evolving systems , 1998, Proceedings of the 20th International Conference on Software Engineering.
[15] Raymonde Guindon,et al. Knowledge Exploited by Experts during Software System Design , 1990, Int. J. Man Mach. Stud..
[16] Hugh J. Watson,et al. Determining Information Requirements for an EIS , 1993, MIS Q..
[17] Franz Lehner,et al. Requirements Engineering as a Success Factor in Software Projects , 2001, IEEE Softw..
[18] N. Hoffart. Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory , 2000 .
[19] Ritu Agarwal,et al. Knowledge Acquisition Using Structured Interviewing: An Empirical Investigation , 1990, J. Manag. Inf. Syst..
[20] Robert P. Bostrom,et al. Development of computer-based information systems: a communication perspective , 1984, CPRS.
[21] Barry Shore. Managing End-User Challenges , 1998, Inf. Syst. Manag..
[22] LeMai Nguyen,et al. Supporting and monitoring the creativity of IS personnel during the requirements engineering process , 2000, Proceedings of the 33rd Annual Hawaii International Conference on System Sciences.
[23] Nicholas P. Vitalari,et al. Differences Between Novice and Expert Systems Analysts: What Do We Know and What Do We Do? , 1998, J. Manag. Inf. Syst..
[24] Alan M. Davis,et al. A Unified Model of Requirements Elicitation , 2004, J. Manag. Inf. Syst..
[25] Neil A. M. Maiden,et al. ACRE: selecting methods for requirements acquisition , 1996, Softw. Eng. J..
[26] J. Davis,et al. Determining a Project's Probability of Success , 2001 .
[27] John A. van der Poll,et al. Towards a Methodology to Elicit Tacit Domain Knowledge from Users , 2007 .
[28] Daniel M. Berry,et al. Formal Methods: The Very Idea Some Thoughts About Why They Work When They Work , 1998, Monterey Workshop.
[29] Iris Vessey,et al. Association for Information Systems Year Information Search Process for a Well-Structured IS Problem : The Role of IS and Application Domain Knowledge , 2008 .
[30] Iris Vessey,et al. Research Report - The Relevance of Application Domain Knowledge: The Case of Computer Program Comprehension , 1995, Inf. Syst. Res..
[31] Izak Benbasat,et al. The Relative Importance of Structural Constraints and Surface Semantics in Information Modeling , 1997, Inf. Syst..
[32] Bill Curtis,et al. A field study of the software design process for large systems , 1988, CACM.
[33] J. Wiley. Expertise as mental set: The effects of domain knowledge in creative problem solving , 1998, Memory & cognition.
[34] Shari Lawrence Pfleeger,et al. Preliminary Guidelines for Empirical Research in Software Engineering , 2002, IEEE Trans. Software Eng..
[35] Venkataraman Ramesh,et al. Understanding Conceptual Schemas: Exploring the Role of Application and IS Domain Knowledge , 2006, Inf. Syst. Res..
[36] Iris Vessey,et al. Learning to Specify Information Requirements: The Relationship between Application and Methodology , 1993, J. Manag. Inf. Syst..
[37] Paul H. Cheney,et al. A Theoretically Grounded Approach to Assist Memory Recall During Information Requirements Determination , 1998, J. Manag. Inf. Syst..
[38] Pamela Jordan. Basics of qualitative research: Grounded theory procedures and techniques , 1994 .
[39] Daniel M. Berry,et al. The importance of ignorance in requirements engineering , 1995, J. Syst. Softw..
[40] Gordon B. Davis,et al. Strategies for Information Requirements Determination , 1982, IBM Syst. J..
[41] Brian A. Malloy,et al. AN APPROACH TO AUTOMATE REQUIREMENTS ELICITATION AND SPECIFICATION , 2003 .
[42] Robert D. Macredie,et al. Effective Communication in Requirements Elicitation: A Comparison of Methodologies , 2002, Requirements Engineering.
[43] Bruce Blum,et al. A paradigm for the 1990s validated in the 1980s , 1989 .
[44] A. Glenberg,et al. Inexpert calibration of comprehension , 1987, Memory & cognition.
[45] Glenn J. Browne,et al. Improving requirements elicitation: an empirical investigation of procedural prompts , 2007, Inf. Syst. J..
[46] Ron Weber,et al. Understanding relationships with attributes in entity-relationship diagrams , 1999, ICIS.
[47] Claes Wohlin,et al. Using students as subjects - an empirical evaluation , 2008, ESEM '08.
[48] Iris Vessey,et al. The Relevance of Application Domain Knowledge: Characterizing the Computer Program Comprehension Process , 1998, J. Manag. Inf. Syst..
[49] Luisa Mich,et al. Applying a pragmatics-based creativity-fostering technique to requirements elicitation , 2005, Requirements Engineering.
[50] Glenn J. Browne,et al. Stopping Behavior of Systems Analysts During Information Requirements Elicitation , 2004, J. Manag. Inf. Syst..