The Rational Unified Process: An Introduction / Edition 1

Paperback (Print)
Used and New from Other Sellers
Used and New from Other Sellers
from $1.99
Usually ships in 1-2 business days
(Save 93%)
Other sellers (Paperback)
  • All (24) from $1.99   
  • New (4) from $24.66   
  • Used (20) from $1.99   
Close
Sort by
Page 1 of 1
Showing All
Note: Marketplace items are not eligible for any BN.com coupons and promotions
$24.66
Seller since 2014

Feedback rating:

(0)

Condition:

New — never opened or used in original packaging.

Like New — packaging may have been opened. A "Like New" item is suitable to give as a gift.

Very Good — may have minor signs of wear on packaging but item works perfectly and has no damage.

Good — item is in good condition but packaging may have signs of shelf wear/aging or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Acceptable — item is in working order but may show signs of wear such as scratches or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Used — An item that has been opened and may show signs of wear. All specific defects should be noted in the Comments section associated with each item.

Refurbished — A used item that has been renewed or updated and verified to be in proper working condition. Not necessarily completed by the original manufacturer.

New
TEXTBOOK BINDING New 0201604590 Brand New US Edition Book in Perfect Condition. Fast Shipping with tracking number.

Ships from: Houston, TX

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
  • Express, 48 States
  • Express (AK, HI)
$50.00
Seller since 2014

Feedback rating:

(181)

Condition: New
Brand new.

Ships from: acton, MA

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
$50.00
Seller since 2014

Feedback rating:

(181)

Condition: New
Brand new.

Ships from: acton, MA

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
$59.00
Seller since 2008

Feedback rating:

(169)

Condition: New
0201604590 BRAND NEW NEVER USED IN STOCK 125,000+ HAPPY CUSTOMERS SHIP EVERY DAY WITH FREE TRACKING NUMBER

Ships from: fallbrook, CA

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
Page 1 of 1
Showing All
Close
Sort by

Overview

This concise book offers a quick introduction to the concepts, structure, content, and motivation of the Rational Unified Process. This revolutionary software development process provides a disciplined approach to assigning, managing, and completing tasks within a software development organization and is the first development process to exploit the full capabilities of the industry-standard Unified Modeling Language. The Rational Unified Process is unique in that it captures many of the proven best practices in modern software development and presents them in a form that can be tailored to a wide range of projects and organizations. In this book, you will discover: what the Rational Unified Process is - and what it is not; the concepts used in the Rational Unified Process, as well as its structure; the best practices that have been synthesized into this process; and how this process can provide the guidance you need for your specific project responsibilities.
Read More Show Less

Editorial Reviews

Booknews
Offers a quick introduction to the concepts, structure, content, and motivation of the Rational Unified Process, a Web-enabled software engineering process that enhances team productivity and delivers software best practices to all team members. This second edition is updated to match the contents of the latest version of the Rational Unified Process, with more guidance on e-development, applying the process, testing, and designing systems using patterns and frameworks. The author has 25 years of experience in the development of large, software-intensive systems. Annotation c. Book News, Inc., Portland, OR (booknews.com)
Jack Woehr

Rational Is As Rational Does

The Rational Unified Process: An Introduction is a good overview of Rational's prescription for whole-project health. The process is unified as in "Unified Field Theory." Thesis, Antithesis, and Synthesis, (or Booch, Jacobson, and Rumbaugh, as they are known today) twine in a celestial dance to the Spheres, Rectangles, Clouds, and stray pointers that make up UML and its increasingly ambitious extensions, additions, and heroic leaps of faith.

Rational visualizes the elements and modalities of code and projects in a fashion found compelling by increasing numbers of corporate customers. It's a vision embodied in several software suites, including the eponymous Rational Unified Process, for which this book is designed to serve as the introduction. Face it, you are going to run into Rational on the job. This volume is a good place to get know about it.

The book is not an independent assessment of Rational. Editor Philippe Kruchten is lead architect of the Rational Unified Process product. The thrust is the process of processes, specifically process in software projects, as viewed by Rational and supported by its project-management toolsets.

