Appendix Bibliography

This highly selective bibliography records the Rational Process Development group 's favorite books (and a few articles) ”books that have had a major impact on the Rational Unified Process as it stands today, along with books that are complementary to the process and books published recently by our colleagues from Rational Software. Note that some books that could have appeared in several categories are listed only once.

General

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

A classic that should be read and reread by everyone involved in software development. I recommend this edition rather than the original 1975 edition.

Davis, Alan. 1995 201 principle of software development. New York: McGraw-Hill.

Full of good advice for every worker.

Katzenbach, Jon R., and Douglas K. Smith. 1993. The Wisdom of Teams . New York:HarperBusiness.

The secret of effective teams.

Yourdon, Edward 1997. Death March: Managing "Mission Imposible" Projects. Upper Saddle River. NJ:Prentice-Hall.

An interesting view of project troubles, which gives many justifications to our iterative and risk-driven approach.

Software Development Process

Boehm, Barry W. 1996. "Anchoring the Software Process." IEEE Software, July, pp. 73 “82.

This article defines the four phases and the corresponding milestones.

Boehm, Barry W. 1998. "A Spiral Model of Software Development and Enhancement." IEEE Computer, May, pp. 61 “72.

This seminal article defines the principles and motivations of iterative development.

Humphrey, W.S. 1989. Managing the Software Process. Reading, MA: Addison-Wesley.

A classic book on the software process and the capability maturity model developed at the Software Engineering Institute.

ISO/IEC 12207.1995. Information Technology ”Software Life-Cycle Processes; and ISO 9000-3. 1991. Guidelines for the Application of ISO 9001 to the Development, Supply, and Maintenance of Software. Geneva:ISO

Two key standards for software process definition and assessment.

Jacobson, Ivar, Grady Booch, and James Rumbaugh. 1999. The Unified Software Development Process. Reading, MA: Addison Wesley Longman.

This recent textbook is a more detailed description of the principles of the Unified Process and is a useful companion to the Rational Unified Process. Also provides examples of UML modeling.

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

This textbook on software reuse is a great complement to the Rational Unified Process. It also features some great chapters on architecture.

Kruchten, Philippe.1991. "Un processus de d veloppement de logiciel it ratif et centr sur l'architecture." Proceedings of the 4th International Conference on Software Engineering. Toulouse, France, EC2, December.

The Rational iterative process explained in French.

Kruchten, Philippe.1996. "A Rational Development Process" CrossTalk 9(7), pp. 11 “16.

Developed with Walker Royce, Sue Mickel, and a score of Rational consultants , this article describes the iterative lifecycle of the Rational Process.

McFeeley, Robert.1996. IDEAL: A User 's Guide for Software Process Improvement. Pittsburgh, PA: Software Engineering Institute.

This book describes a software process improvement program model: IDEAL, a generic description of a sequence of recommended steps for initiating and managing a process implementation project.

Paulk, Mark, et al. 1993. Capability Maturity Model for Software, Version 1.1. Pittsburgh, PA: Software Engineering Institute.

The original reference for the capability maturity model.

Object-Oriented Technology

Booch, Grady. 1994 Object-Oriented Analysis and Design with Applications, Second -Edition. Menlo Park, CA: Addison-Wesley.

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

Rumbaugh, James, et al. 1991. Object-Oriented Modeling and Design. Englewood Cliffs, NJ: Prentice-Hall.

These three books, the original roots of the object-oriented analysis and design workflow, were written by "the three amigos" just before the advent of the UML and the Rational Unified Process. Despite the use of their original notations, these books are still the key references for the OO designer.

Buhr, R.J.A., and R.S. Casselman. 1996. Use Case Maps for Object-Oriented Systems. Upper Saddle River, NJ: Prentice-Hall.

This book develops views on use cases other than ours.

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

Larman, Craig. 1998. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design. Upper Saddle River, NJ: Prentice-Hall.

An alternate set of artifacts, activities, and guidelines in a process framework not too different from ours.

Rumbaugh, James. 1996. OMT Insights New York: SIGS Books.

A complement to the original OMT book, this dives into special topics: inheritance, use cases, and so on.

Selic, Bran, Garth Gullekson, and Paul Ward.1994. Real-Time Object-Oriented Modeling. New York: John Wiley & Sons.

The reference work on using object technology for the design of reactive systems by the people who developed Rose for Real-Time.

Modeling and the Unified Modeling Language

Booch, G., J. Rumbaugh, and I. Jacobson. 1998. The Unified Modeling Language. Documentation set, version 1.3. Cupertino, CA: Rational Software.

The latest OMG standard on the UML at the time of this writing. Available online at http://www.rational.com.

Booch, Grady, James Rumbaugh, and Ivar Jacobson. 1999. The Unified Modeling Language User Guide. Reading, MA: Addison Wesley Longman.

Published at the same time as the Rational Unified Process 5.0, this manual is an excellent -user's guide on UML by its main authors.

