The rational unified process made easy : a practitioner's guide to the RUP PDF
Preview The rational unified process made easy : a practitioner's guide to the RUP
This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Tha.nks [ 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 a comprehensive 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 of component 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 with the RUP-and how to avoid them This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks . >Use this book to get quickly up to speed with the RUP, so you can easily employ the significant power of this process to increase the productivity of your team. [ Team LiB ] This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com 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 Copyright The Addison-Wesley Object Technology Series The Component Software Series FIGURES TABLES Foreword Preface Why We Wrote This Book What You Will Learn from This Book Who Should Read This Book? Structure and Contents of This Book How to Read This Book Part I. Introducing the Rational Unified Process Chapter 1. Introducing the Rational Unified Process What Is the Rational Unified Process? The RUP?The Approach The RUP?A Well-Defined Software Engineering Process The RUP?A Customizable Process Product Conclusion Chapter 2. The Spirit of the RUP: Guidelines for Success Attack Major Risks Early and Continuously. , or They Will Attack You Ensure That You Deliver Value to Your Customer Stay Focused on Executable Software Accommodate Change Early in the Project This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks. Baseline an Executable Architecture Early On Build Your System with Components Work Together as One Team Make Quality a Way of Life, Not an Afterthought Conclusion Chapter 3. Comparing Processes: The RUP, Agile Methods, and Heavyweight Government Standards How Can We Compare Processes? Agile Development: Low-Ceremony, Iterative Approaches SEI CMM, SEI CMMI, ISO/IEC, DOD-STD, MIL-STD: High Ceremony Striving for Higher Predictability The RUP: An Iterative Approach with an Adaptable Level of Ceremony How Iterative Do You Want to Be? How Much Ceremony Do You Want? What Kind of RUP Configuration Meets Your Process Needs? Conclusion Chapter 4. The RUP for a Team of One: Project Deimos A Solo Software Project: Project Deimos The Commitment (Monday Lunch) Digging In (Later Monday) Pressing On (Tuesday) More Progress, More Changes (Wednesday) Nearing Completion (Thursday) Beta and Ship (Friday) Conclusion Part II. The Lifecycle of a Rational Unified Process Project Chapter 5. Going Through the Four Phases A Major Misconception Major Milestones No Fixed Workflows No Frozen Artifacts Three Types of Projects Chapter 6. The Inception Phase Objectives of the Inception Phase Inception and Iterations Objective 1: Understand What to Build Objective 2: Identify Key System Functionality Objective 3: Determine at Least One Possible Solution Objective 4: Understand the Costs, Schedule, and Risks Associated with the Project Objective 5: Decide What Process to Follow and What Tools to Use Project Review: Lifecycle Objective Milestone Conclusion Chapter 7. The Elaboration Phase Objectives of the Elaboration Phase Elaboration and Iterations Objective 1: Get a More Detailed Understanding of the Requirements Objective 2: Design, Implement, Validate, and Baseline the Architecture This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks. Objective 3: Mitigate Essential Risks, and Produce Accurate Schedule and Cost Estimates Objective 4: Refine the Development Case, and Put the Development Environment in Place Project Review: Lifecycle Architecture Milestone Conclusion Chapter 8. The Construction Phase Objectives of the Construction Phase Construction and Its Iterations Objective 1: Minimize Development Costs and Achieve Some Degree of Parallelism Objective 2: Iteratively Develop a Complete Product That Is Ready to Transition to Its User Community Project Review: Initial Operational Capability Milestone Conclusion Chapter 9. The Transition Phase Objectives of the Transition Phase Transition Iterations and Development Cycles Objective 1: Beta Test to Validate That User Expectations Are Met Objective 2: Train Users and Maintainers to Achieve User Self-Reliability Objective 3: Prepare Deployment Site and Convert Operational Databases Objective 4: Prepare for Launch: Packaging, Production, and Marketing Rollout Objective 5: Achieve Stakeholder Concurrence That Deployment Is Complete Objective 6: Improve Future Project Performance Through Lessons Learned Project Review: Product Release Milestone Conclusion Part III. Adopting the Rational Unified Process Chapter 10. Configuring, Instantiating, and Customizing the Rational Unified Process Configuring the RUP Instantiating the RUP in a Project Customizing the RUP Conclusion Chapter 11. Adopting the Rational Unified Process Adopting the RUP in a Project Adopting the RUP in a Large Organization A Typical Program for Moderate Change A Typical Program for Major Change An Aggressive Program for Major Change Conclusion Chapter 12. Planning an Iterative Project Motivation Key Concepts Coarse-Grain and Fine-Grain Plans: Project Plans and Iteration Plans Building a Project Plan Iteration Planning Estimating An Iterative Estimation Technique: Wideband Modified Delphi Optimizing the Project Plan Conclusion This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to regis.ter it. Thanks Chapter 13. Common Mistakes When Adopting and Using the RUP ?and How to Avoid Them Mistakes When Adopting the RUP Mistakes When Managing Iterative Development Mistakes in Analysis, Architecture, Design., Implementation, and Testing Conclusion Part IV. A Role-Based Guide to the Rational Unified Process Chapter 14. A Project Manager's Guide to the RUP The Mission of a Project Manager Project Management Activities of a Project Manager Finding Your Way in the RUP Conclusion Resources for the Project Manager Chapter 15. An Analyst's Guide to the RUP Your Mission as an Analyst Where Do You Start? Understand How Your Business Should Operate Understand Stakeholder Needs Develop a Vision Develop a Use-Case Model and Glossary Example: Use-Case Specification for Register for Courses Fine-Tune Your Models Update and Refine Requirements Ensure That the Requirements Are Delivered and Tested The Analyst's Role in the Rational Unified Process Resources for Analysts Chapter 16. An Architect's Guide to the RUP The Mission of an Architect Architecture An Evolving Role What Do Architects Do? The Architect's Activities in the RUP The Architect's Roles in the RUP Finding Your Way in the RUP Product Resources for the Architect Chapter 17. A Developer's Guide to the RUP Your Mission as a Developer Overview of the Developer's Tasks Understand the Requirements and Design Constraints Design, Implement, and Test Use Cases and Components Design, Implement, and Test Any Necessary Databases Frequently Integrate Your Application with the Work of Other Developers Developer Best Practices Available Resources for Developers This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks . Chapter 18. A Tester's Guide to the RUP The Mission of the Tester What Is Testing? The RUP Testing Philosophy The Test Discipline in the RUP Product Activities of the Tester Conclusion Resources for Testers Glossary Bibliography Index [ Team LiB ] This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to regis.ter it. Thanks [ Team LiB ] Copyright Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and Addison-Wesley was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. Rational Unified Process, RUP, Rational Process Workbench, Rational Rose, Rational RequisitePro, Rational Suite, Rational ClearCase, Rational ClearQuest, Rational XDE, and Rational ProjectConsole are registered trademarks of Rational Software Corporation in the United States and in other countries. Special permission to use and reproduce excerpts and images from the RUP product in The Rational Unified Process Made Easy is granted by Rational Software Corporation. Robillard/Kruchten/d'Astous, Software Engineering Process with the UPEDU, Chapter 1, © 2003 Pearson Education, Inc. Reprinted by permission of Pearson Education, Inc. The authors and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The publisher offers discounts on this book when ordered in quantity for bulk purchases and special sales. For more information, please contact: U.S. Corporate and Government Sales (800) 382-3419 [email protected] For sales outside of the U.S., please contact: International Sales (317) 581-3793 [email protected] Visit Addison-Wesley on the Web: www.awprofessional.com Library of Congress Cataloging-in-Publication Data Kroll, Per. The Rational unified process made easy : a practitioner's guide to the RUP / Per Kroll, Philippe Kruchten. p. cm. Includes bibliographical references and index. ISBN 0-321-16609-4 (alk. paper) 1. Computer software—Development. 2. Software engineering. I. Kruchten, Philippe. II. Title. QA76.76.D47K75 2003 005.1—dc21 2002043780 This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks . Copyright © 2003 by Pearson Education, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior consent of the publisher. Printed in the United States of America. Published simultaneously in Canada. For information on obtaining permission for use of material from this work, please submit a written request to: Pearson Education, Inc. Rights and Contracts Department 75 Arlington Street, Suite 300 Boston, MA 02116 Fax: (617) 848-7047 Text printed on recycled paper 1 2 3 4 5 6 7 8 9 10—CRS—0706050403 First printing, April 2003 Dedication To Susan and Sylvie [ Team LiB ] This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks . [ Team LiB ]
The list of books you might like