The tone is set for the book in Chapter One, which is Grady Booch's "Software Development Best Practices." Booch lists 19 "Symptoms and Root Causes of Software Development Problems." Booch clearly hasn't worked anywhere I've worked, because missing from his list are "Moron from acquired business unit appointed director," "Manager owns nice suit but can't follow logical proof," and "Inept team member keeps job by threatening suicide."

All of us have our own notations, albeit hastily scribbled, for the steps and players of a project or computational process. Believing, as nerds tend to do, that the methods used to describe program objects and execution steps are suitable for managing human social units, Rational's scientists, to their credit, have elevated napkin scratching and whiteboard scrawls to an art form, and given our industry a certain shared vocabulary of icons for these familiar entities. They've also made a few not entirely obvious comments about software testing that can't do any harm by their addition to the literature.

However, I found nothing new in this volume that was helpful, and nothing helpful that was new. I summarize here at random from The Rational Unified Process:

One should cope with risk by a policy of risk avoidance, risk transfer, risk acceptance, risk mitigation and contingency planning.

A metric is a measurable attribute of an entity.

If you must hit the market early, you can shorten the construction phase and lengthen the transition phase.

In other words, if you can't dazzle them with brilliance, baffle them with ISO-9001. The first two of the above are self-referential and the third is a tautology. We don't need more planning gurus -- we need more software engineers with liberal arts educations and a minor in Formal Logic.

Here are more hastily excerpted gems, with my comments in parentheses:

The following are examples of iteration goals [in the Transition Phase]:

1. Fix all severity 1 problems discovered at beta customer sites.... This may be related to credibility in the market.

(Fix the major problems your beta sites report? What a concept! This could revolutionize software development.)

In building a base plan, you must assess trade-offs between staff, schedule and project scope.

(You mean, I have to carefully marshal my resources? Didn't Sun Tzu say this umpteen years ago? Doesn't anyone read classics anymore?)

The scary thing is that statements like these may come as news to some folks working for your company. Apparently, they are the intended audience, those people who know nada about software development yet are managing projects (and who also, one assumes, have purchase authority for project management software).

A good idea, well-positioned within the technology of the time and in accordance with the genuine needs of an informed user group, designed and executed by a team sharing a vision and managed by an inscrutable, diplomatic, restrained, and benevolent management team... In such a case development, delivery, installation, training, and maintenance are simplicity itself and demand no special tools at all.

It's the worst-designed programs that you spend the most time debugging, and it's the worst thought-out projects that are laden with fashionable project-management tools. In my worm's-eye view, you will always find management using these tools on the screwed-up projects.

Assuming I'm correct in my assessment, we can probably expect the Rational Unified Process to be mandated by law in the near future. With that in mind, The Rational Unified Process: An Introduction is a mercifully short introduction.--Dr. Dobb's Electronic Review of Computer Books

Read More Show Less

Product Details

  • ISBN-13: 9780201604597
  • Publisher: Addison-Wesley
  • Publication date: 11/1/1998
  • Series: Object Technology Series
  • Edition description: Older Edition
  • Edition number: 1
  • Pages: 255
  • Product dimensions: 7.04 (w) x 9.00 (h) x 0.58 (d)

Meet the Author


Philippe Kruchten is the lead architect of the Rational Unified Process product. He has more than 25 years of experience in the development of large, softwareintensive systems in the areas of telecommunication, defense, aerospace, transportation, and software development tools. He holds a degree in mechanical engineering from the Ecole Centrale de Lyon (France) and a doctorate in computer science from the French Institute of Telecommunications.
Read More Show Less

Read an Excerpt

PREFACE:

The Rational Unified Process is a software engineering process developed and marketed by Rational Software. It is a disciplined approach to assigning and managing tasks and responsibilities in a development organization. The goal of this process is to produce, within a predictable schedule and budget, high-quality software that meets the needs of its end users.

The Rational Unified Process captures many of the best practices in modern software development and presents them in a tailorable form that is suitable for a wide range of projects and organizations. The Rational Unified Process delivers these best practices to the project team online in a detailed, practical form.

This book provides an introduction to the concepts, structure, contents, and motivation of the Rational Unified Process.

Goals of This Book

