Looking for a Tutor Near You?

Post Learning Requirement »
x

Choose Country Code

x

Direction

x

Ask a Question

x

x
x
x
Hire a Tutor

Rational Unified Process

Loading...

Published in: Computer Science
3,919 Views

Rational Unified Process is a software development process which helps in making a high quality software. The topic is a part of object oriented software development subject.

Jigyasa K / Faridabad

2 years of teaching experience

Qualification: MCA

Teaches: Computer Science, IT & Computer Subjects, BCA Tuition, IT, Data Structures, DBMS & RDBMS, BCA Subjects, MCA Subjects

Contact this Tutor
  1. RATIONAL UNIFIED PROCESS
  2. THE RATIONAL UNIFIED PROCESS RUP is an 00 Software Development from O Rational, a unit of IBM. Goal :develop high quality software that meets the O needs of its end-users, within a prediccable schedule and budget. i prOvides industry-tested practices for software and systems delivery and implementation and for effective project management.
  3. FEATURES o Process product -development team for the RUP works closely with customers, partners, Rational's product groups. ensures that the process is continuously updated and improved upon to reflect recent expel/ences and evolving and proven bes@practices. models createvs maintains models. No large o paper work. Tie RUP is a guide for how to effectively use the Unified Modeling Language that clearly communicate requirements,architectures and designs.originally created by Rational Software,
  4. o configurable process - No single process. The Unified Process fits small development teams as well as large development organizations founded on process architecture that provides commonality across a family of processes. can be varied to accommodate different situations. It contains a Development)KiC providing support for configuring the process to suit the needs of a given organization. o best practices - describes how to effectively dépioy commercially proven approaches to software development for software development teams. These are called "best practices" because r commonly used in industry by successful organizations.
  5. FROM SEQUENTIAL TO AN ITERATIVE CYCLE One Iteration Time R; Requirements Analysis D: Design C: Coding, Unit Testing T; Integration. Test
  6. Phases Workflows Business Modeling Requirements Analysis & Design Implementation Test Deployment Configuration & Change Mgmt Project Management Environment Inception Initial Elaboration Construction Transition Elab Elab #2 Const Const Iterations Const Tran Tran #2
  7. RUP is divided into four phases is to distinguish O among the different focuses of activities at different times in the project lifecycle. o Inception - do you and the Customer have a shared understanding of the system? Elaboration - do you have an architegqure to be O able to build the system? Construction - arg;you åeveloping product? O Transition i- are you trying to get the Customer to O Otåke ownership of the system?
  8. ? ? ? ? ? ? ? ? 'J ? ? i ? ? ? ? ? ? fi ? ? ? Of ? ? ? ? ? ? ion ? 3 ? tem *form P ? ? 9 ? ? ? ? ? ? ? n ? n ? ? und ?
  9. In an iteration, you walk through all workflows ITERATIVE MODEL GRAPH Inceptio Elaboratio Business Modeling Requirements Analysis & Design Implementation Test Deployment onfiguration Mgm Management Workflows Environment group activities logically Constructi" 1 Transitio 2
  10. OUTCOME A vision document: a general vision of the core O project's requirements, key features, and main constraints. An initial use-case model (10% -20%) complete).i O An initial business case, which ingludés business O context, success criteria (revenue projection, market recognitionÄnd so on), and financial forecast. j & Afi initial risk assessment. A project plan, showing phases and iterations. O
  11. IMPLEMENTING THE SYSTEM Phases Construction Core Process Disciplines Business Modeling Requirements Analysis and Design Implementation Test Deployment C) D/ -%eunes Core Suppo and Change Mgmt Hroject Management Environment Inception Elaboration Transition Prelirr'ül*ry iter- heretico(s) 1 agt. itet. 2 Iterations itee iter- iter-
  12. OUTCOME The software product integrated on the adequate O platforms. The user manuals. O A description of the current release. O