Programming Microsoft Visual C++

FIGURE 1.1 Iterative Development in the RUP

FIGURE 1.2 Two Dimensions of the RUP

FIGURE 1.3 Milestones for the RUP Lifecycle Phases

FIGURE 1.4 Roles, Activities, and Artifacts

FIGURE 1.5 The Workflow of the Requirements Discipline

FIGURE 1.6 Adding Templates, Tool Mentors, and Guidelines

FIGURE 1.7 The RUP Process Framework

FIGURE 1.8 The RUP's Component-Based Architecture Allows the RUP to Be Configured to Project Needs

FIGURE 1.9 MyRUP Provides Personalized Views

FIGURE 1.10 RUP Context-Sensitive Extended Help

FIGURE 2.1 Risk Reduction Profiles for Waterfall and Iterative Developments

FIGURE 2.2 How Use Cases Relate to Other Software Engineering Models

FIGURE 2.3 Consider the RUP as a Smorgasbord

FIGURE 2.4 The Cost of Introducing Change Varies Throughout the Lifecycle

FIGURE 2.5 A System Architecture

FIGURE 2.6 A Functional Decomposition Architecture

FIGURE 2.7 A Component-Based Architecture

FIGURE 2.8 Teams Organized Around Architecture

FIGURE 2.9 Testing Is Initiated Early and Expanded Upon in Each Iteration

FIGURE 3.1 Process Map for Process Comparison

FIGURE 3.2 Agile Processes on the Process Map

FIGURE 3.3 SEI CMM and CMMI on the Process Map

FIGURE 3.4 Various Military Standards for Software Development on the Process Map

FIGURE 3.5 RUP Configurations on the Process Map

FIGURE 3.6 Example Projects on the Process Map

FIGURE 4.1 Creating a Vision

FIGURE 4.2 The Plan

FIGURE 4.3 Assessing Risks

FIGURE 4.4 Sketch of Sample Architecture

FIGURE 4.5 Modified Plan

FIGURE 4.6 Assessing Risks, Take Two

FIGURE 4.7 Sketch of Product Interface

FIGURE 4.8 Screen Shot of Completed Product Interface

FIGURE 5.1 Major Milestones

FIGURE 6.1 The Inception Phase

FIGURE 6.2 System Overview: User Kinds and Their Use Cases

FIGURE 6.3 Three Options for a Client/Server Architecture

FIGURE 7.1 The Elaboration Phase

FIGURE 7.2 The Architecture Provides a Skeleton Structure of Your Application

FIGURE 7.3 Architecturally Significant Use Cases Drive the Architecture

FIGURE 7.4 An Example Sequence Diagram

FIGURE 7.5 Packaging Should Localize Impact of Change

FIGURE 7.6 Architectural Coverage

FIGURE 7.7 Architectural Mechanisms

FIGURE 8.1 The Construction Phase

FIGURE 8.2 Work Distribution over the RUP Phases

FIGURE 8.3 Organization Around Architecture Minimizes Communication Overload

FIGURE 8.4 Incremental Builds Facilitate Builds for Large Systems

FIGURE 8.5 Evolution of Components over Time

FIGURE 9.1 The Transition Phase

FIGURE 9.2 Number of Iterations in Transition

FIGURE 9.3 Development Cycles

FIGURE 9.4 Trend Analysis of Defects

FIGURE 10.1 RUP Builder Publishes RUP Process Configurations

FIGURE 10.2 Process Views in MyRUP

FIGURE 10.3 Development Case ”Artifacts and Formality

FIGURE 10.4 Development Case ”Roles

FIGURE 10.5 Project Web Site in Rational ProjectConsole

FIGURE 10.6 RUP Organizer Allows You to Build Thin RUP Plug-Ins

FIGURE 10.7 RUP Modeler Allows You to Visualize and Customize Your Process

FIGURE 11.1 Rollout of the Requirements, Analysis & Design, and Project Management Disciplines

FIGURE 11.2 Rollout of the RUP and Tools

FIGURE 11.3 A Typical Approach to Implementing Moderate Change

FIGURE 11.4 A Typical Approach to Implementing Major Change

FIGURE 11.5 An Aggressive Approach to Implementing the RUP and Supporting Tools

FIGURE 12.1 Typical Time Line for an Initial Development Cycle

FIGURE 12.2 Project Plan and Iteration Plan

FIGURE 12.3 Typical Resource Profile for a Development Cycle

FIGURE 12.4 Example Resource Profile Across Project Lifecycle Phases

FIGURE 13.1 Functional Teams Have Inherent Communication Barriers

FIGURE 13.2 Break Up a Project into Multiple Bids

FIGURE 13.3 The Number of Developers Should Be Limited at Project Start

FIGURE 13.4 Similar Iteration Lengths Help to Develop a Project Rhythm

FIGURE 13.5 Large Iteration Overlap Defocuses Teams

FIGURE 13.6 Rate of Change in Interfaces Indicates When Elaboration Can Be Ended

FIGURE 15.1 An Analyst's Involvement in the RUP Lifecycle

FIGURE 15.2 Business Use-Case Model for Product Company

FIGURE 15.3 Business Object Model for Order

FIGURE 15.4 System Overview: Actors and Use Cases

FIGURE 15.5 Structuring of Flows of Events

FIGURE 16.1 Architecting: The Art of Compromise

FIGURE 16.2 The 4+1 Views of Architecture

FIGURE 16.3 Overview of the Architect's Activities

FIGURE 17.1 A Developer's Role in the RUP

FIGURE 17.2 Example of the View of Participating Classes

FIGURE 17.3 Example of a Collaboration Diagram

FIGURE 17.4 Example of a Sequence Diagram

FIGURE 17.5 Runtime Analysis Can Detect Performance Bottlenecks

FIGURE 18.1 The Overall Test Workflow