The Waterfall Model - Revision history

S220123: /* Disadvantages */

2022-03-27T13:42:56Z

Disadvantages

← Older revision		Revision as of 13:42, 27 March 2022
Line 146:		Line 146:
	The Waterfall Model has always been widely criticized because of the significant disadvantage: it cannot handle any considerable requirement changes during the project, especially after reaching the testing phase, it is difficult to change. It is difficult for the Waterfall Model to handle a requirement change because all the previous phases must be changed together with previous documentation. Therefore, it is recommended to use another model than the Waterfall Model if it is known before the beginning of the project that there might be changes during the project.<ref name="Large-Scale"/><ref name="Best Practices"/>		The Waterfall Model has always been widely criticized because of the significant disadvantage: it cannot handle any considerable requirement changes during the project, especially after reaching the testing phase, it is difficult to change. It is difficult for the Waterfall Model to handle a requirement change because all the previous phases must be changed together with previous documentation. Therefore, it is recommended to use another model than the Waterfall Model if it is known before the beginning of the project that there might be changes during the project.<ref name="Large-Scale"/><ref name="Best Practices"/>

	Another disadvantage is that the final product often has an extended delivery; this can be because there is no previous available prototype to compare to the developed application. The risk of error is higher without a prototype, and errors can be a big problem with the Waterfall Model. Because the testing phase is late in. the process, it can be hard to identify risks, errors, and challenges in an early phase.<ref name="Large-Scale"/><ref name="Best Practices"/>		Another disadvantage is that the final product often has an extended delivery; this can be because there is no previous available prototype to compare to the developed application. The risk of error is higher without a prototype, and errors can be a big problem with the Waterfall Model. Because the testing phase is late in the process, it can be hard to identify risks, errors, and challenges in an early phase.<ref name="Large-Scale"/><ref name="Best Practices"/>

	=Annotated bibliography=		=Annotated bibliography=

S220123: /* Application of the Waterfall Model */

2022-03-27T13:34:09Z

Application of the Waterfall Model

← Older revision		Revision as of 13:34, 27 March 2022
Line 10:		Line 10:
	A good project manager is familiar with different project life cycle models and knows where and when to use which project life cycle, whether it is a predictive or an adaptive lifecycle. To understand where and when the Waterfall Model potentially works best. An adapted version of Stacey's Matrix from Domain I: Agile Principles and Mindset by Sumanta Boral<ref name= "Agile Principles"> Boral, S. (2016). Domain I: Agile Principles and Mindset. In: Ace the PMI-ACP® exam. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2526-4_1</ref> is used. The Stacey Matrix was published and developed by Ralph Douglas Stacey. It is developed to give an understanding of which factors there contribute to the complexity and how to address the different degrees of complexity and, with that knowledge, choose the best-suited project life cycle. <ref name="strategic management"> Stacey RD. Strategic management and organizational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002 </ref>		A good project manager is familiar with different project life cycle models and knows where and when to use which project life cycle, whether it is a predictive or an adaptive lifecycle. To understand where and when the Waterfall Model potentially works best. An adapted version of Stacey's Matrix from Domain I: Agile Principles and Mindset by Sumanta Boral<ref name= "Agile Principles"> Boral, S. (2016). Domain I: Agile Principles and Mindset. In: Ace the PMI-ACP® exam. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2526-4_1</ref> is used. The Stacey Matrix was published and developed by Ralph Douglas Stacey. It is developed to give an understanding of which factors there contribute to the complexity and how to address the different degrees of complexity and, with that knowledge, choose the best-suited project life cycle. <ref name="strategic management"> Stacey RD. Strategic management and organizational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002 </ref>
	The Stacey Matrix is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>		The Stacey Matrix is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>

S220123 at 13:30, 27 March 2022

2022-03-27T13:30:53Z

