Home > Store

Rational Unified Process Made Easy, The: A Practitioner's Guide to the RUP

Register your product to gain access to bonus material or receive a coupon.

Rational Unified Process Made Easy, The: A Practitioner's Guide to the RUP

eBook (Watermarked)

  • Your Price: $35.19
  • List Price: $43.99
  • Includes EPUB, MOBI, and PDF
  • About eBook Formats
  • This eBook includes the following formats, accessible from your Account page after purchase:

    ePub EPUB The open industry format known for its reflowable content and usability on supported mobile devices.

    MOBI MOBI The eBook format compatible with the Amazon Kindle and Amazon Kindle applications.

    Adobe Reader PDF The popular standard, used most often with the free Adobe® Reader® software.

    This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.

Description

  • Copyright 2003
  • Edition: 1st
  • eBook (Watermarked)
  • ISBN-10: 0-13-265131-9
  • ISBN-13: 978-0-13-265131-8

"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

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.

Sample Content

Table of Contents



Figures.


Tables.


Foreword.


Preface.

I. INTRODUCING THE RATIONAL UNIFIED PROCESS.

1. Introducing the Rational Unified Process.

What Is the Rational Unified Process?

The RUP—The Approach.

Underlying Principles of the RUP Approach.

The RUP and Iterative Development.

The RUP--A Well-Defined Software Engineering Process.

The Dynamic Structure of the Rational Unified Process.

The Static Structure of the Rational Unified Process.

The RUP-A Customizable Process Product.

Configuration and Process Authoring Tools.

Process Delivery Tools.

Who Uses the RUP Product?

Conclusion.

2. The Spirit of the RUP: Guidelines for Success.

Attack Major Risks Early and Continuously, or They Will Attack You.

Summary.

Ensure That You Deliver Value to Your Customer.

Summary.

Stay Focused on Executable Software.

Summary.

Accommodate Change Early in the Project.

Summary.

Baseline an Executable Architecture Early On.

Summary.

Build Your System with Components.

Summary.

Work Together as One Team.

Summary.

Make Quality a Way of Life, Not an Afterthought.

Summary.

Conclusion.

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.

SEI CMM: Process Assessment Framework.

SEI CMMI: Process Assessment Framework.

ISO/IEC 15504: Process Assessment Framework.

DOD-STD and MIL-STD: High-Ceremony Processes.

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?

Project Deimos: Team of One.

Project Ganymede: Small Project with Tight Timeline.

Project Mars: Average-Size Project without Iterative Development Experience.

Project Jupiter: Large Distributed Project.

Conclusion.

4. The RUP for a Team of One: Project Deimos.

A Solo Software Project: Project Deimos.

The Seminal Idea (Saturday Night).

The Proposal (Monday Morning).

The Vision.

The Plan.

The Risk List.

The Business Case.

The Architecture.

The Commitment (Monday Lunch).

The Vision, Take Two.

The Plan, Take Two.

The Risk List, Take Two.

The Business Case, Take Two.

Digging In (Later Monday).

Pressing On (Tuesday).

More Progress, More Changes (Wednesday).

Nearing Completion (Thursday).

Beta and Ship (Friday).

Conclusion.

II. THE LIFECYCLE OF A RATIONAL UNIFIED PROCESS PROJECT.

5. Going Through the Four Phases.

A Major Misconception.

Major Milestones.

No Fixed Workflows.

No Frozen Artifacts.

Three Types of Projects.

6. The Inception Phase.

Objectives of the Inception Phase.

Inception and Iterations.

Objective 1: Understand What to Build.

Produce a Vision Document.

Generate a “Mile-Wide, Inch-Deep” Description.

Hold a Workshop or Brainstorming Session.

Detail Key Actors and Use Cases.

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.

7. The Elaboration Phase.

Objectives of the Elaboration Phase.

Elaboration and Iterations.

First Iteration in Elaboration.

Second Iteration in Elaboration.

Objective 1: Get a More Detailed Understanding of the Requirements.

Objective 2: Design, Implement, Validate, and Baseline the Architecture.

Architecture: Defining Subsystems, Key Components, and Their Interfaces.

Use Architecturally Significant Use Cases to Drive the Architecture.