Eriksson, Hans-Erik, and Magnus Penker. 1997. UML Toolkit. New York: John Wiley & Sons.

A comprehensive book on UML as seen from Sweden by another pair of Rational friends .

Fowler, Martin. 1999. UML Distilled: Applying the Standard Object Modeling Language,Second Edition. Reading, MA: Addison Wesley Longman.

A very nice little introduction to UML if you are in a hurry.

Muller, Pierre-Alain. 1998. Instant UML. Chicago: Wrox, Inc.

Another short introduction to UML by a former colleague of ours.

Quatrani, Terry. 1998. Visual Modeling with Rational Rose and UML. Reading, MA: Addison- Wesley Longman.

Provides step-by-step guidance on how to build UML models. At the same time, it follows the Rational Unified Process for which this book provides, in effect, a small-scale example.

Rumbaugh, James, Ivar Jacobson, and Grady Booch.1999. The Unified Modeling Language Reference Manual. Reading, MA: Addison Wesley Longman.

Certainly more digestible than the OMG standard, this book is an in-depth examination of UML by its main authors.

Project Management

Boehm, Barry W. 1991. "Software Risk Management: Principles and Practices." IEEE Software, Jan., pp. 32 “41.

Still the best little introduction to risk management.

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

A pragmatic book for managers of object-oriented projects; one of the sources of the under-lying philosophy of the Rational Unified Process.

Carr Marvin J., et al. 1993. Taxonomy-Based Risk Identification. Technical report CMU/SEI-93-TR-6, SEI, June.

A source of inspiration to get started on your own list of risks.

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

Practical perspective on risk management.

Fairley, Richard. 1994. "Risk Management for Software Projects." IEEE Software 11(3), May, pp. 57 “67.

Straightforward strategy for risk management if you have never done it.

Gilb, Tom. 1988. Principles of Software Engineering Management. Harlow, UK: Addison-Wesley.

A great book by a pioneer of iterative development, full of pragmatic advice for the project manager.

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

An indispensable source of risks to check to make sure your list is complete.

Karolak, Dale. 1996. Software Engineering Risk Management. Los Alamitos, CA: IEEE Computer Society Press.

Offers sophisticated advice and techniques for risk management.

McConnell, Steve. 1998. Software Project Survival Guide. Redmond,WA: Microsoft Press.

O'Connell, Fergus. 1994. How to Run Successful Projects. New York: Prentice-Hall International.

A real gem. Everything you really need to know to manage your first project, in 170 pages.

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

An indispensable companion to the Rational Unified Process, this book describes the spirit and the underlying software economics of the Rational Unified Process. It is full of great advice for the project manager.

Requirements Management

Davis, Alan. 1993. Software Requirements: Objects, Functions and States. Englewood Cliffs, NJ: Prentice-Hall.

Gause, Donald, and Gerald Weinberg.1989. Exploring Requirements: Quality before Design. New York: Dorset House.

IEEE Std 830-1998. 1998. Recommended Practice for Software Requirements Specifications. New York: Software Engineering Standards Committee of the IEEE Computer Society.

Leffingwell, Dean, and D. Widrig. 1999. Managing Software Requirements: A Unified Approach. Reading, MA: Addison Wesley Longman.

Grounded in years of practical experience with numerous projects in a wide range of application, this book extends the requirements workflow with practical tips, examples, cases studies, and war stories.

Weinberg, Gerald. 1995. "Just Say No! Improving the Requirements Process." American Programmer, October.

Configuration Management

Berlack, H. 1992. Software Configuration Management. New York: John Wiley & Sons.

Buckley, F. 1993. Implementing Configuration Management: Hardware, Software and Firmware. Los Alamitos, CA: IEEE Computer Science Press.

White, Brian. 2000. Software Configuration Management Solutions Using ClearCase. Reading, MA: Addison Wesley Longman.

Provides the philosophy and history of configuration management and describes a simple but powerful usage pattern adaptable to a large set of project situations.

Whitgift, David. 1991. Methods and Tools for Software Configuration Management. New York: John Wiley & Sons.

Testing and Quality

Beizer, Boris. 1995. Black Box Testing. New York: John Wiley & Sons.

A treasure of strategies to develop test cases for the functional testing of software. Dr. Beizer's writing style (and wit) makes this book easy and fun to read, with excellent, understandable examples.

Goglia, Patricia. 1993 Testing Client/Server Applications. Wellesley, MA: QED Press.

This was the first book that focused on testing client/server applications.

Hetzel, Bill 1988. The Complete Guide to Software Testing, Second. Edition. New York: J. Wiley/QED Press.

IEEE 829-1983. 1983 Standard for Software Test Documentation. New York: Software Engineering Standards Committee of the IEEE Computer Society.

Perry, William E 1995. Effective Methods for Software Testing. New York: J. Wiley/QED Press.