In this book, you will

  • learn what the Rational Unified Process is and what it is not;
  • master the vocabulary of the Rational Unified Process and understand its structure;
  • develop an appreciation for the best practices that we have synthesized in this process; and
  • understand how the Rational Unified Process can give you the guidance you need for your specific responsibility in a project.

This book is an integral part of the Rational Unified Process, but it is not the complete Rational Unified Process. Rather, it is a small subset. In the full Rational Unified Process you will find the detailed guidance needed to carry out your work. The full Rational Unified Process product—the online knowledge base—can be obtained from Rational Software.

This book makes numerousreferences to the Unified Modeling Language (UML), but it is not an introduction to the UML. That is the focus of two other books: The Unified Modeling Language User Guide and The Unified Modeling Language Reference Manual.

This introductory book speaks about modeling and object-oriented techniques, but it is not a design method, and it does not teach you how to model. Detailed steps and guidance on the various techniques that are embedded in the Rational Unified Process can be found only in the process product.

Several chapters of this book discuss project management issues. They describe aspects of planning an iterative development, managing risks, and so on. This book, however, is by no means a complete manual on project management and software economics. For more information, we refer you to the book Software Project Management: A Unified Framework.

The Rational Unified Process is a specific and detailed instance of a more generic process described in the textbook The Unified Software Development Process.

Who Should Read This Book?

The Rational Unified Process, An Introduction, Second Edition is written for a wide range of people involved in software development: project managers, developers, quality engineers, process engineers, method specialists, system engineers, and analysts.

This book is relevant especially to members of an organization that has adopted the Rational Unified Process or is about to adopt it. It is likely that an organization will tailor the Rational Unified Process to suit its needs, but the core process described in this book should remain the common denominator across all instances of the Rational Unified Process.

This book will be a useful companion to students taking one of the many professional education courses delivered by Rational Software and its partners in industry and academia. It provides a general context for the specific topics covered by the course.

This book assumes that you have a basic understanding of software development. It does not require specific knowledge of a programming language, of an object-oriented method, or of the Unified Modeling Language.

How to Use This Book

Software professionals who are working in an organization that has adopted the Rational Unified Process, in whole or part, should read the book linearly. The chapters have been organized in a natural progression.

Project managers can limit their reading to Chapters 1, 2, 4, and 7, which provide an introduction to the implications of an iterative, risk-driven development process.

Process engineers or methodologists may have to tailor and install the Rational Unified Process in their organizations. They should carefully study Chapters 3 and 17, which describe the process structure and the overall approach to implementing the Rational Unified Process.

Organization and Special Features

The book has two parts: Part I describes the process, its context, its history, its structure, and its software development lifecycle. It describes some of the key features that differentiate the Rational Unified Process from other software development processes:

  • Chapter 1: Software Development Best Practices
  • Chapter 2: The Rational Unified Process
  • Chapter 3: Static Structure: Process Description
  • Chapter 4: Dynamic Structure: Iterative Development
  • Chapter 5: An Architecture-centric Process
  • Chapter 6: A Use-Case-Driven Process


Part II gives an overview of the various process components, or workflows. There is one chapter for each core process workflow.

  • Chapter 7: The Project Management Workflow
  • Chapter 8: The Business Modeling Workflow
  • Chapter 9: The Requirements Workflow
  • Chapter 10: The Analysis and Design Workflow
  • Chapter 11: The Implementation Workflow
  • Chapter 12: The Test Workflow
  • Chapter 13: The Configuration and Change Management Workflow
  • Chapter 14: The Environment Workflow
  • Chapter 15: The Deployment Workflow
  • Chapter 16: Typical Iteration Plans
  • Chapter 17: Configuring and Implementing the Rational Unified Process


Most workflow chapters are organized into six sections:

  • Purpose of the workflow
  • Definitions and key concepts
  • Workers and artifacts
  • A typical workflow: an overview of the activities
  • Tool support
  • Summary


Two appendixes summarize all the workers (the roles of the process) and artifacts (the work products of the process) that are introduced in Chapters 7 through 15. A list of acronyms and glossary of common terms are provided, as is a short annotated bibliography.

For More Information

Information about the Rational Unified Process, such as a data sheet and a downloadable demo version, can be obtained from Rational Software via the Internet at www.rational.com/rup_info/.

