1 / 10

Rational Unified Process RUP

What is being presented. Familiar with some common symptoms of project failuresUnderstand what is RUPKnow the benefits of utilizing RUPHow it can be applicable to other disciplines. Symptoms of Failing Projects. Ad hoc requirements managementAmbiguous and imprecise communicationBrittle archite

sidonie
Download Presentation

Rational Unified Process RUP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Rational Unified Process (RUP) Presented by Lee, Yat Wei, Edward

    2. What is being presented Familiar with some common symptoms of project failures Understand what is RUP Know the benefits of utilizing RUP How it can be applicable to other disciplines

    3. Symptoms of Failing Projects Ad hoc requirements management Ambiguous and imprecise communication Brittle architecture Overwhelming complexity Undetected inconsistencies in requirements, designs, and implementations Insufficient testing Failure to attack risk Uncontrolled change propagation Insufficient automation

    4. Solution to the problem Rational Unified Process (RUP) Iterative software design method Development process framework Encompass a large number of different activities Design to be tailored

    5. Benefits of using RUP Develop software iteratively Manage requirements Use component based architecture Visually model software Verify software quality Control changes to software

    6. Business Modeling Purpose Establish better understanding or a communication channel between business engineering and software engineering Rationale Increase dependency on software and hardware systems. Gain competitive advantage with the help of IT Provides a well-organized approach

    7. Job Posting MORGAN STANLEY New York, New York Sr. Business Analyst Aug’03 – May’04 Performed the Analysis & Design workflow for same- day/ next-day/ zero day trade settlement systems by following the Rational Unified Process (RUP) including modeling the pre-defined business requirements with Rational Rose/XDE to document Business Use Cases, System Use Cases and create Process Scenarios.

    8. How all these are applicable to other disciplines Negotiation skills with clients Analysis of problem domains Technical writing skills Risk management

    9. References Rational Unified Process - Wikipedia, the free encyclopedia http://en.wikipedia.org/wiki/Rational_Unified_Process Interdisciplinary influences in software engineering practices, Bunting, R.; Coallier, F.; Lewis, G.; Software Technology and Engineering Practice, 2002. STEP 2002. Proceedings. 10th International Workshop on 6-8 Oct. 2002 Page(s):62 - 69 Software Development for Small Teams: A RUP-Centric Approach, Pollice, G.; Augustine, L.; Lowe, C.; Madhur, J.; Addison-Wesley Professional; 1st edition IRIS 2.0 software suite automates the Rational Unified Process (RUP), TORONTO, Dec. 6 2004 PR Newswire US

    10. Any Questions?

More Related