This document was created by an unregistered ChmMagic, please go to register it. Thanks.
[ Team LiB ]
• Table of Contents
• Index
Rational Unified Process Made Easy: A Practitioner's Guide to the RUP, The
By Per Kroll, Philippe Kruchten
Publisher: Addison Wesley
Pub Date: April 11, 2003
ISBN: 0-321-16609-4
Pages: 464
"Per Kroll and Philippe Kruchten are especially well suited to explain the RUP...because they have been the central forces inside
Rational Software behind the creation of the RUP and its delivery to projects around the world."
-From the Foreword by Grady Booch
This book is prehensive guide to modern software development practices, as embodied in the Rational Unified Process, or RUP.
With the help of this book's practical advice and insight, software practitioners will learn how to tackle challenging development
projects-small and large-using an iterative and risk-driven development approach with a proven track record.
The Rational Unified Process Made Easy will teach you the key points involved in planning and managing iterative projects, the
fundamentals ponent design and software architecture, and the proper employment of use cases. All team members--from project
managers to analysts, from developers to testers--will learn how to immediately apply the RUP to their work. You will learn that the RUP
is a flexible, versatile process framework that can be tailored to suit the needs of development projects of all types and sizes.
Key topics covered include:
How to use the RUP to develop iteratively, adopt an architecture-centric approach, mitigate risk, and verify software quality
Tasks associated with the four phases of the RUP: Inception, Elaboration, Construction, and Transition
Roles and responsibilities of project managers, architects, analysts, developers, testers, and process engineers in a RUP
project
Incrementally adopting the RUP with minimal risk
Common patterns for failure
Addison Wesley - The Rational Unified Process Made Easy - A Practitioner's Guide To The RUP (2003) 来自淘豆网m.daumloan.com转载请标明出处.