If you are already using the Rational Unified Process, additional information is available from the Rational Unified Process Resource Center, which has extra goodies, updates, and links to partners. The hyperlink to the Resource Center is in the online version.

Academic institutions can contact Rational Software for information on a special program for including the Rational Unified Process in the curriculum.

Second Edition

This second edition of The Rational Unified Process: An Introduction makes the book current with the Rational Unified Process 2000. With this latest release, the Rational Unified Process has improved in both breadth and depth. In breadth, new content has been added to cover business engineering, management of nonfunctional requirements, and development and deployment of multitier distributed applications. Existing content has been refined as well, including improved coverage of application interface design (especially applied to developing effective Web applications) and designing systems using patterns and frameworks. Coverage for developing real-time and reactive systems has also been added. Testing has been expanded to cover the entire lifecycle, from validation of architectural prototypes to verification of the delivered product. Finally, process roadmaps have been added that provide overviews of how to apply the process to different kinds of projects and technologies. In addition, content depth has been added, including expanded checklists and guidelines for process artifacts, activities, and phases.

Acknowledgments

The Rational Unified Process reflects the wisdom of a great many software professionals from Rational Software and elsewhere. The history of the process can be found in Chapter 2. But putting together a book, even as small and modest as this one, required the dedicated effort of a slate of people, whom I would like to recognize here.

The members of the Rational Process Development Group assembled the Rational Unified Process and contributed to this introduction. You will see some of their names associated with specific chapters.

  • Kurt Bittner contributed to the analysis and design chapter, contributed to project management and test, and developed the data engineering aspects.
  • Maria Ericsson developed the business engineering and requirements management aspect and was a keeper of the process architecture.
  • Leslee Probasco contributed to the requirements management workflow.
  • Stefan Bylund contributed to the analysis and design chapter and integrated the user-interface design aspects.
  • Håkan Dyrhage contributed many ideas to the organization and structure of the process and to its implementation and configuration and also coordinated the development of the online version.
  • John Smith expanded the project management aspects for RUP 2000.
  • Jas Madhur contributed the ideas on configuration management, change management, and deployment.
  • Bruce Katz contributed the testing aspects of the process.
  • Margaret Chan was responsible for the product integration and for the assembly of most of the artwork in this book.
  • Debbie Gray is the devoted administrative assistant of a team spread across nine time zones.

We are very grateful to Grady Booch for writing Chapter 1.

Per Kroll is the marketing manager for the Rational Unified Process, and Paer Jansson is its product manager, joined recently by Matt Herdon. Christina Gisselberg and Eric Turesson designed and developed the online version. Stefan Ahlqvist developed the ideas on user-interface design. Chinh Vo helped assemble the book.

The Rational Unified Process and this book benefited from the reviews and ideas of Dave Bernstein, Grady Booch, Geoff Clemm, Catherine Connor, Mike Devlin, Christian Ehrenborg (Dr. Usecase), Sam Guckenheimer, Björn Gustafsson, Ivar Jacobson, Ron Krubek, Dean Leffingwell, Andrew Lyons, Bruce Malasky, Roger Oberg, Gary Pollice, Leslee Probasco, Terri Quatrani, Walker Royce, Jim Rumbaugh, John Smith, and Brian White.

We would also like to thank our partners—Scott Ambler, Ensemble Systems, IBM Global Services, and Content Integration—for their contributions.

Special thanks go to the Rational field, and especially our British friends, who have always had some special interest in the Rational process: Ian Gavin, Ian Spence, and Mike Tudball.

The Frenglish and the Swenglish were ironed out by Joy Hemphill and Pamela Clarke.

And finally many thanks to our editor, J. Carter Shanklin, as well as Kristin Erickson, Marilyn Rash and her team, and all the staff at Addison Wesley Longman for getting this book out as quickly as they did.

Philippe Kruchten
Vancouver, B.C., Canada


Read More Show Less

Table of Contents