← Older revision		Revision as of 13:30, 27 March 2022
Line 6:		Line 6:
	Winston W. Royce wrote the first description of the Waterfall Model in 1970. Back then, he did not call it the Waterfall Model. <ref name="Large-Scale"> Petersen, K. Wohlin, C. Baca, D. (2009) 'The Waterfall Model in Large-Scale Development', In: Bomarius, F. Oivo, M. Jaring, P. Abrahamsson, P. (eds) Product-Focused Software Process Improvement. PROFES 2009. Lecture Notes in Business Information Processing, vol 32. Springer, Berlin, Heidelberg. doi: https://doi-org.proxy.findit.cvt.dk/10.1007/978-3-642-02152-7_29 </ref> Later, it got the name because all the phases are done one by one and flow downwards like a waterfall. It is the finest and oldest known SDLC model. There are defined and designed various SDLC models such as V-Shaped model, Big Bang Model, Iterative model, etc. <ref name="Best Practices"> Kramer, M. (2018) 'Best Practices in Systems Development Lifecycle: An Analyses Based on the Waterfall Model', Review of Business & Finance Studies, v. 9 (1) p. 77-84, SSRN: https://ssrn.com/abstract=3131958</ref> These models are also called Software Development Process Models and are all ''”process consisting of a sequence of planned phases to develop or to amend the software products.”'' (Dubey, 2009)<ref> Dubey, A. Jain, A. Mantri, A. (2015) 'Comparative Study: Waterfall v/s Agile Model', International Journal of Engineering Sciences & Research Technology (IJESRT) </ref>		Winston W. Royce wrote the first description of the Waterfall Model in 1970. Back then, he did not call it the Waterfall Model. <ref name="Large-Scale"> Petersen, K. Wohlin, C. Baca, D. (2009) 'The Waterfall Model in Large-Scale Development', In: Bomarius, F. Oivo, M. Jaring, P. Abrahamsson, P. (eds) Product-Focused Software Process Improvement. PROFES 2009. Lecture Notes in Business Information Processing, vol 32. Springer, Berlin, Heidelberg. doi: https://doi-org.proxy.findit.cvt.dk/10.1007/978-3-642-02152-7_29 </ref> Later, it got the name because all the phases are done one by one and flow downwards like a waterfall. It is the finest and oldest known SDLC model. There are defined and designed various SDLC models such as V-Shaped model, Big Bang Model, Iterative model, etc. <ref name="Best Practices"> Kramer, M. (2018) 'Best Practices in Systems Development Lifecycle: An Analyses Based on the Waterfall Model', Review of Business & Finance Studies, v. 9 (1) p. 77-84, SSRN: https://ssrn.com/abstract=3131958</ref> These models are also called Software Development Process Models and are all ''”process consisting of a sequence of planned phases to develop or to amend the software products.”'' (Dubey, 2009)<ref> Dubey, A. Jain, A. Mantri, A. (2015) 'Comparative Study: Waterfall v/s Agile Model', International Journal of Engineering Sciences & Research Technology (IJESRT) </ref>

	=Application of the Waterfall ~~model~~=		=Application of the Waterfall Model=
	[[File:TheStaceyMatrix.png\|thumb\|right\|500px\|Figure 1: Application of the Waterfall ~~model~~<ref name= "Agile Principles"/>]]		[[File:TheStaceyMatrix.png\|thumb\|right\|500px\|Figure 1: Application of the Waterfall Model<ref name= "Agile Principles"/>]]
	A good project manager is familiar with different project life cycle models and knows where and when to use which project life cycle, whether it is a predictive or an adaptive lifecycle. To understand where and when the ~~waterfall model~~ potentially works best. An adapted version of Stacey's Matrix from Domain I: Agile Principles and Mindset by Sumanta Boral<ref name= "Agile Principles"> Boral, S. (2016). Domain I: Agile Principles and Mindset. In: Ace the PMI-ACP® exam. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2526-4_1</ref> is used. The Stacey Matrix was published and developed by Ralph Douglas Stacey. It is developed to give an understanding of which factors there contribute to the complexity and how to address the different degrees of complexity and, with that knowledge, choose the best-suited project life cycle. <ref name="strategic management"> Stacey RD. Strategic management and organizational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002 </ref>		A good project manager is familiar with different project life cycle models and knows where and when to use which project life cycle, whether it is a predictive or an adaptive lifecycle. To understand where and when the Waterfall Model potentially works best. An adapted version of Stacey's Matrix from Domain I: Agile Principles and Mindset by Sumanta Boral<ref name= "Agile Principles"> Boral, S. (2016). Domain I: Agile Principles and Mindset. In: Ace the PMI-ACP® exam. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2526-4_1</ref> is used. The Stacey Matrix was published and developed by Ralph Douglas Stacey. It is developed to give an understanding of which factors there contribute to the complexity and how to address the different degrees of complexity and, with that knowledge, choose the best-suited project life cycle. <ref name="strategic management"> Stacey RD. Strategic management and organizational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002 </ref>
	The Stacey Matrix is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>		The Stacey Matrix is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>

