Agile technologies in open source development

Agile Technologies in Open Source Development

Volumn , Issue , 2009, Pages 1-371

  Russo, Barbara ^a   Scotto, Marco ^a   Sillitti, Alberto ^a   Succi, Giancarlo ^a  

^a FREE UNIVERSITY OF BOZEN BOLZANO   (Italy)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84898167616     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.4018/978-1-59904-681-5     Document Type: Book

References (264)

1. Beck, K. (1999). Extreme programming explained: Embrace change. Addison-Wesley Professional.
2. Beck, K. (2004). Extreme programming explained: Embrace change, second ed. Addison-Wesley Professional.
3. Beck, K., & Fowler, M. (2000). Planning extreme programming. Addison-Wesley Professional.
4. Boehm, B. (1988). A spiral model of software development and enhancement. IEEE Computer, 21(5), 61-72.
5. Boehm, B. (2002). Get ready for agile methods, with care. IEEE Computer, 35(1), 64-69.
6. rd International Conference on the Software Process (ICSP94). New York: IEEE Press.
7. st International Conference on Requirements Engineering (ICRE94). Colorado Springs, CO: IEEE Computer Society Press.
8. Boehm, B., & Turner, R. (2003). Balancing agility and discipline: A guide for the perplexed. Addison-Wesley Professional.
9. Fowler, M., Beck, K., Brant, J., Opdyke, W., & Roberts, D. (1999) Refactoring: Improving the design of existing code. Addison-Wesley Professional.
10. Highsmith, J. (2002). Agile software development ecosystems. Addison-Wesley Professional.
11. Jeffries, R. (1999). We'll try. Retrieved on November 11, 2008 from http://www.xprogramming.com/xpmag/well_try.htm
12. Poppendieck, M., & Poppendieck, T. (2003). Lean software development: An agile toolkit. Addison-Wesley Professional.
13. Scacchi, W. (2002) Open source software development processes. Version 2.5. Retrieved on November 11, 2008 from http://www.ics.uci.edu/~wscacchi/Software-Process/Open-Software-Process-Models/Open-Source-Software-Development-Processes.ppt
14. Wake, W. C. (2002) Extreme programming explored. Addison-Wesley Professional.
15. rd Workshop on Open Source Software Engineering, Portland, OR.
16. Womack, J. P., & Jones, D. T. (1996). Lean thinking: Banish waste and create wealth in your corporation. Simon & Schuster.
17. Goldman, R., & Gabriel, R. P. (2005). Innovation happens elsewhere: Open source as business strategy. Morgan Kaufmann.
18. th Annual Hawaii International Conference on System Sciences (HICSS'05). IEEE Computer Society Press.
19. Ambler, S. (2002). Agile modeling: Effective practices for extreme programming and the unified process. Wiley.
20. Beck, K. (1999). Extreme programming explained: Embrace change. Addison-Wesley Professional.
21. Beck, K. (2002). Test driven development: By example. Addison-Wesley Professional.
22. Beck, K. (2004). Extreme programming explained: Embrace change, second ed. Addison-Wesley Professional.
23. Fowler, M. (2003). Principles of XP. Retrieved on November 11, 2008 from http://www.martinfowler.com/bliki/PrinciplesOfXP.html
24. Jeffries, R., Anderson, A., & Hendrickson, C. (2001). Extreme programming installed. Addison-Wesley Professional.
25. Raymond, E. S. (2000). The cathedral and the bazaar. Retrieved on November 11, 2008 from http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/
26. Ambler, S. (2006). Supersize me. Dr. Dobb's Journal. Retrieved on November 11, 2008, from http://www.ddj.com/architect/184415491
27. Beck, K. (1999). Extreme programming explained: Embrace change. Addison-Wesley Professional.
28. Ceschi, M., Sillitti, A., Succi, G., & De Panfilis, S. (2005). Project management in plan-based and agile companies. IEEE Software, 22(3), 21-27. doi:10.1109/MS.2005.75
29. Chrissis, M. B., Konrad, M., & Shrum, S. (2003). CMMI: Guidelines for process integration and product improvement. Addison-Wesley Professional.
30. Cohen, D., Lindvall, M., & Costa, P. (2004). An introduction to agile methods. In M. Zelkowitz (Ed.), Advances in computers (pp. 1-66). New York: Elsevier Science.
31. Eckstein, J. (2004). Agile software development in the large: Diving into the deep. Dorset House Publishing.
32. th IEEE International Symposium on Software Metrics (METRICS 2005).
33. Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2003). Agile software development methods: Review and Analysis (p. 478). Espoo, Finland: Technical Research Centre of Finland, VTT Publications.
34. Beck, K. (1999). Extreme programming explained: Embrace change. Addison-Wesley Professional.
35. Brooks, F. (1987). No silver bullet: Essence and accidents of software engineering. IEEE Computer, 20(4), 10-19.
36. Camerer, C. F., & Knez, M. (1996). Coordination in organizations: A game-theoretic perspective. In Z. Shapira (Ed.), Organizational decision making. New York: Cambridge University Press.
37. Carmel, E. (1999). Global software teams: Collaborating across borders and timezones. Prentice Hall.
38. Carmel, E., & Agarwal, R. (2001). Tactical approaches for alleviating distance in global software development. IEEE Software, 18(2), 22-29. doi:10.1109/52.914734
39. th International Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises.
40. Cooper, R. W. (1999). Coordination game: Complementarities and macroeconomics. Cambridge University Press.
41. Crowston, K. (1994). A taxonomy of organizational dependencies and coordination mechanisms. Retrieved on November 11, 2008, from http://ccs.mit.edu/papers/CCSWP174.html
42. Crowston, K. (2005). The bug fixing process in proprietary and free/libre open source software: A coordination theory analysis. In V. Grover & M. L. Markus (Eds.), Business process transformation. Armonk, NY: M. E. Sharpe Inc.
43. th Workshop on Enabling Technologies (WETICE '99).
44. Curtis, W., Krasner, H., & Iscoe, N. (1988). A field study of the software design process for large systems. Communications of the ACM, 31(11), 1268-1287. doi:10.1145/50087.50089
45. Feller, J., & Fitzgerald, B. (2002). Understanding open source software development. Addison-Wesley.
46. Fowler, M., Beck, K., Brant, J., Opdyke, W., & Roberts, D. (1999) Refactoring: Improving the design of existing code. Addison-Wesley Professional.
47. Grinter, R. E., Herbsleb, J. D., & Perry, D. E. (1999). The geography of coordination: Dealing with distance in R&D work. ACM SIGGROUP Conference on Supporting Group Work.
48. Gutwin, C., Penner, R., & Schneider, K. (2004). Group awareness in distributed software development. 2004 ACM Conference on Computer Supported Cooperative Work.
49. Herbsleb, J. D., & Grinter, R. E. (1999). Splitting the organization and integrating the code: Conway's law revisited. International Conference on Software Engineering (ICSE'99).
50. Kraut, R., & Streeter, L. (1995). Coordination in software development. Communications of the ACM, 38(3), 69-81. doi:10.1145/203330.203345
51. Lawrence, P. R., & Lorsch, J. W. (1967). Organization and environment: Managing differentiation and integration. Harvard Business School Press.
52. Malone, T. W., & Crowston, K. (1990). What is coordination theory and how can it help design cooperative work systems. 1990 ACM Conference on Computer-Supported Cooperative Work.
53. Malone, T. W., & Crowston, K. (1994). The interdisciplinary theory of coordination. ACM Computing Surveys, 26(1), 87-119. doi:10.1145/174666.174668
54. Marchesi, M., Succi, G., Wells, D., & Williams, L. (2002). Extreme programming perspectives. Addison-Wesley.
55. Mintzberg, H. (1979). The structuring of organization. Englewood Cliffs, NJ: Prentice-Hall.
56. Ohno, T. (1988). Toyota production system: Beyond large-scale production. Productivity Press.
57. Poppendieck, M., & Poppendieck, T. (2003). Lean software development: An agile toolkit. Addison-Wesley Professional.
58. Thompson, J. D. (1967). Organizations in action: Social science bases of administrative theory. New York: McGraw-Hill.
59. Toffolon, C., & Dakhli, S. (2000). A framework for studying the coordination process in software engineering. 2000 ACM Symposium on Applied Computing.
60. Weber, R. (2001). Organizational coordination: A game-theoretic view. Retrieved on November 11, 2008, from http://www.andrew.cmu.edu/user/rweber/Files/orgcoord.pdf
61. Womack, J. P., Jones, D., & Roos, D. (1991). The machine that changed the world: The story of lean production. Harper Perennial.
62. Yamauchi, Y., Yokozawa, M., Shinohara, T., & Ishida, T. (2000). Collaboration with lean media: How open-source software succeeds. Computer Supported Cooperative Work Conference (CSCW'00).
63. Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2003). Agile software development methods: Review and analysis (p. 478). Espoo, Finland: Technical Research Centre of Finland, VTT Publications.
64. Ambler, S. (2002). Agile modeling. Wiley.
65. Beck, K. (1999). Extreme programming explained: Embrace change. Addison-Wesley Professional.
66. Cockburn, A. (2004). Crystal "clear": A human-powered software development methodology for small teams. Addison-Wesley Professional.
67. Kilpatrick, J. (2003). Lean principles. UT: Utah manufacturing extension partnership.
68. Ohno, T. (1988). Toyota production system: Beyond large-scale production. Productivity Press Inc.
69. Palmer, S., & Felsing, J. (2002). Practical guide to feature-driven development. Prentice Hall.
70. Poppendieck, M., & Poppendieck, T. (2003). Lean software development: An agile toolkit. Addison-Wesley Professional.
71. Schwaber, K., & Beedle, M. (2001). Agile software development with SCRUM. Prentice Hall.
72. Stapleton, J. (1997). DSDM: The dynamic systems development method. Addison-Wesley Professional.
73. Black, R. (2002). Managing the testing process. Wiley.
74. Burnstein, I. (2003). Practical software testing. Springer.
75. Kaner, C., Bach, J., & Pettichord, B. (2002). Lessons learned in software testing. Wiley.
76. Myers, G. J. (1979). The art of software testing. Wiley.
77. Spillner, A., Linz, T., & Schaefer, H. (2007) Software testing foundations: A study guide for the certified tester exam. Rocky Nook Inc.
78. Beck, K. (1999). Extreme programming explained: Embrace change. Addison-Wesley Professional.
79. Feller, J., & Fitzgerald, B. (2001). Understanding open source software development. Addison-Wesley Professional.
80. Scotto, M., Sillitti, A., & Succi, G. (2007). An empirical study on the open source development process based on mining of source code repositories. [IJSEKE]. International Journal of Software Engineering and Knowledge Engineering, 17(2), 1-17. doi:10.1142/S0218194007003215
81. Ambler, S. (2004). The object primer: Agile model driven development with UML 2. Cambridge University Press.
82. th International Conference on Software Engineering.
83. Eisenbarth, T., Koschke, R., & Simon, D. (2001). Aiding program comprehension by static and dynamic feature analysis. IEEE International Conference on Software Maintenance.
84. El Emam, K., Melo, W., & Machado, J. C. (2001). The prediction of faulty classes using object-oriented metrics. Journal of Systems and Software, 56(1), 63-75. doi:10.1016/S0164-1212(00)00086-8
85. Fowler, M. (1999). UML distilled: A brief guide to the standard object modeling language. Addison-Wesley Professional.
86. Fowler, M., Beck, K., Brant, J., Opdyke, W., & Roberts, D. (1999). Refactoring: improving the design of existing code. Addison-Wesley Professional.
87. Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1994). Design patterns: Elements of reusable object-oriented software. Addison-Wesley Professional.
88. th IEEE International Workshop on Program Comprehension.
89. st International Workshop on Software Evolution Transformations.
90. th IEEE International Workshop on Program Comprehension.
91. Pelz, D. C. (1985). Innovation complexity and sequence of innovating strategies. Knowledge: Creation Diffusion. Utilization, 6, 261-291.
92. Siegel, S., & Castellan, N. J. (1988). Nonparametric statistics for behavioral sciences. McGraw-Hill.
93. Brooks, F. P. (1995). The mythical man-month: Essays on software engineering, anniversary ed. Addison-Wesley.
94. DeMarco, T. (1982). Controlling software projects-management, measurement, & estimation. Yourdan Press.
95. Basili, V. R., & Rombach, D. (1988). The TAME project: Towards improvement-oriented software environments. IEEE Transactions on Software Engineering, 14(6), 758-773. doi:10.1109/32.6156
96. Basili, V. R., & Weiss, D. M. (1984). A methodology for collecting valid software engineering data. IEEE Transactions on Software Engineering, 10(6), 728-738.
97. Campbell, D. T., & Stanley, J. C. (1990). Experimental and quasi-experimental designs for research. Houghton Mifflin Company College Division.
98. Goldman, R. (2002). Scenarios. OOPSLA Workshop on Distributed eXtreme Programming, Tackling the Discovery Costs of Evolving Software Systems, and Pair Programming Explored.
99. Highsmith, J. (2002). Agile software development ecosystems. Addison-Wesley Professional.
100. th International Conference on Software Engineering.
101. th International Conference on XP and Flexible Processes in Software Engineering.
102. Poppendieck, M., & Poppendieck, T. (2003). Lean software development: An agile toolkit for software development managers. Addison-Wesley Professional.
103. rd International Conference on XP and Flexible Processes in Software Engineering.
104. Sillitti, A., Janes, A., Succi, G., & Vernazza, T. (2003). Collecting, integrating, and analyzing software metrics and personal software process data. EUROMICRO.
105. Succi, G. (2002). A lightweight evaluation of a lightweight process. In M. Marchesi, G. Succi, D. Wells & L. Williams (Eds.), Extreme programming perspectives. Addison-Wesley Professional.
106. rd International Conference on XP and Flexible Processes in Software Engineering.
107. Wells, D. (2001). XP and databases. Retrieved on November 11, 2008, from http://www.extremeprogramming.org/stories/testdb.html
108. Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (1999). Experimentation in software engineering: An introduction. Kluwer Academic Publishers.
109. th ACM Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA'04).
110. Basili, V. R., Briand, L., & Melo, W. L. (1996). A validation of object-oriented design metrics as quality indicators. IEEE Transactions on Software Engineering, 22(10), 751-761. doi:10.1109/32.544352
111. Beck, K. (1999). Extreme programming explained: Embrace change. Addison-Wesley Professional.
112. Bishop, C. M. (1994). Neural networks for pattern recognition. Oxford University Press.
113. Boehm, B. W. (1981). Software engineering economics. Prentice-Hall.
114. Boehm, B. W., Brown, J. R., & Kaspar, J. R. (1978). Characteristics of software quality. TRW series of software technology.
115. Bois, B. D., & Mens, T. (2003). Describing the impact of refactoring on internal program quality. International Workshop on Evolution of Large-scale Industrial Software Applications (ELISA).
116. Bontempi, G. (2003). Resampling techniques for statistical modeling. Retrieved on November 11, 2008, from http://www.ulb.ac.be/di/map/gbonte/ecares/boot1.pdf
117. Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P., & Stal, M. (1996). Pattern oriented software architecture. Wiley.
118. Chidamber, S., & Kemerer, C. F. (1994). A metrics suite for object-oriented design. IEEE Transactions on Software Engineering, 20(6), 476-493. doi:10.1109/32.295895
119. Cohn, M. (2006). Agile estimating and planning. Pearson Education.
120. th International Workshop on in Program Comprehension.
121. th ACM Symposium on Applied Computing (SAC 2002).
122. DeMarco, T., & Lister, T. (1999). Peopleware: Productive projects and teams. Dorset House Publishing Company.
123. th ACM Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA'00).
124. Efron, B., & Tibshirani, R. J. (1993). An introduction to the bootstrap. Chapman and Hall.
125. Fenton, N. E., & Pfleeger, S. H. (1997). Software metrics: A rigorous & practical approach. PWS Publishing Company.
126. Fowler, M. (2002). Refactoring improving the design of existing code. Addison-Wesley Professional.
127. Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1995). Design patterns: Elements of reusable object-oriented software. Addison-Wesley.
128. Halstead, M. (1977). Elements of software science. Elsevier.
129. Hannay, J. E., Sjoberg, D. I. K., & Dybå, T. (2007). A systematic review of theory use in software engineering experiments. IEEE Transactions on Software Engineering, 33(2), 87-107. doi:10.1109/TSE.2007.12
130. Hedges, L. V., & Olkin, I. (1985). Statistical methods for meta-analysis. Academic Press.
131. Henry, S., & Kafura, D. (1981). Software structure metrics based on information flow. IEEE Transactions on Software Engineering, 7(5), 510-518. doi:10.1109/TSE.1981.231113
132. Hollander, M., & Wolfe, D. A. (1973). Nonparametric statistical inference. Wiley.
133. Hu, Q. (1997). Evaluating alternative software production functions. IEEE Transactions on Software Engineering, 23(6), 379-387. doi:10.1109/32.601078
134. Hubert, M., & Verboven, S. (2003). A robust PCR method for high-dimensional regressors. Journal of Chemometrics, 17(8-9), 438-452. doi:10.1002/cem.783
135. Humphrey, W. (1995). A discipline for software engineering. Addison-Wesley Professional.
136. Hunter, J. E., & Schmidt, F. L. (1990). Methods for meta-analysis: Correcting error and bias in research findings. Sage.
137. th International Symposium on the Foundations of Software Engineering (SIGSOFT'98).
138. th International Conference on Software Engineering, Portland.
139. Kataoka, Y., Imai, T., Andou, H., & Fukaya, T. A. (2002). Quantitative evaluation of maintainability enhancement by refactoring. International Conference on Software Maintenance.
140. Kendall, M. G., & Gibbons, J. D. (1990). Rank correlation methods. Oxford University Press.
141. Kerievsky, J. (2004). Refactoring to patterns. Addison-Wesley Professional.
142. Kerth, N. L. (2001). Project retrospectives: A handbook for team reviews. Dorset House Publishing Company.
143. Layman, L., Williams, L., & Cunningham, L. (2004). Exploring extreme programming in context: An industrial case study. Agile Development Conference.
144. th International Software Metrics Symposium.
145. Lehmann, E. L. (1986). Testing statistical hypotheses. Springer-Verlag.
146. st International Workshop on Predictor Models in Software Engineering (PROMISE 2005).
147. Marchesi, M., & Succi, G. (2003). Extreme programming and agile processes in software engineering. Springer.
148. McCabe, T. (1976). Complexity measure. IEEE Transactions on Software Engineering, 2(4), 308-320. doi:10.1109/TSE.1976.233837
149. McCall, J. A., Richards, P. K., & Walters, G. F. (1977). Factors in software quality. US Rome Air Development Center Reports.
150. Meyers, J. L., & Well, A. D. (2003). Research design and statistical analysis. Lawrence Erlbaum Associates Inc.
151. Mišić, V. B., & Tešić, D. N. (1998). Estimation of effort and complexity: An object-oriented case study. Journal of Systems and Software, 41(2), 133-143. doi:10.1016/S0164-1212(97)10014-0
152. Mooney, C., & Duval, R. (1993). Bootstrapping. A nonparametric approach to statistical inference (p. 95). In Quantitative Applications in the Social Sciences. Sage Publications.
153. Myrtveit, I., & Stensrud, E. (1999). A controlled experiment to assess the benefits of estimating with analogy and regression models. IEEE Transactions on Software Engineering, 25(4), 510-524. doi:10.1109/32.799947
154. th International Conference on Software Engineering.
155. Pearson, K. (1907). Mathematical contributions to the theory of evolution. XVI. On further methods of determining correlation. Drapers' Company Research Memoirs (Biometric Series 4). Cambridge University Press.
156. Poppendieck, M., & Poppendieck, T. (2003). Lean software development: An agile toolkit for software development managers. Addison-Wesley Professional.
157. Rosenthal, R. (1991). Meta-analytical procedures for social research. Sage.
158. Shepperd, M. C., & Schofield, C. (1997). Estimating software project effort using analogies. IEEE Transactions on Software Engineering, 23(11), 736-743. doi:10.1109/32.637387
159. Sillitti, A., Janes, A., Succi, G., & Vernazza, T. (2003). Collecting, integrating, and analyzing software metrics and personal software process data. EUROMICRO.
160. Tichy, W. (1998). Should computer scientists experiment more? IEEE Computer, 31(5), 32-40.
161. th Working Conference on Reverse Engineering (WCRE 2001).
162. th Working Conference on Reverse Engineering.
163. Ahituv, N., Zviran, M., & Glezer, C. (1999). Top management toolbox for managing corporate IT. Communications of the ACM, 42(4), 93-99. doi:10.1145/299157.299177
164. Albrecht, A. J., & Gaffney, J. E. (1983). Software function, source lines of code, and development effort prediction. IEEE Transactions on Software Engineering, 9(6), 639-648. doi:10.1109/TSE.1983.235271
165. Alshayeb, M., & Li, W. (2003). An empirical validation of object-oriented metrics in two different iterative software processes. IEEE Transactions on Software Engineering, 29(11), 1043-1048. doi:10.1109/TSE.2003.1245305
166. th International Symposium on Software Metrics.
167. Basili, V. R., Briand, L., & Melo, W. L. (1996). A validation of object-oriented design metrics as quality indicators. IEEE Transactions on Software Engineering, 22(10), 751-761. doi:10.1109/32.544352
168. Boehm, B. W. (1981). Software engineering economics. Prentice-Hall.
169. Boehm, B. W., Abts, C., & Chulani, S. (2000). Software development cost estimation approaches-a survey. Annals of Software Engineering.
170. Boehm, B. W., Clark, B., Horowitz, E., Madachy, R., Shelby, R., & Westland, C. (1995). Cost models for future software life cycle processes: COCOMO 2.0. Annals of Software Engineering.
171. Briand, L. C., & Wieczorek, I. (2000). Resource estimation in software engineering (Tech. Rep. No. ISERN-00-05). Germany: Fraunhofer Institute for Experimental Software Engineering.
172. Briand, L. C., & Wüst, J. (2001). Modeling development effort in object-oriented systems using design properties. IEEE Transactions on Software Engineering, 27(11), 963-986. doi:10.1109/32.965338
173. Chen, S., Cowan, C. F. N., & Grant, P. M. (1991). Orthogonal least squares learning algorithm for radial basis function networks. IEEE Transactions on Neural Networks, 2(2), 302-309. doi:10.1109/72.80341
174. st International Workshop on Predictor Models in Software Engineering (PROMISE 2005).
175. Chidamber, S., & Kemerer, C. F. (1994). A metrics suite for object-oriented design. IEEE Transactions on Software Engineering, 20(6), 476-493. doi:10.1109/32.295895
176. Conrow, E. H., & Shishido, P. S. (1997). Implementing risk management on software intensive projects. IEEE Software.
177. th International Workshop on in Program Comprehension.
178. Fayad, M. E., Laitinen, M., & Ward, R. P. (2000). Software engineering in the small. Communications of the ACM, 43(3), 115-118. doi:10.1145/330534.330555
179. Girosi, F., & Poggio, T. (1990). Networks and the best approximation property. Biological Cybernetics, 63, 169-176. doi:10.1007/BF00195855
180. Glass, R. L. (1998). Short-term and long-term remedies for runaway projects. Communications of the ACM, 41(7), 13-15. doi:10.1145/278476.278480
181. Hagan, M. T., & Menhaj, M. (1994). Training feedforward networks with the Marquardt algorithm. IEEE Transactions on Neural Networks, 5(6), 989-993. doi:10.1109/72.329697
182. th International Symposium on the Foundations of Software Engineering (SIGSOFT'98).
183. th International Conference on Software Engineering.
184. Jørgensen, M., & Shepperd, M. (2007). A systematic review of software development cost estimation studies document actions. IEEE Transactions on Software Engineering, 33(1), 33-53. doi:10.1109/TSE.2007.256943
185. Layman, L., Williams, L., & Cunningham, L. (2004). Exploring extreme programming in context: An industrial case study. Agile Development Conference.
186. Lederer, A. L., & Prasad, J. (1995). Causes of inaccurate software development cost estimates. Journal of Systems and Software, 31(2), 125-134.doi:doi:10.1016/0164-1212(94)00092-2
187. Lee, H. (1993). A structured methodology for software development effort prediction using the analytic hierarchy process. Journal of Systems and Software, 21.
188. th International Software Metrics Symposium (METRICS'03).
189. st International Workshop on Predictor Models in Software Engineering (PROMISE 2005).
190. McConnell, S. (1996). Avoiding classic mistakes. IEEE Software.
191. th International Conference on Software Engineering.
192. Miyazaki, Y., Terakado, M., Ozaki, K., & Nozaki, H. (1994). Robust regression for developing software estimation models. Journal of Systems and Software, 27(1), 3-16. doi:10.1016/0164-1212(94)90110-4
193. Mohanty, S. (1981). Software cost estimation: Present and future. Software, Practice & Experience, 11, 103-121. doi:10.1002/spe.4380110202
194. th International Symposium on Software Metrics (METRICS'04).
195. Pendharkar, C. P. C., Subramanian, G. H., & Rodger, J. A. (2005). A probabilistic model for predicting software development effort. IEEE Transactions on Software Engineering, 31(7), 615-624. doi:10.1109/TSE.2005.75
196. Poppendieck, M., & Poppendieck, T. (2003). Lean software development: An agile toolkit for software development managers. Addison-Wesley Professional.
197. Putnam, L. H. A. (1978). A general empirical solution to the macro software sizing and estimation problem. IEEE Transactions on Software Engineering, 4(4), 345-381. doi:10.1109/TSE.1978.231521
198. Sauer, C., & Cuthbertson, C. (2003). The state of IT project management in the UK 2002-2003. Templeton College, University of Oxford.
199. Shepperd, M. C., & Schofield, C. (1997). Estimating software project effort using analogies. IEEE Transactions on Software Engineering, 23(11), 736-743. doi:10.1109/32.637387
200. Shin, M., & Goel, A. L. (2000). Empirical data modeling in software engineering using radial basis functions. IEEE Transactions on Software Engineering, 26(6), 567-576. doi:10.1109/32.852743
201. th EUROMICRO.
202. Specht, D. F. (1991). A general regression neural network. IEEE Transactions on Neural Networks, 2(6), 568-576. doi:10.1109/72.97934
203. Srinivasan, K., & Fisher, D. (1995). Machine learning approaches to estimating software development effort. IEEE Transactions on Software Engineering, 21(2), 126-137. doi:10.1109/32.345828
204. Succi, G., Pedrycz, W., Djokic, S., Zuliani, P., & Russo, B. (2005). An empirical exploration of the distributions of the Chidamber and Kemerer object-oriented metrics suite. Empirical Software Engineering, 10(1), 81-104. doi:10.1023/B:EMSE.0000048324.12188.a2
205. th International Conference on Software Engineering.
206. Baheti, P., Williams, L., Gehringer, E., Stotts, D., & Smith, J. (2002). Distributed pair programming empirical studies and supporting environments (Tech. Rep. No. TR02-010). Department of Computer Science, University of North Carolina at Chapel Hill.
207. Kircher, M., Jain, P., Corsaro, A., & Levine, D. (2001). Distributed eXtreme programming. XP 2001.
208. Succi, G., Marchesi, M., Pedrycz, W., & Williams, L. (2002). Preliminary analysis of the effects of pair programming on job satisfaction. XP 2002.
209. Williams, L., Kessler, R., Cunningham, W., & Jeffries, R. (2000). Strengthening the case for pair programming. IEEE Software.
210. Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2000). Experimentation in software engineering: An introduction. Kluwer Academic Publishers.
211. st Westminster Conference on Professional Awareness in Software Engineering.
212. Basili, V. R. (1992). Software modeling and measurement: The goal/question/metric paradigm (Tech. Rep. No. CS-TR-2956). Department of Computer Science, University of Maryland.
213. Basili, V. R., & Perricone, B. (1984). Software errors and complexity: An empirical investigation. Communications of the ACM, 27(1), 42-52. doi:10.1145/69605.2085
214. Berry, D. M. (2002). The inevitable pain of software development: Why there is no silver bullet. Innovation of software and systems engineering in the future.
215. Boehm, B. (1981). Software engineering economics. Prentice-hall.
216. Brooks, F. P. (1987). No silver bullet: Essence and accidents of software engineering. IEEE Computer, 20(4).
217. Byrd, T. A., Cossik, K. C., & Zmund, R. W. (1992). A synthesis research on requirements analysis and knowledge acquisition techniques, MIS Quarterly.
218. Converse, J. M., & Presser, S. (1986). Survey questions: Handcrafting the standardized questionnaire. Sage.
219. Cook, D. A. (2002). Requirements risks can drown software projects. Crosstalk.
220. 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. doi:10.1145/50087.50089
221. Davis, G. B. (1982). Strategies for information requirements determination. IBM Systems Journal, 21(1).
222. nd IEEE Symposium on Requirements Engineering.
223. Gougen, J. A., & Linde, C. (1993). Techniques for requirements elicitation. IEEE International Conference on Requirements Engineering.
224. th International Workshop on Requirements Engineering: Foundation for Software Quality.
225. Harker, S. D. P., & Eason, K. D. (1992). The change and evolution of requirements as a challenge to the practice of software engineering. IEEE Computer.
226. Highsmith, J. (2002). Agile software development ecosystem. Addison-Wesley Professional.
227. Land, F. (1982). Adapting to changing user requirements. Information & Management, 5.
228. Lauesen, S. (2002). Software requirements styles and techniques. Addison-Wesley Professional.
229. Lubars, M., Potts, C., & Richter, C. (1993). A review of the state of practice in requirements modeling. IEEE Computer.
230. MacCormack, A., & Verganti, R. (2003). Managing the sources of uncertainty: Matching process and context in software development. Journal of Product Innovation Management, 20.
231. Marbach, G. (1996). Le ricerche di mercato. Utet.
232. March, J. G. (1998). Theories of choice and making decisions. Society, 20.
233. Marshall, C., & Rossman, G. B. (1989). Designing qualitative research. Sage Publications.
234. May, L. J. (1998). Major causes of software project failures. The Journal of Defense Software Engineering.
235. Naumann, J. D., Davis, G. B., & McKeen, J. D. (1980). Determining information requirements: A contingency method for selection of a requirements assurance strategy. Journal of Systems and Software, 1.
236. Nuseibeh, B., & Easterbrook, S. (2000). Requirements engineering: A roadmap. IEEE Computer.
237. Saiedian, H., & Dale, R. (2000). Requirements engineering: Making the connection between the software developer and the customer. Information and Software Technology, 42.
238. Siegel, S., & Castellan, N. J. (1988). Nonparametric statistics. McGraw-Hill.
239. Silverman, D. (2000). Doing qualitative research. Sage Publications.
240. Stark, G. (1998). An examination of the effects of requirements changes on software releases. Crosstalk.
241. Tan, M. (1992). The effects of verbal and nonverbal behaviors on mutual understanding: An empirical study. Communication of ACM.
242. Verganti, R. (1999). Planned flexibility: Linking anticipation and reaction in product development projects. Journal of Product Innovation Management, 16(4), 363-376. doi:10.1016/S0737-6782(98)00067-8
243. Basili, V. R. (1992). Software modeling and measurement: The goal/question/metric paradigm (Tech. Rep. No. CS-TR-2956). Department of Computer Science, University of Maryland.
244. Beck, K. (1999). Extreme programming explained. Addison-Wesley Professional.
245. Boehm, B. (2002). Six reasons for software project failure. IEEE Software.
246. Cambell, D. T., & Stanley, J. C. (1966). Experimental and quasi-experimental designs for research. Houghton Mifflin Company.
247. Charette, R. (2003). The decision is in: Agile vs. heavy methodologies. Cutter IT Journal, 2(19).
248. Converse, J. M., & Presser, S. (1986). Survey questions: Handcrafting the standardized questionnaire. Sage.
249. Highsmith, J., & Cockburn, A. (2001). Agile software development: The business of innovation. IEEE Computer.
250. Johnson, J. (1999). Turning chaos into success. Software Magazine.
251. Marbach, G. (1996). Le ricerche di mercato. Utet.
252. Petroski, H. (1992). To engineer is human: The role of failure in successful design. Vintage Books of Random House.
253. Philips, D. (1998). The software project manager's handbook principles that work at work. IEEE Computer Society Press.
254. Schumpeter, J. (1911). The theory of economic development. Harvard University Press.
255. Schwaber, K., & Beedle, M. (2001). Agile software development with SCRUM. Prentice Hall.
256. Siegel, S., & Castellan, N. J. (1988). Nonparametric statistics for behavioral sciences. McGraw-Hill.
257. Thomsett, R. (1993). Third wave project management upper Saddle River. Yourdon Press.
258. Atos-Origin. (2006). Method for qualification and selection of open source software (QSOS). Retrieved on November 11, 2008, from http://www.qsos.org/download/qsos-1.6-en.pdf
259. Duijnhouwer, F. W., & Widdows, C. (2003). Open source maturity model. Cap Gemini.
260. Golden, B. (2005). Making open source ready for the enterprise: The open source maturity model. Navica.
261. Wasserman, A., Pal, M., & Chan, C. (2005). The business readiness rating model: An evaluation framework for open source. Retrieved on November 11, 2008, from http://www.openbrr.org/ff
262. Conger, S. A. (1994). The new software engineering. International Thomson Publishing.
263. Mashiko, Y., & Basili, V. R. (1997). Using the GQM paradigm to investigate influential factors for software process improvement. Journal of Systems and Software, 36(1), 17-32. doi:10.1016/0164-1212(95)00194-8
264. QualiPSo. (2008). Trust and quality in open source systems. Retrieved on November 11, 2008, from http://www.qualipso.org/