Rup Phan Viec



Comments



Description

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