Line 23:		Line 23:


	The Waterfall ~~model~~ is placed in the bottom left corner in the zone called ''"simple,"'' as illustrated in the figure. The requirements are almost certain in this region, and there is a good consensus around the project. In this zone, the decision-making is based on reliable data gathered from the past to predict the future. <ref name= "Agile Principles"/>		The Waterfall Model is placed in the bottom left corner in the zone called ''"simple,"'' as illustrated in the figure. The requirements are almost certain in this region, and there is a good consensus around the project. In this zone, the decision-making is based on reliable data gathered from the past to predict the future. <ref name= "Agile Principles"/>

	=The Waterfall Model=		=The Waterfall Model=
	[[File:WaterfallModel.png\|thumb\|right\|600px\|Figure 2: Waterfall Model]]		[[File:WaterfallModel.png\|thumb\|right\|600px\|Figure 2: Waterfall Model]]
	The ~~waterfall model~~ is a stage-gate model, which is a category of life cycle models. A stage-gate model consists of multiple phases. Each phase includes one stage and one gate. The project has to pass a gate to get from one phase to another. A stage consists of a description of activities there need to be done during each state. The gate is the requirement and the review that determines whether a project can continue. The phases must be processed in order, without overlapping, and within a specified timeframe. In the ~~waterfall model~~, it is not possible to move back and forth between phases. Once a phase is completed, it will freeze, and therefore it is not possible to move back and work on it again. The ~~waterfall model~~ consists of 6 phases, 1) Requirements Gathering and Analysis, 2) Systems Development, 3) Systems Implementation and Coding, 4) Testing, 5) Deployment, 6) Systems Operations and Maintenance. All six phases must be completed to achieve a positive outcome. <ref name="Best Practices"/>		The Waterfall Model is a stage-gate model, which is a category of life cycle models. A stage-gate model consists of multiple phases. Each phase includes one stage and one gate. The project has to pass a gate to get from one phase to another. A stage consists of a description of activities there need to be done during each state. The gate is the requirement and the review that determines whether a project can continue. The phases must be processed in order, without overlapping, and within a specified timeframe. In the Waterfall Model, it is not possible to move back and forth between phases. Once a phase is completed, it will freeze, and therefore it is not possible to move back and work on it again. The Waterfall Model consists of 6 phases, 1) Requirements Gathering and Analysis, 2) Systems Development, 3) Systems Implementation and Coding, 4) Testing, 5) Deployment, 6) Systems Operations and Maintenance. All six phases must be completed to achieve a positive outcome. <ref name="Best Practices"/>


Line 47:		Line 47:
	'''State'''		'''State'''

	This phase is in some descriptions of the ~~waterfall model~~ called the design phase because this phase is all about describing the architecture of the system and documenting it. <ref name="Large-Scale"/> This can be done		This phase is in some descriptions of the Waterfall Model called the design phase because this phase is all about describing the architecture of the system and documenting it. <ref name="Large-Scale"/> This can be done
	by converting all the detailed requirements, from the previous phase, into a completed detailed systems design. The detailed systems design is a detailed description of how the required functionalities (must- and wish- list)		by converting all the detailed requirements, from the previous phase, into a completed detailed systems design. The detailed systems design is a detailed description of how the required functionalities (must- and wish- list)
	can be delivered to the system. It includes an accurate description of the key components and the interface for the components.<ref name="Best Practices"/>		can be delivered to the system. It includes an accurate description of the key components and the interface for the components.<ref name="Best Practices"/>
Line 61:		Line 61:
	'''State'''		'''State'''

	In this phase, all the information, requirements, and analysis gathered in the two previous phases are converted into code. This will show whether the previous phases are documented well enough for the developer to develop the application and implement the design. Depending on the size of the application, this can be the longest phase of the ~~waterfall model~~. <ref name="Best Practices"/>		In this phase, all the information, requirements, and analysis gathered in the two previous phases are converted into code. This will show whether the previous phases are documented well enough for the developer to develop the application and implement the design. Depending on the size of the application, this can be the longest phase of the Waterfall Model. <ref name="Best Practices"/>
	Before moving on to the next phase, the developer conducts basic unit tests to ensure that the application is running. <ref name="Large-Scale"/>		Before moving on to the next phase, the developer conducts basic unit tests to ensure that the application is running. <ref name="Large-Scale"/>

Line 108:		Line 108:
	'''Gate'''		'''Gate'''

	In this phase, there is no gate because the state is an ongoing process. There are some documents there can be a good idea to keep updated to keep an overview of the operation and maintenance. If a new application needs to be developed, The ~~waterfall model~~ can be used again from the beginning.		In this phase, there is no gate because the state is an ongoing process. There are some documents there can be a good idea to keep updated to keep an overview of the operation and maintenance. If a new application needs to be developed, The Waterfall Model can be used again from the beginning.

	Deliverables: User Manual, List of Production Tickets (Resolved), List of New Features Implemented		Deliverables: User Manual, List of Production Tickets (Resolved), List of New Features Implemented
