The old Waterfall Model versus Man-Month

Posted on jueves, mayo 06, 2010 by Pedro Wave

Software development is the act or art of working to produce or create software. The main purpose is to meet some needs of potential users.

Software development is also the process of writing and maintaining source code including research, design, implementation, modification, re-engineering, verification, maintenance, software documentation, etc.

As I come from industrial engineering, when I started working at software engineering I liked the waterfall development model that had its roots in manufacturing and construction industries, in which subsequent changes were costly, so that the processes previous design had to be very precise and error free.

First phases in the software development process involve departments as marketing, engineering, R&D and general management but normaly they are not involved sufficiently in the requirements specification early in the process of project development, so that the needs of customers or end-users are not well-defined by the first time.

The waterfall model is easy to understand because it is a sequential model, but requires that development processes are rigorous as in the case of the building architecture and this doesn't usually happen in software architecture.

For this reason you can not pass from one process to another as in a waterfall, unable to turn back because the software application programs tend to be adapted throughout all their life cycle to satisfy the user needs, involving the customer as much as possible, and should be easy to modify as a smart building.

The book The Mythical Man-Month shows us the software engineering problems, spelling out the difficulties of software development, principally:
1) Adding manpower to a late software project makes it later (man-month increases!)
2) After users use our software application, when they know what want.

As there is always a deadline and changes are finite, otherwise the development can not be completed, and there arises the need for software releases life cycle.

A good software code is constantly changing to make sure we end up with the simplest, and best possible application that reflects the current needs of the user.

To my project of knowing how to make a Perpetual Calendar, I won't add man-months more than mine for not making it a perpetual development.

Thanks for your attention.
Traducción al español aquí.

4 Response to "The old Waterfall Model versus Man-Month"

Pedro Wave Says....

@Matthew.. I'm glad you like my post.
You can follow me with Google Friend Connect at your right.

Only one notice, opening your main website page with Chrome navigator give me an advise, that it contains site, which appears to host malware and can harm my computer.

Could you test it?

Casey Evans Asante Says....

Sorry to post on your blog. But I need help. Your blog looks great! How did you get the feature content slider on the front page to work to work?

The codes just stack under the first for me.
What was the code you use?

Email me:

Thanks, and keep on blogging.

Pedro Wave Says....

Casey, thanks for your kind words.

To resolve your problem, read the original blog about Chucky template installation here:
4) Using Featured Content
Just add the showed code and modify in that way to make it work.

I hope that help you. Good luck!

Leave A Reply

Dime si te gusta lo que lees y, si no te gusta, dime por qué. Tengo habilitada la moderación de comentarios. Tu comentario se publicará pronto.

Tell me if you like what you read here and if you don't like, tell me why. I've enabled comment moderation. Your comment will be published ASAP.

Mi Lista de Blogs- My Blog List