RUP

11,286 views
10,806 views

Published on

RUP presentation was awarded best presentation in the course.

2 Comments
5 Likes
Statistics
Notes
No Downloads
Views
Total views
11,286
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
349
Comments
2
Likes
5
Embeds 0
No embeds

No notes for slide

RUP

  1. 1. AN OVERVIEW OF THE RATIONAL UNIFIED PROCESS (RUP) Eric Villagomez TS5130 - System Development Theory and Practice
  2. 2. What is RUP? <ul><li>RUP was originally developed by Rational Software (now part of IBM). </li></ul><ul><ul><li>It is a Software engineering process </li></ul></ul><ul><ul><li>It is a process product </li></ul></ul><ul><ul><li>It enhances team productivity </li></ul></ul><ul><ul><li>It creates and maintains models </li></ul></ul><ul><ul><li>It is a guide to effectively use the Unified Modeling Language </li></ul></ul><ul><li>Its goal is to delivery a high quality product that the customer actually wants. </li></ul>
  3. 3. Why not use Waterfall instead? <ul><li>The Waterfall method follows a sequential approach to software development. </li></ul><ul><ul><li>This limits the ability to react to any change or correct problems in a timely matter. </li></ul></ul><ul><li>Assumptions: </li></ul><ul><ul><li>Requirements never change. </li></ul></ul><ul><ul><li>All information is known upfront. </li></ul></ul><ul><ul><li>The customer will be satisfied with the end results. </li></ul></ul><ul><ul><li>Technology will not change when it comes time to integrate. </li></ul></ul>
  4. 4. The RUP Lifecycle
  5. 5. The Four Phases of RUP <ul><li>The Inception Phase </li></ul><ul><ul><li>The goal is to obtain buy-in from key stakeholders. </li></ul></ul><ul><li>The Elaboration Phase </li></ul><ul><ul><li>Objective is to specify requirements in greater detail and define the architecture for the system. </li></ul></ul><ul><li>The Construction Phase </li></ul><ul><ul><li>The focus here is to develop the application to the point where it is ready for deployment. </li></ul></ul><ul><li>The Transition Phase </li></ul><ul><ul><li>We can now delivery the system into production. </li></ul></ul>
  6. 6. The Six Disciplines of RUP <ul><li>Business Modeling </li></ul><ul><ul><li>The goal is to understand the business of the organization. </li></ul></ul><ul><li>Requirements </li></ul><ul><ul><li>The goal is to define Scope: What is and is not to be built. </li></ul></ul><ul><li>Analysis and Design </li></ul><ul><ul><li>The goal is to analyze the requirements and design the solution. </li></ul></ul><ul><li>Implementation </li></ul><ul><ul><li>The goal is to execute the code based on the design. </li></ul></ul>
  7. 7. The Six Disciplines of RUP (Cont.) <ul><li>Test </li></ul><ul><ul><li>The goal is to verify all aspects of the system to ensure quality. </li></ul></ul><ul><li>Deployment </li></ul><ul><ul><li>The goal is plan and deliver a working system to the customer. </li></ul></ul>
  8. 8. Best Practices of the RUP <ul><li>Adapt the process </li></ul><ul><ul><li>Adapt RUP appropriately based on the development needs. </li></ul></ul><ul><li>Balance competing stakeholders </li></ul><ul><ul><li>Take an evolutionary approach by keeping stakeholders as active participants. </li></ul></ul><ul><li>Collaborating Across Teams </li></ul><ul><ul><li>Keep an open communication process </li></ul></ul><ul><li>Demonstrate Value Iteratively </li></ul><ul><ul><li>Deliver working software early and regularly </li></ul></ul>
  9. 9. Best Practices of the RUP (Cont.) <ul><li>Elevate the level of Abstraction </li></ul><ul><ul><li>Adapt modeling tools, reuse existing code, and focus on architecture </li></ul></ul><ul><li>Focus continuously on Quality </li></ul><ul><ul><li>This is done by testing at every major part of the project. </li></ul></ul>
  10. 10. Disadvantages of RUP <ul><li>The process may be too complex to implement </li></ul><ul><li>Development can get out of control </li></ul><ul><li>It is a heavyweight process </li></ul><ul><li>You need an expert to fully adopt this process </li></ul>
  11. 11. Advantages of RUP <ul><li>Regular feedback from and to stakeholders </li></ul><ul><li>Efficient use of resources </li></ul><ul><li>You deliver exactly what the customer wants </li></ul><ul><li>Issues are discovered early in your project </li></ul><ul><li>Improved control </li></ul><ul><li>Improved risk management </li></ul>
  12. 12. References <ul><li>Rational Unified Process: Best Practices for Software Development Teams </li></ul><ul><ul><li>http://www.ibm.com/developerworks/rational/library/content/03July/1000/1251/1251_bestpractices_TP026B.pdf </li></ul></ul><ul><li>A Manager’s Introduction to the Rational Unified Process (RUP) </li></ul><ul><ul><li>http://www.ambysoft.com/downloads/managersIntroToRUP.pdf </li></ul></ul><ul><li>The Rational Unified Process </li></ul><ul><ul><li>http://www.menloinnovations.com/freestuff/whitepapers/Rational%20Unified%20Process.pdf </li></ul></ul>

×