Line 143:		Line 143:

	=Advantages=		=Advantages=
	The ~~waterfall model~~ is widely used and recognized in the industry because of its precise and rigid stages. It is easy to understand and thereby also easy to implement. It is methodical, simple, and works well. Other than that, it is easy to maintain because of the one at a time stage execution and easy to identify deliverables and milestones, which helps to ensure the quality. The ~~waterfall model~~ is not a stressful model because of the well-defined start and finish criteria. <ref name="Large-Scale"/><ref name="Best Practices"/>		The Waterfall Model is widely used and recognized in the industry because of its precise and rigid stages. It is easy to understand and thereby also easy to implement. It is methodical, simple, and works well. Other than that, it is easy to maintain because of the one at a time stage execution and easy to identify deliverables and milestones, which helps to ensure the quality. The Waterfall Model is not a stressful model because of the well-defined start and finish criteria. <ref name="Large-Scale"/><ref name="Best Practices"/>

	=Disadvantages=		=Disadvantages=
	The ~~waterfall model~~ has always been widely criticized because of the significant disadvantage: it cannot handle any considerable requirement changes during the project, especially after reaching the testing phase, it is difficult to change. It is difficult for the ~~waterfall model~~ to handle a requirement change because all the previous phases must be changed together with previous documentation. Therefore, it is recommended to use another model than the ~~waterfall model~~ if it is known before the beginning of the project that there might be changes during the project.<ref name="Large-Scale"/><ref name="Best Practices"/>		The Waterfall Model has always been widely criticized because of the significant disadvantage: it cannot handle any considerable requirement changes during the project, especially after reaching the testing phase, it is difficult to change. It is difficult for the Waterfall Model to handle a requirement change because all the previous phases must be changed together with previous documentation. Therefore, it is recommended to use another model than the Waterfall Model if it is known before the beginning of the project that there might be changes during the project.<ref name="Large-Scale"/><ref name="Best Practices"/>

	Another disadvantage is that the final product often has an extended delivery; this can be because there is no previous available prototype to compare to the developed application. The risk of error is higher without a prototype, and errors can be a big problem with the ~~waterfall model~~. Because the testing phase is late in. the process, it can be hard to identify risks, errors, and challenges in an early phase.<ref name="Large-Scale"/><ref name="Best Practices"/>		Another disadvantage is that the final product often has an extended delivery; this can be because there is no previous available prototype to compare to the developed application. The risk of error is higher without a prototype, and errors can be a big problem with the Waterfall Model. Because the testing phase is late in. the process, it can be hard to identify risks, errors, and challenges in an early phase.<ref name="Large-Scale"/><ref name="Best Practices"/>

	=Annotated bibliography=		=Annotated bibliography=
Line 154:		Line 154:
	'''Petersen, K. Wohlin, C. Baca, D. (2009) 'The Waterfall Model in Large-Scale Development',''' <ref name="Large-Scale"/>		'''Petersen, K. Wohlin, C. Baca, D. (2009) 'The Waterfall Model in Large-Scale Development',''' <ref name="Large-Scale"/>

	This article aims to provide empirical evidence about the ~~waterfall model~~ to address what they call a research gap between the problems mentioned in literature and empirical evidence. This is done through a case study at Ericsson AB in Sweden. This case study aims to investigate the issues mentioned in the literature about the ~~waterfall model~~. Through the case study, they found the same issues as described in the literature, but they could give a more detailed explanation of the issues with the case study.		This article aims to provide empirical evidence about the Waterfall Model to address what they call a research gap between the problems mentioned in literature and empirical evidence. This is done through a case study at Ericsson AB in Sweden. This case study aims to investigate the issues mentioned in the literature about the Waterfall Model. Through the case study, they found the same issues as described in the literature, but they could give a more detailed explanation of the issues with the case study.


	'''Kramer, M. (2018) 'Best Practices in Systems Development Lifecycle: An Analyses Based on the Waterfall Model','''<ref name="Best Practices"/>		'''Kramer, M. (2018) 'Best Practices in Systems Development Lifecycle: An Analyses Based on the Waterfall Model','''<ref name="Best Practices"/>

	This article discusses the theory, best practice, and gate deliverables for the Systems Development Lifecycle; the analyses and discussion are based on the ~~waterfall model~~. The author Kramer, M. have worked on and completed numerous projects using different models for businesses to Fortune 1000 companies. At the end of the article, the advantages and disadvantages of the ~~waterfall model~~ are discussed.		This article discusses the theory, best practice, and gate deliverables for the Systems Development Lifecycle; the analyses and discussion are based on the Waterfall Model. The author Kramer, M. have worked on and completed numerous projects using different models for businesses to Fortune 1000 companies. At the end of the article, the advantages and disadvantages of the Waterfall Model are discussed.

S220123 at 13:26, 27 March 2022

2022-03-27T13:26:00Z

