A contingency model for requirements development

Journal of the Association for Information Systems

Volumn 8, Issue 11, 2007, Pages 569-597

  Mathiassen, Lars ^a   Saarinen, Timo ^b   Tuunanen, Tuure ^c   Rossi, Matti ^b  

^a GEORGIA STATE UNIVERSITY   (United States)

^b HELSINKI SCHOOL OF ECONOMICS   (Finland)

^c UNIVERSITY OF AUCKLAND   (New Zealand)

Author keywords

Contingency theory; Requirements development; Risk management

Indexed keywords

SOFTWARE DESIGN;

CONTINGENCY MODELS; CONTINGENCY THEORY; DEVELOPMENT PROGRAMMES; DEVELOPMENT RISK; DEVELOPMENT TECHNIQUE; JOURNAL ARTICLES; REQUIREMENT DEVELOPMENT; RISK PROFILE; RISK RESOLUTION; RISKS MANAGEMENT;

RISK MANAGEMENT;

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

References (159)

1. Alter, S. and M. Ginzberg (1978) "Managing uncertainty in MIS implementation," Sloan Management Review (20) 1, pp. 23-31.
2. Andrea, H. P. and R. W. Zmud (2002) "A Contingency Approach to Software Project Coordination," Journal of Management Information Systems (18) 3, pp. 41-70.
3. Andreou, A. S. (2003) "Promoting software quality through a human, social and organisational requirements elicitation process," Requirements Engineering Journal (8) 2, pp. 85-101.
4. Antón, A. I., R. A. Carter, A. Dagnino, J. H. Dempster et al. (2001) "Deriving Goals from a Use-Case Based Requirements Specification," Requirements Engineering Journal (6) 1, pp. 63-73.
5. Apte, U., C. S. Sankar, M. Thakur, and J. E. Turner (1990) "Reusability-Based Strategy for Development of Information Systems: Implementation Experience of a Bank," MIS Quarterly (14) 4, pp. 421-433.
6. Arthur, J. D. and M. K. Gröner (2005) "An operational model for structuring the requirements generation process," Requirements Engineering Journal (10) 1, pp. 45-62.
7. Atkinson, C. J. (2000) "Socio-Technical and Soft Approaches to Information Requirements Elicitation in the Post- Methodology Era," Requirements Engineering Journal (5) 2, pp. 67-73.
8. Barki, H., S. Rivard, and J. Talbot (1993) "Toward an Assessment of Software Development Risk," Journal of Management Information Systems (10) 2, pp. 203-225.
9. Barki, H., S. Rivard, and J. Talbot (2001) "An Integrative Contingency Model of Software Project Risk Management," Journal of Management Information Systems (17) 4, pp. 37-69.
10. Barley, S. R. (1990) "The Alignment of Technology and Structure through Roles and Networks," Administrative Science Quarterly (35) 1, pp. 61-103.
11. Basili, V. R. and H. D. Rombach (1988) "The TAME project: towards improvement-oriented software environments," IEEE Transactions Software Engineering (14) 6, pp. 758-773.
12. Basili, V. R. and A. J. Turner (1975) "Iterative Enhancement: A Practical Technique for Software Development," IEEE Transactions Software Engineering (1) 4, pp. 390-296.
13. Baskerville, R., L. Levine, J. Pries-Heje, B. Ramesh et al. (2001) "How Internet software companies negotiate quality," Computer (34) 5, pp. 51-57.
14. Bergman, M., J. L. King, and K. Lyytinen (2002) "Large Scale Requirements Analysis Revisited: The Need for Understanding the Political Ecology of Requirements Engineering," Requirements Engineering (7) 3, pp. 152-171.
15. Bersoff, E. H. and A. M. Davis (1991) "Impacts of Life-Cycle Models on Software Configuration Management," Communications of the ACM (34) 8, pp. 104-118.
16. Blackburn, J. D., G. D. Scudder, and L. N. Van Wassenhove (1996) "Improving speed and productivity of software development: A global survey of software developers," IEEE Transactions on Software Engineering (22) 12, pp. 875-885.
17. Boehm, B. (1988) "A Spiral model of software development and enhancement," IEEE Computer (21) 5, pp. 61-72.
18. Boehm, B. (1991) "Software Risk Management: Principles and Practices," IEEE Software (8) 1, pp. 32-41.
19. Boehm, B. and R. Ross (1989) "Theory-W software project management principles and examples," IEEE Transactions Software Engineering (15) 7, pp. 902-916.
20. Bostrom, R. P. (1977) "MIS Problems and Failures: A Socio-Technical Perspective PART 1:THE CAUSES," MIS Quarterly (1) 3, pp. 17-32.
21. Bostrom, R. P. (1989) "Successful application of communication techniques to improve the systems development process," Information & Management (16) 5, pp. 279-275.
22. Bowen, J. P. and M. G. Hinchey (1995) "10-Commandments of Formal Methods," IEEE Computer (28) 4, pp. 56-63.
23. Breitman, K. K., J. C. S. d. P. Leite, and D. M. Berry (2005) "Supporting scenario evolution," Requirements Engineering Journal (10) 2, pp. 112-131.
24. Brooks, F. P. (1987) "No Silver Bullet - Essence and Accidents of Software Engineering," IEEE Computer (20) 4, pp. 10-19.
25. Browne, G. J. and V. Ramesh (2002) "Improving information requirements determination: a cognitive perspective," Information & Management (39) 8, pp. 625-645.
26. Browne, G. J. and M. B. Rogich (2001) "An empirical investigation of user requirements elicitation: Comparing the effectiveness of prompting techniques," Journal of Management Information Systems (17) 4, pp. 223-249.
27. Bryant, J. (1997) "Requirements capture using SODA," European Journal of Information Systems (6) 3, pp. 155-163.
28. Burns, T. and G. M. Stalker (1994) The management of innovation, revised ed. edition. New York: Oxford University Press Inc.
29. Byrd, T. A., K. L. Cossick, and R. W. Zmud (1992) "A Synthesis of Research on Requirements Analysis and Knowledge Acquisition Techniques," MIS Quarterly (16) 1, pp. 117-138.
30. Chatzoglou, P. D. and L. A. Macaulay (1996) "Requirements capture and IS methodologies," Information Systems Journal (6) 3, pp. 209-225.
31. Chen, J. Y. J. and S. C. Chou (1999) "Consistency management in a process environment," Journal of Systems and Software (47) 2-3, pp. 105-110.
32. Chen, M. and J. F. Nunamaker Jr. (1991) "The Architecture and Design of a Collaborative Environment for Systems Definition," DATA BASE (22) 1-2, pp. 22-29.
33. Cohen, M. D., J. G. March, and J. Olsen (1972) "A garbage can theory of organizational choice," Administrative Science Quarterly (17) 1, pp. 1-25.
34. Coughlan, J. and R. D. Macredie (2002) "Effective Communication in Requirements Elicitation: A Comparison of Methodologies," Requirements Engineering Journal (7) 2, pp. 47-60.
35. Curtis, B., M. I. Kellner, and J. Over (1992) "Process modeling," Communications of the ACM (35) 9, pp. 75-90.
36. Curtis, B., H. Krasner, and N. Iscoe (1988) "A field study of the software design process for large systems," Communications of the ACM (31) 11, pp. 1268-1287.
37. Cysneiros, L. M. and J. C. S. D. Leite (2004) "Nonfunctional requirements: From elicitation to conceptual models," IEEE Transactions on Software Engineering (30) 5, pp. 328-350.
38. Daft, R.L. and R.H. Lengel (1981) "Organizational information requirements, media richness and structural design," Management Science (32) 5, pp. 554-571.
39. Damian, D. E. and D. Zowghi (2003) "RE Challenges in multi-site software development organizations," Requirements Engineering Journal (8) 3, pp. 149-160.
40. Darke, P. and G. Shanks (1997) "User viewpoint modelling: understanding and representing user viewpoints during requirements definition," Information Systems Journal (7) 3, pp. 213-239.
41. Davidson, E. J. (2002) "Technology frames and framing: A socio-cognitive investigation of requirements determination," MIS Quarterly (26) 4, pp. 329-358.
42. Davis, G. (1982) "Strategies for information requirements determination," IBM Systems Journal (21) 1, pp. 4-31.
43. Dennis, A. R., J. F. George, L. M. Jessup, J. F. Nunamaker Jr. et al. (1988) "Information Technology to Support Electronic Meetings," MIS Quarterly (12) 4, pp. 591-624.
44. Donaldson, S. E. and S. G. Siegel (2001) Successful Software Development. Upper Saddle River, NJ: Prentice Hall.
45. Drehmer, D. E. and S. M. Dekleva (2001) "A note on the evolution of software engineering practices," Journal of Systems and Software (57) 1, pp. 1-7.
46. Dubois, E. and K. Pohl (2003) "RE 02: A major step toward a mature requirements engineering community," IEEE Software (20) 1, pp. 14-15.
47. Duggan, E. W. (2003) "Generating systems requirements with facilitated group techniques," Human-Computer Interaction (18) 4, pp. 373-394.
48. Duggan, E. W. and C. S. Thachenkary (2004) "Integrating nominal group technique and joint application development for improved systems requirements determination," Information & Management (41) 4, pp. 399-411.
49. Elboushi, M. I. and J. S. Sherif (1997) "Object-oriented software design utilizing quality function deployment," Journal of Systems and Software (38) 2, pp. 133-143.
50. Fazlollahi, B. and M. R. Tanniru (1991) "Selecting a Requirement Determination Methodology-Contingency Approach Revisited," Information & Management (21) 5, pp. 291-303.
51. Fitzgerald, B. (1996) "Formalized systems development methodologies: A critical perspective," Information Systems Journal (6) 1, pp. 3-23.
52. Franch, X. and J. P. Carvallo (2003) "Using Quality Models in Software Package Selection," IEEE Software (20) 1, pp. 34-41.
53. Frolick, M. N. and B. P. Robichaux (1995) "EIS Information Requirements Determination - Using a Group Support System to Enhance the Strategic Business Objectives Method," Decision Support Systems (14) 2, pp. 157-170.
54. Galbraith, J. R. (1973) Designing Complex Organizations, 1st edition. Boston, MA: Addison-Wesley Longman Publishing Co., Inc.
55. García-Duque, J., M. López-Nores, J. J. Pazos-Arias, A. Fernández-Vilas et al. (2006) "Guidelines for the incremental identification of aspects in requirements specifications," Requirements Engineering Journal (11) 4, pp. 239-263.
56. Gillenson, M. and J. Stutz (1991) "Academic Issues in MIS: Journals and Books," MIS Quarterly (15) 4, pp. 147-452.
57. Glass, R. L., I. Vessey, and S. A. Conger (1992) "Software Tasks - Intellectual or Clerical," Information & Management (23) 4, pp. 183-191.
58. Halling, M., S. Biffl, and P. Grunbacher (2003) "An economic approach for improving requirements negotiation models with inspection," Requirements Engineering Journal (8) 4, pp. 236-247.
59. Hardgrave, B. and K. Walstrom (1997) "Forums for Management Information Systems Scholars," Communications of the ACM (38) 3, pp. 93-102.
60. Haumer, P., K. Pohl, and K. Weidenhaupt (1998) "Requirements elicitation and validation with real world scenes," IEEE Transactions on Software Engineering (24) 12, pp. 1036-1054.
61. Hausler, P. A., R. C. Linger, and C. J. Trammell (1994) "Adopting Cleanroom Software Engineering with a Phased Approach," IBM Systems Journal (33) 1, pp. 89-109.
62. Hevner, A. R. and H. D. Mills (1993) "Box-structured methods for systems development with objects," IBM Systems Journal (32) 2, pp. 232-251.
63. Hevner, A. R. and H. D. Mills (1995) "Box-Structured Requirements Determination Methods," Decision Support Systems (13) 3-4, pp. 223-239.
64. Hickey, A. M. and A. Davis (2004) "A Unified Model of Requirements Elicitation," Journal of Management Information Systems (20) 4, pp. 65-84.
65. Hirschheim, R. and M. Newman (1991) "Symbolism and Information Systems Development: Myth, Metaphors and Magic," Information Systems Research (2) 1, pp. 29-62.
66. Holsapple, C., L. Johnson, H. Manakyan, and J. Tanner (1994) "Business Computing Research Journals: A Normalized Citation Analysis," Journal of Management Information Systems (11) 1, pp. 131-140.
67. Holtzblatt, K. (1995) "Requirements Gathering: The Human Factor," Communications of The ACM (38) 5, pp. 31-33.
68. Houston, D. X., G. T. Mackulak, and J. S. Collofello (2001) "Stochastic simulation of risk factor potential effects for software development risk management," Journal of Systems and Software (59) 3, pp. 247-257.
69. Iivari, J. (1990) "Hierarchical Spiral Model for Information-System and Software- Development .1. Theoretical Background," Information and Software Technology (32) 6, pp. 386-399.
70. Iivari, J. (1992) "The organizational fit of information systems," Journal of Information Systems (2) 1, pp. 3-29.
71. Iivari, J., R. Hirschheim, and H. K. Klein (2000) "A Dynamic Framework for Classifying Information Systems Development Methodologies and Approaches," Journal of Management Information Systems (17) 3, pp. 179-218.
72. Iversen, J. H., L. Mathiassen, and P. A. Nielsen (2004) "Managing Risk in Software Process Improvement: An Action Research Approach," MIS Quarterly (28) 3, pp. 395-433.
73. Jarke, M., X. T. Bui, and J. M. Carroll (1998) "Scenario Management: An Interdisciplinary Approach," Requirements Engineering Journal (3) 3-4, pp. 155-173.
74. Jayaratna, N. (1994) Understanding and Evaluating Methodologies. London: McGraw Hill.
75. Jenkins, A. M., J. D. Naumann, and J. C. Wetherbe (1984) "Empirical investigation of systems development practices and results," Information & Management (7) 2, pp. 73-82.
76. Jirotka, M. and P. Luff (2006) "Supporting Requirements with Video-Based Analysis," IEEE Software (23) 3, pp. 42-44.
77. Jones, R. M., L. Candy, and E. A. Edmonds (1993) "Knowledge-Based System Requirements," Knowledge-Based Systems (6) 1, pp. 31-37.
78. Kaiya, H., D. Shinbara, J. Kawano, and S. Motoshi (2005) "Improving the detection of requirements discordances among stakeholders," Requirements Engineering Journal (10) 4, pp. 289-303.
79. Katerattanakul, P., B. Han, and S. Hong (2003) "Objective Quality Ranking of Computing Journals," Communications of the ACM (46) 10, pp. 111-114.
80. Keil, M. and E. Carmel (1995) "Customer-developer links in software development," Communications of the ACM (38) 5, pp. 33-44.
81. Keil, M., P. E. Cule, K. Lyytinen, and R. C. Schmidt (1998) "A Framework for Identifying Software Project Risks," Communications of the ACM (41) 11, pp. 76-83.
82. Kickert, W. J. M. (1983) "Research note: Research models underlying situational dependency," Organization Studies (4) 1, pp. 55-72.
83. Kraut, R. E. and L. A. Streeter (1995) "Coordination in software development," Communications of the ACM (38) 3, pp. 69-81.
84. Kujala, S. (2003) "User involvement: a review of the benefits and challenges," Behaviour & Information Technology (22) 1, pp. 1-16.
85. Lamb, R. and R. Kling (2003) "Reconceptualizing Users as Social Actors in Information Systems Research," MIS Quarterly (27) 2, pp. 197-235.
86. Lang, M. and M. Duggan (2001) "A Tool to Support Collaborative Software Requirements Management," Requirements Engineering Journal (6) 3, pp. 161-172.
87. Larman, C. and V. R. Basili (2003) "Iterative and Incremental Development: A Brief History," IEEE Software (36) 6, pp. 47-56.
88. Larsen, T. J. and J. D. Naumann (1992) "An Experimental Comparison of Abstract and Concrete Representations in Systems-Analysis," Information & Management (22) 1, pp. 29-40.
89. Lausen, S. and J. P. Vium (2005) "Communication gaps in a tender process," Requirements Engineering Journal (10) 4, pp. 247-261.
90. Lawrence, P. R. and J. W. Lorsch (1974) Organization and Environment - Managing Differentiation and Integration. Homewood, Illinois: Richard D. Irwin Inc.
91. Lee, W. J., S. D. Cha, and Y. R. Kwon (1998) "Integration and analysis of use cases using modular Petri nets in requirements engineering," IEEE Transactions on Software Engineering (24) 12, pp. 1115-1130.
92. Leifera, R., S. Leeb, and J. Durgeea (1994) "Deep structures: Real information requirements determination," Information & Management (27) 5, pp. 275-285.
93. Leite, J. and P. A. Freeman (1991) "Requirements Validation through Viewpoint Resolution," IEEE Transactions on Software Engineering (17) 12, pp. 1253-1269.
94. Liou, Y. I. and M. Chen (1993) "Using group support systems and joint application development for requirement specification," Journal of Management Information Systems (10) 3, pp. 25-41.
95. Liu, S., A. J. Offutt, C. Ho-Stuart, Y. Sun et al. (1998) "SOFL: A formal engineering methodology for industrial applications," IEEE Transactions on Software Engineering (24) 1, pp. 24-45.
96. Lyytinen, K. (1987) "Different Perspectives on Information-Systems - Problems and Solutions," ACM Computing Surveys (19) 1, pp. 5-46.
97. Lyytinen, K. (1988) "Expectation Failure Concept and Systems Analysts' View of Information System Failures: Results of an Exploratory Study," Information & Management (14) 1, pp. 45-56.
98. Lyytinen, K., L. Mathiassen, and J. Ropponen (1996) "A framework for software risk management," Journal of Information Technology (11) 4, pp. 275-285.
99. Lyytinen, K., L. Mathiassen, and J. Ropponen (1998) "Attention shaping and software risk - A categorical analysis of four classical risk management approaches," Information Systems Research (9) 3, pp. 233-255.
100. Maiden, N. A. M. and M. Hare (1998) "Problem domain categories in requirements engineering," International Journal of Human-Computer Studies (49) 3, pp. 281-304.
101. Marakas, G. M. and J. J. Elam (1998) "Semantic structuring in analyst acquisition and representation of facts in requirements analysis," Information Systems Research (9) 1, pp. 37-63.
102. Markus, L. M. and J.-Y. Mao (2004) "Participation in Development and Implementation - Updating An Old, Tired Concept for Today's IS Contexts," Journal of AIS (5) 11-12, pp. 514-544.
103. Mathiassen, L., T. Seewaldt, and J. Stage (1995) "Prototyping and Specifying: Principles and Practices of a Mixed Approach," Scandinavian Journal of Information Systems (7) 1, pp. 55-72.
104. McFarlan, F. W. (1981) "Portfolio Approach to Information Systems," Harvard Business Review (59) 5, pp. 142-150.
105. McFarlan, W. (1982) "Portfolio Approach to Information Systems," Journal of Systems Management (33) 1, pp. 12-19.
106. McKeen, J. D., T. Guimaraes, and J. C. Wetherbe (1994) "The Relationship between User Participation and User Satisfaction - an Investigation of 4 Contingency Factors," MIS Quarterly (18) 4, pp. 427-451.
107. Mich, L., C. Anesi, and D. M. Berry (2005) "Applying a pragmatics-based creativity-fostering technique to requirements elicitation," Requirements Engineering Journal (10) 4, pp. 262-275.
108. Mills, H. D. (1999) "The management of software engineering - Part I: Principles of software engineering (Reprinted from IBM Systems Journal, vol 19, 1980)," IBM Systems Journal (38) 2-3, pp. 289-295.
109. Minzberg, H. (1983) Structure in fives: designing effective organizations. New Jersey: Prentice-Hall International.
110. Montazemi, A. R. and D. W. Conrath (1986) "The Use of Cognitive Mapping for Information Requirements Analysis," MIS Quarterly (10) 1, pp. 44-56.
111. Mylonopoulos, N. and V. Theoharakis (2001) "On-Site: Global Perceptions of IS Journals," Communications of the ACM (44) 9, pp. 29-33.
112. Neill, C. J. and P. A. Laplante (2003) "Requirements Engineering: The State of the Practice," IEEE Software (20) 6, pp. 40-45.
113. Nguyen, L. and P. A. Swatman (2003) "Managing the requirements engineering process," Requirements Engineering Journal (8) 1, pp. 55-68.
114. Nidumolu, S. (1995) "The Effect of Coordination and Uncertainty on Software Project Performance: Residual Performance Risk as an Intervening Variable," Information Systems Research (6) 3, pp. 191-219.
115. Nunamaker, J. F., A. R. Dennis, J. S. Valacich, D. Vogel et al. (1991) "Electronic meeting systems to Support Group Work," Communications of the ACM (34) 7, pp. 40-61.
116. Nuseibeh, B., J. Kramer, and A. Finkelstein (1994) "A Framework for Expressing the Relationships Between Multiple Views in Requirements Specification," IEEE Transactions Software Engineering (20) 10, pp. 760-773.
117. Pai, W. C. (2002) "A quality-enhancing software function deployment model," Information Systems Management (19) 3, pp. 20-24.
118. Pedersen, T. B., C. S. Jensen, and C. E. Dyreson (2001) "A foundation for capturing and querying complex multidimensional data," Information Systems (26) 5, pp. 383-423.
119. Peffers, K., C. E. Gengler, and T. Tuunanen (2003) "Extending critical success factors methodology to facilitate broadly participative information systems planning," Journal of Management Information Systems (20) 1, pp. 51-85.
120. Peffers, K. and Y. Tang (2003) "Identifying and Evaluating the Universe of Outlets for Information Systems Research: Ranking the Journals," Journal of Information Technology Theory and Application (5) 1, pp. 63-84.
121. Pohl, K. (1994) "The Three Dimensions of Requirements Engineering - a Framework and Its Applications," Information Systems (19) 3, pp. 243-258.
122. Potts, C., K. Takahashi, and A. I. Antón (1994) "Inquiry-Based Requirements Analysis," IEEE Software (11) 2, pp. 21-32.
123. Pugh, D. S. (ed.) (1998) The Aston Programme - The Aston Study and its developments, Volume I. Classic Research in Management, Hants: Ashgate Publishing Company.
124. Quintas, P. (1994) "A Product-Process Model of Innovation in Software-Development," Journal of Information Technology (9) 1, pp. 3-17.
125. Rai, A. and H. Al-Hindi (2000) "The effects of development process modeling and task uncertainty on development quality performance," Information & Management (37) 6, pp. 335-346.
126. Ramamoorthy, C. V. and W. T. Tsai (1996) "Advances in software engineering," Computer (29) 10, pp. 47-58.
127. Ramesh, B. and K. Sengupta (1995) "Multimedia in a design rationale decision support system," Decision Support Systems (15) 3, pp. 181-196.
128. Ramesh, V. and G. J. Browne (1999) "Expressing casual relationships in conceptual database schemas," Journal of Systems and Software (45) 3, pp. 225-232.
129. Ravichandran, T. and A. Rai (1999) "Total quality management in information systems development: Key constructs and relationships," Journal of Management Information Systems (16) 3, pp. 119-155.
130. Ravichandran, T. and A. Rai (2000) "Quality management in systems development: An organizational system perspective," MIS Quarterly (24) 3, pp. 381-415.
131. Ravid, A. and D. M. Berry (2000) "A Method for Extracting and Stating Software Requirements that a User Interface Prototype Contains," Requirements Engineering Journal (5) 4, pp. 225-241.
132. Regnell, B., M. Höst, J. Natt och Dag, P. Beremark et al. (2001) "An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software," Requirements Engineering Journal (6) 1, pp. 51-62.
133. Rolland, C., C. Souveyet, and M. B. Ayed (2003) "Guiding Lyee user requirements capture," Knowledge-Based Systems (16) 7-8, pp. 351-359.
134. Rolland, C., C. Souveyet, and C. Ben Achour (1998) "Guiding goal modeling using scenarios," IEEE Transactions on Software Engineering (24) 12, pp. 1055-1071.
135. Ropponen, J. and K. Lyytinen (1997) "Can software risk management improve system development: An exploratory study," European Journal of Information Systems (6) 1, pp. 41-50.
136. Ropponen, J. and K. Lyytinen (2000) "Components of software development risk: How to address them? A project manager survey," IEEE Transactions on Software Engineering (26) 2, pp. 98-112.
137. Saiedian, H., P. Kumarakulasingam, and M. Anan (2005) "Scenario-based requirements analysis techniques for real-time software systems: a comparative evaluation," Requirements Engineering Journal (10) 1, pp. 22-33.
138. Salaway, G. (1987) "An Organizational Learning Approach to Information Systems Development," MIS Quarterly (20) 1, pp. 244-264.
139. Sawyer, S. and P. J. Guinan (1998) "Software development: Processes and performance," IBM Systems Journal (37) 4, pp. 552-569.
140. Shin, J. E., A. G. Sutcliffe, and A. Gregoriades (2005) "Scenario advisor tool for requirements engineering," Requirements Engineering Journal (10) 2, pp. 132-145.
141. Simon, H. (1955) "A Behavioral Model of Rational Choice," Quarterly Journal of Economics (69) 1, pp. 99-118.
142. Simon, H. (1957) Models of Man. New York.
143. Stallinger, F. and P. Grunbacher (2001) "System dynamics modelling and simulation of collaborative requirements engineering," Journal of Systems and Software (59) 3, pp. 311-321.
144. Sutton, D. C. (2000) "Linguistic Problems with Requirements and Knowledge Elicitation," Requirements Engineering Journal (5) 2, pp. 114-124.
145. Telem, M. (1988) "Information Requirements Specification I: Brainstorming a Collective Decision- Making Approach," Information Processing & Management (24) 5, pp. 549-557.
146. Trammell, C. J., M. G. Pleszkoch, R. C. Linger, and A. R. Hevner (1996) "The incremental development process in Cleanroom software engineering," Decision Support Systems (17) 1, pp. 55-71.
147. Walz, D., J. Elam, and B. Curtis (1993) "Inside a software design team: Knowledge acquisistion, Sharing and Integration," Communications of the ACM (36) 10, pp. 62-77.
148. van Lamsweerde, A. and E. Letier (2000) "Handling obstacles in goal-oriented requirements engineering," IEEE Transactions on Software Engineering (26) 10, pp. 978-1005.
149. Watson, H. J. and M. N. Frolick (1993) "Determining information requirements for an EIS," MIS Quarterly (17) 3, pp. 255-269.
150. Webster, J. and R. T. Watson (2002) "Analyzing the Past to Prepare for the Future: Writing a Literature Review," MIS Quarterly (26) 2, pp. xiii-xx.
151. Weill, P. and M. H. Olson (1989) "An Assessment of the Contingency Theory of Management Information Systems," Journal of Management Information Systems (6) 1, pp. 59-85.
152. Vessey, I. and S. A. Conger (1994) "Requirements Specification: Learning Object, Process, and Data Methodologies," Communications of the ACM (37) 5, pp. 102-113.
153. Wetherbe, J. C. (1991) "Executive Information Requirements - Getting It Right," MIS Quarterly (15) 1, pp. 51-65.
154. Whitman, M., A. Hendrickson, and A. Townsend (1999) "Research Commentary. Academic Rewards for Teaching, Research and service: Data and Discourse," Information Systems Research (10) 2, pp. 99-109.
155. Willcocks, L. and H. Margetts (1994) "Risk assessment and information systems," European Journal of Information Systems (3) 2, pp. 127-138.
156. Woodward, J. (1994) Industrial Organization, 2nd edition. Oxford: Oxford University Press.
157. Zhang, P. and N. Li (2005) "The Intellectual Development of Human-Computer Interaction Research: A Critical Assessment of the MIS Literature (1990-2002)," Journal of AIS (6) 1, pp. 227-292.
158. Zmud, R. W. (1980) "Management of Large Software Development Efforts," MIS Quarterly (4) 2, pp. 45-55.
159. Zultner, R. E. (1993) "TQM for technical teams," Communications of the ACM (36) 10, pp. 79-91.