Extending the RUP with the Enterprise Unified Process (EUP)

This is the Scott W. Ambler's proposal: extend the RUP, creating the EUP (Enterprise Unified Process), to meet the real-world needs of mid-to-large-sized organizations.

The Rationale:

Thousands of organizations worldwide have adopted the Rational Unified Process (RUP) to help improve their software development processes. But Scott Ambler points out that we need to go even further; the Enterprise Unified Process (EUP) extends the RUP to meet the real-world needs of mid- to large-sized organizations.

Beyond Sw Development:

There is more to the lifecycle of a system than software development. The operation and support of a system after it’s in production are crucial to your success; why bother building the system if you can’t run it? The retirement of a system that is no longer needed or that is to be replaced by another system is also important

The EUP phases are:
1. Inception. During this phase, you achieve stakeholder consensus regarding the objectives for the project and obtain funding;
2. Elaboration. During this phase, you specify requirements in greater detail and prove the architecture for the system;
3. Construction. The focus of this phase is developing the system to the point where it’s ready for deployment;
4. Transition. This phase focuses on delivering the system into production;
5. Production. This phase encompasses the period of the system lifecycle at which you operate and support a system until it’s either replaced with a new version or retired and removed completely from use;
6. Retirement. The focus of this phase is the removal of a system from production;