The RUP

calendar Jul 18, 2018 · 2 min read  en featured  · software  ·
Share on: linkedin copy

Because some friend of mine did not know about RUP, and deal with waterfall process, I decided to make a small recall for all poor young Project Manager dealing with bad developers, bad consultants and so on, out of there,

 

The Rational Unified Process (RUP) is an iterative software development process framework created by the Rational Software Corporation, a division of IBM since 2003.[1] RUP is not a single concrete prescriptive process, but rather an adaptable process framework, intended to be tailored by the development organizations and software project teams that will select the elements of the process that are appropriate for their needs. RUP is a specific implementation of the Unified Process.
Insight from the Wikipedia description:

The six best practices for modern software engineering:

  1. Develop iteratively, with risk as the primary iteration driver[4]
  2. Manage requirements
  3. Employ a component-based architecture
  4. Model software visually
  5. Continuously verify quality
  6. Control changes
[...]

Between 2000 and 2003, a number of changes introduced guidance from ongoing Rational field experience with iterative development, in addition to tool support for enacting RUP instances and for customization of the RUP framework. These changes included:

  1. the introduction of concepts and techniques from approaches such as eXtreme Programming (XP), that would later come to be known collectively as agile methods. This included techniques such as pair programming, test-first design, and papers that explained how RUP enabled XP to scale for use on larger projects.
  2. a complete overhaul of the testing discipline to better reflect how testing work was conducted in different iterative development contexts.
  3. the introduction of supporting guidance - known as "tool mentors" - for enacting the RUP practices in various tools. These essentially provided step-by-step method support to Rational tool users.
  4. automating the customization of RUP in a way that would allow customers to select parts from the RUP process framework, customize their selection with their own additions, and still incorporate improvements in subsequent releases from Rational.
IBM acquired Rational Software in February 2003.

Anyway if your organization seems too in trouble with classic waterfall or agile methods, give RUP a try!