← Older revision		Revision as of 13:26, 27 March 2022
Line 1:		Line 1:

	This article is focusing on when and how the ~~waterfall model~~ should be used in a software development environment. The ~~waterfall model~~ is a Software Development Life Cycle model (SDLC) and was the first process model introduced. The ~~waterfall model~~ is easy to understand and use. It is a stage-gate model, which means that the model consists of stages and gates. Each phase consists of one stage and one gate. Each phase has some pre-determined activities and requirements. The current phase must be completed before the next phase can begin, and to end a phase, it must pass a gate. A stage is the activities, and the gate is the requirements and the review that determine whether a project can continue. The ~~waterfall model~~ consists of six different stages, 1) Requirements Gathering and Analysis, 2) Systems Development, 3) Systems Implementation and Coding, 4) Testing, 5) Deployment, 6) Systems Operations and Maintenance.		This article is focusing on when and how the Waterfall Model should be used in a software development environment. The Waterfall Model is a Software Development Life Cycle model (SDLC) and was the first process model introduced. The Waterfall Model is easy to understand and use. It is a stage-gate model, which means that the model consists of stages and gates. Each phase consists of one stage and one gate. Each phase has some pre-determined activities and requirements. The current phase must be completed before the next phase can begin, and to end a phase, it must pass a gate. A stage is the activities, and the gate is the requirements and the review that determine whether a project can continue. The Waterfall Model consists of six different stages, 1) Requirements Gathering and Analysis, 2) Systems Development, 3) Systems Implementation and Coding, 4) Testing, 5) Deployment, 6) Systems Operations and Maintenance.

	The ~~waterfall model~~ is widely used for software development, but it is also widely criticized. The model is often criticized for the late detection of defects in the process and how to handle change requests. It is most optimal to use the ~~waterfall model~~ for simple projects with precise requirements and projects that do not change through the development process.		The Waterfall Model is widely used for software development, but it is also widely criticized. The model is often criticized for the late detection of defects in the process and how to handle change requests. It is most optimal to use the Waterfall Model for simple projects with precise requirements and projects that do not change through the development process.
	==About==		==About==
	Winston W. Royce wrote the first description of the Waterfall ~~model~~ in 1970. Back then, he did not call it the Waterfall ~~model~~. <ref name="Large-Scale"> Petersen, K. Wohlin, C. Baca, D. (2009) 'The Waterfall Model in Large-Scale Development', In: Bomarius, F. Oivo, M. Jaring, P. Abrahamsson, P. (eds) Product-Focused Software Process Improvement. PROFES 2009. Lecture Notes in Business Information Processing, vol 32. Springer, Berlin, Heidelberg. doi: https://doi-org.proxy.findit.cvt.dk/10.1007/978-3-642-02152-7_29 </ref> Later, it got the name because all the phases are done one by one and flow downwards like a waterfall. It is the finest and oldest known SDLC model. There are defined and designed various SDLC models such as V-Shaped model, Big Bang Model, Iterative model, etc. <ref name="Best Practices"> Kramer, M. (2018) 'Best Practices in Systems Development Lifecycle: An Analyses Based on the Waterfall Model', Review of Business & Finance Studies, v. 9 (1) p. 77-84, SSRN: https://ssrn.com/abstract=3131958</ref> These models are also called Software Development Process Models and are all ''”process consisting of a sequence of planned phases to develop or to amend the software products.”'' (Dubey, 2009)<ref> Dubey, A. Jain, A. Mantri, A. (2015) 'Comparative Study: Waterfall v/s Agile Model', International Journal of Engineering Sciences & Research Technology (IJESRT) </ref>		Winston W. Royce wrote the first description of the Waterfall Model in 1970. Back then, he did not call it the Waterfall Model. <ref name="Large-Scale"> Petersen, K. Wohlin, C. Baca, D. (2009) 'The Waterfall Model in Large-Scale Development', In: Bomarius, F. Oivo, M. Jaring, P. Abrahamsson, P. (eds) Product-Focused Software Process Improvement. PROFES 2009. Lecture Notes in Business Information Processing, vol 32. Springer, Berlin, Heidelberg. doi: https://doi-org.proxy.findit.cvt.dk/10.1007/978-3-642-02152-7_29 </ref> Later, it got the name because all the phases are done one by one and flow downwards like a waterfall. It is the finest and oldest known SDLC model. There are defined and designed various SDLC models such as V-Shaped model, Big Bang Model, Iterative model, etc. <ref name="Best Practices"> Kramer, M. (2018) 'Best Practices in Systems Development Lifecycle: An Analyses Based on the Waterfall Model', Review of Business & Finance Studies, v. 9 (1) p. 77-84, SSRN: https://ssrn.com/abstract=3131958</ref> These models are also called Software Development Process Models and are all ''”process consisting of a sequence of planned phases to develop or to amend the software products.”'' (Dubey, 2009)<ref> Dubey, A. Jain, A. Mantri, A. (2015) 'Comparative Study: Waterfall v/s Agile Model', International Journal of Engineering Sciences & Research Technology (IJESRT) </ref>

	=Application of the Waterfall model=		=Application of the Waterfall model=
	[[File:TheStaceyMatrix.png\|thumb\|right\|500px\|Figure 1: Application of the Waterfall model<ref name= "Agile Principles"/>]]		[[File:TheStaceyMatrix.png\|thumb\|right\|500px\|Figure 1: Application of the Waterfall model<ref name= "Agile Principles"/>]]
	A good project manager is familiar with different project life cycle models and knows where and when to use which project life cycle, whether it is a predictive or an adaptive lifecycle. To understand where and when the waterfall model potentially works best. An adapted version of Stacey's ~~matrix~~ from Domain I: Agile Principles and Mindset by Sumanta Boral<ref name= "Agile Principles"> Boral, S. (2016). Domain I: Agile Principles and Mindset. In: Ace the PMI-ACP® exam. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2526-4_1</ref> is used. The Stacey Matrix was published and developed by Ralph Douglas Stacey. It is developed to give an understanding of which factors there contribute to the complexity and how to address the different degrees of complexity and, with that knowledge, choose the best-suited project life cycle. <ref name="strategic management"> Stacey RD. Strategic management and organizational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002 </ref>		A good project manager is familiar with different project life cycle models and knows where and when to use which project life cycle, whether it is a predictive or an adaptive lifecycle. To understand where and when the waterfall model potentially works best. An adapted version of Stacey's Matrix from Domain I: Agile Principles and Mindset by Sumanta Boral<ref name= "Agile Principles"> Boral, S. (2016). Domain I: Agile Principles and Mindset. In: Ace the PMI-ACP® exam. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2526-4_1</ref> is used. The Stacey Matrix was published and developed by Ralph Douglas Stacey. It is developed to give an understanding of which factors there contribute to the complexity and how to address the different degrees of complexity and, with that knowledge, choose the best-suited project life cycle. <ref name="strategic management"> Stacey RD. Strategic management and organizational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002 </ref>
	The Stacey ~~matrix~~ is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>		The Stacey Matrix is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>