Schmauch, charles H. 1994 ISO 9000 for Software Developers. Milwaukee, WI: ASQC Quality Press.

Software Architecture

Buschmann, Frank, Regine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stahl.1996. Pattern-Oriented Software Architecture: A System of Patterns. New York: John Wiley & Sons.

This book makes an inventory of a wide range of design patterns at the level of the architecture.

Bass, Len, Paul Clements, and Rick Kazman. 1998. Software Architecture in Practice. Reading, MA: Addison Wesley Longman.

A handbook of software architecture, with numerous case studies.

Hofmeister, Christine, Robert Nord, and Dilip Soni.1999. Applied Software Architecture. Reading, MA: Addison Wesley Longman.

The architectural design approach these authors recommend is very similar to that of the Rational Unified Process and is based on multiple coordinated views.

IEEE Recommended Practice for Architectural Description. 1999. Draft 5.0 of IEEE P1471.

This proposed standard recommends architectural description based on the concept of multiple views.

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

A great companion book to the Rational Unified Process, this book offers insights into the design of components and of systems of interconnected systems. It lays out a strategy for institutionalizing the practice of systematic reuse at the corporate level.

Kruchten, Philippe. 1995. "The 4+1 View Model of Architecture." IEEE Software 12(6).

The origin of the 4+1 views used for architectural description in the Rational Unified Process.

Rechtin, Eberhardt. 1991. Systems Architecting: Creating and Building Complex Systems. Englewood Cliffs, NJ: Prentice-Hall; and Rechtin, Eberhard, and Mark Maier. 1997. The Art of System Architecting. Boca Raton, FL: CRC Press.

Although not directed specifically to software engineers , these two books are extremely valuable for software architects : they introduce an invaluable set of heuristics and many examples of architecture.

Shaw, Mary, and David Garlan. 1996. Software Architecture: Perspectives on an Emerging Discipline. Upper Saddle River, NJ: Prentice Hall.

A good introduction to the concepts and problems of software architecture.

Witt, Bernard I., F. Terry Baker and Everett W. Merritt. 1994. Software Architecture and Design: Principles, Models, and Methods. New York: Van Nostrand Reinhold.

One of the first comprehensive books written on software architecture.

Business Engineering

Eriksson, Hans-Erik, and Magnus Penker. 1999. siness Modeling with UML. New York: John Wiley & Sons.

An alternative approach to that of the RUP, but the business patterns they propose are a very valuable complement to the business engineering workflow.

Hammer, Michael, and James Champy. 1993. Reengineering the Corporation: A Manifesto for Business Revolution. New York: HarperBusiness.

The book that popularized the movement of business (re-)engineering. An excellent complement to the Jacobson book.

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

The basis of the business modeling workflow, this is the first book that applied object technology to the field of business engineering.

Others

Ambler, Scott. 1998. Process Patterns. New York: SIGS Books/CUP.

Ambler, Scott. 1999. More Process Patterns patterns. New York: SIGS Books/CUP.

Constantine, Larry, and Lucy Lockwood. 1999. Software for Use. Reading, MA: Addison Wesley Longman.

A practical guide to the models and methods of usage-centered design, or how user-interface design connects with use cases.

DeGrace, Peter, and Leslie Stahl. 1990. Wicked Problems, Righteous Solutions: A Catalog of Modern Software Engineering Practices. Englewood Cliffs, NJ: Yourdon Press.

An insightful book on various process life cycles, their origins, their flaws, and their strengths; useful for an understanding of the importance of process.

Graham, Ian, Brian Henderson-Sellers, and Houman Younessi. 1997. The OPEN Process Specification. Harlow, UK: Addison-Wesley.

Another process model, this one coming from down under, that shares some principles with the Rational Unified Process.

IBM. 1997. Developing Object-Oriented Software: An Experience-Based Approach. Upper Saddle River, NJ: Prentice-Hall.

As with the Rational Unified Process, this book describes an iterative, incremental, object-oriented-, scenario-driven, risk-aware process developed by IBM's Object Technology Center-.

Kettani, Nasser, et al.1998. De Merise UML. Paris: Editions Eyrolles.

Merise, a popular software development methodology in France, has been upgraded to use UML. It has some similarity to the Rational Unified Process.

McCarthy, J. 1995. Dynamics of Software Development. Redmond, WA: Microsoft Press.

Fifty-three rules of thumb by a Microsoft development manager.

McConnell, Steve. 1993. Code Complete: A Practical Handbook of Software Construction. Redmond, WA: Microsoft Press.

A great book for the implementer and test workers, this looks at the implementation, integration, and test aspects of the development process.

Stapleton, Jennifer. 1997. The Dynamic System Development Method. Reading, MA: Addison Wesley Longman.

At 15,000 feet, the DSDM approach could be seen as an introduction to the Rational Unified Process. Although they use different terminologies, the two processes are very close to each other, and you can see the Rational Unified Process as an instance or an implementation of DSDM.