The influence of analyst communication in IS projects

Journal of the Association for Information Systems

Volumn 14, Issue 9, 2013, Pages 482-520

  Shuraida, Shadi ^a   Barki, Henri ^b  

^a CITY UNIVERSITY OF NEW YORK   (United States)

^b HEC MONTRÉAL   (Canada)

Author keywords

Case Study; IS Analyst Learning; IS Development; IS Implementation; IS Project; User Analyst Communication

Indexed keywords

CONCRETE TESTING; INFORMATION USE; PROJECT MANAGEMENT;

CASE-STUDIES; COMMUNICATIONS ACTIVITIES; INFORMATION SYSTEM ANALYST LEARNING; INFORMATION SYSTEM DEVELOPMENT; INFORMATION SYSTEM PROJECTS; INFORMATION SYSTEMS IMPLEMENTATION; PROJECT OUTCOMES; SYSTEMS ANALYSTS; USER NEED; USER-ANALYST COMMUNICATION;

INFORMATION SYSTEMS;

EID: 84885629719     PISSN: 15583457     EISSN: 15369323     Source Type: Journal    
DOI: 10.17705/1jais.00343     Document Type: Article

References (179)

1. Agarwal, R., & Tanniru, M. R. (1990). Knowledge acquisition using structured interviewing: An empirical investigation. Journal of Management Information Systems, 7(1), 123-140.
2. Agarwal, R., De, P., & Sinha, A. P. (1999). Comprehending object and process models: An empirical study. IEEE Transactions on Software Engineering, 25(4), 541-556.
3. Al-Salem, L. S., & A. Samaha (2007). Eliciting web application requirements-an industrial case study. The Journal of Systems and Software, 80(3), 294-294.
4. Andreou, A. S. (2003). Promoting software quality through a human, social and organisational requirements elicitation process. Requirements Engineering, 8, 85-101.
5. Appan, R., & Browne, G. J. (2010). Investigating retrieval-induced forgetting during information requirements determination. Journal of the Association for Information Systems, 11(5), 250-275.
6. Argyris, C. (1976). Single-loop and double-loop models in research on decision making. Administrative Science Quarterly, 21(3), 363-375.
7. Argyris, C. (2002). Double-loop learning, teaching, and research. Academy of Management Learning and Education, 1(2), 206-218.
8. Argyris, C., & Schon, D. A. (1974). Theory in practice: Increasing professional effectiveness. San Francisco, CA: Jossey-Bass Inc.
9. Argyris, C., & Schon, D. A. (1978). Organizational learning: A theory of action perspective. Reading, MA: Addison Wesley.
10. Argyris, C., & Schon, D. A. (1996). Organizational learning II. Reading, MA: Addison Wesley.
11. Argyris, C., Putnam, R., & McLain Smith, D. (1985). Action science: Concepts, methods, and skills for research and intervention. San Fransisco, California: Jossey Bass.
12. Arthur, J. D., & Gröner, M. K. (2005). An operational model for structuring the requirements generation process. Requirements Engineering Journal, 10(1), 45-62.
13. Arthur, J. B., & Aiman-Smith, L. (2001). Gainsharing and organizational learning: An analysis of employee suggestions over time. The Academy of Management Journal, 44(4), 737-754.
14. Athanassopoulou, P., & Johne, A. (2004). Effective communication with lead customers in developing new banking products. The International Journal of Bank Marketing, 22(2/3), 100-125.
15. Baker, W. E., & Sinkula, J. M. (1999). The synergistic effect of market orientation and learning orientation on organizational performance. Journal of the Academy of Marketing Science, 27(4), 411-427.
16. Baker, W. E., & Sinkula, J. M. (2002). Market orientation, learning orientation and product innovation: Delving into the organization's black box. Journal of Market-Focused Management, 5, 5-23.
17. Banker, R. D., & Kauffman, R. J. (2004). The evolution of research on information systems: A fiftieth-year survey of the literature in management science. Management Science, 50(3), 281-298.
18. Barki, H., Rivard, S., & Talbot, J. (1993). Toward an assessment of software development risk. Journal of Management Information Systems, 10(2), 203-225.
19. Baskerville, R., Levine, L., & Pries-Heje, J. (2006). High-speed software development practices: What works, what doesn't. IT Professional Magazine, 8(4), 29-36.
20. Beath, C. M., & Orlikowski, W. J. (1994). The contradictory structure of systems development methodologies: Deconstructing the IS-user relationship in information engineering. Information Systems Research, 5(4), 350-377.
21. Beecham, S., Hall, T., & Austen, R. (2005). Defining a requirements process improvement model. Software Quality Journal, 13(3), 247-279.
22. Berlo, D. K. (1960). Process of communication: An introduction to theory and practice. New York: Holt, Rinehart and Winston.
23. Boland Jr., R.J. (1978). The process and product of system design. Management Science, 24(9), 887-898.
24. Boland Jr., R. J., & Tenkasi, R.V. (1995). Perspective making and perspective taking in communities of knowing. Organization Science, 6(4), 350-372.
25. Bolman, L. G., & Deal, T. E. (2008). Reframing organizations: Artistry, choice, and leadership (4th Ed.). San Fransisco, CA: Jossey-Bass.
26. Bostrom, R. P. (1989). Successful application of communication techniques to improve the systems development process. Information and Management, 16, 279-295.
27. Breitman, K. K., Leite, J. C. S. d. P., & Berry, D. M. (2005). Supporting scenario evolution. Requirements Engineering Journal, 10(2), 112-131.
28. Browne, G.J., & Rogich, M. B. (2001). An empirical investigation of user requirements elicitation: Comparing the effectiveness of prompting techniques. Journal of Management Information Systems, 17(4), 223-249.
29. Browne, G. J., & Ramesh, V. (2002). Improving information requirements determination: A cognitive perspective. Information and Management, 39, 625-645.
30. Bryant, J. (1997). Requirements capture using SODA. European Journal of Information Systems, 6(3), 155-163.
31. Butler, T., & Fitzgerald, B. (2001). The relationship between user participation and the management of change surrounding the development of information systems: A European perspective. Journal of Organizational and End User Computing, 13(1), 12-25.
32. Byrd, T.A., Cossick, K. L., & Zmud, R. W. (1992). A synthesis of research on requirements analysis and knowledge acquisition techniques. MIS Quarterly, 16(1), 117-138.
33. Carte, T. A., & Russell, C. J. (2003). In pursuit of moderation: Nine common errors and their solutions1. MIS Quarterly, 27(3), 479-501.
34. Chakraborty, S., Sarker, S., & Sarker, S. (2010). An exploration into the process of requirements elicitation: A grounded approach. Journal of the AIS, 11(4), 212-249.
35. Choudhury, V., & Karahanna, E. (2008). The relative advantage of electronic channels: A multidimensional view. MIS Quarterly, 32(1), 179-200.
36. Churchman, C., & Schainblatt, A. (1965). The researcher and manager: A dialectic of implementation. Management Science, 11(4), B69-B87.
37. Cleland-Huang, J., Dumitru, H., Duan, C., & Castro-Herrera, C. (2009). Automated support for managing feature requests in open forums. Communications of the ACM,52(10), 68-74.
38. 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.
39. Damas, C., Lambeau, B., Dupont, P., & van Lamsweerde, A. (2005). Generating annotated behavior models from end-user scenarios. IEEE Transactions on Software Engineering, 31(12), 1056-1073.
40. Darke, P., & Shanks, G. (1997). User viewpoint modeling: Understanding and representing user viewpoints during requirements definition. Information Systems Journal, 7(3), 213-239.
41. Davis, C. J., Fuller, R. M., & Berndt, D. J. (2006). Communication challenges in requirements elicitation and the use of the repertory grid technique. The Journal of Computer Information Systems, 46(5), 78-86.
42. Davis, G. (1982). Strategies for information requirements determination. IBM Systems Journal, 21(1), 4-31.
43. Day, J. (2007). Strangers on the train. Information Technology & People, 20(1), 6-31.
44. Decker, B., Ras, E., Rech, J., Jaubert, P., & Rieth, M. (2007). Wiki-based stakeholder participation in requirements engineering. IEEE Software, 24(2), 28-35.
45. Dieste, O., Juristo, N., & Shull, F. (2008). Understanding the customer: What do we know about requirements elicitation? IEEE Software, 25(2), 11-13.
46. Dishaw, M., & Strong, D. M. (1999). Extending the technology acceptance model with task-technology fit constructs. Information and Management, 36, 9-21.
47. Dubé, L., & Paré, G. (2003). Rigor in information systems positivist research: Current practices, trends, and recommendations. MIS Quarterly, 27(4), 597-635.
48. Duggan, E. W. (2003). Generating systems requirements with facilitated group techniques. Human-Computer Interaction, 18(4), 373-394.
49. Duggan, E. W., & Thachenkary, C. S. (2003). Higher quality requirements: Supporting joint application development with the nominal group technique. Information Technology and Management, 4(4), 391-408.
50. Duggan, E. W., & Thachenkary, C. S. (2004). Supporting the JAD facilitator with the nominal group technique. Journal of Organizational and End User Computing, 16(2), 1-19.
51. Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383.
52. Edstrom, A. (1977). User influence and the success of MIS projects: A contingency approach. Human Relations, 30(7), 589-607.
53. Eisenhardt, K. (1989). Building theories from case study research. Academy of Management, 14(4), 532-550.
54. Eisenhardt, K.M., & Graebner, M. E. (2007). Theory building from cases: Opportunities and challenges. Academy of Management Journal, 50(1), 25-32.
55. Farooq, U., Ganoe, C. H., Carroll, J. M., Councill, I. G., & Giles, C. L. (2008). Design and evaluation of awareness mechanisms in Citeseer. Information Processing & Management, 44(2), 596.
56. Frolick, M. N., & Robichaux, B. P. (1995). EIS information requirements determination-using a group support system to enhance the strategic business objectives method. Decision Support Systems, 14(2), 157-170.
57. Galliers, R. D., & Swan, J. A. (1997). Against structured approaches: Information requirements analysis as a socially mediated process. In Proceedings of The Thirtieth Annual Hawwaii International Conference on System Sciences, IEEE Computer Society, Hawwaii.
58. Gallivan, M. J., & Keil, M. (2003). The user-developer communication process: A critical case study. Information Systems Journal, 13(1), 37-68.
59. Garceau, L. R., Jancura, E. G., & Kneiss, J. (1993). Object-oriented analysis and design: A new approach to systems development. Journal of Systems Management, 44(1), 25-25.
60. García-Duque, J., López-Nores, M., Pazos-Arias, J. J., Fernández-Vilas, A., Diaz-Redondo, R. P., Gil-Solla, A., Ramos-Cabrer, M., & Blanco-Fernandez, Y. (2006). Guidelines for the incremental identification of aspects in requirements specifications. Requirements Engineering Journal, 11(4), 239-263.
61. Gemino, A., & Parker, D. (2009). Use case diagrams in support of use case modeling: Deriving understanding from the picture. Journal of Database Management, 20(1), 1-24.
62. Gill, T. G. (1995). High-tech hidebound: Case studies of information technologies that inhibited organizational learning. Accounting, Management, and Information Technology, 5(1), 41-60.
63. Glass, R. L. (2008). Divided by a common language: The story of requirements triage. Information Systems Management, 25(2), 190.
64. Goodhue, D. L., & Thompson, R. L. (1995). Task-technology fit and individual performance. MIS Quarterly, 19(2), 213-236.
65. Guimaraes, T., Staples, D. S., & McKeen, J. D. (2003). Empirically testing some main user-related factors for systems development quality. The Quality Management Journal, 10(4), 39-54.
66. Habermas, J. (1984). The theory of communicative action (T. McCarthy, Trans., Vol. 1). Boston, Massachusetts: Beacon Press.
67. Habermas, J. (1987). The theory of communicative action. (T. McCarthy, Trans.). Volume 2: Lifeworld and system, a critique of functionalist reason. Boston, Massachusetts: Beacon Press.
68. Hagström, L., Ritzen, S., & Johansson, J. (2006). The use and implementation of CAD in the Swedish furniture industry. Forest Products Journal, 56(1), 73-81.
69. Haley, C., Laney, R., Moffett, J., & Nuseibeh, B. (2008). Security requirements engineering: A framework for representation and analysis. IEEE Transactions on Software Engineering, 34(1), 133-153.
70. Hansen, M. (1999). The search-transfer problem: The role of weak ties in sharing knowledge across organization subunits. Administrative Science Quarterly, 44(1), 82-111.
71. Hartwick, J., & Barki, H. (1994). Explaining the role of user participation in information system use. Management Science, 40(4), 440-465.
72. Hartwick, J., & Barki, H. (2001). Communication as a dimension of user participation. IEEE Transactions on Professional Communication, 44(1), 21-36.
73. Haumer, P., Pohl, K., & Weidenhaupt, K. (1998). Requirements elicitation and validation with real world scenes. IEEE Transactions on Software Engineering, 24(12), 1036-1054.
74. Hevner, A. R., & Mills. H. D. (1995). Box-structured requirements determination methods. Decision Support Systems, 13(3-4), 223-239.
75. Hickey, A. M., & Davis, A. M. (2004). A unified model of requirements elicitation. Journal of Management Information Systems, 20(4), 65-65-84.
76. Hirschheim, R., & Klein, H. K. (1989). Four paradigms of information systems development. Communications of the ACM, 32(10), 1199-1216.
77. Hong, D., Chiu, D. K. W., Shen, V. Y., Cheung, S. C., & Kafeza, E. (2007). Ubiquitous enterprise service adaptations based on contextual user behavior. Information Systems Frontiers, 9(4), 343-358.
78. Hostick, C. J., Billo, R. E., & Rucker, R. H. (1991). Making the most of structured analysis in manufacturing information system design: Application of icons and cycle-time. Computers in Industry, 16(3), 267-267.
79. Huber, G. P. (1991). Organizational learning: The contributing processes and the literatures. Organization Science, 2(1), 88-115.
80. Jarke, M., Bui, X. T., & Carroll, J. M. (1998). Scenario management: An interdisciplinary approach. Requirements Engineering Journal, 3(3-4), 155-173.
81. Jirotka, M., & Luff, P. (2006). Supporting requirements with video-based analysis. IEEE Software, 23(3), 42-44.
82. Jones, R. M., Candy, L., & Edmonds, E. A. (1993). Knowledge-based system requirements. Knowledge-Based Systems, 6(1), 31-37.
83. Joshi, K. D., Sarker, S., & Sarker, S. (2007). Knowledge transfer within information systems development teams: Examining the role of knowledge source attributes. Decision Support Systems, 43(2), 322-335.
84. Jwo, J.-S., & Cheng, Y. C. (2010). Pseudo software: A mediating instrument for modeling software requirements. The Journal of Systems and Software, 83(4), 599.
85. Kaiser, K., & Srinivasan, A. (1982). User-analyst differences: An empirical investigation of attitudes related to systems development. Academy of Management Journal, 25(3), 630-630.
86. Kaiya, H., Shinbara, D., Kawano, J., & Motoshi, S. (2005). Improving the detection of requirements discordances among stakeholders. Requirements Engineering Journal, 10(4), 289-303.
87. Kazman, R., & Hong-Mei, C. (2005). From requirements negotiation to software architecture decisions. Information and Software Technology, 47(8), 511-520.
88. Keil, M., & Carmel, E. (1995). Customer-developer links in software development. Communications of the ACM, 38(5), 33-44.
89. Kensing, F., & Munk-Madsen, A. (1993). PD: Structure in the toolbox. Communications of the ACM, 36(6), 78-78.
90. Kim, J., Kim, J., Park, S., & Sugumaran, V. (2004). A multi-view approach for requirements analysis using goal and scenario. Industrial Management + Data Systems, 104(8/9), 702-711.
91. Kirsch, L. J., & Beath, C. M. (1996). The enactments and consequences of token, shared, and compliant participation in information systems development. Accounting, Management and Information Technologies, 6(4), 221-254.
92. Ko, D.G., Kirsch, L. J., & King, W. R. (2005). Antecedents of knowledge transfer from consultants to clients in enterprise system implementations. MIS Quarterly, 29(1), 59-85
93. Kraut, R. E., & Streeter, L. A. (1995). Coordination in software development. Communications of the ACM, 38(3), 69-81.
94. Kujala, S. (2003). User involvement: A review of the benefits and challenges. Behaviour & Information Technology, 22(1), 1-16.
95. Kwan, I., Schroter, A., & Damian, D. (2011). Does socio-technical congruence have an effect on software build success? A study of coordination in a software project. IEEE Transactions on Software Engineering, 37(3), 307-324.
96. Laporti, V., Borges, M. R. S., & Braganholo, V. (2009). Athena: A collaborative approach to requirements elicitation. Computers in Industry, 60(6), 367-380.
97. Lee, A. S. (1989). A scientific methodology for MIS case studies. MIS Quarterly, 13(1), 33-50.
98. Lee, W. J., Cha, S. D., & Kwon, Y. R. (1998). Integration and analysis of use cases using modular petri nets in requirements engineering. IEEE Transactions on Software Engineering, 24(12), 1115-1130.
99. Leifera, R., Leeb, S., & Durgeea, J. (1994). Deep structures: Real information requirements determination. Information & Management, 27(5), 275-285.
100. Leite, J., & Freeman, P. A. (1991). Requirements validation through viewpoint resolution. IEEE Transactions on Software Engineering, 17(12), 1253-1269.
101. Levina, N., & Vaast, E. (2008). Innovating or doing as told? Status differences and overlapping boundaries in offshore collaboration. MIS Quarterly, 32(2), 307-332.
102. Lichter, H., Schneider-Hufschmidt, M., & Zullighoven, H. (1994). Prototyping in industrial software projects-bridging the gap between theory and practice. IEEE Transactions on Software Engineering, 20(11), 825-832.
103. Liker, J., Fleischer, M., Nagamachi, M., & Zonnevylle, M. (1992). Designers and their machines: CAD use and support in the US and Japan. Communications of the ACM, 35(2), 77-95.
104. Lind, M. R., & Zmud, R. W. (1991). The influence of a convergence in understanding between technology providers and users on information technology innovativeness. Organization Science, 2(2), 195-217.
105. Lussier, S. (2004). New tricks: How open source changed the way my team works. IEEE Software, 21(1), 68-72.
106. Maiden, N. A. M., & Hare, M. (1998). Problem domain categories in requirements engineering. International Journal of Human-Computer Studies, 49(3), 281-304.
107. Majchrzak, A., Beath, C. M., & Lim, R. A. (2005). Managing client dialogues during information systems design to facilitate client learning. MIS Quarterly, 29(4), 653-672.
108. Marakas, G. M., & Elam, J. J. (1998). Semantic structuring in analyst acquisition and representation of facts in requirements analysis. Information Systems Research, 9(1), 37-63.
109. Markus, M. L. (2004). Technochange management: Using IT to drive organizational change. Journal of Information Technology, 19, 4-20.
110. Markus, M. L., & Mao, J.-Y. (2004). Participation in development and implementation-updating an old, tired concept for today's IS contexts. Journal of the AIS, 5(11/12), 514-544.
111. Markus, M. L., & Benjamin, R. I. (1996). Change agentry-the next IS frontier. MIS Quarterly, 20(4), 385-407.
112. Martin, M. P. (1995). The case against CASE. Journal of Systems Management, 46(1), 54-54.
113. Mathiassen, L., Saarinen, T., Tuunanen, T., & Rossi, M. (2007). A contingency model for requirements development. Journal of the AIS, 8(11), 569-597.
114. McKeen, J. D., & Guimaraes, T. (1997). Successful strategies for user participation in systems development. Journal of Management Information Systems, 14(2), 133-150.
115. McKeen, J. D., Guimaraes, T., & Wetherbe, J. C. (1994). The relationship between user participation and user satisfaction. MIS Quarterly, 18(4), 427-427.
116. Moody, D. (2009). The "physics" of notations: Toward a scientific basis for constructing visual notations in software engineering. IEEE Transactions on Software Engineering, 35(6), 756-779.
117. Moody, J. W., Blanton, J. E., & Cheney, P. H. (1998). A theoretically grounded approach to assist memory recall during information requirements determination. Journal of Management Information Systems, 15(1), 79-98.
118. Moynihan, T. (1996). An experimental comparison of object-orientation and functional-decomposition as paradigms for communicating system functionality to users. The Journal of Systems and Software, 33(2), 163-163.
119. Neill, C. J., & Laplante, P. A. (2003). Requirements engineering: The state of the practice. IEEE Software, 20(6), 40-45.
120. Nelson, K. M., & Cooprider, J. G. (1996). The contribution of shared knowledge to IS group performance. MIS Quarterly, 20(4), 409-432.
121. Nelson, R. (2007). IT project management: Infamous failures, classic mistakes, and best practices. MISQ Exec, 6(2), 67-78.
122. Newman, M., & Noble, F. (1990). User involvement as an interaction process: A case study. Information Systems Research, 1(1), 89-113.
123. Nichols, M. L. (1981). A behavioral analysis for planning MIS implementation. MIS Quarterly, 5(1), 57-66.
124. Nordberg Iii, M. E. (2003). Managing code ownership. IEEE Software, 20(2), 26-33.
125. Nuseibeh, B., Kramer, J., & Finkelstein, A. (1994). A framework for expressing the relationships between multiple views in requirements specification. IEEE Transactions Software Engineering, 20(10), 760-773.
126. Orlikowski, W. J., & Gash, D. C. (1994). Technological frames: Making sense of information technology in organizations. ACM Transactions on Information Systems, 12(2), 174-207.
127. Pai, J.-C., & Yeh, C.-H. (2008). Factors affecting the implementation of e-business strategies: An empirical study in Taiwan. Management Decision, 46(5), 681-690.
128. Patnayakuni, R., Ruppel, C., & Rai, A. (2006). Managing the complementarity of knowledge integration and process formalization for systems development performance. Journal of the AIS, 7(1), 545-567.
129. Patton, M. Q. (2002). Qualitative research and evaluation methods (3rd Ed.). Thousand Oaks, CA: Sage Publications.
130. Pitts, M.G., & Browne, G. J. (2004). Stopping behavior of systems analysts during information requirements elicitation. Journal of Management Information Systems, 21(1), 203-226.
131. Pitts, M. G., & Browne, G. J. (2007). Improving requirements elicitation: An empirical investigation of procedural prompts. Information Systems Journal, 17, 89-110.
132. Potts, C., Takahashi, K., & Antón, A. I. (1994). Inquiry-based requirements analysis. IEEE Software, 11(2), 21-32.
133. Qurban, M. H., & Austria, R. D. (2009). Improving the communication skills of is developers during requirements elicitation using experiential learning. Journal of Information Systems Education, 20(3), 301-311.
134. Ramos, I., Berry, D. M., & Carvalho, J. A. (2005). Requirements engineering for organizational transformation. Information and Software Technology, 47(7), 479-495.
135. Ravid, A., & Berry, D. M. (2000). A method for extracting and stating software requirements that a user interface prototype contains. Requirements Engineering Journal, 5(4), 225-241.
136. Rexfelt, O. (2009). Consumer acceptance of product-service systems. Journal of Manufacturing Technology Management, 20(5), 674-699.
137. Robertson, S., & Robertson, J. (2006). Mastering the requirements process. Upper Saddle River, NJ: Addison-Wesley.
138. Saiedian, H., Kumarakulasingam, P., & Anan, M. (2005). Scenario-based requirements analysis techniques for real-time software systems: A comparative evaluation. Requirements Engineering Journal, 10(1), 22-33.
139. Salaway, G. (1987). An organizational learning approach to information systems development. MIS Quarterly, 11(2), 245-264.
140. Saleem, N., Jones, D. R., & Moses, B. (2006). Forming design teams to develop healthcare information systems. Hospital Topics, 84(1), 22-30.
141. Sardinha, J., Choren, R., da Silva, V., Milidiú, R. & de Lucena, C. (2006). A combined specification language and development framework for agent-based application engineering. The Journal of Systems and Software, 79(11), 1565-1577.
142. Sawyer, S., & Guinan, P. J. (1998). Software development: Processes and performance. IBM Systems Journal, 37(4), 552-569.
143. Shen, V. (1989). Faults, failures, and a metrics revolution. IEEE Software,6(2), 85, 91.
144. Shin, J. E., Sutcliffe, A. G., & Gregoriades, A. (2005). Scenario advisor tool for requirements engineering. Requirements Engineering Journal, 10(2), 132-145.
145. Shirani, A. I. (2006). Sampling and pooling of decision-relevant information: Comparing the efficiency of face-to-face and GSS supported groups. Information & Management, 43(4), 521-529.
146. Siau, K., & Tan, X. (2006). Using cognitive mapping techniques to supplement UML and up in information requirements determination. The Journal of Computer Information Systems, 46(5), 59-66.
147. Siau, K., & Tan, X. (2008). Use of cognitive mapping techniques in information systems development. The Journal of Computer Information Systems, 48(4), 49-49-57.
148. Sinkula, J. M., Baker, W. E., & Noordewier, T. (1997). A framework for market-based organizational learning: Linking values, knowledge, and behavior. Journal of the Academy of Marketing Science, 25(4), 305-318.
149. Soh, C., Kien, S., & Tay-Yap, J. (2000). Enterprise resource planning: Cultural fits and misfits: Is ERP a universal solution? Communications of the ACM, 43(4), 47-51.
150. Some, S. S. (2006). Supporting use case based requirements engineering. Information and Software Technology, 48(1), 43-58.
151. Spinellis, D. (2009). Start with the most difficult part. IEEE Software, 26(2), 70-70-71.
152. Stallinger, F., & Grunbacher, P. (2001). System dynamics modelling and simulation of collaborative requirements engineering. Journal of Systems and Software, 59(3), 311-321.
153. Standish Group. (2009). CHAOS reports on IT project failures. Retreived February 12, 2010, from http://www1.standishgroup.com/newsroom/chaos_2009.php
154. Stein, E. W., & Vandenbosch, B. (1996). Organizational learning during advanced system development: Opportunities and obstacles. Journal of Management Information Systems, 13(2), 115-136.
155. Stingel, J. D., & Componation, P. J. (2006). The utilization of modeling and simulation as a supply chain management tool for a recapitalization program. Engineering Management Journal, 18(2), 44-50.
156. Stobart, S. C., Thompson, J. B., & Smith, P. (1991). Use, problems, benefits and future direction of computer-aided software engineering in united kingdom. Information and Software Technology, 33(9), 629-629.
157. Sustar, H., Pfeil, U., & Zaphiris, P. (2008). Requirements elicitation with and for older adults. IEEE Software, 25(3), 16-17.
158. Szajna, B., & Scamell, R. W. (1993). The effects of information system user expectations on their performance and perceptions. MIS Quarterly, 17(4), 493-493.
159. Telem, M. (1988). Information requirements specification I: Brainstorming a collective decision-making approach. Information Processing & Management, 24(5), 549-557.
160. Thew, S., Sutcliffe, A., Procter, R., de Bruijn, O., McNaught, J., Venters, C. C., & Buchan, I. (2009). Requirements engineering for e-science: Experiences in epidemiology. IEEE Software, 26(1), 80-87.
161. Topi, H., & Ramesh, V. (2002). Human factors research on data modeling: A review of prior research, an extended framework and future research directions. Journal of Database Management, 13(2), 3-19.
162. Toth, K. (2006). Experiences with open source software engineering tools. IEEE Software, 23(6), 44-52.
163. Tucker, A. L., Edmondson, A. C., & Spear, S. (2002). When problem solving prevents organizational learning. Journal of Organizational Change Management, 15(2), 122-137.
164. Ullah, A., & Lai, R. (2011). Modeling business goal for business/IT alignment using requirements engineering. The Journal of Computer Information Systems, 51(3), 21-28.
165. van Lamsweerde, A., & Letier, E. (2000). Handling obstacles in goal-oriented requirements engineering. IEEE Transactions on Software Engineering, 26(10), 978-1005.
166. Vessey, I., & Sravanapudi, A. P. (1995). CASE tools as collaborative support technologies. Communications of the ACM, 38(1), 83-83.
167. Viega, J., Kohno, T., & Potter, B. (2001). Trust (and mistrust) in secure applications. Communications of the ACM, 44(2), 31-36.
168. Vitalari, N. P. (1985). Knowledge as a basis for expertise in systems analysis: An empirical study. MIS Quarterly, 9(3), 221-241.
169. Vitalari, N. P., & Dickson, G. W. (1983). Problem solving for effective systems analysis: An experimental exploration. Communications of the ACM, 26(11), 948-956.
170. Walz, D. B., Elam, J.J., & Curtis, B. (1993). Inside a software design team: Knowledge acquisition, sharing, and integration. Communications of the ACM, 36(10), 63-77.
171. Watson, H. J., & Frolick, M. N. (1993). Determining information requirements for an EIS. MIS Quarterly, 17(3), 255-269.
172. Weick, K. E., & Ashford, S. J. (2001). Learning in organizations. In F. M. Jablin and L. L. Putnam, The new handbook of organizational communication: Advances in theory, research, and methods (pp. 704-731). Thousand Oaks, CA: Sage.
173. Wetherbe, J. C. (1991). Executive information requirements-getting it right. MIS Quarterly, 15(1), 51-65.
174. Wolf, T., Schroter, A., Damian, D., Panjer, L. D., & Nguyen, T. H. D. (2009). Mining task-based social networks to explore collaboration in software teams. IEEE Software, 26(1), 58-66.
175. Wu, I.-L., & Hung, C.-Y. (2009). A strategy-based process for effectively determining system requirements in ecrm development. Information and Software Technology, 51(9), 1308-1318.
176. Wu, I.-L., & Shen, Y.-C. (2006). A model for exploring the impact of purchasing strategies on user requirements determination of E-SRM. Information and Management, 43(4), 411-422.
177. Yan, W., Chen, C.-H., & Khoo, L. P. (2005). Creams: A customer requirements elicitation and management system for product conceptualization. International Journal of Product Development, 2(4), 303-320.
178. Yin, R. (2003). Case study research: Design and methods (3rd Ed.). Thousand Oaks, California: Sage Publications.
179. Zimmermann, T., Premraj, R., Bettenburg, N., Just, S., Schroter, A., & Weiss, C. (2010). What makes a good bug report? IEEE Transactions on Software Engineering, 36(5), 618-643.