S220123: /* Application of the Waterfall model */

2022-03-27T13:22:25Z

Application of the Waterfall model

← Older revision		Revision as of 13:22, 27 March 2022
Line 7:		Line 7:

	=Application of the Waterfall model=		=Application of the Waterfall model=
			[[File:TheStaceyMatrix.png\|thumb\|right\|500px\|Figure 1: Application of the Waterfall model<ref name= "Agile Principles"/>]]
	A good project manager is familiar with different project life cycle models and knows where and when to use which project life cycle, whether it is a predictive or an adaptive lifecycle. To understand where and when the waterfall model potentially works best. An adapted version of Stacey's matrix from Domain I: Agile Principles and Mindset by Sumanta Boral<ref name= "Agile Principles"> Boral, S. (2016). Domain I: Agile Principles and Mindset. In: Ace the PMI-ACP® exam. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2526-4_1</ref> is used. The Stacey Matrix was published and developed by Ralph Douglas Stacey. It is developed to give an understanding of which factors there contribute to the complexity and how to address the different degrees of complexity and, with that knowledge, choose the best-suited project life cycle. <ref name="strategic management"> Stacey RD. Strategic management and organizational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002 </ref>		A good project manager is familiar with different project life cycle models and knows where and when to use which project life cycle, whether it is a predictive or an adaptive lifecycle. To understand where and when the waterfall model potentially works best. An adapted version of Stacey's matrix from Domain I: Agile Principles and Mindset by Sumanta Boral<ref name= "Agile Principles"> Boral, S. (2016). Domain I: Agile Principles and Mindset. In: Ace the PMI-ACP® exam. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2526-4_1</ref> is used. The Stacey Matrix was published and developed by Ralph Douglas Stacey. It is developed to give an understanding of which factors there contribute to the complexity and how to address the different degrees of complexity and, with that knowledge, choose the best-suited project life cycle. <ref name="strategic management"> Stacey RD. Strategic management and organizational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002 </ref>
	The Stacey matrix is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>		The Stacey matrix is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>

	~~[[File:TheStaceyMatrix.png\|thumb\|right\|500px\|Figure 1: Application of the Waterfall model<ref name= "Agile Principles"/>]]~~

S220123: /* Application of the Waterfall model */

2022-03-27T13:21:21Z

Application of the Waterfall model