Design Critical Use Cases.

Consolidate and Package Identified Classes.

Ensure Architectural Coverage.

Design the Database.

Outline Concurrency, Processes, Threads, and Physical Distribution.

Identify Architectural Mechanisms.

Implement Critical Scenarios.

Integrate Components.

Test Critical Scenarios.

What Is Left to Do?

Objective 3: Mitigate Essential Risks, and Produce Accurate Schedule and Cost Estimates.

Plan the Project and Estimate Costs.

Objective 4: Refine the Development Case and Put the Development Environment in Place.

Project Review: Lifecycle Architecture Milestone.

Conclusion.

8. The Construction Phase.

Objectives of the Construction Phase.

Construction and Its Iterations.

Objective 1: Minimize Development Costs and Achieve Some Degree of Parallelism.

Organize Around Architecture.

Configuration Management.

Enforce the Architecture.

Ensure Continual Progress.

Objective 2: Iteratively Develop a Complete Product That is Ready to Transition to Its User Community.

Describe the Remaining Use Cases and Other Requirements.

Fill in the Design.

Design the Database.

Implement and Unit-Test Code.

Do Integration and System Testing.

Early Deployments and Feedback Loops.

Prepare for Beta Deployment.

Prepare for Final Deployment.

Project Review: Initial Operational Capability Milestone.

Conclusion.

9. The Transition Phase.

Objectives of the Transition Phase.

Transition Iterations and Development Cycles.

Transition and Iterations.

Transition and Development Cycles.

Objective 1: Beta Test to Validate That User Expectations are Met.

Capturing, Analyzing, and Implementing Change Requests.

Transition Testing.

Patch Releases and Additional Beta Releases.

Metrics for Understanding When Transition Will be Complete.

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.

Packaging, Bill of Materials, and Production.

Marketing Rollout.

Objective 5: Achieve Stakeholder Concurrence That Deployment is Complete.

Product Acceptance Test.

Objective 6: Improve Future Project Performance Through Lessons Learned.

Project Review: Product Release Milestone.

Conclusion.

III. ADOPTING THE RATIONAL UNIFIED PROCESS.

10. Configuring, Instantiating, and Customizing the Rational Unified Process.

Configuring the RUP.

Producing a RUP Process Configuration.

Producing Process Views.

Customizing RUP Templates.

Instantiating the RUP in a Project.

A RUP Development Case.

Project Web Site.

Alternatives to Producing a Development Case.

Customizing the RUP.

Rational Process Workbench and Process Engineering Process.

Creating Thin RUP Plug-Ins Using RUP Organizer.

Creating Structural RUP Plug-Ins Using RUP Organizer.

Conclusion.

11. Adopting the Rational Unified Process.

Adopting the RUP in a Project.

Assess.

Plan.

Configure and Customize.

Execute.

Evaluate.

Adopting the RUP in Small Projects.

Adopting the RUP in a Large Organization.

Process and Tool Enhancement Projects (PTEP).

Pilot Projects.

Software Development Projects.

A Typical Program for Moderate Change.

A Typical Program for Major Change.

An Aggressive Program for Major Change.

Conclusion.

12. Planning an Iterative Project.

Motivation.

Key Concepts.

Cycle.

Phases.

Iteration.

Build.

Time-Boxing.

Coarse-Grain and Fine-Grain Plans: Project Plans and Iteration Plans.

The Project Plan.

The Iteration Plan.

Building a Project Plan.

Determining the Number of Iterations.

Iteration Length.

Staffing the Project.

Iteration Planning.

Inception and Elaboration.

Construction and Transition.

Identifying Activities.

Estimating.

An Iterative Estimation Technique: Wideband Modified Delphi.

Optimizing the Project Plan.

Overlapping Iterations.

Parallel Iterations.

Conclusion.

13. Common Mistakes When Adopting and Using the RUP--and How to Avoid Them.

Mistakes When Adopting the RUP.

Adopting Too Much of What Is in the RUP.

Adopting Everything at Once, Rather than Incrementally.

Not Planning the Implementation of the RUP.

Not Coupling Process Improvement with Business Results.

Customizing Too Much of the RUP Too Early.

Paying Lip Service to the RUP.

