Software engineering quality practices

Software Engineering Quality Practices

Volumn , Issue , 2005, Pages 1-256

  Kandt, Ronald Kirk ^a  

^a CALIFORNIA INSTITUTE OF TECHNOLOGY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

APPLICATION PROGRAMS;

ARCHITECTURAL FRAMEWORKS; ENGINEERING QUALITY; FUNDAMENTAL PRINCIPLES; HIGH QUALITY; PROFESSIONAL MANNER; QUALITY PRACTICE; QUALITY SOFTWARE; SOFTWARE PROFESSIONALS;

COMPUTER SOFTWARE SELECTION AND EVALUATION;

EID: 84861088662     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1201/9781420031102     Document Type: Book

References (401)

1. Engelman, C., Towards an Analysis of the LISP Programming Language, Mitre Corporation, Report 2648-IV, 1973.
2. Hirsch, P., What’s Wrong with the Air Traffic Control System?, Datamation, August 1972.
3. Brooks, F.P., Jr., The Mythical Man-Month: Essays on Software Engineering Anniversary Edition, Addison-Wesley, 1995.
4. Boehm, B.W., Software and its Impact: A Quantitative Assessment, Datamation, May 1973.
5. Gibbs, W.W., Software’s Chronic Crisis, Scientific American, 86, September 1994.
6. Casini, J. et al., Report on the Loss of the Mars Climate Orbiter Mission, Jet Propulsion Laboratory, Internal Document D-18441, 1999.
7. Floyd, R.W., The Paradigms of Programming, Commun. of the ACM, 22, 455, 1979.
8. Shaw, M., Toward Higher-Level Abstractions for Software Systems, Data and Knowledge Engineering, 5, 119, 1990.
9. Beizer, B., Software Testing Techniques, Van Nostrand Reinhold, 1990.
10. Myers, G.J., Software Reliability: Principles and Practices, Wiley, 1976.
11. Freeman, P., Software Perspectives: The System is the Message, Addison-Wesley, 1987.
12. Pardee, W.J., To Satisfy and Delight Your Customer: How to Manage for Customer Value, Dorset House, 1996.
13. Smart, K.L., Assessing Quality Documents, ACM J. of Computer Documentation, 26, 130, 2002.
14. Weigers, K.E., Creating a Software Engineering Culture, Dorset House, 1996.
15. Metzger, P. and Boddie, J., Managing a Programming Project: Processes and People, Prentice Hall, 1996.
16. Dijkstra, E., The Humble Programmer, Commun. of the ACM, 15, 859, 1972.
17. McConnell, S., Less is More, Software Development, October 1997.
18. Boehm, B. and Basili, V.R., Software Defect Reduction Top 10 List, IEEE Computer, 2, January 2001.
19. Boehm, B.W., Software Engineering Economics, Prentice Hall, 1981.
20. Clark, B.K., The Effects of Software Process Maturity on Software Development Effort, Ph.D. dissertation, Computer Science Department, University of Southern California, 1987.
21. Neufelder, A.M., System Software Reliability Training Program, Reliability Analysis Center, 2003.
22. Nikora, A.P., Software System Defect Content Prediction from Development Process and Product Characteristics, Ph.D. dissertation, University of Southern California, 1998.
23. Jones, C., Assessment and Control of Software Risks, Prentice Hall, 1994.
24. Hooks, I.F. and Farry, K.A., Customer-Centered Products: Creating Successful Products through Smart Requirements Management, AMACOM, 2001.
25. Kotonya, G. and Sommerville, I., Requirements Engineering: Processes and Techniques, Wiley, 1998.
26. Lauesen, S. and Vitner, O., Preventing Requirement Defects: An Experiment in Process Improvement, Requirements Engineering, 6, 37, 2001.
27. Lederer, A.L. and Prasad, J., Nine Management Guidelines for Better Cost Estimating, Commun. of the ACM, 35:2, 51, 1992.
28. Vosburgh, B.C. et al., Productivity Factors and Programming Environments, in Proc. of the Int. Conf. on Software Engineering, 1984, 143.
29. Christel, M.G. and Kang, K.C., Issues in Requirements Elicitation, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-92-TR-012, 1992.
30. Chudge, J. and Fulton, D., Trust and Co-operation in System Development: Applying Responsibility Modelling to the Problem of Changing Requirements, Software Engineering J., 193, May 1996.
31. Boehm, B. and Egyed, A., Software Requirements Negotiation: Some Lessons Learned, in Proc. of the Int. Conf. on Software Engineering, 1998, 503.
32. Hofmann, H.F. and Lehner, F., Requirements Engineering as a Success Factor in Software Projects, IEEE Software, 18(4), 58, 2001.
33. Kelly, J.C., Sherif, J.S., and Hops, J., An Analysis of Defect Densities Found during Software Inspections, J. of Systems and Software, 17, 111, 1992.
34. Lutz, R.R. and Mikulski, I.C., Requirements Discovery during the Testing of Safety-Critical Software, Jet Propulsion Laboratory, unpublished report, 2002.
35. Myers, G.J., The Art of Software Testing, Wiley, 1979.
36. Jones, C., Software Assessments, Benchmarks, and Best Practices, Addison-Wesley, 2000.
37. DeMarco, T., Structured Analysis and System Specification, Yourdon Press/Prentice Hall, 1978.
38. Freeman, P. and Wasserman, A.I., Software Design Techniques, IEEE Computer Society, 1980.
39. Martin, J., Information Engineering, Volumes 1-3, Prentice Hall, 1990.
40. Rumbaugh, J. et al., Object-Oriented Modeling and Design, Prentice Hall, 1991.
41. Yourdon, E., The Decline and Fall of the American Programmer, Yourdon Press/Prentice Hall, 1993.
42. Brooks, F.P., Jr., No Silver Bullet: Essence and Accidents of Software Engineering, IEEE Computer, 20(4), 10, 1987.
43. Barbacci, M.R., Klein, M.H., and Weinstock, C.B., Principles for Evaluating the Quality Attributes of a Software Architecture, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-96-TR-036, 1996.
44. McIlroy, M.D., Mass Produced Software Components, in Proc. of the NATO Conf. on Software Engineering, 1968.
45. Humphrey, W.S., Managing Technical People: Innovation, Teamwork, and the Software Process, Addison-Wesley, 1997.
46. Putnam, L.H. and Myers, W., Measures for Excellence: Reliable Software on Time, within Budget, Yourdon Press, 1992.
47. Sackman, H., Erikson, W.J., and Grant, E.E., Exploratory Experimental Studies Comparing Online and Offline Programming Performance, Commun. of the ACM, 11, 3, 1968.
48. Sackman, H., Man-Computer Problem-Solving: Experimental Evaluation of Time-Sharing and Batch Processing, Auerbach, 1970.
49. Weinberg, G.M., Understanding the Professional Programmer, Dorset House, 1988.
50. Weinberg, G.M., Quality Software Management: Systems Thinking, Dorset House, 1992.
51. Hunt, A. and Thomas, D., The Pragmatic Programmer, Addison-Wesley, 2000.
52. Booch, G., Rumbaugh, J., and Jacobson, I., The Unified Modeling Language User Guide, Addison-Wesley, 1999.
53. Carr, D.K. and Johansson, H.J., Best Practices in Reengineering: What Works and What Doesn’t in the Reengineering Process, McGraw-Hill, 1995.
54. Diaz, M. and Slago, J., How Software Process Improvement Helped Motorola, IEEE Software, 14(5), 75, 1997.
55. Laporte, C.Y. and Trudel, S., Addressing the People Issues of Process Improvement Activities at Oerlikon Aerospace, Software Process: Improvement and Practice, 4(4), 187, 1998.
56. Lawrence, P.R., How to Deal with Resistance to Change, in Management of Change, Harvard Business Review, 1991, 77.
57. Moitra, D., Managing Change for Software Process Improvement Initiatives: A Practical Experience-Based Approach, Software Process: Improvement and Practice, 4, 199, December 1998.
58. Paulk, M.C. et al., The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, 1994.
59. Kabat, D.J., Information Technologies to Manage the Next Dynamic, in The Change Management Handbook: A Road Map to Corporate Transformation, Berger, L.A. and Sikora, M.J. (Eds.), Irwin, 1994.
60. Beer, M., Eigenstat, R.A., and Spector, B., Why Change Programs Don’t Produce Change, Harvard Business Review, 68, 158, November–December 1990.
61. Burrill, C.W., Ten Ways to Kill a Quality Program, IEEE Engineering Management Review, 24, 105, 1996.
62. Hall, T., Rainer, A., and Baddoo, N., Implementing Software Process Improvement: An Empirical Study, Software Process: Improvement and Practice, 7, 3, March 2002.
63. Keen, P.G.W., Information Systems and Organizational Change, Commun. of the ACM, 24, 24, 1981.
64. Price Waterhouse Change Integration Team, Better Change: Best Practices for Transforming Your Organization, Irwin Professional Publishing, 1995.
65. Gabriel, R.P., Patterns of Software: Tales from the Software Community, Oxford University Press, 1996.
66. Fitz-enz, J., The 8 Practices of Exceptional Companies: How Great Organizations Make the Most of Their Human Assets, AMACOM, 1997.
67. Juran, J.M. and Gryna, F.M., Quality Planning and Analysis: From Product Development through Use, McGraw-Hill, 1993.
68. Pitterman, B., Telcordia Technologies: The Journey to High Maturity, IEEE Software, 17(4), 89, 2000.
69. Debou, C. and Kuntzmann-Combelles, A., Linking Softwar e Process Improvement to Business Strategies: Experiences from Industry, Software Process: Improvement and Practice, 5, 55, March 2000.
70. Kotter, J.P., Leading Change: Why Transformation Efforts Fail, Harvard Business Review, 73, 59, 1995.
71. Stelzer, D. and Mellis, W., Success Factors of Organizational Change in Software Process Improvement, Software Process: Improvement and Practice, 4, 227, 1998.
72. Eckes, G., Making Six Sigma Last, Wiley, 2001.
73. March, A., A Note on Quality: The Views of Deming, Juran, and Crosby, IEEE Engineering Management Review, 24, 6, Spring 1996.
74. Ferguson, P. et al., Software Process Improvement Works!, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-99-TR-27, 1999.
75. Floyd, R.W., The Paradigms of Programming, Commun. of the ACM, 22, 455, 1979.
76. Boehm, B.W., Software Engineering Economics, Prentice Hall, 1981.
77. Weigers, K.E., Software Requirements, Microsoft Press, 2003.
78. Butler, K. and Lipke, W., Software Process Achievement at Tinker Air Force Base, Oklahoma, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-2000-TR-14, 2000.
79. Grady, R.B., Successful Software Process Improvement, Prentice Hall, 1997.
80. Haley, T. et al., Raytheon Electronic Systems Experience in Software Process Improvement, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-95-TR-17, 1995.
81. Herbsleb, J.D. and Goldenson, D.R., A Systematic Survey of CMM Experience and Results, in Proc. of the Int. Conf. on Software Engineering, 1996, 323.
82. Willis, R.R. et al., Hughes Aircraft’s Widespread Deployment of a Continuously Improving Software Process, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-98-TR-6, 1998.
83. Zelkowitz, M.V., Software Engineering Technology Infusion within NASA, IEEE Trans. on Engineering Management, 43, 250, 1996.
84. Dion, R., Process Improvement and the Corporate Balance Sheet, IEEE Software, 10(4), 28, 1993.
85. Rainer, A. and Hall, T., An Analysis of Some Core Studies of Software Process Improvement, Software Process: Improvement and Practice, 6, 169, 2001.
86. Fowler, P. and Rifkin, S., Software Engineering Process Group Guide, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-90-TR-24, 1990.
87. Basili, V.R. et al., Lessons Learned from 25 Years of Process Improvement: The Rise and Fall of the NASA Software Engineering Laboratory, in Proc. of the Int. Conf. on Software Engineering, 2002, 69.
88. Crosby, P.B., Quality is Free, McGraw-Hill, 1979.
89. Wilson, D.N., Hall, T., and Baddoo, N., A Framework for Evaluation and Prediction of Software Process Improvement Success, J. of Systems and Software, 59, 135, 2001.
90. Humphrey, W.S., Snyder, T.R., and Willis, R.R., Software Process Improvement at Hughes Aircraft, IEEE Software, 8(4), 11, 1991.
91. Markus, M.L., Power, Politics, and MIS Implementation, Commun. of the ACM, 26, 430, 1983.
92. McGarry, F., A Presentation on Software Process Improvement, Jet Propulsion Laboratory, 2002.
93. Curtis, B., The Global Pursuit of Process Maturity, IEEE Software, 76, July/August 2000.
94. Conner, D.R., The Next Generation of Fire Walkers, in The Handbook of Change Management: A Road Map to Corporate Transformation, Berger, L.A. and Sikora, M J. (Eds.), Irwin, 1994, 257.
95. Labovitz, G. and Rosansky, V., The Power of Alignment, Wiley, 1997.
96. Humphrey, W.S., Managing Technical People: Innovation, Teamwork, and the Software Process, Addison-Wesley, 1997.
97. Rothman, J., Hiring the Best Knowledge Workers, Techies, and Nerds: The Secrets and Science of Hiring Technical People, Dorset House, 2004.
98. Kaltio, T. and Kinnula, A., Deploying the Defined SW Process, Software Process: Improvement and Practice, 5(1), 65, 2000.
99. Freeman, P., Software Perspectives: The System is the Message, Addison-Wesley, 1987.
100. Weinberg, G.M., Understanding the Professional Programmer, Dorset House, 1988.
101. Herman, R.E., Keeping Good People: Strategies for Solving the Dilemma of the Decade, Oakhill Press, 1997.
102. Kitson, D.H. and Masters, S.M., An Analysis of SEI Software Assessment Results, in Proc. of the Int. Conf. on Software Engineering, 1993.
103. Weigers, K.E., Creating a Software Engineering Culture, Dorset House, 1996.
104. Leffingwell, D. and Widrig, D., Managing Software Requirements: A Use Case Approach, Addison-Wesley, 2003.
105. Brodman, J.G. and Johnson, D.L., Return on Investment (ROI) from Software Process Improvement as Measured by US Industry, Software Process: Improvement and Practice, 1, 35, August 1995.
106. Kozar, K., Adopting Systems Development Methods: An Exploratory Study, J. of Management Information Systems, 5(4), 73, 1989.
107. Riemenschneider, C.K., Hardgrave, B.C., and Davis, F.D., Explaining Software Developer Acceptance of Methodologies: A Comparison of Five Theoretical Models, IEEE Trans. on Software Engineering, 28, 1135, 2002.
108. McGarry, F. et al., Software Process Improvement in the NASA Software Engineering Laboratory, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-94-TR-22, 1994.
109. Wohlwend, H. and Rosenbaum, S., Schlumberger’s Software Improvement Program, IEEE Trans. on Software Engineering, 20, 833, 1994.
110. Berger, L.A., Change Management, in The Handbook of Change Management: A Road Map to Corporate Transformation, Berger, L.A. and Sikora, M.J. (Eds.), Irwin, 1994, 3.
111. Baddoo, N. and Hall, T., Motivators of Software Process Improvement: An Analysis of Practitioners’ Views, J. of Systems and Software, 62, 85, 2002.
112. Hammer, M., Beyond Reengineering, HarperCollins, 1996.
113. Carr, D.K., Hard, K.J., and Trahant, W.J., Managing the Change Process: A Field Book for Change Agents, Consultants, Team Leaders, and Reengineering Managers, McGraw-Hill, 1996.
114. Abrahamsson, P., Commitment Development in Software Process Improvement: Critical Misconceptions, in Proc. of the Int. Conf. on Software Engineering, 2001, 71.
115. Herbsleb, J.D. and Grinter, R.E., Conceptual Simplicity Meets Organizational Complexity: Case Study of a Corporate Metrics Program, in Proc. of the Int. Conf. on Software Engineering, 1998, 271.
116. Boehm, B.W., Software Engineering Economics, Prentice Hall, 1981.
117. DeMarco, T. and Lister, T., Peopleware: Productive Projects and Teams, Dorset House, 1987.
118. Humphrey, W.S., Managing Technical People: Innovation, Teamwork, and the Software Process, Addison-Wesley, 1997.
119. Paulk, M.C. et al., The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, 1994.
120. Weigers, K.E., Creating a Software Engineering Culture, Dorset House, 1996.
121. Curtis, B., Substantiating Programmer Variability, Proc. of the IEEE, 69, 846, 1981.
122. Curtis, B. et al., Software Psychology: The Need for an Interdisciplinary Program, Proc. of the IEEE, 74, 1092, 1986.
123. DeMarco, T. and Lister, T., Programmer Performance and the Effects of the Workplace, in Proc. of the Int. Conf. on Software Engineering, 1985, 268.
124. McConnell, S., Rapid Development: Taming Wild Software Schedules, Microsoft Press, 1996.
125. Mills, H., Software Productivity, Brown, 1983.
126. Sackman, H., Erikson, W.J., and Grant, E.E., Exploratory Experimental Studies Comparing Online and Offline Programming Performance, Commun. of the ACM, 11, 3, 1968.
127. Valett, J.D. and McGarry, F.E., A Summary of Software Measurement Experiences in the Software Engineering Laboratory, J. of Systems and Software, 9, 137, 1989.
128. Putnam, L.H. and Myers, W., Measures for Excellence: Reliable Software on Time, within Budget, Yourdon Press, 1992.
129. Sackman, H., Man-Computer Problem-Solving: Experimental Evaluation of Time-Sharing and Batch Processing, Auerbach, 1970.
130. Weinberg, G.M., Understanding the Professional Programmer, Dorset House, 1988.
131. Weinberg, G.M., Quality Software Management: Systems Thinking, Dorset House, 1992.
132. Gibbs, W.W., Software’s Chronic Crisis, Scientific American, September 1994, 86.
133. Sheppard, S.B. et al., Modern Coding Practices and Programmer Performance, IEEE Computer, 12(12), 41, 1979.
134. Curtis, B., Krasner, H., and Iscoe, N., A Field Study of the Software Design Process for Large Systems, Commun. of the ACM, 31, 1268, 1988.
135. Yourdon, E., The Decline and Fall of the American Programmer, Yourdon Press/Prentice Hall, 1993.
136. Brooks, F.P., Jr., The Mythical Man-Month: Essays on Software Engineering Anniversary Edition, Addison-Wesley, 1995.
137. Brooks, F.P., Jr., No Silver Bullet: Essence and Accidents of Software Engineering, IEEE Computer, 20(4), 10, 1987.
138. Larman, C., Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design, Prentice Hall, 1998.
139. Bisant, D.B. and Groninger, L., Cognitive Processes in Software Fault Detection: A Review and Synthesis, Int. J. of Human–Computer Interaction, 5, 189, 1993.
140. Brooks, R., Towards a Theory of the Comprehension of Computer Programs, Int. J. of Man–Machine Studies, 18, 543, 1983.
141. Computer Science Accreditation Board, Computer Science Programs Accredited by the Computer Science Accreditation Commission of the Computing Sciences Accreditation Board, http://csab.org/~csab/acrsch.html.
142. Curtis, B., Hefley, W.E., and Miller, S.A., People Capability Maturity Model, Version 2.0, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-2001-MM-01, 2001.
143. Rothman, J., Hiring the Best Knowledge Workers, Techies, and Nerds: The Secrets and Science of Hiring Technical People, Dorset House, 2004.
144. Page-Jones, M., The Seven Stages of Expertise in Software Engineering, American Programmer, July–August 1990.
145. Herman, R.E., Keeping Good People: Strategies for Solving the Dilemma of the Decade, Oakhill Press, 1997.
146. Levesque, J.D., Complete Manual for Recruiting, Hiring, and Retaining Quality Employees, Prentice Hall, 1996.
147. Mercer, M.W., Hire the Best … and Avoid the Rest, AMACOM, 1993.
148. Jones, C., Assessment and Control of Software Risks, Prentice Hall, 1994.
149. Weigers, K.E., Software Requirements, Microsoft Press, 2003.
150. Mead, N., Tobin, L., and Couturiaux, S., Best Training Practices within the Software Engineering Industry, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-96-TR-034, 1996.
151. McCue, G.M., IBM’s Santa Teresa Laboratory — Architectural Design for Program Development, IBM Systems Journal, 17, 4, 1978.
152. Wasserman, A.I., The Future of Programming, Commun. of the ACM, 25, 196, 1982.
153. Weinberg, G.M., The Psychology of Computer Programming, Van Nostrand-Reinhold, 1971.
154. Schulmeyer, G.G., Zero Defect Software, McGraw-Hill, 1990.
155. Gabriel, R.P., Patterns of Software: Tales from the Software Community, Oxford University Press, 1996.
156. Dijkstra, E.W., Computing Science: Achievements and Challenges, ACM SIGAPP Applied Computing Review, 7(2), 2, 1999.
157. McConnell, S., Rapid Development: Taming Wild Software Schedules, Microsoft Press, 1996.
158. Humphrey, W.S., Managing Technical People: Innovation, Teamwork, and the Software Process, Addison-Wesley, 1997.
159. Jones, C., Assessment and Control of Software Risks, Yourdon Press, 1994.
160. Boehm, B. et al., Cost Models for Future Software Life Cycle Processes: COCOMO 2.0, Annals of Software Engineering, Special Volume on Software Process and Product Measurement, Arthur, J.D. and Henry, S.M. (Eds.), J.C. Baltzer AG Science Publishers, 1995.
161. Brooks, F.P., Jr., The Mythical Man-Month: Essays on Software Engineering Anniversary Edition, Addison-Wesley, 1995.
162. Lederer, A.L. and Prasad, J., Nine Management Guidelines for Better Cost Estimating, Commun. of the ACM, 35:2, 51, February 1992.
163. DeMarco, T. and Lister, T., Peopleware: Productive Projects and Teams, Dorset House, 1987.
164. Van Genuchten, M., Why is Software Late? An Empirical Study of the Reasons for Delay in Software Development, IEEE Trans. on Software Engineering, 17, 582, 1991.
165. Stubberud, A.R., A Hard Look at Software, IEEE Control Systems, 9, February 1985.
166. Putnam, L.H. and Myers, W., Measures for Excellence: Reliable Software on Time, within Budget, Yourdon Press, 1992.
167. Daly, E.B., Management of Software Development, IEEE Trans. on Software Engineering, SE-3, 229, 1977.
168. Stephenson, W.E., An Analysis of the Resources Used in the SAFEGUARD System Software Development, Proc. of the Int. Conf. on Software Engineering, 312, 1976.
169. Putnam, L.H., A General Empirical Solution to the Macro Software Sizing and Estimating Problem, IEEE Trans. on Software Engineering, SE-4, 345, 1978.
170. Norden, P.V., Useful Tools for Project Management, in Operations Research in Research and Development, Dean, B.V. (Ed.), Wiley, 1963.
171. Weinberg, G.M., Understanding the Professional Programmer, Dorset House, 1988.
172. Boehm, B. and Huang, L.G., Value-Based Software Engineering: A Case Study, IEEE Computer, 36, 33, March 2003.
173. Grady, R.B. and Caswell, D.L., Software Metrics: Establishing a Company-Wide Program, Prentice Hall, 1987.
174. Gabriel, R.P., Patterns of Software: Tales from the Software Community, Oxford University Press, 1996.
175. Cockburn, A., Agile Software Development, Addison-Wesley, 2001.
176. Paulk, M.C. et al., The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, 1994.
177. Tichy, W.F., Design, Implementation, and Evaluation of a Revision Control System, in Proc. of the Int. Conf. on Software Engineering, 1982, 58.
178. Rochkind, M.J., The Source Code Control System, IEEE Trans. on Software Engineering, SE-1, 364, 1975.
179. Kandt, R.K., Software Configuration Management Principles and Best Practices, in Proc. of the Product Focused Software Process Improvement Conference, Oivo, M. and Komi-Sirvio, S. (Eds.), Springer-Verlag, 2002, 300.
180. Wingerd, L. and Seiwald, C., High-Level Best Practices in Software Configuration Management, in Proc. of the Int. Workshop on Software Configuration Management, 1998.
181. Babich, W.A., Software Configuration Management: Coordination for Team Productivity, Addison-Wesley, 1986.
182. Jones, C., Software Assessments, Benchmarks, and Best Practices, Addison-Wesley, 2000.
183. Berlack, H.R., Software Configuration Management, Wiley, 1992.
184. Bersoff, E.H., Software Configuration Management, An Investment in Product Integrity, Prentice Hall, 1980.
185. Whitgift, D., Methods and Tools for Software Configuration Management, Wiley, 1991.
186. Berczuk, S.P. and Appleton, B., Software Configuration Management Patterns: Effective Teamwork, Practical Integration, Addison-Wesley, 2003.
187. Rigg, W., Burrows, C., and Ingram, P., Ovum Evaluates: Configuration Management Tools, Ovum Limited, 1995.
188. McConnell, S., Rapid Development: Taming Wild Software Schedules, Microsoft Press, 1996.
189. Robertson, S. and Robertson, J., Mastering the Requirements Process, Addison-Wesley, 1999.
190. Kotonya, G. and Sommerville, I., Requirements Engineering: Processes and Techniques, Wiley, 1998.
191. Hofmann, H.F. and Lehner, F., Requirements Engineering as a Success Factor in Software Projects, IEEE Software, 18(4), 58, 2001.
192. Hooks, I.F. and Farry, K.A., Customer-Centered Products: Creating Successful Products through Smart Requirements Management, AMACOM, 2001.
193. Christel, M.G. and Kang, K.C., Issues in Requirements Elicitation, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-92-TR-012, 1992.
194. Booch, G., Rumbaugh, J., and Jacobson, I., The Unified Modeling Language User Guide, Addison-Wesley, 1999.
195. Weigers, K.E., Software Requirements, Microsoft Press, 2003.
196. Young, R.R., The Requirements Engineering Handbook, Artech House, 2004.
197. Grünbacher, P. et al., Repeatable Quality Assurance Techniques for Requirements Negotiations, in Proc. of the Hawaii Int. Conf. on System Sciences, 2003, 23.
198. Vitalari, N.P. and Dickson, G.W., Problem Solving for Effective Systems Analysis: An Experimental Exploration, Commun. of the ACM, 26, 948, 1983.
199. Humphrey, W.S., Managing Technical People: Innovation, Teamwork, and the Software Process, Addison-Wesley, 1997.
200. Vosburgh, J.B., Wolverton, R., Albers, B., Malec, H., Hoben, S., and Liu, Y., Productivity Factors and Programming Environments, in Proc. of the Int. Conf. on Software Engineering, 1984, 143.
201. Zowghi, D. and Nurmuliani, N., A Study of the Impact of Requirements Volatility on Software Project Performance, in Proc. of the Asia-Pacific Software Engineering Conf., 2002, 3.
202. Blum, B.I., Beyond Programming: To a New Era of Design, Oxford University Press, 1996.
203. Institute for Electrical and Electronics Engineers, IEEE Guide for Information Technology — System Definition — Concept of Operations (ConOps) Document, IEEE Computer Society, IEEE Std. 1362-1998, 1998.
204. Software Engineering Standards Committee, IEEE Recommended Practice for Software Requirements Specifications, The Institute of Electrical and Electronics Engineers, IEEE Std. 830-1998, 1998.
205. Potts, C., Takahashi, K., and Antón, A.I., Inquiry-Based Requirements Analysis, IEEE Software, 11, 21, March 1994.
206. Lauesen, S. and Vitner, O., Preventing Requirement Defects: An Experiment in Process Improvement, Requirements Engineering, 6, 37, 2001.
207. Curtis, B., Krasner, H., and Iscoe, N., A Field Study of the Software Design Process for Large Systems, Commun. of the ACM, 31, 1268, 1988.
208. Potts, C., Invented Requirements and Imagined Customers: Requirements Engineering for Off-the-Shelf Software, in Proc. of the IEEE International Symp. on Requirements Engineering, 1995, 128.
209. Stark, G., Skillicorn, A., and Smeele, R., A Micro and Macro Based Examination of the Effects of Requirements Changes on Aerospace Software Maintenance, in Proc. of the IEEE Aerospace Conf., 4, 165, 1998.
210. Szyperski, C., Component Software: Beyond Object-Oriented Programming, Addison-Wesley, 1998.
211. Barbacci, M. et al., Quality Attributes, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-95-TR-021, 1995.
212. Barbacci, M.R., Klein, M.H., and Weinstock, C.B., Principles for Evaluating the Quality Attributes of a Software Architecture, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-96-TR-036, 1996.
213. Bass, L. and John, B.E., Linking Usability to Software Architecture Patterns through General Scenarios, J. of Systems and Software, 66, 187, 2003.
214. Folmer, E., van Gurp, J., and Bosch, J., A Framework for Capturing the Relationship between Usability and Software Architecture, Software Process Improvement and Practice, 8, 67, 2003.
215. Pardee, W.J., To Satisfy and Delight Your Customer: How to Manage for Customer Value, Dorset House, 1996.
216. Miller, G.A., The Magical Number Seven, Plus or Minus Two: Some limits on Our Capacity for Processing Information, Psychological Review, 63, 81, March 1956.
217. Curtis, B. et al., Software Psychology: The Need for an Interdisciplinary Program, Proc. of the IEEE, 74, 1092, 1986.
218. Robinson, W.N., Pawlowski, S.D., and Volkov, V., Requirements Interaction Management, ACM Computing Surveys, 35, 132, June 2003.
219. Sommerville, I. and Sawyer, P., Requirements Engineering: A Good Practice Guide, Wiley, 1997.
220. Daneva, M., Lessons Learnt from Five Years of Experience in ERP Requirements Engineering, in Proc. of the IEEE Int. Requirements Engineering Conf., 2003, 45.
221. Gabriel, R.P., Patterns of Software: Tales from the Software Community, Oxford University Press, 1996.
222. Carmone, F.J., Kara, A., and Zanakis, S.H., A Monte Carlo Investigation of Incomplete Pairwise Comparison Matrices in AHP, European J. of Operational Research, 102, 538, 1997.
223. Harker, P.T., Incomplete Pairwise Comparison in the Analytic Hierarchy Process, Mathematical Modelling, 9, 837, 1987.
224. Harker, P.T., Alternative Modes of Questioning in the Analytic Hierarchy Process, Mathematical Modelling, 9, 353, 1987.
225. Karlsson, J., Software Requirements Prioritizing, in Proc. of the Int. Conf. on Requirements Engineering, 1996, 110.
226. Satay, T.L., The Analytic Hierarchy Process, McGraw-Hill, 1980.
227. Satay, T.L., Priority Setting in Complex Problems, IEEE Trans. on Engineering Management, EM-30, 140, 1983.
228. Potts, C. and Bruns, G., Recording the Reasons for Design Decisions, in Proc. of the Int. Conf. on Software Engineering, 1988, 418.
229. Wilson, W.M., Rosenberg, L.H., and Hyatt, L.E., Automated Analysis of Requirement Specifications, in Proc. of the Int. Conf. on Software Engineering, 1997, 161.
230. Glass, R.L., Software Reliability Guidebook, Prentice Hall, 1979.
231. Leveson, N.G., Safeware: System Safety and Computers, Addison-Wesley, 1995.
232. Shaw, M.L.G. and Gaines, B.R., Requirements Acquisition, Software Engineering Journal, 11, 149, May 1996.
233. Prowell, S.J. and Poore, J.H., Sequence-Based Specification of Deterministic Systems, Software — Practice and Experience, 28, 329, 1998.
234. Prowell, S.J. et al., Cleanroom Software Engineering: Technology and Process, Addison-Wesley, 1999.
235. Prowell, S.J. and Poore, J.H., Foundations of Sequence-Based Software Specification, IEEE Trans. on Software Engineering, 29, 417, 2003.
236. Chudge, J. and Fulton, D., Trust and Co-operation in System Development: Applying Responsibility Modelling to the Problem of Changing Requirements, Software Engineering Journal, 11, 193, May 1996.
237. Jones, C., Assessment and Control of Software Risks, Prentice Hall, 1994.
238. Gibbs, W.W., Software’s Chronic Crisis, Scientific American, 271:3, 86, September 1994.
239. Crnkovic, I., Funk, P., and Larsson, M., Processing Requirements by Software Configuration Management, in Proc. of the EUROMICRO Conference, 2, 260, 1999.
240. Nguyen, L., Armarego, J., and Swatman, P.A., Understanding Requirements Engineering: A Challenge for Practice and Education, School of Management Information Systems, Deakin University, School Working Papers 2002/10, 2002.
241. Boehm, B. and Egyed, A., Software Requirements Negotiation: Some Lessons Learned, in Proc. of the Int. Conf. on Software Engineering, 1998, 503.
242. Parnas, D.L., Designing Software for Ease of Extension and Contraction, IEEE Trans. on Software Engineering, SE-5, 128, 1979.
243. Curtis, B., Krasner, H., and Iscoe, N., A Field Study of the Software Design Process for Large Systems, Commun. of the ACM, 31, 1268, 1988.
244. Goel, V. and Pirolli, P., The Structure of Design Problem Spaces, Cognitive Science, 16, 395, 1992.
245. Guindon, R., Designing the Design Process: Exploiting Opportunistic Thoughts, Human–Computer Interaction, 5, 305, 1990.
246. Vitalari, N.P. and Dickson, G.W., Problem Solving for Effective Systems Analysis: An Experimental Exploration, Commun. of the ACM, 26, 948, 1983.
247. Shrobe, H.E., Dependency Directed Reasoning for Complex Program Understanding, Artificial Intelligence Laboratory, Massachusetts Institute of Technology, Technical Report 503, 1979.
248. Curtis, B. et al., Software Psychology: The Need for an Interdisciplinary Program, Proc. of the IEEE, 74, 1092, 1986.
249. Rosson, M.B. and Alpert, S.R., The Cognitive Consequences of Object-Oriented Design, Human–Computer Interaction, 5, 345, 1990.
250. Thomas, J.C. and Carroll, J.M., The psychological study of design, IBM T. J. Watson Research Center, Research Report RC7695, 1979.
251. Wirth, N., On the Composition of Well-Structured Programs, ACM Computing Surveys, 6, 247, 1974.
252. Larman, C., Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design, Prentice Hall, 1998.
253. Dijkstra, E.W., The Humble Programmer, Commun. of the ACM, 15, 859, 1972.
254. Booch, G., Rumbaugh, J., and Jacobson, I., The Unified Modeling Language User Guide, Addison-Wesley, 1999.
255. Gabriel, R.P., Patterns of Software: Tales from the Software Community, Oxford University Press, 1996.
256. Martin, R.C., Agile Software Development: Principles, Patterns, and Practices, Prentice Hall, 2003.
257. Brooks, F.P. Jr., The Mythical Man-Month: Essays on Software Engineering Anniversary Edition, Addison-Wesley, 1995.
258. Pressman, R.S., Software Engineering: A Practitioner’s Approach, McGraw-Hill, 1992.
259. Brooks, F.P., Jr., No Silver Bullet: Essence and Accidents of Software Engineering, IEEE Computer, 20, 10, 1987.
260. Knuth, D.E., Structured Programming with go to Statements, ACM Computing Surveys, 6, 261, 1974.
261. Brooks, R., Towards a Theory of the Comprehension of Computer Programs, Int. J. of Man–Machine Studies, 18, 543, 1983.
262. Wirth, N., Program Development by Stepwise Refinement, Commun. of the ACM, 14, 221, 1971.
263. Gunter, C., Mitchell, J., and Notkin, D., Strategic Directions in Software Engineering and Programming Languages, ACM Computing Surveys, 28, 727, 1996.
264. Parnas, D.L., On the Criteria to Be Used in Decomposing Systems into Modules, Commun. of the ACM, 15, 1053, 1971.
265. Ghezzi, C., Jazayeri, M., and Mandrioli, D., Fundamentals of Software Engineering, Prentice Hall, 1991.
266. Stevens, W., Myers, G., and Constantine, L., Structured Design, IBM Systems Journal, 13, 115, 1974.
267. Beizer, B., Software Testing Techniques, Van Nostrand Reinhold, 1990.
268. Hohmann, L., Journey of the Software Professional: A Sociology of Software Development, Prentice Hall, 1997.
269. Sommerville, I., Software Engineering, Addison-Wesley, 1992.
270. Shneiderman, B., Software Psychology, Little-Brown, 1980.
271. Succi, G. et al., Practical Assessment of the Models for Identification of Defect-Prone Classes in Object-Oriented Commercial Systems Using Design Metrics, J. of Systems and Software, 65, 1, 2003.
272. Selby, R.W. and Basili, V.R., Analyzing Error-Prone System Structure, IEEE Trans. on Software Engineering, 17, 141, 1991.
273. Szyperski, C., Component Software: Beyond Object-Oriented Programming, Addison-Wesley, 1998.
274. Blum, B.I., Beyond Programming: To a New Era of Design, Oxford University Press, 1996.
275. Kang, K.C. et al., Feature-Oriented Domain Analysis (FODA) Feasibility Study, Software Engineering Institute, Carnegie Mellon University, Technical Report CMU/SEI-90-TR-21, 1990.
276. Rumbaugh, J. et al., Object-Oriented Modeling and Design, Prentice Hall, 1991.
277. Neighbors, J.M., The Evolution from Software Components to Domain Analysis, Int. J. of Software Engineering and Knowledge Engineering, 2, 325, 1992.
278. Jones, C., Software Assessments, Benchmarks, and Best Practices, Addison-Wesley, 2000.
279. Leveson, N.G., Safeware: System Safety and Computers, Addison-Wesley, 1995.
280. Hunt, A. and Thomas, D., The Pragmatic Programmer, Addison-Wesley, 2000.
281. Karr, M. and Loveman, D.B., Incorporation of Units into Programming Languages, Commun. of the ACM, 21, 385, 1978.
282. Shumate, K. and Keller, M., Software Specification and Design: A Disciplined Approach for Real-Time Systems, Wiley, 1992.
283. Dijkstra, E.W., Go To Statement Considered Harmful, Commun. of the ACM, 11, 147, 1968.
284. Lipton, R.J., Eisenstadt, S.C., and DeMillo, R.A., The Complexity of Control Structures and Data Structures, in Proc. of the ACM Symp. on the Theory of Computing, 7, 1975, 186.
285. Nikora, A. and Munson, J., Determining Fault Insertion Rates for Evolving Software Systems, in Proc. of the Int. Symp. on Software Reliability Engineering, 1998.
286. Wulf, W. and Shaw, M., Global Variables Considered Harmful, SIGPLAN Notices, 8, 28, February 1973.
287. Wirth, N., A Plea for Lean Software, IEEE Computer, 28, 64, 1995.
288. Winograd, T., Beyond Programming Languages, Commun. of the ACM, 22, 391, 1979.
289. McConnell, S., Rapid Development: Taming Wild Software Schedules, Microsoft Press, 1996.
290. Fenton, N.E. and Ohlsson, N., Quantitative Analysis of Faults and Failures in a Complex Software System, IEEE Trans. on Software Engineering, 26, 797, 2000.
291. Weinberg, G.M., Quality Software Management: Systems Thinking, Dorset House, 1992.
292. Myers, G.J., The Art of Software Testing, Wiley, 1979.
293. Paulk, M.C. et al., The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, 1994.
294. Freeman, P. and Newell, A., A Model for Functional Reasoning in Design, in Proc. of the Int. Joint Conf. on Artificial Intelligence, 1971.
295. Kandt, R.K., Pegasus: A Software Design Tool, in Proc. of the Hawaii Int. Conf. on System Sciences, 2, 650, 1985.
296. Kandt, R.K., A Tool to Support Competitive Argumentation, J. of Management Information Systems, 3, 54, Spring 1987.
297. Moran, T.P. and Carroll, J.M., Design Rationale: Concepts, Techniques, and Use, Lawrence Erlbaum, 1996.
298. Halstead, M.H., Elements of Software Science, Elsevier North-Holland, 1977.
299. McCabe, T.J., A Complexity Measure, IEEE Trans. on Software Engineering, SE-2, 308, 1976.
300. Henderson-Sellers, B., Object-Oriented Metrics: Measures of Complexity, Prentice Hall, 1995.
301. Fairley, R., Software Engineering Concepts, McGraw-Hill, 1985.
302. Davis, J.S., Chunks: A Basis for Complexity Measurement, Information Processing and Management, 20(12), 119, 1984.
303. Miller, G.A., The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information, Psychological Review, 63, 81, March 1956.
304. Cowan, N., The Magical Number 4 in Short-Term Memory: A Reconsideration of Mental Storage Capacity, Behavioral and Brain Sciences, 24, 87, 2001.
305. Dijkstra, E., Structured Programming, in Classics in Software Engineering, Yourdon, E.N. (Ed.), Yourdon Press, 1979, 43.
306. Nii, H.P., Blackboard Systems, Knowledge Systems Laboratory, Stanford University, Report No. KSL 86-18, 1986.
307. Hayes-Roth, B. et al., A Domain-Specific Software Architecture for Adaptive Intelligent Systems, IEEE Trans. on Software Engineering, 21, 288, 1995.
308. Gomaa, H., Software Development of Real-Time Systems, Commun. of the ACM, 29, 657, 1986.
309. Hunt, A. and Thomas, D., The Pragmatic Programmer, Addison-Wesley, 2000.
310. Paulk, M.C. et al., The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, 1994.
311. Brooks, F.P., Jr., The Mythical Man-Month: Essays on Software Engineering Anniversary Edition, Addison-Wesley, 1995.
312. Wasserman, A.I., The Future of Programming, Commun. of the ACM, 25, 196, 1982.
313. Jones, C., Software Assessments, Benchmarks, and Best Practices, Addison-Wesley, 2000.
314. Brooks, F.P., Jr., No Silver Bullet: Essence and Accidents of Software Engineering, IEEE Computer, 20, 10, April 1987.
315. Glass, R.L., Software Reliability Guidebook, Prentice Hall, 1979.
316. Putnam, L.H. and Myers, W., Measures for Excellence: Reliable Software on Time, within Budget, Yourdon Press, 1992.
317. Miara, R.J. et al., Program Indentation and Comprehension, Commun. of the ACM, 26, 861, 1983.
318. Brooks, R., Towards a Theory of the Comprehension of Computer Programs, Int. J. of Man–Machine Studies, 18, 543, 1983.
319. Rumbaugh, J. et al., Object-Oriented Modeling and Design, Prentice Hall, 1991.
320. Gordon, V.S. and Bieman, J.M., Rapid Prototyping: Lessons Learned, IEEE Software, January 1995.
321. Bustard, D.W., Concepts of Concurrent Programming, Software Engineering Institute, Carnegie Mellon University, Technical Report SEI-CM-24, 1990.
322. Myers, G.J., Software Reliability: Principles and Practices, Wiley, 1976.
323. Beizer, B., Software Testing Techniques, Van Nostrand Reinhold, 1990.
324. Fagan, M.E., Design and Code Inspections to Reduce Errors in Program Development, IBM Systems Journal, 15, 182, 1976.
325. Bush, M.W., Improving Software Quality: The Use of Formal Inspections at the Jet Propulsion Laboratory, in Proc. of the Int. Conf. on Software Engineering, 1990, 196.
326. Ackerman, A.F., Buchwald, L.S., and Lewski, F.H., Software Inspections: An Effective Verification Process, IEEE Software, 6:3, 31, May 1989.
327. Fagan, M.E., Advances in Software Inspections, IEEE Trans. on Software Engineering, 12, 744, 1986.
328. Gilb, T. and Graham, D., Software Inspection, Addison-Wesley, 1993.
329. Laitenberger, O., El Emam, K., and Harbich T.G., An Internally Replicated Quasi-Experimental Comparison of Checklist and Perspective-Based Reading of Code Documents, IEEE Trans. on Software Engineering, 27, 387, 2001.
330. Myers, G.J., A Controlled Experiment in Program Testing and Code Walk-throughs/Inspections, Commun. of the ACM, 21, 760, 1978.
331. Myers, G.J., The Art of Software Testing, Wiley, 1979.
332. Porter, A.A. et al., Understanding the Sources of Variation in Software Inspections, ACM Trans. on Software Engineering and Methodology, 7, 41, 1998.
333. Basili, V.R. and Selby, R.W., Comparing the effectiveness of software testing techniques, IEEE Trans. on Software Engineering, 13, 1278, 1987.
334. Biffl, S., Freimut, B., and Laitenberger, O., Investigating the Cost-Effective-ness of Reinspections in Software Development, in Proc. of the Int. Conf. on Software Engineering, 2001, 155.
335. Briand, L. et al., Using Simulation to Build Inspection Efficiency Benchmarks for Development Projects, in Proc. of the Int. Conf. on Software Engineering, 1998, 340.
336. Rifkin, S. and Deimel, L., Program Comprehension Techniques Improve Software Inspections: A Case Study, in Proc. of the Int. Workshop on Program Comprehension, 2000, 131.
337. Brooks, F.P., Jr., The Mythical Man-Month: Essays on Software Engineering Anniversary Edition, Addison-Wesley, 1995.
338. Biffl, S. and Halling, M., Investigating the Influence of Inspector Capability Factors with Four Inspection Techniques on Inspection Performance, in Proc. of the Int. Symp. on Software Metrics, 2002, 1.
339. Miller, J., Wood, M., and Roper, M., Further Experiences with Scenarios and Checklists, Empirical Software Engineering, 3, 37, 1998.
340. Parnas, D.L. and Weiss, D.M., Active Design Reviews: Principles and Practices, Proc. of the Int. Conf. on Software Engineering, 1985, 215.
341. Porter, A., Votta, L., and Basili, V., Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment, IEEE Trans. on Software Engineering, 21, 563, 1995.
342. Porter, A. and Votta, L., Comparing Detection Methods for Software Requirements Inspections: A Replication using Professional Subjects, Empirical Software Engineering, 3, 355, 1998.
343. Bisant, D. and Lyle, J., A Two-Person Inspection Method to Improve Programming Productivity, IEEE Trans. on Software Engineering, 15, 1294, 1989.
344. El Emam, K. and Laitenberger, O., Evaluating Capture-Recapture Models with Two Inspectors, IEEE Trans. on Software Engineering, 27, 851, 2001.
345. Kusomoto, S. et al., A Promising Approach to Two-Person Software Review in an Educational Environment, J. of Systems and Software, 40, 115, 1998.
346. Neu, H. et al., Simulation-Based Risk Reduction for Planning Inspections, in Proc. of the Fourth Int. Conf. on Product Focused Software Process Improvement, Springer, 2002, 78.
347. Porter, A. et al., An Experiment to Assess the Cost-Benefi ts of Code Inspections in Large Scale Software Development, IEEE Trans. on Software Engineering, 23, 329, 1997.
348. Johnson, P. and Tjahjono, D., Does Every Inspection Really Need a Meeting?, Empirical Software Engineering, 3, 9, 1998.
349. Laitenberger, O. and DeBaud, J.M., An Encompassing Life-Cycle Centric Survey of Software Inspection, J. of Systems and Software, 50, 5, 2000.
350. Eick, S.G. et al., Estimating Software Fault Content before Coding, in Proc. of the Int. Conf. on Software Engineering, 1992, 59.
351. Humphrey, W.S., Managing the Software Process, Addison-Wesley, 1989.
352. Vermunt, A., Smits, M., and Van der Pijl, G., Using GSS to Support Error Detection in Software Specifications, in Proc. of the Hawaii Int. Conf. on System Sciences, 1988, 566.
353. van Genuchten, M. et al., Using Group Support Systems for Software Inspections, IEEE Software, 60, May/June 2001.
354. Aurum, A., Petersson, H., and Wohlin, C., State-of-the-Art: Software Inspections after 25 Years, Software Testing, Verification and Reliability, 12, 133, 2002.
355. Parnas, D.L., van Schouwen, A.J., and Kwan, S.P., Evaluation of Safety-Critical Software, Commun. of the ACM, 33, 636, 1990.
356. Weigers, K.E., Creating a Software Engineering Culture, Dorset House, 1996.
357. Watson, A.H. and McCabe, T.J., Structured Testing: A Testing Methodology Using the Cyclomatic Complexity Metric, National Institute of Standards and Technology, NIST Special Publication 500-235, 1996.
358. Musa, J.D. and Ackerman, A.F., Quantifying Software Validation: When to Stop Testing?, IEEE Software, 6, 19, May 1989.
359. Boehm, B.W., Software Engineering Economics, Prentice Hall, 1981.
360. Nikora, A.P., Software System Defect Content Prediction from Development Process and Product Characteristics, Ph.D. dissertation, Computer Science Department, University of Southern California, 1998.
361. Weinberg, G.M., Quality Software Management: Systems Thinking, Dorset House, 1992.
362. Holzmann, G., The SPIN Model Checker: Primer and Reference Model, Addison-Wesley, 2003.
363. Grady, R.B. and Caswell, D.L., Software Metrics: Establishing a Company-Wide Program, Prentice Hall, 1987.
364. McConnell, S., Rapid Development: Taming Wild Software Schedules, Microsoft Press, 1996.
365. So, S.S. et al., An Empirical Evaluation of Six Methods to Detect Faults in Software, Software Testing, Verification and Reliability, 12, 155, 2002.
366. Smart, K.L., Madrigal, J.L., and Seawright, K.K., The Effect of Documentation on Customer Perception of Product Quality, IEEE Trans. on Professional Communication, 39, 157, 1996.
367. Dean, M. et al., Producing Quality Technical Information, ACM J. of Computer Documentation, 26, 66, 2002.
368. Hackos, J.T., Choosing a Minimalist Approach for Expert Users, in Minimalism beyond the Nurnberg Funnel, Carroll, J.M. (Ed.), MIT Press, 1998, 149.
369. Mirel, B. Minimalism for Complex Tasks, in Minimalism beyond the Nurnberg Funnel, Carroll, J.M. (Ed.), MIT Press, 1998, 179.
370. Redish, J., Minimalism in Technical Communication: Some Issues to Consider, in Minimalism beyond the Nurnberg Funnel, Carroll, J.M. (Ed.), MIT Press, 1998, 219.
371. van der Meij, H. and Carroll, J.M., Principles and Heuristics for Designing Minimalist Instruction, in Minimalism beyond the Nurnberg Funnel, Carroll, J.M. (Ed.), MIT Press, 1998, 19.
372. Klare, G.R., The Measurement of Readability: Useful Information for Communicators, ACM J. of Computer Documentation, 24, 107, 2000.
373. Frakes, W. and Terry, C., Software Reuse: Metrics and Models, ACM Computing Surveys, 28, 415, 1996.
374. Neighbors, J., Draco: A Method for Engineering Reusable Software Systems, in Software Reusability, Biggerstaff, T.J. and Perlis, A.J. (Eds.), 1, Addison-Wesley, 1989, 295.
375. Prieto-Diaz, R., A Software Classification Scheme, Ph.D. dissertation, Information and Computer Science Department, University of California, Irvine, 1985.
376. Kandt, R.K., Reuse of Design Information, Master’s thesis, Information and Computer Science Department, University of California, Irvine, 1984.
377. Selby, R.W., Quantitative studies of software reuse, in Software Reusability, II, Biggerstaff, T.J. and Perlis, A.J. (Eds.), Addison-Wesley, 1989.
378. Krueger, C.W., Software Reuse, ACM Computing Surveys, 24, 131, 1992.
379. Yourdon, E., The Decline and Fall of the American Programmer, Yourdon Press/Prentice Hall, 1993.
380. Abbott, R.J., Knowledge Abstraction, Commun. of the ACM, 30, 664, 1987.
381. Gabriel, R.P., Patterns of Software: Tales from the Software Community, Oxford University Press, 1996.
382. Jones, C., Applied Software Measurement: Assuring Productivity and Quality, McGraw-Hill, 1991.
383. Paulk, M.C. et al., The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, 1994.
384. Halstead, M.H., Elements of Software Science, Elsevier North-Holland, 1977.
385. Beizer, B., Software Testing Techniques, Van Nostrand Reinhold, 1990.
386. Wohlin, C. and Runeson, P., Defect Content Estimations from Review Data, in Proc. of the Int. Conf. on Software Engineering, 1998, 400.
387. Stringfellow, C. et al., Estimating the Number of Components with Defects Post-Release that Showed No Defects in Testing, Software Testing, Verification and Reliability, 12, 93, 2002.
388. Thelin, T. and Runeson, P., Robustness Estimations of Fault Content with Capture-Recapture and Detection Profile Estimators, J. of Systems and Software, 52, 139, 2000.
389. Briand, L.C. et al., A Comprehensive Evaluation of Capture-Recapture Models for Estimating Software Defect Content, IEEE Trans. on Software Engineering, 26, 518, 2000.
390. El Emam, K. and Laitenberger, O., Evaluating Capture-Recapture Models with Two Inspectors, IEEE Trans. on Software Engineering, 27, 851, 2001.
391. Miller, J., Estimating the Number of Remaining Defects after Inspection, Software Testing, Verification and Reliability, 9, 167, 1999.
392. Biffl, S., Freimut, B., and Laitenberger, O., Investigating the Impact of Reading Techniques on the Accuracy of Different Defect Content Estimation Techniques, in Proc. of the Int. Symp. on Software Metrics, 2001, 51.
393. Beck, K., Extreme Programming Explained: Embrace Change, Addison-Wesley, 2000.
394. Jacobson, I., Booch, G., and Rumbaugh, J., The Unified Software Development Process, Addison-Wesley, 1999.
395. Kroll, P. and Kruchten, P., The Rational Unified Process Made Easy: A Practitioner’s Guide to the RUP, Addison-Wesley, 2003.
396. Prowell, S.J. et al., Cleanroom Software Engineering: Technology and Process, Addison-Wesley, 1999.
397. Chrissis, M.B., Konrad, M., and Shrum, S., CMMI: Guidelines for Process Integration and Product Improvement, Addison-Wesley, 2003.
398. Beck, K. and Fowler, M., Planning Extreme Programming, Addison-Wesley, 2001.
399. Poore, J.H., Mills, H.D., and Mutchler, D., Planning and Certifying Software System Reliability, IEEE Software, 10, 88, January 1993.
400. Prowell, S.J. and Poore, J.H., Sequence-Based Specification of Deterministic Systems, Software — Practice and Experience, 28, 329, 1998.
401. Balzer, R., Cheatham, T.E., Jr., and Green, C.C., Software Technology in the 1990’s: Using a New Paradigm, IEEE Computer, 16(11), 39, 1983.