Bibliography

Allen 2002. Eric E Allen. "Diagnosing Java Code: Assertions and Temporal Logic in Java." Found online in IBM's developerWorks Web site at http://www-106.ibm.com/developerworks/java/library/j-diag0723.html.

Ambler 2002. Scott W. Ambler and Ron Jeffries. Agile Modeling: Effective Practices for Extreme Programming and the Unified Process. Hoboken, NJ:John Wiley & Sons, 2002.

Ambler 2003. Scott W. Ambler. Agile Database Techniques: Effective Strategies for the Agile Software Developer. Hoboken, NJ: John Wiley & Sons, 2003.

Ambler 2004. Scott W. Ambler. The Object Primer: Agile Model-Driven Development with UML 2.0.Cambridge, UK:Cambridge University Press, 2004.

Ambler 2005. Scott W. Ambler, John Nalbone, and Michael J. Vizdos. The Enterprise Unified Process: Extending the Rational Unified Process. Upper Saddle River, NJ: Prentice Hall, 2005.

Ambler 2006. Scott W. Ambler and Pramodkumar J. Sadalage. Refactoring Databases: Evolutionary Database Design.Boston: Addison-Wesley, 2006.

Arlow 2002. Jim Arlow and Ila Neustadt. UML and the Unified Process: Practical Object-Oriented Analysis and Design.Boston:Addison-Wesley, 2002.

Arnold 1993. Robert S. Arnold. Software Reengineering (IEEE Computer Society Press Tutorial). Institute of Electrical & Electronics Engineers, 1993.

Astels 2003. David Astels. Test-Driven Development: A Practical Guide. Upper Saddle River, NJ: Prentice Hall, 2003.

Augustine 2005. Sanjiv Augustine. Managing Agile Projects.Boston: Addison-Wesley, 2005.

Bass 2003. Len Bass, Paul Clements, and Rick Kazman. Software Architecture in Practice, Second Edition. Boston: Addison-Wesley, 2003.

Beck 2000. Kent Beck. Extreme Programming Explained: Embrace Change.Boston: Addison-Wesley, 2000.

Beck 2001. Kent Beck and Martin Fowler. Planning Extreme Programming.Boston: Addison-Wesley, 2001.

Beck 2003. Kent Beck. Test-Driven Development: By Example.Boston: Addison-Wesley, 2003.

Beck 2004. Kent Beck withCynthia Andres. Extreme Programming Explained: Embrace Change, Second Edition.Boston: Addison-Wesley, 2004.

Beizer 1995. Boris Beizer. Black Box Testing. Hoboken, NJ: John Wiley & Sons, 1995.

Bellagio 2004. David Bellagio and Ana Giordano. UCM Stream Strategies and Best Practices. Grapevine, TX:Rational Software Development User Conference, July 2004.

Bellagio 2005. David Bellagio and Tom Milligan. Software Configuration Management Strategies and IBM Rational ClearCase: A Practical Introduction, Second Edition. IBM Press, 2005.

Bennett 1997. Douglas W. Bennett. Designing Hard Software: The Essential Tasks. Chicago, IL: Independent Publishers Group, 1997.

Berczuk 2002. S. Berczuk and B. Appleton. Software Configuration Management Patterns: Effective Teamwork, Practical Integration. Addison-Wesley, 2002.

Bergström 2004. Stefan Bergström and Lotta Råberg. Adopting the Rational Unified Process: Success with the RUP. Boston: Addison-Wesley, 2004.

Bittner 2002. Kurt Bittner and Ian Spence. Use Case Modeling.Boston: Addison-Wesley, 2002.

Boehm 1988. Barry W. Boehm. "A Spiral Model of Software Development and Enhancement."IEEE Computer 21(5), May 1988, pp. 6172.

Boehm 1991. Barry W. Boehm, "Software Risk Management: Principles and Practices." IEEE Software, January 1991, pp. 3241.

Boehm 2000. Barry W. Boehm et al. Software Cost Estimation with COCOMO II. Upper Saddle River, NJ: Prentice Hall, 2000.

Boehm 2002. Barry W. Boehm. "Get Ready for Agile Methods, with Care."IEEE Computer, Volume 35, January 2002.

