Waterfall model - Revision history

S212522: /* Description of the model in phases */

2022-03-18T15:56:25Z

Description of the model in phases

← Older revision		Revision as of 15:56, 18 March 2022
Line 36:		Line 36:
	Like a waterfall, the different phases of this model follow each other consecutively and chronologically. One cannot move on to a new step without having validated the previous one and each step must be accompanied by solid documentation.		Like a waterfall, the different phases of this model follow each other consecutively and chronologically. One cannot move on to a new step without having validated the previous one and each step must be accompanied by solid documentation.
	The first person to theorise this model was W.W. Royce in 1970. In his article: Imagining the development of large software system, he represents graphically the phases of the model without using the name waterfall. In his article, Royce already criticises this model at the time<ref name = "Ref1">W.W. Royce, Managing the Development of Large Software Systems</ref>.		The first person to theorise this model was W.W. Royce in 1970. In his article: Imagining the development of large software system, he represents graphically the phases of the model without using the name waterfall. In his article, Royce already criticises this model at the time<ref name = "Ref1">W.W. Royce, Managing the Development of Large Software Systems</ref>.

	~~[[File:Waterfall Figure 1.png\|border\|right\|middle\|upright = 0.01\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]~~

	[[File:Waterfall Figure 1.png\|frame\|right\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]		[[File:Waterfall Figure 1.png\|frame\|right\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]

S212522: /* Description of the model in phases */

2022-03-18T15:55:53Z

Description of the model in phases

← Older revision		Revision as of 15:55, 18 March 2022
Line 39:		Line 39:
	[[File:Waterfall Figure 1.png\|border\|right\|middle\|upright = 0.01\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]		[[File:Waterfall Figure 1.png\|border\|right\|middle\|upright = 0.01\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]

	[[File:Waterfall Figure 1.png\|~~border~~\|right~~\|middle\|upright~~\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]		[[File:Waterfall Figure 1.png\|frame\|right\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]

	==Applications==		==Applications==

S212522: /* Description of the model in phases */

2022-03-18T15:55:12Z

Description of the model in phases

← Older revision		Revision as of 15:55, 18 March 2022
Line 38:		Line 38:

	[[File:Waterfall Figure 1.png\|border\|right\|middle\|upright = 0.01\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]		[[File:Waterfall Figure 1.png\|border\|right\|middle\|upright = 0.01\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]

			[[File:Waterfall Figure 1.png\|border\|right\|middle\|upright\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]

	==Applications==		==Applications==

S212522: /* Description of the model in phases */

2022-03-18T15:49:48Z

Description of the model in phases

← Older revision		Revision as of 15:49, 18 March 2022
Line 37:		Line 37:
	The first person to theorise this model was W.W. Royce in 1970. In his article: Imagining the development of large software system, he represents graphically the phases of the model without using the name waterfall. In his article, Royce already criticises this model at the time<ref name = "Ref1">W.W. Royce, Managing the Development of Large Software Systems</ref>.		The first person to theorise this model was W.W. Royce in 1970. In his article: Imagining the development of large software system, he represents graphically the phases of the model without using the name waterfall. In his article, Royce already criticises this model at the time<ref name = "Ref1">W.W. Royce, Managing the Development of Large Software Systems</ref>.

	[[File:Waterfall Figure 1.png\|right\|middle\|upright = 0.1\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]		[[File:Waterfall Figure 1.png\|border\|right\|middle\|upright = 0.01\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]

	==Applications==		==Applications==

S212522: /* Description of the model in phases */

2022-03-18T15:45:36Z

Description of the model in phases

← Older revision		Revision as of 15:45, 18 March 2022
Line 37:		Line 37:
	The first person to theorise this model was W.W. Royce in 1970. In his article: Imagining the development of large software system, he represents graphically the phases of the model without using the name waterfall. In his article, Royce already criticises this model at the time<ref name = "Ref1">W.W. Royce, Managing the Development of Large Software Systems</ref>.		The first person to theorise this model was W.W. Royce in 1970. In his article: Imagining the development of large software system, he represents graphically the phases of the model without using the name waterfall. In his article, Royce already criticises this model at the time<ref name = "Ref1">W.W. Royce, Managing the Development of Large Software Systems</ref>.

	[[File:Waterfall Figure 1.png\|right\|upright = 0.~~5\|frame~~\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]		[[File:Waterfall Figure 1.png\|right\|middle\|upright = 0.1\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]

	==Applications==		==Applications==

S212522: /* Description of the model in phases */

2022-03-18T15:41:39Z

Description of the model in phases

← Older revision		Revision as of 15:41, 18 March 2022
Line 37:		Line 37:
	The first person to theorise this model was W.W. Royce in 1970. In his article: Imagining the development of large software system, he represents graphically the phases of the model without using the name waterfall. In his article, Royce already criticises this model at the time<ref name = "Ref1">W.W. Royce, Managing the Development of Large Software Systems</ref>.		The first person to theorise this model was W.W. Royce in 1970. In his article: Imagining the development of large software system, he represents graphically the phases of the model without using the name waterfall. In his article, Royce already criticises this model at the time<ref name = "Ref1">W.W. Royce, Managing the Development of Large Software Systems</ref>.

	[[File:Waterfall Figure 1.png\|right\|upright\|frame\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]		[[File:Waterfall Figure 1.png\|right\|upright = 0.5\|frame\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]

	==Applications==		==Applications==

S212522: /* Description of the model in phases */

2022-03-18T15:41:07Z

Description of the model in phases

← Older revision		Revision as of 15:41, 18 March 2022
Line 37:		Line 37:
	The first person to theorise this model was W.W. Royce in 1970. In his article: Imagining the development of large software system, he represents graphically the phases of the model without using the name waterfall. In his article, Royce already criticises this model at the time<ref name = "Ref1">W.W. Royce, Managing the Development of Large Software Systems</ref>.		The first person to theorise this model was W.W. Royce in 1970. In his article: Imagining the development of large software system, he represents graphically the phases of the model without using the name waterfall. In his article, Royce already criticises this model at the time<ref name = "Ref1">W.W. Royce, Managing the Development of Large Software Systems</ref>.

	[[File:Waterfall Figure 1.png\|right\|frame\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]		[[File:Waterfall Figure 1.png\|right\|upright\|frame\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]

	==Applications==		==Applications==

S212522: /* Description of the model in phases */

2022-03-18T15:37:13Z

Description of the model in phases

← Older revision		Revision as of 15:37, 18 March 2022
Line 36:		Line 36:
	Like a waterfall, the different phases of this model follow each other consecutively and chronologically. One cannot move on to a new step without having validated the previous one and each step must be accompanied by solid documentation.		Like a waterfall, the different phases of this model follow each other consecutively and chronologically. One cannot move on to a new step without having validated the previous one and each step must be accompanied by solid documentation.
	The first person to theorise this model was W.W. Royce in 1970. In his article: Imagining the development of large software system, he represents graphically the phases of the model without using the name waterfall. In his article, Royce already criticises this model at the time<ref name = "Ref1">W.W. Royce, Managing the Development of Large Software Systems</ref>.		The first person to theorise this model was W.W. Royce in 1970. In his article: Imagining the development of large software system, he represents graphically the phases of the model without using the name waterfall. In his article, Royce already criticises this model at the time<ref name = "Ref1">W.W. Royce, Managing the Development of Large Software Systems</ref>.

			[[File:Waterfall Figure 1.png\|right\|frame\|Figure 1: Waterfall model with Royce’s iterative feedback.<ref name = "Ref3"></ref>]]

	==Applications==		==Applications==

S212522 at 15:06, 18 March 2022

2022-03-18T15:06:58Z

← Older revision		Revision as of 15:06, 18 March 2022
Line 3:		Line 3:
	The waterfall model is a linear form of project organisation. The model is generally divided into six sequential phases: requirement, analysis, design, implementation, validation, and commissioning first presented in 1970 by W.W. Royce<ref name = "Ref1"></ref>. Each of these phases corresponds to a specialisation of tasks. The particularity of this model is that each phase follows chronologically and depends directly on the results of the previous phase.		The waterfall model is a linear form of project organisation. The model is generally divided into six sequential phases: requirement, analysis, design, implementation, validation, and commissioning first presented in 1970 by W.W. Royce<ref name = "Ref1"></ref>. Each of these phases corresponds to a specialisation of tasks. The particularity of this model is that each phase follows chronologically and depends directly on the results of the previous phase.
	Although considered obsolete, this model is still widely used in the business world, for instance in software development companies<ref name = "Ref2"></ref>. The waterfall model is often chosen for its simplicity of use, its clarity and its ease of management on projects with reduced scope. However, since the first appearance of the waterfall principle in the literature<ref name = "Ref1"></ref>, this model has been criticised for its rigidity: the final result depends on the success of each of the phases and a mistake along the way can mean a complete setback for the project in progress.		Although considered obsolete, this model is still widely used in the business world, for instance in software development companies<ref name = "Ref2"></ref>. The waterfall model is often chosen for its simplicity of use, its clarity and its ease of management on projects with reduced scope. However, since the first appearance of the waterfall principle in the literature<ref name = "Ref1"></ref>, this model has been criticised for its rigidity: the final result depends on the success of each of the phases and a mistake along the way can mean a complete setback for the project in progress.
	Since the emergence of the agile project management method, many comparative studies<ref name = "Ref3">Nayan B. Ruparelia et al, Software Development Lifecycle Models, 2010</ref> have been published to demonstrate the benefits of one model over another.		Since the emergence of the agile project management method, many comparative studies<ref name = "Ref3">Nayan B. Ruparelia et al, Software Development Lifecycle Models, 2010</ref> have been published to demonstrate the benefits of one model over another. This article critically reviews the tool that is the waterfall model and provides insights in comparing this model with the agile methods.

	==The Big Idea==		==The Big Idea==

S212522 at 15:03, 18 March 2022

2022-03-18T15:03:43Z

← Older revision		Revision as of 15:03, 18 March 2022
Line 2:		Line 2:

	The waterfall model is a linear form of project organisation. The model is generally divided into six sequential phases: requirement, analysis, design, implementation, validation, and commissioning first presented in 1970 by W.W. Royce<ref name = "Ref1"></ref>. Each of these phases corresponds to a specialisation of tasks. The particularity of this model is that each phase follows chronologically and depends directly on the results of the previous phase.		The waterfall model is a linear form of project organisation. The model is generally divided into six sequential phases: requirement, analysis, design, implementation, validation, and commissioning first presented in 1970 by W.W. Royce<ref name = "Ref1"></ref>. Each of these phases corresponds to a specialisation of tasks. The particularity of this model is that each phase follows chronologically and depends directly on the results of the previous phase.
	Although considered obsolete, this model is still widely used in the business world, for instance in software development companies<ref name = "Ref2"></ref>. The waterfall model is often chosen for its simplicity of use, its clarity and its ease of management on projects with reduced scope. However, since the first appearance of the waterfall principle in the literature<ref name = "Ref1></ref>, this model has been criticised for its rigidity: the final result depends on the success of each of the phases and a mistake along the way can mean a complete setback for the project in progress.		Although considered obsolete, this model is still widely used in the business world, for instance in software development companies<ref name = "Ref2"></ref>. The waterfall model is often chosen for its simplicity of use, its clarity and its ease of management on projects with reduced scope. However, since the first appearance of the waterfall principle in the literature<ref name = "Ref1"></ref>, this model has been criticised for its rigidity: the final result depends on the success of each of the phases and a mistake along the way can mean a complete setback for the project in progress.
	Since the emergence of the agile project management method, many comparative studies<ref name = "Ref3"></ref> have been published to demonstrate the benefits of one model over another.		Since the emergence of the agile project management method, many comparative studies<ref name = "Ref3">Nayan B. Ruparelia et al, Software Development Lifecycle Models, 2010</ref> have been published to demonstrate the benefits of one model over another.

	==The Big Idea==		==The Big Idea==