V-Model - Revision history

Tkokotas at 14:59, 18 December 2018

2018-12-18T14:59:37Z

← Older revision		Revision as of 14:59, 18 December 2018
Line 1:		Line 1:
	''Developed by Gaëtan ~~André Georges Jules~~ Garnotel''		''Developed by Gaëtan Garnotel''

Tkokotas at 14:59, 18 December 2018

2018-12-18T14:59:21Z

← Older revision		Revision as of 14:59, 18 December 2018
Line 1:		Line 1:
	~~[[Category:Project Management\|V-Model]]~~		''Developed by Gaëtan André Georges Jules Garnotel''
	~~[[Category:Product Development\|V-Model]]~~
	~~[[Category:IT]]~~
	The '''V-Model''' is a project management method for project planning and execution. It comes from the “Waterfall methods” and has begun to be widely used in the eighties. Nowadays, the method is still widely used in industries that launch complex, long and costly projects, such as the Defense industry, the Construction and Transport industry, or the Software industry. The process is divided into three main phases: the development phase when the system and components requirements are expressed and the system design is specified; the implementation phase when the simplest part of the system are built; and the test phase when all the parts are put together step by step so they form the complete system at the end. Moreover, the management methods related to the V-cycle offers project managers the opportunity to monitor and minimize the risks efficiently, to manager their costs effectively, to ensure a high-quality system, and to create a good relationship with all the project’s stakeholders through a documented and clear collaboration. The standardization and transparency of the V-model are particularly appreciated. Nevertheless, the V-Model has some drawbacks, especially in terms of cross-department collaboration or flexibility. That is why new project management methods have been created, such as the Agile methods in the nineties. Nevertheless, the V-Model is still widely used and is an interesting method to approach project management in a very structured way. In what follows, many information, and especially the industrial example, come from the experience of the author in the industry.		The '''V-Model''' is a project management method for project planning and execution. It comes from the “Waterfall methods” and has begun to be widely used in the eighties. Nowadays, the method is still widely used in industries that launch complex, long and costly projects, such as the Defense industry, the Construction and Transport industry, or the Software industry. The process is divided into three main phases: the development phase when the system and components requirements are expressed and the system design is specified; the implementation phase when the simplest part of the system are built; and the test phase when all the parts are put together step by step so they form the complete system at the end. Moreover, the management methods related to the V-cycle offers project managers the opportunity to monitor and minimize the risks efficiently, to manager their costs effectively, to ensure a high-quality system, and to create a good relationship with all the project’s stakeholders through a documented and clear collaboration. The standardization and transparency of the V-model are particularly appreciated. Nevertheless, the V-Model has some drawbacks, especially in terms of cross-department collaboration or flexibility. That is why new project management methods have been created, such as the Agile methods in the nineties. Nevertheless, the V-Model is still widely used and is an interesting method to approach project management in a very structured way. In what follows, many information, and especially the industrial example, come from the experience of the author in the industry.

Line 158:		Line 158:
	==References==		==References==
	<references \>		<references \>

			[[Category:Project Management\|V-Model]]
			[[Category:Product Development\|V-Model]]
			[[Category:IT]]

Tkokotas at 21:04, 24 October 2018

2018-10-24T21:04:58Z