Preface
Pt. I The Process 1
1 Software Development Best Practices 3
2 The Rational Unified Process 17
3 Static Structure: Process Description 35
4 Dynamic Structure: Iterative Development 53
5 An Architecture-Centric Process 81
6 A Use-Case-Driven Process 97
Pt. II Process Disciplines 111
7 The Project Management Discipline 113
8 The Business Modeling Discipline 141
9 The Requirements Discipline 157
10 The Analysis and Design Discipline 173
11 The Implementation Discipline 187
12 The Test Discipline 197
13 The Configuration and Change Management Discipline 215
14 The Environment Discipline 229
15 The Deployment Discipline 237
16 Typical Iteration Plans 247
17 Implementing the Rational Unified Process 259
App. A Summary of Roles 273
App. B Summary of Artifacts 277
App. C: Acronyms 281
Glossary 283
Bibliography 291
Index 299
Read More Show Less

Preface

The Rational Unified Process is a software engineering process developed and marketed by Rational Software. It provides a disciplined approach to assigning and managing tasks and responsibilities within a development organization. The goal of this process is to produce, within a predictable schedule and budget, high-quality software that meets the needs of its end users.

The Rational Unified Process captures many of the best practices in modern software development and presents them in a tailorable form that is suitable for a wide range of projects and organizations. The Rational Unified Process delivers these best practices to the project team online in a detailed, practical form.

This book provides an introduction to the concepts, structure, contents, and motivation of the Rational Unified Process.

Goals of this book In this book, you will Learn what the Rational Unified Process is and what it is not Master the vocabulary of the Rational Unified Process and understand its structure Develop an appreciation for the best practices that we have synthesized in this process Understand how the Rational Unified Process can give you the guidance you need for your specific responsibility in a project

This book is an integral part of the Rational Unified Process, but it is not the complete Rational Unified Process. Rather, it is only a small subset. In the full Rational Unified Process you will find the detailed guidance needed to carry out your work. See Chapter 2, Figure 2-2 for a complete map of all the manuals that constitute the Rational Unified Process. The full Rational Unified Process product-the online knowledge base-can be obtained from Rational Software.

This introductory book makes numerous references to the Unified Modeling Language (UML), but it is not an introduction to the UML. That is the focus of two other books: The Unified Modeling Language User Guide and The Unified Modeling Language Reference Manual . This introductory book speaks about modeling and object-oriented techniques, but it is not a design method and it does not teach you how to model. Detailed steps and guidance on the various techniques that are embedded in the Rational Unified Process can be found only in the process product.

Several chapters of this book discuss project management issues. They describe aspects of planning an iterative development, managing risks, and so on. This book, however, is by no means a complete manual on project management and software economics. For more information, we refer you to the book Software Project Management: A Unified Framework.

The Rational Unified Process is a specific and detailed instance of a more generic process described in the textbook The Unified Software Development Process.

 

Who should read this book?

The Rational Unified Process: An Introduction is written for a wide range of people involved in software development: project managers, developers, quality engineers, process engineers, method specialists, system engineers, and analysts.

This book is especially relevant to members of an organization that has adopted the Rational Unified Process or is about to adopt it. It is likely that an organization will tailor the Rational Unified Process to suit its needs, but the core process described in this book should remain the common denominator across all instances of the Rational Unified Process. This book will be a useful companion to students taking one of the many professional education courses delivered by Rational Software and its partners from industry and academia. It provides a general context for the specific topics covered by the course. This book assumes that you have a basic understanding of software development. It does not require any specific knowledge of a programming language, of an object-oriented method, or of the Unified Modeling Language.

 

How to use this book

Software professionals who are working in an organization that has adopted the Rational Unified Process, in whole or part, should read the book linearly. The chapters have been organized in a natural progression.

Project managers can limit their reading to Chapters 1, 2, 4, and 7, which provide an introduction to the implications of an iterative, risk-driven development process. Process engineers or methodologists may have to tailor and install the Rational Unified Process in their organizations. They should carefully study Chapters 3 and 17, which describe the process structure and the overall approach to implementing the Rational Unified Process.

 

Organization and special features

The book has two parts.

Part I describes the process, its context, its history, its structure, and its software development life cycle. It describes some of the key features that differentiate the Rational Unified Process from other software development processes.

  • Chapter 1: Software Development Best Practices
  • Chapter 2: The Rational Unified Process
  • Chapter 3: Static Structure: Process Representation
  • Chapter 4: Dynamic Structure: Iterative Development
  • Chapter 5: An Architecture-Centric process
  • Chapter 6: A Use-Case-Driven Process

 

