Rational Unified Process (RUP)
From apppm
(Difference between revisions)
| Line 1: | Line 1: | ||
The '''Rational Unified Process (RUP)''' is an iterative, software development methodology, firstly introduced by the [https://en.wikipedia.org/wiki/Rational_Software Rational Software Corporation] which was [http://www-03.ibm.com/press/us/en/pressrelease/314.wss acquired by IBM] in 2003. RUP is a disciplined approach to assign tasks within a development organization and software project teams. It was developed, to ensure the production of high quality software who could meet and exceed the needs and expectations of end-users, strictly following a predictable budget and schedule. RUP is the most popular and extensively documented refinement of the [https://en.wikipedia.org/wiki/Unified_Process Unified Process], an iterative and incremental software development process framework. Other worth mentioning forms are the [https://en.wikipedia.org/wiki/OpenUP OpenUP] and [https://en.wikipedia.org/wiki/Agile_Unified_Process Agile Unified Process]. | The '''Rational Unified Process (RUP)''' is an iterative, software development methodology, firstly introduced by the [https://en.wikipedia.org/wiki/Rational_Software Rational Software Corporation] which was [http://www-03.ibm.com/press/us/en/pressrelease/314.wss acquired by IBM] in 2003. RUP is a disciplined approach to assign tasks within a development organization and software project teams. It was developed, to ensure the production of high quality software who could meet and exceed the needs and expectations of end-users, strictly following a predictable budget and schedule. RUP is the most popular and extensively documented refinement of the [https://en.wikipedia.org/wiki/Unified_Process Unified Process], an iterative and incremental software development process framework. Other worth mentioning forms are the [https://en.wikipedia.org/wiki/OpenUP OpenUP] and [https://en.wikipedia.org/wiki/Agile_Unified_Process Agile Unified Process]. | ||
| + | |||
| + | |||
==History== | ==History== | ||
== Ten Essentials == | == Ten Essentials == | ||
| + | === Vision === | ||
| + | === Plan === | ||
| + | === Risks === | ||
| + | === Issues === | ||
| + | === Business Case === | ||
| + | === Architecture === | ||
| + | === Product === | ||
| + | === Evaluation === | ||
| + | === Change Requests === | ||
| + | === User Support === | ||
| + | |||
== Best Practices == | == Best Practices == | ||
| + | === Develop Software iteratively === | ||
| + | === Manage requirements === | ||
| + | === Use component-based architectures === | ||
| + | === Visually model software === | ||
| + | === Continuously verify software quality === | ||
| + | === Control changes to software === | ||
==Process Overview== | ==Process Overview== | ||
Revision as of 13:54, 13 September 2015
The Rational Unified Process (RUP) is an iterative, software development methodology, firstly introduced by the Rational Software Corporation which was acquired by IBM in 2003. RUP is a disciplined approach to assign tasks within a development organization and software project teams. It was developed, to ensure the production of high quality software who could meet and exceed the needs and expectations of end-users, strictly following a predictable budget and schedule. RUP is the most popular and extensively documented refinement of the Unified Process, an iterative and incremental software development process framework. Other worth mentioning forms are the OpenUP and Agile Unified Process.
Contents |
