My seminar for 8th semester.

1. Rational Unified Process Omkar Dash 8th Semester, IT 0501227436

3. Created by the Rational Software Corporation, a division of IBM since 2003.

4. RUP is not a single concrete prescriptive process, but rather an adaptable process framework.

6. Needs to be configured/tailored

7. Contains phases, iterations, and workflows

8. Helps an organization achieve CMM level 2/3 capabilities

9. Improve existing processes based on proven Rational software engineering expertise

10. Provide standards for requirements management

11. Provide processes that support object-oriented analysis, design development for new J2EE efforts based on industry standard UML

13. CMM (Capability Maturity Model) by the Software Engineering Institute (SEI) has become a beacon.

14. Theoretical know-how fails to materialize in practice.

16. RUP : A Process Product "Software processes are software, too” Software like characteristics of RUP : Designed and documented using the Unified Modeling Language (UML). Delivered online using Web technology Software upgrades are released by Rational Software Modular and in electronic form, it can be tailored Integrated with the many software development tools

17. RUP : Architecture One development cycle is divided into four consecutive phases. Inception phase Elaboration phase Construction phase Transition phase Each phase is concluded with a well-defined milestone Each phase has a specific purpose.

18. RUP : Architecture Inception phase A vision document An initial use-case model An initial project glossary An initial business case An initial risk assessment A project plan, showing phases and iterations. A business model Project milestone: The Lifecycle Objectives Milestone

19. RUP : Architecture Elaboration phase A use-case model (at least 80% complete) Supplementary requirements (non functional requirements) A Software Architecture Description. An executable architectural prototype. A revised risk list and a revised business case. A development plan for the overall project An updated development case specifying the process to be used. A preliminary user manual (optional). Project milestone: The Lifecycle Architecture Milestone

20. RUP : Architecture Construction Phase The software product integrated on the adequate platforms. The user manuals. A description of the current release. Project Milestone : Initial Operational Capability

21. RUP : Architecture Transition Phase “Beta testing” to validate the new system against user expectations Parallel operation with a legacy system that it is replacing conversion of operational databases Training of users and maintainers Roll-out the product to the marketing, distribution, and sales teams Project milestone: The Product Release Milestone

23. Change is more manageable

24. Higher level of reuse

25. The project team can learn along the way

28. Transportation, aerospace, defense

29. Manufacturing

30. Financial services

32. Thank You Queries Please.