Mistakes When Managing Iterative Development.

Having a Functional, Specialized Organization.

Not Setting the Right Stakeholder Expectations or Using an Old-Fashioned Acquisition Model.

Too Many Developers at Project Start.

Solving the Easy Stuff First.

Having an Extended Initial Iteration.

Having Overlapping Iterations.

Allowing Too Many Changes Late in the Project.

Mistakes in Analysis, Architecture, Design, Implementation, and Testing.

Creating Too Many Use Cases.

Having Analysis-Paralysis.

Including Design Decisions in Your Requirements.

Not Having Stakeholder Buy-In on Requirements.

“Not Invented Here” Mentality.

Ending Elaboration Before the Architecture Is Sufficiently Stable.

Focusing on Inspections Instead of Assessing Executable Software.

Conclusion.

IV. A ROLE-BASED GUIDE TO THE RATIONAL UNIFIED PROCESS.

14. A Project Manager's Guide to the RUP.

The Mission of a Project Manager.

A Complex Role.

A Person or a Team?

Project Management.

Scope of the Project Management Discipline in the RUP.

Software Development Plan (SDP).

Iterative Development.

Risks.

Metrics.

Activities of a Project Manager.

Launching a New Project.

Developing the Software Development Plan.

Starting and Closing Phases and Iteration.

Monitoring the Project.

Finding Your Way in the RUP.

Conclusion.

Resources for the Project Manager.

Further Reading.

On the Web.

Training Resources.

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.

Problem Statement.

Feature List.

Develop a Use-Case Model and Glossary.

Describe Requirements “Mile-Wide, Inch-Deep”.

Detail Actors and Use Cases.

Example Use-Case Specification for Register for Courses.

Fine-Tune Your Model.

Develop User-Interface Prototypes.

Develop Use-Case Storyboard or Prototype.

Capture Nonfunctional Requirements.

Update and Refine Requirements.

Ensure That the Requirements Are Delivered and Tested.

The Analyst's Role in the Rational Unified Process.

Resources for Analysts.

Further Reading.

Training Resources.

16. An Architect's Guide to the RUP.

The Mission of an Architect.

A Jack-of-All-Trades.

A Person or a Team?

A Vertex of Communication.

Architecture.

Architecture Defined.

Models and Views.

Software Architecture Document.

Executable Architectural Prototype.

Architectural Mechanisms.

Additional Architecture?

An Evolving Role.

What Do Architects Do?

Vision.

Rhythm.

Anticipation.

Partnering.

Simplification.

The Architect's Activities in the RUP.

Working with the Requirements and Project Management.

Refining the Architecture.

Maintaining Architectural Integrity.

The Architect's Roles in the RUP.

Finding Your Way in the RUP Product.

Resources for the Architect.

Further Reading.

Useful Web Sites.

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 Use-Case Realizations and Components.

Implement Use Cases and Components.

Developer Testing.

Design, Implement, and Test Any Necessary Databases.

Frequently Integrate Your Application with the Work of Other Developers.

Configuration Management Workspaces.

Integration Planning.

Produce a Build.

Developer Best Practices.

Test First.

Refactor Your Code and Design.

Use Patterns, Architectural Mechanisms, and Other Reusable Assets.

Keep Your Design Simple.

Pair Programming.

The Developer Role in the Rational Unified Process.

Available Resources for Developers.

Recommended Reading.

Recommended Training.

18. A Tester's Guide to the RUP.

The Mission of the Tester.

The Concept of Product Quality in the RUP.

Paradigms of “Good Enough”.

The Cost of Quality.

Wouldn't Quantification Help?.

Conformance to Standards.

What Is Testing?

The RUP Testing Philosophy.

Mission.

Test Cycles.

The Test Discipline in the RUP Product.

Various Roles Related to Test in the RUP.

Key Test Artifacts.

Activities of the Tester.

Define Test Mission.

Verify Test Approach.

Validate Build Stability (Smoke Test).

Test and Evaluate.

Achieve an Acceptable Mission.

Improve Test Assets.

Other Related Activities.

Conclusion.

Resources for Testers.

Further Reading.

Training Resources.

Glossary.
Bibliography.
Index. 0321166094T03252003

Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020