Successfully reported this slideshow.

Rational Unified Process


Published on

My seminar for 8th semester.

Published in: Technology

Rational Unified Process

  1. 1. Rational Unified Process<br />Omkar Dash<br />8th Semester, IT <br />0501227436<br />
  2. 2. Introduction<br /><ul><li>The Rational Unified Process (RUP) is an iterative software development process framework.
  3. 3. Created by the Rational Software Corporation, a division of IBM since 2003.
  4. 4. RUP is not a single concrete prescriptive process, but rather an adaptable process framework.
  5. 5. Tailored by the development organizations that will select the elements of the process that are appropriate for their needs.</li></li></ul><li>Overview <br /><ul><li>Stands for Rational Unified Process Framework
  6. 6. Needs to be configured/tailored
  7. 7. Contains phases, iterations, and workflows
  8. 8. Helps an organization achieve CMM level 2/3 capabilities
  9. 9. Improve existing processes based on proven Rational software engineering expertise
  10. 10. Provide standards for requirements management
  11. 11. Provide processes that support object-oriented analysis, design development for new J2EE efforts based on industry standard UML
  12. 12. Well supported by industry leading Rational tools (Rose, RequisitePro)</li></li></ul><li>RUP : A Software Engineering Process<br /><ul><li>Well-defined and well-documented software development process is key to the success of software projects.
  13. 13. CMM (Capability Maturity Model) by the Software Engineering Institute (SEI) has become a beacon.
  14. 14. Theoretical know-how fails to materialize in practice.
  15. 15. Sometimes, there is no process know-how at all.</li></ul>Result : Chaos, Failure, Loss<br /><ul><li>The RUP can help!</li></ul>A mature, rigorous, and flexible software engineering process.<br />
  16. 16. RUP : A Process Product<br />&quot;Software processes are software, too”<br />Software like characteristics of RUP :<br />Designed and documented using the Unified Modeling Language (UML).<br />Delivered online using Web technology<br />Software upgrades are released by Rational Software<br />Modular and in electronic form, it can be tailored<br />Integrated with the many software development tools<br />
  17. 17. RUP : Architecture<br />One development cycle is divided into four consecutive phases.<br /> <br />Inception phase <br />Elaboration phase <br />Construction phase <br />Transition phase <br />Each phase is concluded with a well-defined milestone<br />Each phase has a specific purpose.<br />
  18. 18. RUP : Architecture<br />Inception phase <br />A vision document<br />An initial use-case model <br />An initial project glossary <br />An initial business case<br />An initial risk assessment<br />A project plan, showing phases and iterations.<br />A business model<br />Project milestone: The Lifecycle Objectives Milestone<br />
  19. 19. RUP : Architecture<br />Elaboration phase<br />A use-case model (at least 80% complete)<br />Supplementary requirements (non functional requirements)<br />A Software Architecture Description. <br />An executable architectural prototype. <br />A revised risk list and a revised business case. <br />A development plan for the overall project<br />An updated development case specifying the process to be used. <br />A preliminary user manual (optional). <br />Project milestone: The Lifecycle Architecture Milestone<br />
  20. 20. RUP : Architecture<br />Construction Phase<br />The software product integrated on the adequate platforms. <br />The user manuals. <br />A description of the current release. <br />Project Milestone : Initial Operational Capability<br />
  21. 21. RUP : Architecture<br />Transition Phase<br />“Beta testing” to validate the new system against user expectations <br />Parallel operation with a legacy system that it is replacing <br />conversion of operational databases <br />Training of users and maintainers <br />Roll-out the product to the marketing, distribution, and sales teams<br />Project milestone: The Product Release Milestone <br />
  22. 22. Iterative Approach<br /> <br />Compared to the traditional waterfall process, the iterative process has the following advantages:<br /> <br /><ul><li>Risks are mitigated earlier
  23. 23. Change is more manageable
  24. 24. Higher level of reuse
  25. 25. The project team can learn along the way
  26. 26. Better overall quality </li></li></ul><li> Deployment of 6 Best Practices<br /> <br />The proven Best practices are : <br />1. Develop software iteratively <br />2. Manage requirements <br />3. Use component-based architectures<br />4. Visually model software <br />5. Verify software quality <br />6. Control changes to software <br />
  27. 27. Who Is Using the RUP?<br /><ul><li>Telecommunications
  28. 28. Transportation, aerospace, defense
  29. 29. Manufacturing
  30. 30. Financial services
  31. 31. Systems integrators</li></li></ul><li> References:<br />Rational Unified Process 2000, Rational Software, Cupertino, CA (2000)<br /> Philippe Kruchten, The Rational Unified Process -- An Introduction, 2nd ed., Addison-Wesley-Longman, Reading, MA (2000).<br /><br />
  32. 32. Thank You<br />Queries Please. <br />