Talk:Waterfall model

message: the waterfall model exists on a timeline, it's not some random bunch of boxes in a drawing. i couldn't figure this out when i was first reading the article, thus, the article is quite worthless, because it fails to actually inform the reader of what the waterfall model actually means. this article doesn't look like it was written for encyclopedia. 5.184.25.166 (talk) 13:23, 17 October 2021 (UTC)
thread_title:  the article fails to explain most fundamental thing 

message: Waterfall model help to restraint required analysis and definitions on system and software development by implementing the specific units of testing and execution of operations and maintenance as itself shows to be cumbersome and liable to cause application delivery lag. 2405:201:C00F:60AF:251B:472B:6159:E14A (talk) 18:21, 19 December 2022 (UTC)
thread_title:  Waterfall project management 

message: Waterfall Model Description
Mannepallinaveen05@gmail.com 
The waterfall model
The waterfall model is a software development methodology that follows a linear, sequential approach. It is named after the way in which tasks flow, like a waterfall, from one phase to the next in a predetermined order. The waterfall model is also sometimes referred to as the "linear-sequential" model.
In the waterfall model, the development process is divided into distinct phases, each of which must be completed before moving on to the next. The phases of the waterfall model are:
1.Requirements gathering and analysis: In this phase, the project requirements are gathered and documented.
2. Design: In this phase, the system is designed based on the requirements gathered in the previous phase.
3.Implementation: In this phase, the code is written based on the design created in the previous phase.
4.Testing: In this phase, the system is tested to ensure it meets the requirements and functions correctly.
5.Deployment: In this phase, the system is deployed and made available for use.
6.Maintenance: In this phase, the system is maintained and any necessary updates or changes are made.
The waterfall model is a linear approach to software development and is well-suited to projects with well-defined requirements and a clear understanding of the problem to be solved. However, it can be inflexible and may not be the best choice for projects with rapidly changing or complex requirements 106.78.85.100 (talk) 11:25, 27 December 2022 (UTC)
replies: text: Ehm...where's that from? Twasonasummersmorn (talk) 23:27, 2 January 2023 (UTC)
thread_title:  The waterfall model 

message: The waterfall model is a breakdown of project activities into linear sequential phases, meaning they are passed down onto each other, where each phase depends on the deliverables of the previous one and corresponds to a specialization of tasks.[1] The approach is typical for certain areas of engineering design. In software development,[1] it tends to be among the less iterative and flexible approaches, as progress flows in largely one direction ("downwards" like a waterfall) through the phases of conception, initiation, analysis, design, construction, testing, deployment and maintenance.[2][better source needed] The waterfall model is the earliest SDLC approach that was used in software development.[citation needed]
The waterfall development model originated in the manufacturing and construction industries,[citation needed] where the highly structured physical environments meant that design changes became prohibitively expensive much sooner in the development process.[citation needed] When first adopted for software development, there were no recognized alternatives for knowledge-based creative work.[3][better source needed] 103.255.145.74 (talk) 14:15, 8 January 2023 (UTC)
thread_title:  The waterfall 

message: At the end of the Criticism section it says: "Rational Unified Process (RUP) phases acknowledge the programmatic need for milestones, for keeping a project on track, but encourage iterations (especially within Disciplines) within the Phases. RUP Phases are often referred to as waterfall-like" There is a citation needed next to this but I've used and read about RUP a lot and I have never heard it "referred to as waterfall-like". What the RUP books say is that you can use it in different ways. I.e., you can use it in an iterative manner (which is how it is mostly intended to be used) or you can use it in a waterfall manner. But that is not at all the same as saying the methodology is "Waterfall-like". I'm going to be bold and just delete that part. MadScientistX11 (talk) 19:52, 26 April 2023 (UTC)
thread_title:  Removing Sentences on RUP 

message: The ending of the Criticism section currently says: "While advocates of agile software development argue the waterfall model is an ineffective process for developing software, some sceptics suggest that the waterfall model is a false argument used purely to market alternative development methodologies" There are plenty of valid criticisms of Agile but the idea that Agile is just a marketing ploy is one I've never heard anyone seriously make. I went to check that reference and it goes to a dead link. Given that there is no actual source information anyway (there is an author but nothing like the name of the source cite, it looks like just a URL to the site: http://get.syr.edu/ which is no longer a site at all). The link is archived to Wayback but still goes to a dead link. Given that this looks to me like it isn't a valid source even if we could find it in the bowels of the web and that this is not what in my experience constitutes a serious argument (anymore than I would consider the same argument applied to Waterfall to be a serious argument) I'm going to delete that claim. MadScientistX11 (talk) 01:32, 2 May 2023 (UTC)
thread_title:  Another Questionable Claim in Criticism Section 

message: Having lived in engineering and consulting industry for 47 years.  Waterfall is a software industry only term.  Nobody outside of the software industry ever used it in the 20th century.  It's only used to describe "everything note agile is waterfall".  Which is obviously not true. 2601:286:C200:1E90:447B:B3AC:AEDD:EDD1 (talk) 22:15, 14 December 2023 (UTC)
replies: text: The article must be based on sources, you cannot make additions based on your personal opinions. That is called 'original research' here and is prohibited by a core policy, which you can read at WP:OR. Wikipedia's not a place for ediorializing. MrOllie (talk) 00:17, 15 December 2023 (UTC)
thread_title:  Waterfall was limited to the Software industry