Enterprise Unified Process (EUP) Home Page

The Rational Unified Process (RUP) is quickly becoming the defacto standard development process, also referred to as a software development methodology, within the object-oriented and component-based software communities. Is it sufficient? My experience is that it isn't, in fact, by its very scope definition it is insufficient because we need more than a development process, we need a full-fledged software process.

The Enterprise Unified Process^TM (EUP) is an extension to the RUP.  Figure 1 depicts the EUP lifecycle. People familiar with RUP can see that the extensions include two new phases, Production and Retirement, and several new disciplines: Operations and Support and the seven enterprise disciplines (Enterprise Business Modeling, Portfolio Management, Enterprise Architecture, Strategic Reuse, People Management, Enterprise Administration, and Software Process Improvement).

Figure 1. The Lifecycle for the Enterprise Unified Process (EUP) v2004.

EUP Resources:

• Adopting the EUP

• Other articles at this site

• Downloads

• Recommended articles at other sites

• EUP Mailing List

• EUP Training

• Search the EUP site

• Site Map

Translations:

• Japanese

We are a proud supporter of Agile Modeling (AM):

Material posted on this site is taken, in part, from The Enterprise Unified Process: Extending the Rational Unified Process by Scott W. Ambler, John Nalbone, and Michael Vizdos.  Whereas the RUP defines a software development lifecycle, the EUP extends it to cover the entire information technology (IT) lifecycle. The extensions include two new phases, Production and Retirement, and several new disciplines: Operations and Support and the seven enterprise disciplines (Enterprise Business Modeling, Portfolio Management, Enterprise Architecture, Strategic Reuse, People Management, Enterprise Administration, and Software Process Improvement).