I want to create a waterfall model.
What do I need to do for that?
What type of document are required for that?
+3
A:
Your question isn't entirely clear, but I am guessing that you want to create a waterfall model of a software project. You are probably picturing a Gannt chart in your head. You can use Microsoft Project to do such a thing.
I don't know of any open source/freeware packages that are equivalent.
Adam Crossland
2010-05-20 19:14:21
i am project manager. and i want to craete document or follow some sdlc then what i need to do?
AjmeraInfo
2010-05-20 19:17:17
@AjmeraInfo: For managing software projects, the Waterfall model is held in extremely low regard almost universally. There are alternatives that are more modern and will give you a much better chance of running a successful project. Look into Agile software development and SCRUM.
Adam Crossland
2010-05-20 19:19:58
@AjmeraInfo: Kanban also gives you the ability to define and document processes and workflow without the pathologies of waterfall. You can graft it on top of almost any methodology - even waterfall - and use it to incrementally improve your process.
2010-05-20 19:28:16
@Adam Crossland, there are plenty of large organizations that successfully use Waterfall, it is not universally held in low regard. Agile doesn't work well for some complex projects.
HLGEM
2010-07-27 14:35:16
+3
A:
Watefall is an approach to build a software. It tells you the steps you need to follow. Like you follow certain steps in certain sequence for writing a program which takes input from user and saves that input into a file.
And you can get free document templates from here :
pokrate
2010-05-20 19:20:54
+2
A:
I'm quite puzzled as to why you'd want anything to do with the waterfall model. As far as I can tell, the waterfall model wasn't originally accepted by anybody as a good way to do things -- from day one, it was set up as a straw man to be knocked down by somebody with something they claimed as better.
The earliest reference to the waterfall model (of which I'm aware, anyway) was in a 1970 paper by a Dr. Winston Royce. His figure 2 shows what (again, as far as I know) is the first "waterfall diagram" ever. Then his figure 3 and 4 point out that the model doesn't work, and show modifications that (in his opinion) gave a better chance of success.
Since then, quite a few people have talked about the waterfall model, but usually in the same way: as a straw man to show how things can't work, and point out their own idea of a better way.
Jerry Coffin
2010-05-20 19:32:30
+2
A:
As Adam stated, it sounds like you're looking for a way to create project documentation. MS Project can create a gannt chart for you. You can also try this free/open source alternative (I haven't used it) http://www.ganttproject.biz/
Basically, your going to break a project into tasks and their dependencies and then schedule them based on estimates in an attempt to derive a realistic deployment date, i.e.
- Design database 40 hours
- Code web site 20 hours
- Deploy 2 hours
- Make Profit
All jokes aside, waterfall is a poor methodology for project estimation and planning. It's almost impossible to be accurate this way and most progressive shops have abandoned it. Look at Lean, Agile, Scrum, etc. - any of those will be better (and less painful).
Chuck
2010-05-20 19:34:12
+1
A:
The "waterfall" model was described by a guy named Winston Royce (although he didn't call it that) in a 1970 paper about designing large software systems. It should be noted that he introduced waterfall as an example of a non-functioning model, used as a talking point to discuss how NOT to do things. It was never intended to be taken as a useful software development model due to its extreme inflexibility, and has mostly been used as a pejorative term ever since.
To learn more about the waterfall process, you should consult the source. Here is his article from 1970: http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfall.pdf
Gus Melo
2010-07-27 14:32:34