Automated Defect Prevention: Best Practices in Software Management

Automated Defect Prevention: Best Practices in Software Management

Volumn , Issue , 2007, Pages 1-426

  Huizinga, Dorota ^a   Kolawa, Adam ^a  

^a NONE

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84889308306     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1002/9780470165171     Document Type: Book

References (189)

1. Kolawa, A., Automated Error Prevention: Delivering Reliable and Secure Software on Time and on Budget, 2005, http://www.parasoft.com (retrieved: July 7, 2006).
2. Burnstein, I., Practical Software Testing: A Process Oriented Approach. Springer, 2002.
3. Institute of Electrical and Electronics Engineers, IEEE Standard 610.12-1990-Glossary of Software Engineering Terminology, 1990.
4. Csikszentmihalyi, Mihaly, Flow: The Psychology of Optimal Experience. Harper & Row, 1990.
5. Institute of Electrical and Electronics Engineers, IEEE Standard 1058.1-1987, 1987.
6. Pressman, R.S., Software Engineering: A Practitioner's Approach. McGraw-Hill, 2005.
7. Armour, P. G., "The Learning Edge," Communications of ACM, Vol. 49, No. 6, June 2006.
8. Inquiry Board (Chairman: Prof. J.L. Lions), ARIANE 5-Flight 501 Failure, Paris, July 19, 1996, http://www.ima.umn.edu/~arnold/disasters/ariane5rep.html (retrieved: July 7, 2006).
9. National Aeronautics and Space Administration, Mars Climate Orbiter Mishap Investigation Board Phase I Report, 1999, http://mars.jpl.nasa.gov/msp98/news/mco991110.html (retrieved: July 7, 2006).
10. "Maine's Medical Mistakes," CIO, April 15, 2006, http://www.cio.com/archive/041506/maine.html (retrieved: July 7, 2006).
11. "2005 Toyota Prius Recalls," AutoBuy.com, 2005, http://www.autobuyguide.com/2005/12-aut/toyota/prius/recalls/index.html (retrieved: July 7, 2006).
12. General Accounting Office-Information Management and Technology Division Report, Patriot Missile Software Problem, 1992, http://www.fas.org/spp/starwars/gao/im92026.htm (retrieved: on July 7, 2006).
13. Leveson, N. and Turner, C.S., "An Investigation of the Therac-25 Accidents," IEEE Computer, Vol. 26, No. 7, July 1993, pp. 18-41.
14. National Institute of Standards and Technology, The Economic Impacts of Inadequate Infrastructure for Software Testing, Washington D.C., 2002, http://www.nist.gov/director/prog-ofc/report02-3.pdf (retrieved: July 7, 2006).
15. Boehm, B. and Basili, B., "Software Defect Reduction Top 10 List," IEEE Computer, Vol. 34, No. 1, January 2001.
16. Chrissis, M.B., Konrad, M., and Shrum, S., CMMI-Guidelines for Process Integration and Product Improvement, Addison Wesley, February 2005.
17. Government Services Administration, Summary of Section 508 Standards, January 23, 2006, http://www.section508.gov/index.cfm?FuseAction=Content&ID=11 (retrieved: April 3, 2006).
18. The American Institute of Certified Public Accountants, Sarbanes-Oxley Act of 2002, January 23, 2002, http://frwebgate.access.gpo.gov/cgibin/getdoc.cgi?dbname=107_cong_bills&docid=f:h3763enr.txt.pdf (retrieved: June 15, 2006).
19. United States Department of Health and Human Services, Public Law 104-191: Health Insurance Portability and Accountability Act of 1996, August 21, 1996, http://aspe.hhs.gov/admnsimp/pl104191.htm (retrieved: July 25, 2006).
20. Federal Trade Commission, Privacy Initiatives: The Gramm-Leach-Bliley Act, 1999, http://www.ftc.gov/privacy/privacyinitiatives/glbact.html (retrieved: July 25, 2006).
21. United States Department of Education, Family Educational Rights and Privacy Act (FERPA), February 17, 2005, http://www.ed.gov/policy/gen/guid/fpco/ferpa/index.html (retrieved: July 25, 2006).
22. Royce, W.W., "Managing the Development of Large Software Systems: Concepts and Techniques," Proceedings of IEEE WESCON, Vol. 26, August 1970, pp. 1-9.
23. Schach, S.R., Object-Oriented and Classical Software Engineering. McGraw Hill, 2002.
24. Boehm, B.W., "A Spiral Model of Software Development and Enhancement," IEEE Computer, Vol. 21, No. 5, May 1988, pp. 61-72.
25. Jacobson, I., Booch, G., and Rumbaugh, J., The Unified Software Development Process. Addison-Wesley, 1999.
26. Beck, K. and Andres, C., Extreme Programming Explained: Embrace Change. Addison-Wesley, 2nd ed., 2004.
27. Martin, J., Rapid Application Development. Prentice-Hall, 1991.
28. Choi, J.S. and Scacchi, W., "E3SD: An Environment Supporting the Structural Correctness of SLC Descriptions," Proceedings of the IASTED-International Conference on Software Engineering and Applications, Las Vegas, Nevada, USA, Nov. 6-9, 2000, pp. 80-85.
29. Choi., J.S. and Scacchi, W., "Formal Analysis of the Structural Correctness of SLC Descriptions," International Journal of Computers and Applications, Vol. 25, No. 2, 2003, pp: 91-97.
30. Deming, W.E., Out of Crisis, MIT Center for Advance Engineering Study, Cambridge MA, 1986.
31. Juran, J.M., "Product Quality: A Prescription for the West," European Organization for Quality Control, Paris, June 9-12, 1981.
32. Humphrey, W., Managing the Software Process. Addison Wesley, 1990.
33. Burnstein, I., Practical Software Testing: A Process Oriented Approach. Springer, 2002.
34. Mays, R., "Defect Prevention and Total Quality Management," in Total Quality Management for Software, Schulmeyer, G. and McManus, J., eds., Van Nostrand Reinhold, New York, 1992.
35. General Accounting Office-Information Management and Technology Division Report, Patriot Missile Software Problem, 1992, http://www.fas.org/spp/starwars/gao/im92026.htm (retrieved: July 7, 2006).
36. Boehm, B., Software Engineering Economics. Prentice Hall, 1981.
37. Boehm, B. and Basili, V., "Software Defect Reduction Top 10 List," IEEE Computer, Vol. 34, No. 1, January 2001.
38. Royce, W., Software Project Management: A Unified Framework. Addison Wesley, 1998.
39. Csikszentmihalyi, Mihaly, Flow: The Psychology of Optimal Experience. Harper and Row, 1990.
40. McGarry, F., Voltz, S., and Valett, J., "Determining Software Productivity Factors in the SEL," Proceedings of the 11th Annual Software Engineering Workshop, NASA Goddard Space Flight Center, December 1986.
41. International Organization for Standardization, ISO Standard 9126: Information Technology Software Product Evaluation-Quality Characteristics and Guidelines for Their Use, Geneva, Switzerland, 1991.
42. Institute of Electrical and Electronics Engineers, IEEE Standard for Software Quality Metrics Methodology. New York, 1998.
43. Clarke, J., Automated Test Generation (From a Behavior Model), November 2000, http://www.stickyminds.com/se/S2018.asp (retrieved: July 8, 2005).
44. Li, B., Blackboard Online Discussion Posting, CPSC 542, "Software Validation and Verification," Department of Computer Science, California State University-Fullerton, June 2006.
45. Inquiry Board (Chairman: Prof. J. L. Lions), ARIANE 5-Flight 501 Failure, July 19, 1996, http://www.ima.umn.edu/~arnold/disasters/ariane5rep.html (retrieved: July 7, 2006).
46. Weisstein, Eric W., "Roundoff Error," from MathWorld-A Wolfram Web Resource, 2002, http://mathworld.wolfram.com/RoundoffError.html (retrieved: July 8, 2006).
47. Breyfogle III, F. W., Implementing Six Sigma: Smarter Solutions Using Statistical Methods. John Wiley & Sons, 2003.
48. Institute of Electrical and Electronics Engineers, IEEE Standard 610.12-1990-Glossary of Software Engineering Terminology, 1990.
49. Marks, E.A. and Bell, M., Service-Oriented Architecture: A Planning and Implementation Guide for Business and Technology. John Wiley & Sons, 2004.
50. Wiegers, K., Software Requirements. Microsoft Press, 2nd ed., 2003.
51. Purdue University, Official RCS Homepage, 2006, http://www.cs.purdue.edu/homes/trinkle/RCS/ (retrieved: September 27, 2006).
52. Tigris.org, Subversion, 2006, http://subversion.tigris.org/ (retrieved: September 27, 2006).
53. Has, A., Configuration Management Principles and Practice. Addison Wesley, 2002.
54. Burnstein, I., Practical Software Testing: A Process Oriented Approach. Springer, 2002.
55. Kolawa, A., "Making Your Regression System Work For You," 2006, http://www.wrox.com/WileyCDA/Section/id-130092.html (retrieved: February 16, 2006).
56. Jacobson, I., Booch, G., and Rumbaugh, J., The Unified Modeling Language User Guide. Addison-Wesley, 1999.
57. Martin, R.C., Fit for Developing Software: Framework for Integrated Tests. Prentice Hall, 2005.
58. Burnstein, I., Practical Software Testing. A Process Oriented Approach. Springer, 2002.
59. Wiegers, K.E., Software Requirements. Microsoft Press, 2nd ed., 2003, pp. 78-90, 120-124, 242-251, 264, 333-337, 485, 488, 489.
60. Ambler, S., "Requirements Wisdom," Software Development. October 2005, pp. 54-57.
61. Venugopal, C., "Single Goal Set: A New Paradigm for IT Megaproject Success," IEEE Software, Vol. 22, No. 5, September/October 2005, p. 49.
62. Boehm, B.W., Gray, T.E., and Seewaltd, T., "Prototyping Versus Specifying: A Multi-Project Experiment," IEEE Transactions on Software Engineering, Vol. 10, No. 5, May 1984, pp. 290-303.
63. Schneider-Hufschmidt, M., and Zullighoven, H., "Prototyping in Industrial Projects-Bridging the Gap between Theory and Practice," IEEE Transactions on Software Engineering, Vol. 20, No. 11, November 1994, pp. 825-832.
64. Kelly, J.C., Sherif, J.S., and Hops, J., "An Analysis of Defect Densities Found During Software Inspections," Journal of Systems and Software, Vol. 17, No. 2, 1992, pp. 111-117.
65. Pressman, R.S., Software Engineering: A Practitioner's Approach. McGraw Hill, 6th ed., 2005.
66. Institute of Electrical and Electronics Engineers, "Glossary of Software Engineering Terminology," IEEE Standard 610.12-1990-1990.
67. The Standish Group International, 2004 Third Quarter Research Report, 2006, www.standishgroup.com (retrieved: August 2, 2006).
68. Institute of Electrical and Electronics Engineers, IEEE Standard 1058.1-1987-Software Project Management Plans (SPMP), 1987.
69. Institute of Electrical and Electronics Engineers, IEEE Standard 610.12-1990-Glossary of Software Engineering Terminology, 1990.
70. The Apache Software Foundation, Apache Tomcat, 2006, http://tomcat.apache.org/ (retrieved: March 13, 2006).
71. Wiegers, K.E., Software Requirements, Microsoft Press, 2nd ed, 2003.
72. Boehm, B., Software Engineering Economics. Prentice Hall, 1981.
73. Boehm, B., Clark, B., Horowitz, E., Madachy, R., Selby, R., and Westland, C., "Cost Models for Future Life Cycle Processes: COCOMO 2.0," Annals of Software Engineering, Special Volume on Process and Product Measurement, The Netherlands, 1995.
74. Boehm, B., Abts, C., Brown, A.W., Chulani, S., Clark, B.K., Horowitz, E., Madachy, R., Reifer, D., and Steece, B., Software Cost Estimation with COCOMOII. Prentice Hall, 2000.
75. University of Southern California, COCOMO, CSE Center for Software Engineering, 2002, http://sunset.usc.edu/research/COCOMOII/index.html, updated date: 9/23/2002 (retrieved: March 14, 2006).
76. Federal Aviation Administration, FAST-Federal Aviation Administration Acquisition Toolset, 2006, http://fast.faa.gov/pricing/c1919-4.htm (retrieved: August 7, 2006).
77. DeMarco, T., Controlling Software Projects: Management, Measurement and Estimation. Prentice Hall, 1986.
78. Kolawa, A., Hicken, W., and Dunlop, C., Bulletproofing Web Applications, Hungry Minds, 2002.
79. Institute of Electrical and Electronics Engineers, IEEE Standard 610.12-1990-Glossary of Software Engineering Terminology, 1990.
80. Channabasavaiah, K., Holley, K., and Tuggle, E., "Migrating to a Service Oriented Architecture," IBM Developer Works, December 16, 2003.
81. Gamma, E., Helm, R., Johnson, R., and Vlissides J., Design Pattern: Elements of Reusable Object-Oriented Software. Addision-Wesley, 1995.
82. Kleppe, A., Warmer, J., and Bast, W., MDA Explained-The Model Driven Architecture: Practice and Promise. Addison Wesley, 2004.
83. Rumbaugh, J., Jacobson, I., and Booch, G., The Unified Modeling Language Reference Manual. Addison-Wesley, 2 ed., 2004.
84. Burnstein, I., Practical Software Testing: A Process Oriented Approach. Springer, 2002.
85. Bosch, J., Design and Use of Software Architectures. Harlow: Addison-Wesley, 2000.
86. Thayer, R.H. and Dorfman, M., System and Software Requirements Engineering. IEEE Press, 1990.
87. Kuchana, P., Software Architecture Design Patterns in Java. CRC Press, 2004.
88. Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P., and Stal, M., Pattern-Oriented Software Architecture: A System of Patterns, Vol. 1. John Wiley & Sons, 1996.
89. OpenGroup, Architecture Patterns, 2006, http://www.opengroup.org/architecture/togaf8-doc/arch/p4/patterns/patterns.htm (retrieved: August 8, 2006).
90. Brown, W.J., Malveau, R.C., McCormick III, H.W., and Mowbray, T.J., Anti-Patterns: Refactoring Software, Architectures, and Projects in Crisis. John Wiley & Sons, 1998.
91. Papazoglou, M.P. and Georgakopoulos, D., "Service-Oriented Computing," Communications of the ACM, Vol. 46, No. 10, October 2003.
92. Schulte, R.W. and Natis, Y.V., "Service Oriented Architecture," Gartner, April 12, 1996.
93. Web Services Description Language (WSDL) Version 2.0, Part 1: Core Language, 2006, http://www.w3.org/TR/wsdl20 (retrieved: August 21, 2006).
94. Sommerville, I., Software Engineerin. Addison-Wesley, 8th ed., 2007.
95. The Object Management Group (OMG), 2006, http://www.omg.org (retrieved: August 12, 2006).
96. Walsh, N., A Technical Introduction to XML, 2006, http://www.xml.com/pub/a/98/10/guide0.html (retrieved: August 12, 2006).
97. Pressman, R.S., Software Engineering: A Practitioner's Approach. McGraw-Hill, 2004.
98. Burnstein, I., Practical Software Testing: A Process Oriented Approach. Springer, 2002.
99. Kaner, C., Falk, J., and Nguyen, H.Q., Testing Computer Softwar. John Wiley & Sons, 2nd ed., 1999.
100. Meyers, S., Effective C++: 55 Specific Ways to Improve Your Programs and Design. Addison-Wesley Professional Computing Series, 3rd ed., 2005.
101. King, P., Naughton, P., DeMoney, M., Kanerva, J., Walrath, K., and Hommel, S., Code Conventions for the Java Programming Language, 2006, http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html (retrived: August 21, 2006).
102. Macadamian, Coding Conventions for C++ and Java, 2006, http://www.macadamian.com/index.php?option=com_content&task=view&id=34&Itemid=37 (retrieved: August 21, 2006).
103. McCabe, T., "A Complexity Measure," IEEE Transactions on Software Engineering, Vol. 2, No. 4, 1976.
104. Halstead, M. H., Elements of Software Science, Operating, and Programming Systems Series. Elsevier, New York 1977.
105. Java Developers Network, Programming with Assertions, 2006, http://java.sun.com/j2se/1.4.2/docs/guide/lang/assert.html (retrieved: August 21, 2006).
106. Meyer, B., "Design by Contract: Technical Report TR-EI-12/CO," Interactive Software Engineering Inc., 1986.
107. Meyer, B., "Design by Contract," in Advances in Object-Oriented Software Engineering, Mandrioli, D. and Meyer, B., eds., Prentice Hall, 1991, pp. 1-50.
108. Meyer, B., "Applying Design by Contract," IEEE Computer, Vol. 25, No. 10, October 1992, pp. 40-51.
109. Nielsen, J., Jakob Nielsen on Usability and Web Design, 2006, http://www.useit.com (retrieved: March 26, 2006).
110. Government Services Administration, "Section 508," Summary of Section 508 Standards, January 23, 2006, http://www.section508.gov/index.cfm?FuseAction=Content&ID=11 (retrieved: April 3, 2006).
111. Bloch, J., Effective Java Programming Language Guide. Addison-Wesley Professional, 2001.
112. Sun Developers Network (SDN), Core Java Javadoc Tool, 2006, http://java.sun.com/j2se/javadoc/ (retrieved: August 27, 2006).
113. Sun Developers Network (SDN), Code Conventions for the Java Programming Language: Naming Conventions, 2006, http://java.sun.com/docs/codeconv/html/CodeConventions.doc8.html (retrieved: August 27, 2006).
114. Johnson, S., "Lint: A C Program Checker," Technical Report 65, Bell Laboratories, December 1977.
115. Sant, J., "Using Mark Previews to Improve Quality of Student Programs," Proceedings of the 2005 International Conference on Frontiers in Education: Computer Science and Computer Engineering, Las Vegas, Nevada, June 2005, pp. 62-68.
116. Gelperin, D. and Hetzel, W., "Software Quality Engineering," Proceedings of the 4th International Conference on Testing Computer Software, Washington, D.C., June 1987.
117. Beck, K., Test Driven Development: By Example. Addison Wesley Professional, 2002.
118. Williams L., Maximilien, E.M., and Vouk, M., "Test Driven Development as a Defect-Reduction Practice," Proceedings of the 14th International Symposium on Software Reliability (ISSRE'03), Denver, Colorado, November 2003, pp. 34-45.
119. Institute of Electrical and Electronics Engineers, IEEE Standard 610.12-1990-Glossary of Software Engineering Terminology, 1990.
120. Zelkowitz, M.V., Shaw, A.C., and Gannon, J.D., Principles of Software Engineering and Design. Prentice-Hall, Englewood Cliffs, NJ, 1979.
121. Holmes, J.S., "Optimizing the Software Life Cycle," Software Quality Professional, Vol. 5, No. 4, 2003.
122. Dei, T., Nyberg, A., Schultz, S., and Willcock, C., "Industrial Deployment of the TTCN-3 Testing Technology," IEEE Software, Vol. 23, No. 4, July/August 2006, pp. 48-54.
123. Tillman, N. and Schulte, W., "Unit Tests Reloaded: Parameterized Unit Testing with Symbolic Execution," IEEE Software, Vol. 23, No. 4, July/August 2006, pp. 38-47.
124. National Institute of Standards and Technology, The Economic Impacts of Inadequate Infrastructure for Software Testing, Washington D.C., 2002, http://www.nist.gov/director/prog-ofc/report02-3.pdf (retrieved: July 7, 2006).
125. Institute of Electrical and Electronics Engineers, IEEE Standard 610.12-1990-Glossary of Software Engineering Terminology, 1990.
126. Myers, G.J., The Art of Software Testing. John Wiley & Sons, New York, 1979.
127. Zhu, P., Hall, P., and May, J. "Software Unit Test Coverage and Adequacy," ACM Computing Surveys, Vol. 29, No. 4, 1997, pp. 366-427.
128. Runeson P., "A Survey of Unit Testing Practices," IEEE Software, Vol. 23, No. 4, July/August 2006, pp. 22-29.
129. Burnstein, I., Practical Software Testing: A Process Oriented Approach. Springer, 2002.
130. Beizer, B., Software Testing Technique. Van Nostrand Reinhold, 2nd ed., 1990.
131. Fagan, M., "Design and Code Inspections to Reduce Errors in Program Development," IBM Systems Journal, Vol. 15, No. 3, 1976, pp. 182-211.
132. Myers, G. "A Controlled Experiment in Program Testing and Code Walkthroughs/Inspections," Communications of ACM, 1978, pp. 760-768.
133. Beck, K. and Andres, C., Extreme Programming Explained: Embrace Chang. Addison Wesley, 2nd ed., 2004.
134. Constantine, L., Constantine on Peopleware. Yourdon Press Computing Series, Prentice Hall, 1995.
135. Hutchins, E., "Cognition in the Wild," MIT Press, Cambridge, MA, 1995.
136. Williams, L., Kessler, R.R., Cunningham, W., and Jeffries, R., "Strengthening the Case for Pair Programming," IEEE Software, Vol. 17, No. 4, July/August 2000, pp. 19-25.
137. Lui, K.M. and Chan, K.C.C., "Pair Programming Productivity: Novice-Novice vs. Expert-Expert," International Journal of Human-Computer Studies, Elsevier, Vol. 64, No. 9, September 2006, pp. 915-925.
138. Manascé, D.A., "Load Testing of Web Sites," IEEE Internet Computing, July/August 2002, pp. 70-74.
139. Kaner, C., Falk, J., and Nguyen, H.Q., Testing Computer Softwar. John Wiley & Sons, 2nd ed., 1999.
140. Institute of Electrical and Electronics Engineers, IEEE Standard 1044-1993-Classification for Software Anomalies, 1993.
141. Shui, E., Blackboard Online Discussion Posting, CPSC 542, "Software Validation and Verification," Department of Computer Science, California State University-Fullerton, June 2006.
142. Cable News Network, TSA: Computer Glitch Led to Atlanta Airport Scare, April 21, 2006, http://www.cnn.com/2006/US/04/20/atlanta.airport/index.html (retrieved: September 22, 2006).
143. Pandian, C.R., Software Metrics: A Guide to Planning, Analysis, and Application. Auerbach Publications, 2004.
144. Humphrey, W., Managing the Software Process. Addison Wesley Publishing, 1990.
145. Deming, W.E., The New Economics: For Industry, Government, Educatio. MIT Press, Cambridge, 2nd ed., 1994.
146. Breyfogle III, F.W., Implementing Six Sigma: Smarter Solutions Using Statistical Methods. John Wiley & Sons, April 2003.
147. Royce, W.W., "Managing the Development of Large Software Systems: Concepts and Techniques," Proceedings of IEEE WESCON, Vol. 26, August 1970, pp. 1-9.
148. Beck, K. and Andres, C., Extreme Programming Explained: Embrace Chang. Addison-Wesley, 2nd ed., 2004.
149. Beck, K., Test Driven Development: By Example. Addison Wesley Professional, 2002.
150. Fleming, Q.W. and Koppelman, J.M., Earned Value Project Management. Project Management Institute, 2nd ed., June 2000.
151. Haack, L., private communication.
152. The American Institute of Certified Public Accountants, Sarbanes-Oxley Act of 2002, January 23, 2002, http://frwebgate.access.gpo.gov/cgibin/getdoc.cgi?dbname=107_cong_bills&docid=f:h3763enr.txt.pdf (retrieved: Jun 15, 2006).
153. Chrissis, M.B., Konrad, M., and Shrum, S., CMMI: Guidelines for Process Integration and Product Improvement. Addison Wesley, February 2005.
154. International Organization for Standardization/International Electrotechnical Commission 90003-2004, Software Engineering: Guidelines for the Application of ISO 9001:2000 to Computer Software, ISO, 2004.
155. Breyfogle III, F.W., Implementing Six Sigma: Smarter Solutions Using Statistical Methods. John Wiley & Sons, 2003.
156. DiamondCluster, IT Outsourcing: Following the Leaders May Well Lead to Failure, October 30, 2002, http://www.diamondcluster.com/press/pressreleases/pressreleases285.asp (retrived: June 8, 2006).
157. Haw, K., "Protecting Sensitive Data While Outsourcing Software Development Projects," Master's Degree Project Report, Computer Science Department, California State University, Fullerton, CA, May 2006.
158. Marks, G., The Complete Idiot's Guide to Successful Outsourcing. New York, Penguin, 2005.
159. Lidman, S. and Jacobson, I., Controlled Offshore Outsourcing with an Active Process, 2006, http://www.jaczone.com/papers/OutsourcingWithActiveProcess7.pdf (retrieved: June 8, 2006).
160. Day, K., Inside the Security Mind: Making the Tough Decisions. Prentice Hall Professional Technical Reference, Upper Saddle River, NJ, 2003.
161. Edwards, V.J., Source Selection Answer Book. Management Concepts, November 1, 2000.
162. Martin, M.G., Delivering Project Excellence with the Statement of Work. Management Concepts, January 1, 2003.
163. Government Services Administration, Summary of Section 508 Standards, January 23, 2006, http://www.section508.gov/index.cfm?FuseAction=Content&ID=11 (retrieved: April 3, 2006).
164. U.S. Census Bureau, Persons with a Disability, Age 5+, 2000, http://quickfacts.census.gov/qfd/meta/long_101608.htm (retrieved: June 8, 2006).
165. U.S. Food and Drug Administration, General Principles of Software Validation. Final Guidance for Industry and FDA Staff, January 11, 2002, http://www.fda.gov/cdrh/comp/guidance/938.html (retrieved: Jun 8, 2006).
166. U.S. General Services Administration, Subpart 1194.22 Web-Based Intranet and Internet Information and Applications, Section 508: Section 508 Standards, March 23, 2006, http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web (Retrieved: June 15, 2006).
167. The World Wide Web Consortium (W3C), WAI Resources on Introducing Web Accessibility, http://www.w3.org/WAI/gettingstarted/Overview.html (retrieved: June 8, 2006).
168. Carnegie Mellon University Software Engineering Institute, List of Published SCAMPI Appraisal Results, http://seir.sei.cmu.edu/pars/pars_list_iframe.asp (retrieved: October 3, 2006).
169. Shrum, S., Choosing a CMMI Model Representation, July 2000, http://www.stsc.hill.af.mil/crosstalk/2000/07/shrum.html (retrieved: October 3, 2006).
170. Royce, W., Software Project Management: A Unified Framework. Addison-Wesley, 1998.
171. The Apache Software Foundation, Apache Ant, 2006, http://ant.apache.org/ (Retrieved: February 17, 2006).
172. Bloch, J., Effective Java: Programming Language Guide. Addison-Wesley, 2001.
173. Martin, J., Rapid Application Development. Prentice-Hall, 1991.
174. Dennis, A., Wixom, B., and Roth, R., Systems Analysis and Desig. John Wiley & Sons, 3rd ed., 2005.
175. Schach, S.R., Object-Oriented and Classical Software Engineering. McGraw Hill, 2002.
176. Boehm, B.W., "A Spiral Model of Software Development and Enhancement," IEEE Computer, Vol. 21, No. 5, May 1988, pp. 61-72.
177. Jacobson, I., Booch, G., and Rumbaugh, J., The Unified Modeling Language User Guide. Addison-Wesley, 1999.
178. Jacobson, I., Booch, G., and Rumbaugh, J., The Unified Software Development Process. Addison-Wesley, 1999.
179. Beck, K. and Andres, C., Extreme Programming Explained: Embrace Chang. Addison-Wesley, 2nd ed., 2004.
180. JPL, Mars Climate Orbiter/Mars Polar Lander Mission Overview, 2006, http://mars.jpl.nasa.gov/msp98/mission_overview.html (retrieved: October 10, 2006).
181. Wikipedia, Mars Polar Lander, 2006, http://en.wikipedia.org/wiki/Mars_Polar_Lander (retrieved: October 10, 2006).
182. Burnstein, I., Practical Software Testing. Springer, 2003.
183. Chaikin, A., Mars Polar Lander's Demise May Never Be Known, Flight Directory Says, 2006, http://www.space.com/scienceastronomy/solarsystem/mpl_latest_update.html (retrieved: October 10, 2006).
184. Jet Propulsion Laboratory (JPL) Special Review Board (SRB) Report, Report on the Loss of Mars Polar Lander and Deep Space 2 Missions, 2000, http://www.jpl.nasa.gov/marsreports/mpl_report.pdf. (retrieved: June 17, 2006); also available at http://www.dcs.gla.ac.uk/~johnson/Mars/mpl_report.pdf (retrieved: October 15, 2006).
185. Bridges, A., Polar Lander Leg Snafu Discovery a Fluke, 2006, http://www.space.com/scienceastronomy/solarsystem/lander_leg_000329.html (retrieved: October 10, 2006).
186. House Science Committee, Testimony of Thomas Young, Chairman of the Mars Program Independent Assessment Team before the House Science Committee, 2006, http://www.spaceref.com/news/viewpr.html?pid=1444 (retrieved: October 10, 2006).
187. Cowing, K., NASA Reveals Probable Cause of Mars Polar Lander and Deep Space-2 Mission Failures, 2006, http://www.spaceref.com/news/viewnews.html?id=105 (retrieved: October 10, 2006).
188. Chrissis, M.B., Konrad, M., and Shrum, S., CMMI Guidelines for Process Integration and Product Improvement. Addison-Wesley, 2003.
189. Easterbrook, S., Bugs in the Space Program: The Role of Software in System Failures, 2006, http://www.cs.toronto.edu/~sme/presentations/BugsInTheSpace Program.pdf (retrieved: October 10, 2006).