Rational Unified Process (RUP)
| Line 13: | Line 13: | ||
==== Transition Phase ==== | ==== Transition Phase ==== | ||
| + | |||
| + | == Workfow == | ||
| + | |||
| + | === Disciplines === | ||
| + | |||
| + | ==== Business Modelling === | ||
| + | ==== Requirements ==== | ||
| + | ==== Analysis and Design ==== | ||
| + | ==== Implementation ==== | ||
| + | ==== Test ==== | ||
| + | ==== Deployment ==== | ||
| + | |||
| + | |||
== Ten Essentials == | == Ten Essentials == | ||
Revision as of 12:55, 17 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 by providing the development team with a set of guidelines, templates and tool mentors, for all the critical life-cycle activities within a project. This way, the deliverable software can 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 |
