This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article does not cite any sources. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.Find sources: "OpenUP" – news · newspapers · books · scholar · JSTOR (January 2017) (Learn how and when to remove this message) The topic of this article may not meet Wikipedia's general notability guideline. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted.Find sources: "OpenUP" – news · newspapers · books · scholar · JSTOR (February 2019) (Learn how and when to remove this message) (Learn how and when to remove this message)

The open unified process (OpenUP) is a part of the Eclipse process framework (EPF), an open source process framework developed within the Eclipse Foundation. Its goals are to make it easy to adopt the core of the rational unified process (RUP) / unified process.

The OpenUP began with a donation to open source of process content known as the basic unified process (BUP) by IBM. It was transitioned to the Eclipse Foundation in late 2005 and renamed OpenUP/Basic in early 2006. It is now known simply as OpenUP.

Overview

OpenUP preserves the essential characteristics of rational unified process / unified process, which include iterative development, use cases and scenarios driving development, risk management, and architecture-centric approach. Most optional parts of RUP have been excluded, and many elements have been merged. The result is a much simpler process that is still true to RUP principles.

OpenUP targets small and colocated teams interested in agile and iterative development. Small projects constitute teams of 3 to 6 people and involve 3 to 6 months of development effort.

Project Lifecycle

Known uses

See also

References