Boehm 2003. Barry Boehm and Richard Turner. Balancing Agility and Discipline.Boston: Addison-Wesley, 2003.

Booch 1996. Grady Booch. Object Solutions: Managing the Object-Oriented Project. Reading, MA: Addison-Wesley, 1996.

Brooks 1995. Frederick P. Brooks, Jr. The Mythical Man-Month, Anniversary Edition. Reading, MA: Addison-Wesley, 1995.

Bryson 2001. Brian Bryson. "Quality by Design: Enabling Cost-Effective Comprehensive Component Testing." The Rational Edge, January 2001.

Buschmann 1996. F. Buschmann et al. Pattern-Oriented Software Architecture: A System of Patterns. Hoboken, NJ: John Wiley & Sons, 1996.

Cantor 2001. Murray Cantor. Software Leadership: A Guide to Successful Software Development. Boston: Addison-Wesley, 2001.

Carnegie 1990. Dale Carnegie. How to Win Friends and Influence People, Revised Edition. New York: Pocket Books, 1990.

Carr 1993. Marvin Carr et al. Taxonomy Based Risk Identification.Technical report #93-TR-006. Pittsburgh, PA: Software Engineering Institute, June 1993.

Chaos 2003. Chaos Chronicle v3.0.The Standish Group International, Inc., 2003.

Charette 1989. Robert Charette. Software Engineering Risk Analysis and Management. New York: McGraw-Hill, 1989.

Cheesman 2000. John Cheesman and John Daniels, UML Components: A Simple Process for Specifying Component-Based Software. Boston: Addison-Wesley, 2000.

Chonoles 2003. Michael Chonoles. UML 2 for Dummies. Hoboken, NJ: John Wiley & Sons, 2003.

Clements 2002. Paul Clements and Linda Northrop. Software Product Lines: Practices and Patterns.Boston: Addison-Wesley, 2002.

Cockburn 2000. Alistair Cockburn and Laurie Williams. "The Costs and Benefits of Pair Programming." Found online at http://collaboration.csc.ncsu.edu/laurie/Papers/XPSardinia.PDF.

Cockburn 2001. Alistair Cockburn. Writing Effective Use Cases. Boston:Addison-Wesley, 2001.

Cockburn 2002. Alistair Cockburn. Agile Software Development. Boston: Addison-Wesley, 2002.

Cockburn 2005. Alistair Cockburn. Crystal Clear: A Human-Powered Methodology for Small Teams. Boston: Addison-Wesley, 2005.

Cooper 1999. Alan Cooper. The Inmates Are Running the Asylum. Indianapolis, IN: Sams, 1999.

de Bono 1970. Edward de Bono. Lateral Thinking: Creativity Step by Step.New York: Harper & Row, 1970.

de Bono 1993. Edward de Bono. Serious Creativity: Using the Power of Lateral Thinking to Create New Ideas. New York: HarperBusiness, 1993.

DeMarco 2003. Tom DeMarco and Timothy Lister. Waltzing with Bears: Managing Risk on Software Projects. New York: Dorset House, 2003.

Denne 2004. Mark Denne and Jane Cleland-Huang. Software by Numbers. Upper Saddle River, NJ: Prentice Hall, 2004.

Devlin 1995. M. T. Devlin and W. E. Royce. Improving Software Economics in the Aerospace and Defense Industry. Technical paper TP-46. Santa Clara, CA: Rational Software Corp., 1995.

Dustin 1999. Elfriede Dustin , Jeff Rashka , and John Paul. Automated Software Testing: Introduction, Management, and Performance. Reading, MA: Addison-Wesley, 1999.

Eeles 2003. Peter Eeles , Kelli Houston , and Wojtek Kozaczynski . Building J2EE™ Applications with the Rational Unified Process.Boston: Addison-Wesley, 2003.

Eeles 2004. Peter Eeles. "Capturing Architectural Requirements." The Rational Edge, April 2004. Found online at http://www.ibm.com/developerworks/rational/library/4706.html.

Evans 2004. Eric Evans. Domain-Driven Design: Tackling Complexity in the Heart of Software. Boston: Addison-Wesley, 2004.