Part II gives an overview of the various process components, or workflows. There is one chapter for each core process workflow.

  • Chapter  7 : The Project Management Workflow
  • Chapter  8 : The Business Modeling Workflow
  • Chapter  9 : The Requirements Workflow
  • Chapter 10: The Analysis and Design Workflow
  • Chapter 11: The Implementation Workflow
  • Chapter 12: The Test Workflow
  • Chapter 13: The Configuration and Change Management Workflow
  • Chapter 14: The Deployment Workflow
  • Chapter 15: The Environment Workflow
  • Chapter 16: Iteration Workflows
  • Chapter 17: Implementing the Rational Unified Process

Most workflow chapters are organized into six sections: Purpose of the workflow Definitions and key concepts Workers and artifacts A typical workflow: an overview of the activities Tool support Summary

Two appendixes summarize all the workers (the "roles" of the process) and artifacts (the "work products" of the process) that are introduced in Chapters 7 through 15. A Glossary of common terms is provided, as is a short annotated Bibliography. acknowledgments

The Rational Unified Process reflects the wisdom of a great many software professionals from Rational Software and elsewhere. The history of the process can be found in Chapter 2. But pulling out a book, even as small and modest as this one, required the dedicated effort of a slate of people, whom I would like to recognize here.

The members of the Rational Process Development Group assembled the Rational Unified Process 5.0 and contributed to this introduction. You will see some of their names associated with specific chapters.

Maria Ericsson developed the business modeling and requirements management aspect and was a keeper of the process architecture.

Stefan Bylund contributed to the analysis and design chapter and integrated the user-interface design aspects.

Kurt Bittner contributed to the analysis and design chapter, contributed to project management, and developed the data engineering aspects.

Håkan Dyrhage contributed many ideas to the organization and structure of the process and to its implementation and configuration and also coordinated the development of the online version.

Jas Madhur contributed the ideas on configuration management and change management. Bruce Katz contributed the testing aspects of the process.

Margaret Chan was responsible for the product integration, and for the assembly of most of the artwork in this book.

Debbie Gray is the devoted administrative assistant of a team spread across nine time zones. We are very grateful to Grady Booch for writing Chapter 1.

Per Kroll is the marketing manager for the Rational Unified Process, and Paer Jansson is its product manager. Christina Gisselberg and Eric Turesson designed and developed the online version. Stefan Ahlqvist developed the ideas on user-interface design.

The Rational Unified Process and this book benefited from the reviews and ideas of Dave Bernstein, Grady Booch, Geoff Clemm, Catherine Connor, Mike Devlin, Christian Ehrenborg (Dr. Usecase), Sam Guckenheimer, Björn Gustafsson, Ivar Jacobson, Ron Krubek, Dean Leffingwell, Andrew Lyons, Bruce Malasky, Roger Oberg, Gary Pollice, Leslee Probasco, Terri Quatrani, Walker Royce, Jim Rumbaugh, John Smith, and Brian White.

Special thanks go to our British friends, who have always had some special interest in the Rational process: Ian Gavin, Ian Spence, and Mike Tudball.

The Frenglish and the Sweglish were ironed out by Joy Hemphill and Pamela Clarke. And finally many thanks to my editor, J. Carter Shanklin, as well as Krysia Bebick, Marilyn Rash and her team, and all the staff at Addison Wesley Longman for getting this book out as quickly as they did.

For more information Information about the Rational Unified Process, such as a data sheet and a downloadable demo version, can be obtained from Rational Software via the Internet at (www.rational.com/rup_info/). If you are already using the Rational Unified Process, additional information is available from the Rational Unified Process Resource Center, which has extra goodies, updates, and links to partners. The hyperlink to the Resource Center is in the online version. Academic institutions can contact Rational Software for information on a special program for including the Rational Unified Process in the curriculum.

Philippe Kruchten
Vancouver, B.C. Canada

Read More Show Less

Introduction

