One of my clients had approached me with a 1 line requirement that asked us to make inventory management software.Nowonder i refused the job considering the fact that projects with less requirements or vague requirements are always a risk to work on. When I spoke about this incident with one of my friends who have been a part of Software Industry for last few years, I realized that we all have been doing similar mistakes in this industry. I have been a part of a Startup and understand how important every client is at the infancy stage of a company. The problem here is that once clients come to us with requirements, we ask our developers to start working on the data base development from the word Go, which harms all of us at a later stage.Web Application, Software Application,Business Application Development or Database Application development require a similar approac how many calories to lose weight h and that is, every single screen should be well documented.I have seen companies not charging clients for requirement analysis and my suggestion is that at least 10 to 25% of the cost should be kept for requirement gathering.In fact if you realize that the cost of software developed would be more than you had expected re approach the client and explain him fairly on how the initial assessment went wrong.The whole process should be well defined in stages:Requirement GatheringScreen Designing Software application development goes wrong due to the fact that the next step is performed without assessing the initial step properly and believe me, you will be back to square one, if you don’t do the above two steps properly.Development The final sign off on the last step would mean taking the prototype to your developers and giving a data base designed and screens programmed.