RUP Definitions

 

 

 1)

Short for Rational Unified Process, a software development methodology from Rational. Based on UML, RUP organizes the development of software into four phases, each consisting of one or more executable iterations of the software at that stage of development.

·          Inception — In this stage, the project’s business case is stated and the team decides if the project is worth doing or if it is even possible. It is important to the process to first formulate the scope of the project and also determine what resources will be needed.

·          Elaboration — In this stage, the developers take a closer look at the project to determine its architecture foundation and to evaluate the architecture in relation to the project. This stage is important to the RUP because it is here that developers analyze the risks associated with changing the scope of the project or adding new technologies along the way.

·          Construction — In this stage, the development of the project is completed. The application design is finished and the source code is written. It is in this stage that the software is tested to determine if the project has met its goal laid out in the inception phase.

·          Transition — In this stage, any fine-tuning is performed. Any final adjustments can be based on user feedback, usability or installation issues.

 2)

IBM Rational Unified Process®, RUP®, is process guidance content included in the Rational Method Composer framework that delivers proven best practices in a configurable architecture.

IBM® Rational® Method Composer allows you to easily customize RUP. It enables you to select and deploy only the process components you need for each stage of your project, and then publish it through the internet.

The RUP process framework with IBM Rational Method Composer includes:

·          A process content library based on the best practices adopted in thousands of projects worldwide. To address all the breadth of process needs of organizations you can reuse what works for other organizations through the content library, rather than inventing everything from scratch.

·          Capability patterns that allow project managers to rapidly add or remove reusable chunks of processes addressing common problems. Since no two projects are alike, project manager’s needs to rapidly modify the process to address the specific project needs. This can be done through capability patterns, plug-ins and process components, allowing content around various domains such as database modeling or advanced requirements management to be added or removed.

·          Out-of-the-box delivery processes to provide the project manager with a quick starting point for planning and initiating a project. A delivery process will provide an initial project template, identify what type milestones to have in the project, what work products to delivered by each milestone, and what resources are needed for each phase.

 

3)

RUP, or the Rational Unified Process is Rational Software’s (now owned by IBM) implementation of the Unified Process. I won’t go into the details of RUP here, but RUP’s (or UP’s) design fits very well into an Object Oriented project’s structure. It allows for an incremental and iterative approach to software development well suited to well-designed OO applications. The goal of any software project is to provide a functional, useable product that provides value to its users. Reaching that lofty goal takes more than code sense, a lot more.

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s