Prepared by:

Mahesh Panchal
MBA-Software Development
&Management
Symbiosis(SCIT) : 07-09
 Overview of RUP
 Overview of XP
 Comparative study
 conclusion
 RUP is a popular off-the-shelf process based on
the idea of highly iterative development
 One thing that makes RUP unique is that it is a product in
addition to a process.
 RUP includes a disciplined approach to
requirements management that is based on the
idea of managing changes.
 RUP incorporates software design using the Unified
Modeling Language (UML), a visual modeling system for
graphically representing the use cases, class model,
object interactions, and components of the software.
 One core element of RUP is the continuous
assessment of the quality of the system.
 XP consists of a set of rules and practices
that govern all areas of software
development: planning, designing,
coding, and testing.
 The goal of XP is to lower the cost of change.
To meet this goal, many XP practices are
highly iterative.
 XP is a disciplined and well-defined process.
 By making the stakeholders part of the project
team, XP addresses the problem of the hands-
off customer.
 Characteristics
 Evolutionary development
Every 2-3
Planning
weeks
Collection of 12 „Best Practices“
 Focus on working code that
Write tests implements customer needs
(rather than documents)
Pair Programming
 Testing is a crucial element of the
Release
+ Refactoring process
 Focus on flexibility and efficiency
Test of the process
 Designed for
Min. small teams (<10)
Integration
daily
Heavyweight Customizable Agile (Lightweight)
e.g., V-Process Framework e.g., eXtreme
e.g., Rational Programming (XP)
Unified
Process (RUP)

Document driven Focus on working code

Elaborate workflow definitions rather than documentation
Many different roles Focus on direct communication
Many checkpoints (between developers and
High management overhead between developers and the customer)
Highly bureaucratic Low management overhead
 Tasks RUP eXtreme Programming
Vision document User Stories
Analysis of the requirements and
Communication Feedback
business modeling
Use-Case analysis On-site customer
Analysis & Design Preliminary architecture design System Metaphor
Implementation Creation of use-cases prototypes
Testing Creation of test plans
Configuration & Change
Change Control Strategy
Management
Project Management Project Schedule Story Estimates
 Tasks RUP
Analysis of the requirements and
business modeling Use-Case analysis
Class, Sequence, Collaboration
Analysis & Design
and Activity modeling
Implementation Architecture prototype
Planning, design and
Testing
implementation of tests
Configuration & Change
Change Request documents
Management
Defined Project Plan
Project Management
Status Assessment document
eXtreme Programming
User Stories
Communication Feedback
On-site customer
Simple Design, System design
sketches (CRC sketches)
Frequent Small Releases
Continual Integration
Collective Ownership
Refactoring
Pair programming
Test-First Programming
Iteration Plan
 Tasks
Analysis of the requirements and
business modeling
Class, Sequence, Collaboration
Analysis & Design
Implementation
Testing
Configuration & Change
Management
Project Management
RUP
Use-Case analysis
Simple Design, System design
and Activity modeling
Planning, design and
implementation of tests
Change Request documents
Status Assessment document
eXtreme Programming
User Stories
Communication Feedback
On-site customer
sketches (CRC sketches)
Frequent Small Releases
Continual Integration
Collective Ownership
Refactoring
Pair programming
Unit Testing
Iteration Plan
 Tasks RUP eXtreme Programming
Analysis of the requirements and User Stories
business modeling Use-Case analysis Communication Feedback
On-site customer
Class, Sequence, Collaboration Simple Design, System design
Analysis & Design
and Activity modeling sketches (CRC sketches)
Frequent Small Releases
Continual Integration
Implementation Collective Ownership
Refactoring
Pair programming
Deployment plan
Deployment User documentation
Support plan
Configuration & Change
Change Request documents
Management
Project Management Status Assessment document Iteration Plan
 RUP
 highly formal and structured
 providing out-of-the-box roadmaps for a
number of project types
 does not say anything about how to actually
run a project
 XP
 devoted to everyday life and low-level
management of the development team
 does not insist on documentation
 does not provide project templates
 people oriented methodology, relying on
human intelligence
 XP is suitable, if both of the following
conditions are true:
 You have a small team (2-12)
 Requirements are vague (users don’t know yet
what they want)
 RUP is suitable if one of the previous
conditions are false.
 When using XP with large teams, the
general (unspoken) idea that everyone
needs to know everyone else's code
details, becomes hard to defend,
especially when 12
Thank you for patient listening.

maheshpanchal1@gmail.com