View source for Rational Unified Process (RUP)

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''' 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 cluster of objects, form a knowledge base that is shared between all project team members. As a result, no matter what each member is working with (e.g testing, designing, managing), they all share a common language and view on how to develop software. Consequently, team productivity is boosted, in order to deliver software that 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 [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].

Maybe Mention UML !!!


== Process Overview ==

[[File:RUP.png|600px|right|thumb| The iterative model graph shows how the process is structured along two dimensions]]
The best possible way to describe this rather complex methodology is through a 2 - dimensional graph.
* The first dimension (horizontal axis) represents the '''dynamic aspect''' of the process. It expresses '''time''' in terms of cycles, phases, iterations and finally milestones. 
* The second dimension (vertical axis) represents the '''static aspect''' of the process. It expresses '''workflows''' in terms of 6 core and 3 supporting disciplines (more on that on "Disciplines" section).



=== The Phases===

==== Inception Phase ====

==== Elaboration Phase ====

==== Construction ====

==== Transition Phase ====

== Workflow ==

=== Disciplines ===

==== Business Modelling ====
==== Requirements ====
==== Analysis and Design ====
==== Implementation ====
==== Test ====
==== Deployment ====



== Ten Essentials ==
=== Vision ===
=== Plan ===
=== Risks ===
=== Issues ===
=== Business Case ===
=== Architecture ===
=== Product ===
=== Evaluation ===
=== Change Requests ===
=== User Support ===


== Best Practices ==
=== Develop Software iteratively ===
=== Manage requirements ===
=== Use component-based architectures ===
=== Visually model software ===
=== Continuously verify software quality ===
=== Control changes to software ===


== Limitations ==

== Conclusion ==