← Older revision		Revision as of 21:04, 24 October 2018
Line 1:		Line 1:
	[[Category:Project Management\|V-Model]]		[[Category:Project Management\|V-Model]]
	[[Category:Product Development\|V-Model]]		[[Category:Product Development\|V-Model]]
	[[Category:~~Software Development Development\|V-Model~~]]		[[Category:IT]]
	The '''V-Model''' is a project management method for project planning and execution. It comes from the “Waterfall methods” and has begun to be widely used in the eighties. Nowadays, the method is still widely used in industries that launch complex, long and costly projects, such as the Defense industry, the Construction and Transport industry, or the Software industry. The process is divided into three main phases: the development phase when the system and components requirements are expressed and the system design is specified; the implementation phase when the simplest part of the system are built; and the test phase when all the parts are put together step by step so they form the complete system at the end. Moreover, the management methods related to the V-cycle offers project managers the opportunity to monitor and minimize the risks efficiently, to manager their costs effectively, to ensure a high-quality system, and to create a good relationship with all the project’s stakeholders through a documented and clear collaboration. The standardization and transparency of the V-model are particularly appreciated. Nevertheless, the V-Model has some drawbacks, especially in terms of cross-department collaboration or flexibility. That is why new project management methods have been created, such as the Agile methods in the nineties. Nevertheless, the V-Model is still widely used and is an interesting method to approach project management in a very structured way. In what follows, many information, and especially the industrial example, come from the experience of the author in the industry.		The '''V-Model''' is a project management method for project planning and execution. It comes from the “Waterfall methods” and has begun to be widely used in the eighties. Nowadays, the method is still widely used in industries that launch complex, long and costly projects, such as the Defense industry, the Construction and Transport industry, or the Software industry. The process is divided into three main phases: the development phase when the system and components requirements are expressed and the system design is specified; the implementation phase when the simplest part of the system are built; and the test phase when all the parts are put together step by step so they form the complete system at the end. Moreover, the management methods related to the V-cycle offers project managers the opportunity to monitor and minimize the risks efficiently, to manager their costs effectively, to ensure a high-quality system, and to create a good relationship with all the project’s stakeholders through a documented and clear collaboration. The standardization and transparency of the V-model are particularly appreciated. Nevertheless, the V-Model has some drawbacks, especially in terms of cross-department collaboration or flexibility. That is why new project management methods have been created, such as the Agile methods in the nineties. Nevertheless, the V-Model is still widely used and is an interesting method to approach project management in a very structured way. In what follows, many information, and especially the industrial example, come from the experience of the author in the industry.

Gaetangarnotel at 07:59, 28 September 2015

2015-09-28T07:59:45Z

← Older revision		Revision as of 07:59, 28 September 2015
Line 2:		Line 2:
	[[Category:Product Development\|V-Model]]		[[Category:Product Development\|V-Model]]
	[[Category:Software Development Development\|V-Model]]		[[Category:Software Development Development\|V-Model]]
	The '''V-Model''' is a project management method for project planning and execution. It comes from the “Waterfall methods” and has begun to be widely used in the eighties. Nowadays, the method is still widely used in industries that launch complex, long and costly projects, such as the Defense industry, the Construction and Transport industry, or the Software industry. The process is divided into three main phases: the development phase when the system and components requirements are expressed and the system design is specified; the implementation phase when the simplest part of the system are built; and the test phase when all the parts are put together step by step so they form the complete system at the end. Moreover, the management methods related to the V-cycle offers project managers the opportunity to monitor and minimize the risks efficiently, to manager their costs effectively, to ensure a high-quality system, and to create a good relationship with all the project’s stakeholders through a documented and clear collaboration. The standardization and transparency of the V-model are particularly appreciated. Nevertheless, the V-Model has some drawbacks, especially in terms of cross-department collaboration or flexibility. That is why new project management methods have been created, such as the Agile methods in the nineties. Nevertheless, the V-Model is still widely used and is an interesting method to approach project management in a very structured way.		The '''V-Model''' is a project management method for project planning and execution. It comes from the “Waterfall methods” and has begun to be widely used in the eighties. Nowadays, the method is still widely used in industries that launch complex, long and costly projects, such as the Defense industry, the Construction and Transport industry, or the Software industry. The process is divided into three main phases: the development phase when the system and components requirements are expressed and the system design is specified; the implementation phase when the simplest part of the system are built; and the test phase when all the parts are put together step by step so they form the complete system at the end. Moreover, the management methods related to the V-cycle offers project managers the opportunity to monitor and minimize the risks efficiently, to manager their costs effectively, to ensure a high-quality system, and to create a good relationship with all the project’s stakeholders through a documented and clear collaboration. The standardization and transparency of the V-model are particularly appreciated. Nevertheless, the V-Model has some drawbacks, especially in terms of cross-department collaboration or flexibility. That is why new project management methods have been created, such as the Agile methods in the nineties. Nevertheless, the V-Model is still widely used and is an interesting method to approach project management in a very structured way. In what follows, many information, and especially the industrial example, come from the experience of the author in the industry.

	==V-Model presentation: process & artefacts==		==V-Model presentation: process & artefacts==