The Rational Unified Process is a software engineering process developed and marketed originally by Rational Software, and now IBM. It is a disciplined approach to assigning and managing tasks and responsibilities in a development organization. The goal of this process is to produce, within a predictable schedule and budget, high-quality software that meets the needs of its end users.

The Rational Unified Process captures many of the best practices in modern software development and presents them in a tailorable form that is suitable for a wide range of projects and organizations. The Rational Unified Process delivers these best practices to the project team online in a detailed, practical form.

This book provides an introduction to the concepts, structure, contents, and motivation of the Rational Unified Process.

GOALS OF THIS BOOK

In this book, you will

  • Learn what the Rational Unified Process is and what it is not.
  • Master the vocabulary of the Rational Unified Process.
  • Understand its structure.
  • Develop an appreciation for the best practices that we have synthesized in this process.
  • Understand how the Rational Unified Process can give you the guidance you need for your specific responsibility in a project.

This book is not the complete Rational Unified Process. Rather, it is a small subset to introduce the RUP. In the full Rational Unified Process you will find the detailed guidance needed to carry out your work. The full Rational Unified Process—the online knowledge base—is a product that can be obtained from IBM.

This book makes numerous references to the UnModeling Language (UML), but it is not an introduction to the UML. That is the focus of two other books: The Unified Modeling Language User Guide and The Unified Modeling Language Reference Manual.

This introductory book speaks about modeling and object-oriented techniques, but it is not a design method, and it does not teach you how to model. Detailed steps and guidance on the various techniques that are embedded in the Rational Unified Process can be found only in the process product.

Several chapters of this book discuss project management issues. They describe aspects of planning an iterative development, managing risks, and so on. This book, however, is by no means a complete manual on project management and software economics. For more information, we refer you to the book Software Project Management: A Unified Framework.

The Rational Unified Process is a specific and detailed instance of a more generic process described in the textbook The Unified Software Development Process.

WHO SHOULD READ THIS BOOK?

The Rational Unified Process, Third Edition is written for a wide range of people involved in software development: project managers, developers, quality engineers, process engineers, method specialists, system engineers, and analysts.

This book is relevant especially to members of an organization that has adopted the Rational Unified Process or is about to adopt it. It is likely that an organization will tailor the Rational Unified Process to suit its needs, but the core process described in this book should remain the common denominator across all instances of the Rational Unified Process.

This book will be a useful companion to students taking one of the many professional education courses delivered by IBM Rational Software and its partners in industry and academia. It provides a general context for the specific topics covered by the course.

This book assumes that you have a basic understanding of software development. It does not require specific knowledge of a programming language, of an object-oriented method, or of the Unified Modeling Language.

HOW TO USE THIS BOOK

Software professionals who are working in an organization that has adopted the Rational Unified Process, in whole or part, should read the book linearly. The chapters have been organized in a natural progression.

Project managers can limit their reading to Chapters 1, 2, 4, and 7, which provide an introduction to the implications of an iterative, risk-driven development process.

Process engineers or methodologists may have to tailor and install the Rational Unified Process in their organizations. They should carefully study Chapters 3, 14 and 17, which describe the process structure and the overall approach to implementing the Rational Unified Process.

ORGANIZATION AND SPECIAL FEATURES

The book has two parts.

Part I describes the process, its context, its history, its structure, and its software development lifecycle. It describes some of the key features that differentiate the Rational Unified Process from other software development processes:

  • Chapter 1: Software Development Best Practices
  • Chapter 2: The Rational Unified Process
  • Chapter 3: Static Structure: Process Description
  • Chapter 4: Dynamic Structure: Iterative Development
  • Chapter 5: An Architecture-centric Process
  • Chapter 6: A Use-Case-Driven Process

Part II gives an overview of the various components of process, or disciplines. There is one chapter for each discipline.

  • Chapter 7: The Project Management Discipline
  • Chapter 8: The Business Modeling Discipline
  • Chapter 9: The Requirements Discipline
  • Chapter 10: The Analysis and Design Discipline
  • Chapter 11: The Implementation Discipline
  • Chapter 12: The Test Discipline
  • Chapter 13: The Configuration and Change Management Discipline
  • Chapter 14: The Environment Discipline
  • Chapter 15: The Deployment Discipline
  • Chapter 16: Typical Iteration Plans
  • Chapter 17: Implementing the Rational Unified Process

