Mastery 02 – USP, Knowledge is power!

USDP sounds like a shipping company but is not, sorry if your whole life has been a lie.

USDP stands for Unified Software Development Process but some people like to refer to it as Unified Process.

What exactly is USDP? Unified Software uses iteration methods which consists of having a base equation and constantly keep replacing the value with the obtained value until you reach the value or an approximation of what you want. It is also used for an increment in software development process and the most common and popularized example is the Rational Unified Process or RUP for short terms.

Many references would point out that USDP is not only about iterative method and keep doing it. Its based on a framework for a certain object, company or even an organization. It also shares and goes hand-by-hand with the RUP method since both work on a customizable framework. With those concepts in mind many claim that it is very hard to differentiate between them so sometimes are miscalled.

USDP v RUP 

One is owned and the other one not. IBM has the rights for RUP or a more technical concept… IBM has the so called trademarks. That is why USDP is usually used for a more generic way and are mostly used in concepts that need refinement; nevertheless, USDP first appearance was on a book named The Unified Software Development whose authors are Ivar Jacobson, James Rumbaugh and Grady Booch. Some may say that both of them have their own respective rights but it always comes down to personal preferences.

Characteristics:

USDP:

  1. Iterative Process that looks for an approximation or result.
  2.  It is always moving forward, in other words incremental.
  3.  The more work the better. The core of the USDP is reflected by the team’s efforts.
  4.  A good death is a reward. Try hard, go for it and make it crash. USDP consists of taking really hard decisions to make the project move forward is a risk-win situation.

USDP is also divided onto sections and are as followed.

  1. Inception: Start developing it.
  2. Elaboration: Look for risk factors.
  3. Construction: Largest and most important phase since it requires a lot of dedication. It involves using UML and diagrams for a better understanding.
  4. Transition: Release the project!

References

 

Ambler, Scott (2002). Agile Modeling: Effective Practices for EXtreme Programming and the Unified Process. J. Wiley. 

Scott, Kendall (2002). The Unified Process Explained.

Bergstrom, Stefan; Raberg, Lotta (2004). Adopting the Rational Unified Process: Success with the RUP.

Ambler, Scott; Constantine, Larry (2002). The Unified Process Transition and Production Phases. CMP Books. ISBN 1-57820-092-X.Larman, Craig (2004). Agile and Iterative Development: A Manager’s Guide.

 

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