Gaetangarnotel: /* References */

2015-09-28T07:58:52Z

References

← Older revision		Revision as of 07:58, 28 September 2015
Line 158:		Line 158:
	==References==		==References==
	<references \>		<references \>


	~~<u>Comment:</u> Many information, and especially the industrial example, come from the experience of the author in the industry.~~

Gaetangarnotel at 07:56, 28 September 2015

2015-09-28T07:56:30Z

← Older revision		Revision as of 07:56, 28 September 2015
Line 159:		Line 159:
	<references \>		<references \>

	<u>Comment:<u/> Many information, and especially the industrial example, come from the experience of the author in the industry.
			<u>Comment:</u> Many information, and especially the industrial example, come from the experience of the author in the industry.

Gaetangarnotel at 07:54, 28 September 2015

2015-09-28T07:54:30Z

← Older revision		Revision as of 07:54, 28 September 2015
Line 158:		Line 158:
	==References==		==References==
	<references \>		<references \>

			<u>Comment:<u/> Many information, and especially the industrial example, come from the experience of the author in the industry.

Gaetangarnotel: /* References */

2015-09-28T07:53:58Z

References

← Older revision		Revision as of 07:53, 28 September 2015
Line 158:		Line 158:
	==References==		==References==
	<references \>		<references \>

	~~<u>Comment:<u/> Many information, and especially the industrial example, come from the experience of the author in the industry.~~

Gaetangarnotel: /* References */

2015-09-28T07:53:37Z

References

← Older revision		Revision as of 07:53, 28 September 2015
Line 158:		Line 158:
	==References==		==References==
	<references \>		<references \>

			<u>Comment:<u/> Many information, and especially the industrial example, come from the experience of the author in the industry.

EvaSchultz: /* Needs & Feasibility Analysis */

2015-09-20T15:28:42Z

Needs & Feasibility Analysis

← Older revision		Revision as of 15:28, 20 September 2015
Line 33:		Line 33:
	Thanks to this document, the project is clearly structured.		Thanks to this document, the project is clearly structured.

	'''<u>Example</u>'''<ref name="NumberThree">Based on the author’s experience in the industry.</ref>: Project management is a very concrete matter. Thus, the example of a fighter aircraft will be run throughout the V-Model description so it becomes understandable. Imagine that you are a project manager for the Defense industry at Dassault Aviation. During this first step, you have to plan the project, understand your customer’s needs and requirements. For instance, you have to take into account that your customer wants a fighter aircraft capable of escaping existing fighter aircrafts or being able to carry pilots up to 1m90 tall. All those information are documented in the Scope Statement.		'''<u>Example</u>'''<ref name="NumberThree">Based on the author’s experience in the industry.</ref>: Project management is a very concrete matter. Thus, the example of a fighter aircraft will be run throughout the V-Model description so it becomes understandable. Imagine that you are a project manager for the Defense industry at Dassault Aviation. During this first step, you have to plan the project, understand your customer’s needs and requirements. For instance, you have to take into account that your customer wants a fighter aircraft capable of escaping existing fighter aircrafts or being able to carry pilots up to 1m90 tall. All those information are documented in the Scope Statement.

	====''Requirements & Specifications Analysis''====		====''Requirements & Specifications Analysis''====