Esselink 2000. Bert Esselink. A Practical Guide to Localization. Amsterdam: John Benjamins, 2000.

Fagan 1976. Michael Fagan. "Design and Code Inspections to Reduce Errors in Program Development." IBM Systems Journal, Volume 15, No. 3, pp. 182211. Found online at www.mfagan.com/ibmfagan.pdf.

Feathers 2005. Michael C Feathers. Working Effectively with Legacy Code. Upper Saddle River, NJ: Prentice Hall, 2005.

Ferm 2003. Fredrik Ferm. "The What, Why, and How of a Subsystem." The Rational Edge, 2003. Found online at http://www.ibm.com/developerworks.

Fewster 1999. Mark Fewster and Dorothy Graham. Software Test Automation: Effective Use of Test Execution Tools. Reading, MA: Addison-Wesley, 1999.

Fowler 1999. Martin Fowler et al. Refactoring: Improving the Design of Existing Code. Reading, MA: Addison-Wesley, 1999.

Fowler 2000. Martin Fowler. Is Design Dead? Keynote XP 2000 conference. Found online at http://www.martinfowler.com/.

Fowler 2003. Martin Fowler. Patterns of Enterprise Application Architecture. Boston: Addison-Wesley, 2003.

Gamma 1995. Erich Gamma et al. Design Patterns: Elements of Reusable Object-Oriented Software. Reading, MA: Addison-Wesley, 1995.

Gilb 1988. Tom Gilb. Principles of Software Engineering Management. Reading, MA: Addison-Wesley, 1988.

Glass 2003. Robert R Glass. Facts and Fallacies of Software Engineering.Boston: Addison-Wesley, 2003.

Gottesdiener 2003. Ellen Gottesdiener. "Team Retrospectives for Better Iterative Assessment." The Rational Edge, April 2003.

Goldratt 2004. Eliyahu M. Goldratt and Jeff Cox. The Goal, Third Edition. Great Barrington, MA: North River Press, 2004.

Grady 1997. Robert Grady. Successful Software Process Improvement. Englewood Cliffs, NJ: Prentice Hall, 1997.

Greenfield 2004. Jack Greenfield et al. Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools. Hoboken, NJ: John Wiley & Sons, 2004.

Harvey 1996. Jerry Harvey. The Abilene Paradox and Other Meditations on Management. San Francisco: Jossey-Bass, 1996.

Herzum 1999. Peter Herzum and Oliver Sims. Business Component Factory: A Comprehensive Overview of Component-Based Development for the Enterprise. Hoboken, NJ: John Wiley & Sons, 1999.

Highsmith 2004. James A Highsmith. Agile Project Management: Creating Innovative Products. Boston: Addison-Wesley, 2004.

Hohpe 2004. Gregor Hohpe and Bobby Woolf. Enterprise Integration Patterns. Boston: Addison-Wesley, 2004.

IEEE 1998. IEEE Standard 1490-1998. IEEE Guide Adoption of PMI Standard: A Guide to the Project Management Body of Knowledge. New York: Software Engineering Standards Committee of the IEEE Computer Society, 1998.

Ishigaki 2003. Doug Ishigaki and Cheryl Jones . "Practical Measurement in the Rational Unified Process." The Rational Edge, January 2003.

Jacobson 1992. Ivar Jacobson et al. Object-Oriented Software Engineering: A Use Case Driven Approach. Reading, MA: Addison-Wesley, 1992.

Jacobson 1995. Ivar Jacobson , Maria Ericsson , and Agneta Jacobson . The Object Advantage: Business Process Reengineering with Object Technology. Reading, MA: Addison-Wesley, 1995.

Jacobson 1997. Ivar Jacobson , Martin Griss , and Patrik Jonsson. Software Reuse: Architecture, Process, and Organization for Business Success. Reading, MA: Addison-Wesley, 1997.

Jacobson 1999. Ivar Jacobson et al. The Unified Software Development Process. Reading, MA: Addison-Wesley, 1999.

Jones 1994. Capers Jones. Assessment and Control of Software Risks. Englewood Cliffs, NJ: Yourdon Press, 1994.