Most discipline chapters are organized into six sections:

  • Purpose of the discipline
  • Definitions and key concepts
  • Roles and artifacts
  • A typical workflow: an overview of the activities
  • Tool support
  • Summary

Two appendixes summarize all the roles of the process and artifacts (the workproducts of the process) that are introduced in Chapters 7 through 15. A list of acronyms and glossary of common terms are provided, as is an annotated bibliography.

FOR MORE INFORMATION

Information about the Rational Unified Process, such as a data sheet and a downloadable demo version, can be obtained from IBM, Rational Software via the Internet.

If you are already using the Rational Unified Process, additional information is available from the Rat and links to partners. The hyperlink to the RDN is in the online version of RUP.

Academic institutions can contact IBM for information on a special program for including the Rational Unified Process in the curriculum.

SECOND EDITION

The second edition of The Rational Unified Process: An Introduction made the book current with the Rational Unified Process 2000.

THIRD EDITION

This third edition of The Rational Unified Process: An Introduction makes the book current with the Rational Unified Process 2003. This edition implements several changes of terminology, some redesign of parts of the process (in particular, the test and environment disciplines), as well as the further development of RUP as a process framework. New elements are introduced, such as the concept of process components and process plug-ins, a new tool set: RUP Modeler, RUP Organizer, RUP Builder and MyRUP, and the introduction of a separate Process Engineering Process. It incorporates the feedback of many readers, and acknowledges the acquisition of Rational Software by IBM.

ACKNOWLEDGMENTS

The Rational Unified Process reflects the wisdom of a great many software professionals from Rational Software and elsewhere. The history of the process can be found in Chapter 2. But putting together a book, even as small and modest as this one, required the dedicated effort of a slate of people, whom I would like to recognize here.

Early members of the Process Development Group assembled the Rational Unified Process and contributed to this introduction. Stefan Bylund, then Kurt Bittner, and finally Bruce Macisaac contributed to the analysis and design chapter. Maria Ericsson developed the business engineering and requirements management aspect with Leslee Probasco. The test part was started by Bruce Katz, and then completely redesigned by Paul Szymkowiak. John Smith expanded the project management aspects for RUP 2000. Jas Madhur contributed the ideas on configuration management, change management, and deployment. Hakan Dyrhage had contributed many ideas to the organization and structure of the process and to its implementation and configuration. Margaret Chan was responsible for the product integration and for the assembly of most of the artwork in this book with Susan Buie. Sigurd Hopen developed the PEP, with the help of Bjoern Gustafsson.

Per Kroll is the manager of the development group, Mike Barnard the product manager. Alfredo Bencomo, Chinh Vo, Philip Denno, Lars Jenzer, Glenys Macisaac and Fionna Chong developed the product infrastructure. And Debbie Gray is the devoted administrative assistant of a team spread across nine time zones.

The Rational Unified Process and this book benefited over the 8 years from the reviews and ideas of Stefan Ahl-qvist, Dave Bernstein, Grady Booch, Murray Cantor, Geoff Clemm, Catherine Connor, Mike Devlin, Christian Ehrenborg, Ian Gavin, Christina Gissel-berg, Sam Guckenheimer, Bjoern Gustafsson, Matt Herdon, Ivar Jacobson, Paer Jansson, Ron Krubek, Dean Leffingwell, Andrew Lyons, Bruce Malasky, Roger Oberg, Gary Pollice, Terri Quatrani, Walker Royce, Jim Rumbaugh, Ian Spence, John Smith, and Brian White.

We are very grateful to Grady Booch for writing Chapter 1.Special thanks go to the Rational field, members of our Chat_RUP list, and our users, members of the RUP_Forum, for their feedback, and contributions. And finally many thanks to our editor Mary O'Brien, our former editor J. Carter Shanklin, as well as Brenda Mulligan, Kristin Erickson, Marilyn Rash and her team, and all the staff at Addison-Wesley for getting this book out as quickly and smoothly as they did.

—Philippe Kruchten
Vancouver, B.C., Canada
Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)