Rational Unified Process

RUP establishes four phases of development, each of which is organized into a number of separate iterations that must satisfy defined criteria before the next phase is undertaken: in the inception phase, developers define the scope of the project and its business case; in the elaboration phase, developers analyze the project's needs in greater detail and define its architectural foundation; in the construction phase, developers create the application design and source code; and in the transition phase, developers deliver the system to users. RUP provides a prototype at the completion of each iteration. The product also includes process support for Java 2 Enterprise Edition (J2EE) and BEA (WebLogic) development, and supplies an HTML-based description of the unified process that an organization can customize for its own use.

Getting started with use Rational Unified Process

To explore how Rational Unified Process is used in the enterprise, here are some additional resources for learning about RUP:

Rational Unified Process learning resources: According to Rational (developers of Rational Rose and the Unified Modeling Language), RUP is like an online mentor that provides guidelines, templates, and examples for all aspects and stages of program development.

Book excerpt: Implementing the IBM Rational Unified Process and Solutions (A Guide to Improving Your Software Development Capability and Maturity) This chapter focuses on key points to bring awareness and generate excitement about RUP. It outlines the ROI you might expect from implementing RUP and IBM Rational Solutions, common problems that these methods may solve and how to sell the executives on this process solution and tools.

Learn more about Traditional software models (RUP, V-Model, CMM, Waterfall)

Can traditional project management and agile development coexist?: Are traditional project managers and agile practitioners fundamentally at odds? Or can they live together and even complement each other?
Survey: Agile interest high, but waterfall still used by many: While there's a strong interest in new software development techniques, SearchSoftwareQuality.com's recent survey found that many still follow traditional development practices.
	CMMI: Good process doesn't always lead to good quality: Having a process such as CMMI in place doesn't guarantee quality software or systems, says Bill Curtis, co-author of CMM. You can still have defects.
Addressing software quality issues with development models, methods: Each development model has its own practices for building quality software. The challenge is determining which one fits your needs. The resources here can help you decide.
Testers debate differences between waterfall, Agile test automation: Two professional testers continue the timeless debate, agile vs waterfall, which is the best methodology for test-driven software development.
Test-driven testing face-off: Waterfall vs. Agile: Most software test pros pick a preferred methology and stand by it, in this tip two testers square-off, one advocating for agile development, the other in the waterfall corner.
Solving problems with session-based test management: A veteran software tester gives real-life examples of using session-based test management in Scrum, RUP and in a completely ad hoc environment.
Best practices for moving testers from waterfall to agile development: Software testers moving from a waterfall environment to the agile development model don't have to be driven to the head-banging stage of frustration.

Do you have something to add to this definition? Let us know. Send your comments to techterms@whatis.com

More resources from around the web: - The Rational Web site provides more information and a free trial download. - The Rational Edge explains the importance of systematic planning and procedures in their article, "Camping Trip? Software Project? Identify Essentials First."

FILE EXTENSION AND FILE FORMAT LIST File Extension and File Format List: A B C D E F G H I J K L M N O P Q R S T U V W X Y Z #

RELATED CONTENT Testers debate differences between waterfall, Agile test automation Two professional testers continue the timeless debate, agile vs waterfall, which is the best methodology for test-driven software development. Test-driven testing face-off: Waterfall vs. Agile Most software test pros pick a preferred methology and stand by it, in this tip two testers square-off, one advocating for agile development, the... Waterfall versus iterative development misconceptions Many programmers have an idea of what their finished product should look like but are confused on where to start and how to finish. Development expert...

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary Capability Maturity Model  (SearchSoftwareQuality.com) collaboration diagram  (SearchSoftwareQuality.com) A collaboration diagram, also called a communication diagram or interaction diagram, is an illustration of the relationships and interactions among...