A software development model in which phases—requirements definition, design, programming, and testing—are executed in strict sequence, with each phase completed before the next begins. It makes progress tracking straightforward, but defects discovered late carry a high cost in rework because earlier stages must be revisited.

Past questions testing this term · 1 questions

• 2015h27a #43ウォータフォールモデルで開発を行うプロジェクトにおいて、システム要件定義の不具合を後続の工程で発見した。不具合を発見した工程のうち、不具合の修正や修正に伴う手戻…