← Older revision		Revision as of 13:21, 27 March 2022
Line 10:		Line 10:
	The Stacey matrix is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>		The Stacey matrix is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>

	[[File:TheStaceyMatrix.png\|thumb\|right\|~~300px~~\|Figure 1: Application of the Waterfall model<ref name= "Agile Principles"/>]]		[[File:TheStaceyMatrix.png\|thumb\|right\|500px\|Figure 1: Application of the Waterfall model<ref name= "Agile Principles"/>]]

S220123: /* Application of the Waterfall model */

2022-03-27T13:21:04Z

Application of the Waterfall model

← Older revision		Revision as of 13:21, 27 March 2022
Line 10:		Line 10:
	The Stacey matrix is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>		The Stacey matrix is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>

	[[File:TheStaceyMatrix.png\|thumb\|right\|~~600px~~\|Figure 1: Application of the Waterfall model<ref name= "Agile Principles"/>]]		[[File:TheStaceyMatrix.png\|thumb\|right\|300px\|Figure 1: Application of the Waterfall model<ref name= "Agile Principles"/>]]

S220123: /* Application of the Waterfall model */

2022-03-27T13:20:12Z

Application of the Waterfall model

← Older revision		Revision as of 13:20, 27 March 2022
Line 10:		Line 10:
	The Stacey matrix is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>		The Stacey matrix is a two-dimensional matrix where the uncertainty of the requirements is plotted against the perceived disagreement of the stakeholders. <ref name= "Agile Principles"/>

	[[File:~~WaterfallorAgile~~.png\|thumb\|right\|600px\|Figure 1: Application of the Waterfall model<ref name= "Agile Principles"/>]]		[[File:TheStaceyMatrix.png\|thumb\|right\|600px\|Figure 1: Application of the Waterfall model<ref name= "Agile Principles"/>]]

S220123: /* The waterfall model */

2022-03-27T13:17:15Z

The waterfall model

← Older revision		Revision as of 13:17, 27 March 2022
Line 24:		Line 24:
	The Waterfall model is placed in the bottom left corner in the zone called ''"simple,"'' as illustrated in the figure. The requirements are almost certain in this region, and there is a good consensus around the project. In this zone, the decision-making is based on reliable data gathered from the past to predict the future. <ref name= "Agile Principles"/>		The Waterfall model is placed in the bottom left corner in the zone called ''"simple,"'' as illustrated in the figure. The requirements are almost certain in this region, and there is a good consensus around the project. In this zone, the decision-making is based on reliable data gathered from the past to predict the future. <ref name= "Agile Principles"/>

	=The ~~waterfall model~~=		=The Waterfall Model=
	[[File:WaterfallModel.png\|thumb\|right\|600px\|Figure 2: Waterfall Model]]		[[File:WaterfallModel.png\|thumb\|right\|600px\|Figure 2: Waterfall Model]]
	The waterfall model is a stage-gate model, which is a category of life cycle models. A stage-gate model consists of multiple phases. Each phase includes one stage and one gate. The project has to pass a gate to get from one phase to another. A stage consists of a description of activities there need to be done during each state. The gate is the requirement and the review that determines whether a project can continue. The phases must be processed in order, without overlapping, and within a specified timeframe. In the waterfall model, it is not possible to move back and forth between phases. Once a phase is completed, it will freeze, and therefore it is not possible to move back and work on it again. The waterfall model consists of 6 phases, 1) Requirements Gathering and Analysis, 2) Systems Development, 3) Systems Implementation and Coding, 4) Testing, 5) Deployment, 6) Systems Operations and Maintenance. All six phases must be completed to achieve a positive outcome. <ref name="Best Practices"/>		The waterfall model is a stage-gate model, which is a category of life cycle models. A stage-gate model consists of multiple phases. Each phase includes one stage and one gate. The project has to pass a gate to get from one phase to another. A stage consists of a description of activities there need to be done during each state. The gate is the requirement and the review that determines whether a project can continue. The phases must be processed in order, without overlapping, and within a specified timeframe. In the waterfall model, it is not possible to move back and forth between phases. Once a phase is completed, it will freeze, and therefore it is not possible to move back and work on it again. The waterfall model consists of 6 phases, 1) Requirements Gathering and Analysis, 2) Systems Development, 3) Systems Implementation and Coding, 4) Testing, 5) Deployment, 6) Systems Operations and Maintenance. All six phases must be completed to achieve a positive outcome. <ref name="Best Practices"/>

S220123 at 13:13, 24 March 2022

2022-03-24T13:13:09Z