Kaner 2001. Cem Kaner , James Bach , and Bret Pettichord. Lessons Learned in Software Testing. Hoboken, NJ: John Wiley & Sons, 2001.

Karolak 1996. Dale Karolak. Software Engineering Risk Management. Washington, DC: IEEE Computer Society Press, 1996.

Katzenbach 2003. Jon R Katzenbach and Douglas K Smith. The Wisdom of Teams: Creating the High-Performance Organization. New York: HarperBusiness, 2003.

Kerievsky 2005. Joshua Kerievsky. Refactoring to Patterns. Boston: Addison-Wesley, 2005.

Kerth 2001. N Kerth. Project Retrospectives: A Handbook for Team Reviews. New York: Dorset House, 2001.

Kircher 2004. Michael Kircher and Prashant Jain. Pattern-Oriented Software Architecture: Patterns for Resource Management. Hoboken, NJ: John Wiley & Sons, 2004.

Kit 1999. Edward Kit. "Integrated, Effective Test Design and Automation." Software Development Magazine (online version), February 1999.

Knuth 1992. Donald E Knuth. Literate Programming. Center for the Study of Language and Information, 1992.

Knuth 1993. Donald E Knuth and Silvio Levy , The CWEB System of Structured Documentation, Version 3.6. Reading, MA: Addison-Wesley, 1993.

Krafzig 2005. Dirk Krafzig , Karl Banke , and Dirk Slama. Enterprise SOA: Service-Oriented Architecture Best Practices. Upper Saddle River, NJ: Prentice Hall, 2005.

Kroll 2001. Per Kroll. "The RUP: An Industry-Wide Platform for Best Practices." The Rational Edge, 2001.

Kroll 2003. Per Kroll and Philippe Kruchten. The Rational Unified Process Made Easy: A Practitioner's Guide to the RUP. Boston: Addison-Wesley, 2003.

Kroll 2004. Per Kroll. "Iterative Development Requires a Different Mindset." The Rational Edge, March 2004.

Kroll 2005. Per Kroll and Walker Royce. "Key Principles for Business-Driven Development." The Rational Edge, October 2005.

Kruchten 1995. Philippe Kruchten. "The 4+1 view model of architecture." IEEE Software 6 (12), 1995, pp. 4550.

Kruchten 1999. Philippe Kruchten. "The Software Architect and the Software Architecture Team." In Software Architecture, P. Donohue, ed. Boston: Kluwer Academic Publishers, 1999, pp. 565583.

Kruchten 2001. Philippe Kruchten. "Using the RUP to Evolve a Legacy System." The Rational Edge, May 2001. http://www.therationaledge.com/content/may_01/t_legacy_pk.html.

Kruchten 2003. Philippe Kruchten. The Rational Unified ProcessAn Introduction, Third Edition. Boston: Addison-Wesley, 2003.

Larman 2004. Craig Larman. Agile and Iterative Development: A Manager's Guide. Boston: Addison-Wesley, 2004.

Larman 2005. Craig Larman. Applying UML and Patterns, Third Edition: An Introduction to Object-Oriented Analysis and Design and Iterative Development. Upper Saddle River, NJ: Prentice Hall, 2005.

Leffingwell 2000. Dean Leffingwell and Don Widrig. Managing Software Requirements: A Unified Approach. Boston: Addison-Wesley, 2000.

Lehman 2000. M M Lehman and J F Ramil. "Software Evolution in the Age of Component-Based Software Engineering." Software, IEE Proceedings, Volume 147, No. 6, December 2000, pp. 249255.

Lencioni 2000. Patrick Lencioni. The Four Obsessions of an Extraordinary Executive. San Francisco: Jossey-Bass, 2000.

Lencioni 2002. Patrick Lencioni. The Five Dysfunctions of a Team. San Francisco: Jossey-Bass, 2002.

Leonard 2003. Jason Leonard. "Simplifying Product Line Development Using UCM Streams." The Rational Edge, http://www.ibm.com/developerworks/rational/library/1748.html.

McConnell 2004. Steve McConnell. Code Complete: A Practical Handbook of Software Construction, Second Edition. Microsoft Press, 2004.

