Rational Unified Process (RUP) - Revision history

Tkokotas at 15:33, 18 December 2018

2018-12-18T15:33:15Z

← Older revision		Revision as of 15:33, 18 December 2018
Line 1:		Line 1:
			''Developed by Vasileios Lessis''


	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 <ref name="Ivar Jacobson, Grady Booch, and Jim Rumbaugh">Ivar Jacobson, Grady Booch, and Jim Rumbaugh, Unified Software Development Process, Addison-Wesley, 1999.</ref>. 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''' 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 <ref name="Ivar Jacobson, Grady Booch, and Jim Rumbaugh">Ivar Jacobson, Grady Booch, and Jim Rumbaugh, Unified Software Development Process, Addison-Wesley, 1999.</ref>. 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].

Lessisv: /* Further Reading */

2015-09-28T23:55:13Z

Lessisv at 23:53, 28 September 2015

2015-09-28T23:53:59Z

← Older revision		Revision as of 23:53, 28 September 2015
Line 232:		Line 232:

	The Rational Unified Process, is an exemplary method for addressing and mitigating risks from the very early stages, by rapidly developing an initial version of the system (prototype) that describes its architecture. There are not fixed requirements from the beginning but rather allows refining requirements , while the project progresses. It expects and actually deals with change pretty well while its main focus is the quality of the product and the degree to which it satisfies its end - users, throughout the project life-cycle. However, while being a complete and well documented methodology, it should be stressed that remains a very complex one. In order to increase the likelihood of success, while adopting this methodology, all the project members need to be '''experts''' in their respective fields. The method can easily become too difficult to learn and most importantly too difficult to apply.		The Rational Unified Process, is an exemplary method for addressing and mitigating risks from the very early stages, by rapidly developing an initial version of the system (prototype) that describes its architecture. There are not fixed requirements from the beginning but rather allows refining requirements , while the project progresses. It expects and actually deals with change pretty well while its main focus is the quality of the product and the degree to which it satisfies its end - users, throughout the project life-cycle. However, while being a complete and well documented methodology, it should be stressed that remains a very complex one. In order to increase the likelihood of success, while adopting this methodology, all the project members need to be '''experts''' in their respective fields. The method can easily become too difficult to learn and most importantly too difficult to apply.

			== Further Reading ==
			An [http://www.differnet.com/crose/CR_Files/CRose-RUPSample/RUPSample-CR1.pdf example] of using RUP

	== References ==		== References ==
	<references/>		<references/>

Lessisv: /* Visually model software */

2015-09-26T13:07:59Z

Visually model software

← Older revision		Revision as of 13:07, 26 September 2015
Line 210:		Line 210:
	=== Visually model software ===		=== Visually model software ===

	A model is an abstraction of reality that can help better comprehend large and complex systems. Visual abstractions help the development team to easily communicate different aspects of the software and see how all the components fit together. RUP uses the [http://www.uml.org/ Unified Modelling Language (UML)] standard which is a graphical language for visualizing and constructing the artifacts of a software-intensive system.		A model is an abstraction of reality that can help better comprehend large and complex systems. Visual abstractions help the development team to easily communicate different aspects of the software and see how all the components fit together. RUP uses the [http://www.uml.org/ Unified Modelling Language (UML)] standard which is a graphical language for visualizing and constructing the artifacts of a software-intensive system. <ref name="Grady Booch, Ivar Jacobson, and James Rumbaugh">Grady Booch, Ivar Jacobson, and James Rumbaugh, Unified Modeling Language 1.3, White paper, Rational Software Corp., 1998</ref>

	=== Continuously verify software quality ===		=== Continuously verify software quality ===

Lessisv: /* Use component-based architectures */

2015-09-26T13:06:32Z

Use component-based architectures

← Older revision		Revision as of 13:06, 26 September 2015
Line 206:		Line 206:
	=== Use component-based architectures ===		=== Use component-based architectures ===

	Component-based architecture makes the system dynamic; components are independent from the system and interact with other components through well-defined interfaces. Their in-dependency from the system, gives them a great flexibility meaning that they can easily be added, updated or totally replaced. RUP supports component-based software development by providing a systematic approach to defining an architecture using new and existing components.		Component-based architecture makes the system dynamic; components are independent from the system and interact with other components through well-defined interfaces. Their in-dependency from the system, gives them a great flexibility meaning that they can easily be added, updated or totally replaced. RUP supports component-based software development by providing a systematic approach to defining an architecture using new and existing components. <ref name="Alan W. Brown (ed.)">Alan W. Brown (ed.), Component-Based Software Engineering, IEEE Computer Society, Los Alamitos, CA, 1996, pp.140.</ref>

	=== Visually model software ===		=== Visually model software ===

Lessisv: /* Develop Software iteratively */

2015-09-26T13:05:01Z

Develop Software iteratively

← Older revision		Revision as of 13:05, 26 September 2015
Line 198:		Line 198:
	=== Develop Software iteratively ===		=== Develop Software iteratively ===

	Today’s high sophisticated software systems, consist of many and complex structures which make it nearly impossible to define the entire system from the very beginning, develop the entire solution and then test the product in the end. RUP uses an iterative approach that allows an increasing understanding of the problem and developing a step – by – step solution, over multiple iterations. Each iteration ends with an executable release, which enables continuous end - user involvement and feedback. As a result, the risks of the project are mitigated at an early stage and stakeholders are ensured that the project requirements are fulfilled <ref name="Barry W. Boehm 2">Barry W. Boehm, A Spiral Model of Software Development and Enhancement, Computer, May 1988, IEEE, pp.61-72 </ref>.		Today’s high sophisticated software systems, consist of many and complex structures which make it nearly impossible to define the entire system from the very beginning, develop the entire solution and then test the product in the end. RUP uses an iterative approach that allows an increasing understanding of the problem and developing a step – by – step solution, over multiple iterations. Each iteration ends with an executable release, which enables continuous end - user involvement and feedback. As a result, the risks of the project are mitigated at an early stage and stakeholders are ensured that the project requirements are fulfilled. <ref name="Barry W. Boehm 2">Barry W. Boehm, A Spiral Model of Software Development and Enhancement, Computer, May 1988, IEEE, pp.61-72 </ref>

	=== Manage requirements ===		=== Manage requirements ===

Lessisv: /* Manage requirements */

2015-09-26T13:04:34Z

Manage requirements

← Older revision		Revision as of 13:04, 26 September 2015
Line 202:		Line 202:
	=== Manage requirements ===		=== Manage requirements ===

	The requirements of a system include the description of the services that the system is able to provide and its operational constraints. RUP documents, organizes and tracks required functionality and constraints and easily communicates business requirements. The use – cases that are used in the process are an excellent way to ensure that requirements are actually those elements that drive the design, implementation and testing of software, making it more likely that the final system fulfills the stakeholders needs.		The requirements of a system include the description of the services that the system is able to provide and its operational constraints. RUP documents, organizes and tracks required functionality and constraints and easily communicates business requirements. The use – cases that are used in the process are an excellent way to ensure that requirements are actually those elements that drive the design, implementation and testing of software, making it more likely that the final system fulfills the stakeholders needs. <ref name="Ivar Jacobson, Magnus Christerson, Patrik Jonsson, and Gunnar Övergaard">Ivar Jacobson, Magnus Christerson, Patrik Jonsson, and Gunnar Övergaard, Object-Oriented Software Engineering—A Use Case Driven Approach, Wokingham, England, Addison-Wesley, 1992, 582p</ref>

	=== Use component-based architectures ===		=== Use component-based architectures ===

Lessisv: /* Develop Software iteratively */

2015-09-26T13:03:24Z

Develop Software iteratively

← Older revision		Revision as of 13:03, 26 September 2015
Line 198:		Line 198:
	=== Develop Software iteratively ===		=== Develop Software iteratively ===

	Today’s high sophisticated software systems, consist of many and complex structures which make it nearly impossible to define the entire system from the very beginning, develop the entire solution and then test the product in the end. RUP uses an iterative approach that allows an increasing understanding of the problem and developing a step – by – step solution, over multiple iterations. Each iteration ends with an executable release, which enables continuous end - user involvement and feedback. As a result, the risks of the project are mitigated at an early stage and stakeholders are ensured that the project requirements are fulfilled. <ref name="Barry W. Boehm 2">Barry W. Boehm, A Spiral Model of Software Development and Enhancement, Computer, May 1988, IEEE, pp.61-72 </ref>		Today’s high sophisticated software systems, consist of many and complex structures which make it nearly impossible to define the entire system from the very beginning, develop the entire solution and then test the product in the end. RUP uses an iterative approach that allows an increasing understanding of the problem and developing a step – by – step solution, over multiple iterations. Each iteration ends with an executable release, which enables continuous end - user involvement and feedback. As a result, the risks of the project are mitigated at an early stage and stakeholders are ensured that the project requirements are fulfilled <ref name="Barry W. Boehm 2">Barry W. Boehm, A Spiral Model of Software Development and Enhancement, Computer, May 1988, IEEE, pp.61-72 </ref>.

	=== Manage requirements ===		=== Manage requirements ===

Lessisv: /* Develop Software iteratively */

2015-09-26T13:03:04Z

Develop Software iteratively

← Older revision		Revision as of 13:03, 26 September 2015
Line 198:		Line 198:
	=== Develop Software iteratively ===		=== Develop Software iteratively ===

	Today’s high sophisticated software systems, consist of many and complex structures which make it nearly impossible to define the entire system from the very beginning, develop the entire solution and then test the product in the end. RUP uses an iterative approach that allows an increasing understanding of the problem and developing a step – by – step solution, over multiple iterations. Each iteration ends with an executable release, which enables continuous end - user involvement and feedback. As a result, the risks of the project are mitigated at an early stage and stakeholders are ensured that the project requirements are fulfilled. <ref name="Barry W. Boehm">Barry W. Boehm, A Spiral Model of Software Development and Enhancement, Computer, May 1988, IEEE, pp.61-72 ~~</ref> <ref name="Barry W. Boehm 2">Anchoring the Software Process, IEEE Software, 13, 4, July 1996, pp. 73-82.~~</ref>		Today’s high sophisticated software systems, consist of many and complex structures which make it nearly impossible to define the entire system from the very beginning, develop the entire solution and then test the product in the end. RUP uses an iterative approach that allows an increasing understanding of the problem and developing a step – by – step solution, over multiple iterations. Each iteration ends with an executable release, which enables continuous end - user involvement and feedback. As a result, the risks of the project are mitigated at an early stage and stakeholders are ensured that the project requirements are fulfilled. <ref name="Barry W. Boehm 2">Barry W. Boehm, A Spiral Model of Software Development and Enhancement, Computer, May 1988, IEEE, pp.61-72 </ref>

	=== Manage requirements ===		=== Manage requirements ===

Lessisv: /* Develop Software iteratively */

2015-09-26T13:01:32Z

Develop Software iteratively

← Older revision		Revision as of 13:01, 26 September 2015
Line 198:		Line 198:
	=== Develop Software iteratively ===		=== Develop Software iteratively ===

	Today’s high sophisticated software systems, consist of many and complex structures which make it nearly impossible to define the entire system from the very beginning, develop the entire solution and then test the product in the end. RUP uses an iterative approach that allows an increasing understanding of the problem and developing a step – by – step solution, over multiple iterations. Each iteration ends with an executable release, which enables continuous end - user involvement and feedback. As a result, the risks of the project are mitigated at an early stage and stakeholders are ensured that the project requirements are fulfilled. <ref name="Barry W. Boehm">Barry W. Boehm, A Spiral Model of Software Development and Enhancement, Computer, May 1988, IEEE, pp.61-72 </ref> <ref name="Barry W. Boehm">Anchoring the Software Process, IEEE Software, 13, 4, July 1996, pp. 73-82.</ref>		Today’s high sophisticated software systems, consist of many and complex structures which make it nearly impossible to define the entire system from the very beginning, develop the entire solution and then test the product in the end. RUP uses an iterative approach that allows an increasing understanding of the problem and developing a step – by – step solution, over multiple iterations. Each iteration ends with an executable release, which enables continuous end - user involvement and feedback. As a result, the risks of the project are mitigated at an early stage and stakeholders are ensured that the project requirements are fulfilled. <ref name="Barry W. Boehm">Barry W. Boehm, A Spiral Model of Software Development and Enhancement, Computer, May 1988, IEEE, pp.61-72 </ref> <ref name="Barry W. Boehm 2">Anchoring the Software Process, IEEE Software, 13, 4, July 1996, pp. 73-82.</ref>

	=== Manage requirements ===		=== Manage requirements ===

← Older revision		Revision as of 23:55, 28 September 2015
Line 234:		Line 234:

	== Further Reading ==		== Further Reading ==
	An [http://www.differnet.com/crose/CR_Files/CRose-RUPSample/RUPSample-CR1.pdf example] of using ~~RUP~~		A [http://www.differnet.com/crose/CR_Files/CRose-RUPSample/RUPSample-CR1.pdf practical example] of using the Rational Unified Process.

	== References ==		== References ==
	<references/>		<references/>