← Older revision		Revision as of 13:13, 24 March 2022
Line 2:		Line 2:
	This article is focusing on when and how the waterfall model should be used in a software development environment. The waterfall model is a Software Development Life Cycle model (SDLC) and was the first process model introduced. The waterfall model is easy to understand and use. It is a stage-gate model, which means that the model consists of stages and gates. Each phase consists of one stage and one gate. Each phase has some pre-determined activities and requirements. The current phase must be completed before the next phase can begin, and to end a phase, it must pass a gate. A stage is the activities, and the gate is the requirements and the review that determine whether a project can continue. The waterfall model consists of six different stages, 1) Requirements Gathering and Analysis, 2) Systems Development, 3) Systems Implementation and Coding, 4) Testing, 5) Deployment, 6) Systems Operations and Maintenance.		This article is focusing on when and how the waterfall model should be used in a software development environment. The waterfall model is a Software Development Life Cycle model (SDLC) and was the first process model introduced. The waterfall model is easy to understand and use. It is a stage-gate model, which means that the model consists of stages and gates. Each phase consists of one stage and one gate. Each phase has some pre-determined activities and requirements. The current phase must be completed before the next phase can begin, and to end a phase, it must pass a gate. A stage is the activities, and the gate is the requirements and the review that determine whether a project can continue. The waterfall model consists of six different stages, 1) Requirements Gathering and Analysis, 2) Systems Development, 3) Systems Implementation and Coding, 4) Testing, 5) Deployment, 6) Systems Operations and Maintenance.

	The waterfall model is widely used for software development, but it is also widely criticized. The model is often criticized for the late detection of defects in the process and how to handle change requests~~, among other things~~. It is most optimal to use the waterfall model for simple projects with precise requirements and projects that do not change through the development process.		The waterfall model is widely used for software development, but it is also widely criticized. The model is often criticized for the late detection of defects in the process and how to handle change requests. It is most optimal to use the waterfall model for simple projects with precise requirements and projects that do not change through the development process.
	==About==		==About==
	Winston W. Royce wrote the first description of the Waterfall model in 1970. Back then, he did not call it the Waterfall model. <ref name="Large-Scale"> Petersen, K. Wohlin, C. Baca, D. (2009) 'The Waterfall Model in Large-Scale Development', In: Bomarius, F. Oivo, M. Jaring, P. Abrahamsson, P. (eds) Product-Focused Software Process Improvement. PROFES 2009. Lecture Notes in Business Information Processing, vol 32. Springer, Berlin, Heidelberg. doi: https://doi-org.proxy.findit.cvt.dk/10.1007/978-3-642-02152-7_29 </ref> Later, it got the name because all the phases are done one by one and flow downwards like a waterfall. It is the finest and oldest known SDLC model. There are defined and designed various SDLC models such as V-Shaped model, Big Bang Model, Iterative model, etc. <ref name="Best Practices"> Kramer, M. (2018) 'Best Practices in Systems Development Lifecycle: An Analyses Based on the Waterfall Model', Review of Business & Finance Studies, v. 9 (1) p. 77-84, SSRN: https://ssrn.com/abstract=3131958</ref> These models are also called Software Development Process Models and are all ''”process consisting of a sequence of planned phases to develop or to amend the software products.”'' (Dubey, 2009)<ref> Dubey, A. Jain, A. Mantri, A. (2015) 'Comparative Study: Waterfall v/s Agile Model', International Journal of Engineering Sciences & Research Technology (IJESRT) </ref>		Winston W. Royce wrote the first description of the Waterfall model in 1970. Back then, he did not call it the Waterfall model. <ref name="Large-Scale"> Petersen, K. Wohlin, C. Baca, D. (2009) 'The Waterfall Model in Large-Scale Development', In: Bomarius, F. Oivo, M. Jaring, P. Abrahamsson, P. (eds) Product-Focused Software Process Improvement. PROFES 2009. Lecture Notes in Business Information Processing, vol 32. Springer, Berlin, Heidelberg. doi: https://doi-org.proxy.findit.cvt.dk/10.1007/978-3-642-02152-7_29 </ref> Later, it got the name because all the phases are done one by one and flow downwards like a waterfall. It is the finest and oldest known SDLC model. There are defined and designed various SDLC models such as V-Shaped model, Big Bang Model, Iterative model, etc. <ref name="Best Practices"> Kramer, M. (2018) 'Best Practices in Systems Development Lifecycle: An Analyses Based on the Waterfall Model', Review of Business & Finance Studies, v. 9 (1) p. 77-84, SSRN: https://ssrn.com/abstract=3131958</ref> These models are also called Software Development Process Models and are all ''”process consisting of a sequence of planned phases to develop or to amend the software products.”'' (Dubey, 2009)<ref> Dubey, A. Jain, A. Mantri, A. (2015) 'Comparative Study: Waterfall v/s Agile Model', International Journal of Engineering Sciences & Research Technology (IJESRT) </ref>