McFeeley 1996. Robert McFeeley. IDEAL: A User's Guide for Software Process Improvement. Pittsburgh, PA: Software Engineering Institute, CMU/SEI-96-HB-001, 1996.

Mili 2002. Hafedh Mili , Reuse-Based Software Engineering: Techniques, Organizations, and Controls. Hoboken, NJ: John Wiley & Sons 2002.

Moore 2004. Bill Moore et al. Eclipse Development Using the Graphical Editing Framework and the Eclipse Modeling Framework, IBM 2004. Found online at http://ibm.com/redbook.

Padburg 2003. Frank Padburg and Matthias M Muller. "Analyzing the Cost and Benefit of Pair Programming." Proceedings of the Ninth International Software Metrics Symposium (METRICS'03), 2003.

Pettichord 2001. Bret Pettichord. "Seven Steps to Test Automation Success." June 2001. Found online at http://www.io.com/~wazmo/papers/seven_steps.html.

Ross 2003. Ronald G Ross. Principles of the Business Rule Approach. Boston: Addison-Wesley, 2003.

Rothman 2004. Johanna Rothman. Hiring the Best Knowledge Workers, Techies & Nerds: The Secrets & Science of Hiring Technical People. New York: Dorset House, 2004.

Royce 1998. Walker Royce. Software Project Management: A Unified Framework. Reading, MA: Addison-Wesley, 1998.

Rumbaugh 2004. James Rumbaugh , Ivar Jacobson , and Grady Booch. The Unified Modeling Language Reference Manual, Second Edition. Boston: Addison-Wesley, 2004.

Santayana 1905. George Santayana. The Life Of Reason, Volume 1.New York:Scribner's, 1905.

Schmidt 2000. Douglas Schmidt , Michael Stal , et al. Pattern-Oriented Software Architecture, Volume 2: Patterns for Concurrent and Networked Objects. Hoboken, NJ: John Wiley, 2000.

Schneider 2001. Geri Schneider and Jason P. Winters. Applying Use Cases: A Practical Approach, Second Edition.Boston: Addison-Wesley, 2001.

Schwaber 2002. Ken Schwaber and M. Beedle. Agile Software Development with SCRUM.Upper Saddle River, NJ: Prentice Hall, 2002.

Schwaber 2004. Ken Schwaber. Agile Project Management with Scrum.Redmond, WA: Microsoft Press, 2004.

Senge 1990. Peter M. Senge. The Fifth Discipline. New York: Doubleday, 1990.

Stapleton 2003. Jennifer Stapleton and DSDM Consortium. DSDM: Business Focused Development, Second Edition. Boston: Addison-Wesley, 2003.

Stojanovic 2005. Zoran Stojanovic and Ajantha Dahanayake, eds. Service-Oriented Software System Engineering: Challenges and Practices. Hershey, PA: Idea Group Publishing, 2005.

Ulrich 2002. William M. Ulrich. Legacy Systems Transformation Strategies.Upper Saddle River, NJ: Prentice Hall, 2002.

White 2005. Stephen A. White. Introduction to BPMN.White Plains, NY: IBM Corporation, 2005.

Whittaker 2003. James Whittaker. How to Break Software: A Practical Guide to Testing. Boston: Addison-Wesley, 2003.

Wideman 2003.R. Max Wideman. "Progressive Acquisition and the RUP Part I-V." The Rational Edge, December 2002April 2003.

Wiegers 2002. Karl Wiegers. Peer Reviews in Software: A Practical Guide. Boston: Addison-Wesley, 2002.

Williams 1998. Laurie Williams et al."Strengthening the Case for Pair Programming."Communications of the ACM, Volume 41, pp. 105108, 1998, and online at http://collaboration.csc.ncsu.edu/laurie/Papers/ieeeSoftware.PDF.

Yourdon 2004. Edward Yourdon . Death March, Second Edition. Upper Saddle River, NJ: Prentice Hall, 2004.

Zurkowski 2002. John Zurkowski. "Magic with Merlin: Working with Assertions." Found online in IBM's developerWorks Web site at http://www-106.ibm.com/developerworks/java/library/j-mer0219.html.