CDN$ 54.99
Usually ships within 3 to 4 weeks.
Ships from and sold by Amazon.ca.
Gift-wrap available.
Quantity:1
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Rational Unified Process, The: An Introduction Paperback – Mar 17 2000


See all 4 formats and editions Hide other formats and editions
Amazon Price New from Used from
Paperback, Mar 17 2000
CDN$ 54.99
CDN$ 9.80 CDN$ 0.01

There is a newer edition of this item:


Up to 90% Off Textbooks

Special Offers and Product Promotions

  • Join Amazon Student in Canada


Customers Who Bought This Item Also Bought



Product Details

  • Paperback: 320 pages
  • Publisher: Addison-Wesley Professional; 2 edition (March 17 2000)
  • Language: English
  • ISBN-10: 0201707101
  • ISBN-13: 978-0201707106
  • Product Dimensions: 18 x 1.3 x 23.4 cm
  • Shipping Weight: 445 g
  • Average Customer Review: 4.1 out of 5 stars  See all reviews (19 customer reviews)
  • Amazon Bestsellers Rank: #1,172,145 in Books (See Top 100 in Books)
  • See Complete Table of Contents

Product Description

Review

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. Read more--Jack Woehr, Dr. Dobb's Journal -- Dr. Dobb's Journal --This text refers to the Textbook Binding edition.

From the Inside Flap

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 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, 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 rational/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 0201707101P04062001

Customer Reviews

4.1 out of 5 stars
Share your thoughts with other customers

Most helpful customer reviews

1 of 1 people found the following review helpful By kashifm on June 13 2004
Format: Paperback
This book introduces the logic behind Rational Unified Process (RUP). RUP is a novel idea. It puts several good practices in a consolidated package. What makes RUP useful is the fact that Rational provides all the necessary software tools to support this. This book does an average job in explaining the RUP. It over stresses obvious and well accepted concepts like "iterative development"; which makes the first half (6 chapters) of this book a bit boring. For a professional with software development and management experience, I found the first sixe chapters are best read at a cursory glance. The second half of the book introduces the workflows - and it is this half that I found more interesting. I finished this book as bed time readoing over the weekend - so this book is an easy reading. However this book is not about teaching how to use Rational Products. This book only gives an overview of the basis of origination of RUP. You would need another book to become an expert in using RUP.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again.
1 of 1 people found the following review helpful By Cem Kaner, J.D, Ph.D. on Oct. 4 2002
Format: Paperback
This book is an introduction to the Rational Unified Process (RUP). It is suitable for readers who have never heard of RUP before and for readers who have little experience with thoughtful analysis of software lifecycles. (I think it's also very useful as a quick, easy-to-read overview of RUP for more advanced readers, but you can read about that use of the book in other reviews.)
I teach Computer Science at Florida Tech, including undergraduate and graduate courses in software testing. Krutchen provides a thoughtful but very readable, persuasive discussion of risks associated with different software lifecycles. In my experience as a teacher, my students' ability to appreciate differences among lifecycles and analyze them critically is significantly boosted by study and discussion of Krutchen. Accordingly, I require my students to read the relevant section of his book, they have detailed small-group discussions of it, and it often appears on their exam.
This book is an introduction. It doesn't address all of the problems with RUP. It doesn't cover all of the areas of RUP equally well. It won't make any reader an expert in the process or its favored practices. It won't persuade someone who doesn't like RUP that they should like. What it does do is expose the reader to the thinking and practices that make up this particular approach to software engineering.
This book is much deeper than marketing fluff, but not so deep as to lose a junior reader. As a teacher, I am delighted to have materials like this available.
(Disclosure: a little bit of my work has been included in RUP, and I have developed a course for Rational on software testing within the Rational process. However, I identify more with the agile development / XP community than with the RUP community.
Read more ›
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again.
Format: Paperback
Target Audience
IT professionals who need to learn about the Rational Unified Process (RUP)
Contents
This book is a relatively high-level overview of the entire RUP process.
The book is divided into the following chapters: Software Development Best Practices; The Rational Unified Process; Static Structure: Process Description; Dynamic Structure: Iterative Development; An Architecture-Centric Process; A Use-Case-Driven Process; The Project Management Discipline; The Business Modeling Discipline; The Requirements Discipline; The Analysis and Design Discipline; The Implementation Discipline; The Test Discipline; The Configuration and Change Management Discipline; The Environment Discipline; The Deployment Discipline; Typical Iteration Plans; Implementing the Rational Unified Process; Summary of Roles; Summary of Artifacts; Acronyms; Glossary; Bibliography; Index
Review
The Rational Unified Process, or RUP, is a software engineering methodology that attempts to map out and document all parts of a software development project. It's extremely comprehensive, but it's also adaptable to whatever level of effort is appropriate for your situation. This book, The Rational Unified Process - An Introduction, is a good start to begin your understanding of RUP.
First off, let me say this is not an easy read. It's a good book with all the information you need to know to start using RUP, but the information is dense and highly detail oriented. Like most developers, I'm more oriented towards coding and testing. But realistically, you need to know what the system should do before you get to the coding piece. RUP helps to put all that into a formal framework so that the necessary things will get done in the proper order.
Read more ›
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again.
Format: Paperback
The Rational Unified Process (RUP) was originally developed by Rational Software, which was recently purchased by IBM. Therefore, you now see the RUP sometimes referred to as IBM's Web-enabled software engineering process. As this name implies, it is a set of guidelines, some soft and others fairly rigid to the point of being a rule, for the creation of software. Like all useful principles of computer science, the RUP is a dynamic entity, being constantly modified to reflect the changes taking place in software creation. Therefore, if you are already familiar with the RUP and are wondering if you should read this book, the answer is an emphatic yes. If you are unfamiliar with the RUP, the answer is an even more emphatic yes.
The purpose of this book is to provide an introduction to RUP 2003, the latest iteration of the process. Like the previous books on RUP, it is written at a level suitable for managers. There is some necessary technical jargon, but nothing beyond what a software project development manager would be expected to be able to comprehend.
The book opens with a history of the RUP, what it is used for and the overall structure of the RUP. This is followed by a very brief introduction to fundamental concepts such as iterative development, architecture-centric processes and use cases. Necessary for beginners, most of this material can be skipped by those having experience in those areas.
Part II covers the various areas, referred to as disciplines. They are:
* The project management discipline.
* The business-modeling discipline.
* The requirements discipline.
* The analysis and design discipline.
* The implementation discipline.
* The test discipline.
* The configuration and change management discipline.
Read more ›
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again.

Most recent customer reviews



Feedback