vijay Nov 19th, 2007 Poor requirements - if requirements are unclear, incomplete, too general, or not testable, there will be problems.Unrealistic schedule - if too much work is crammed in too little time, problems are inevitable.Inadequate testing - no one will know whether or not the program is any good until the customer complains or systems crash.Featuritis - requests to pile on new features after development is underway; extremely common.Miscommunication - if developers don't know what's needed or customer's have erroneous expectations, problems are guaranteed .
rhkvarma24.qa Profile Answers by rhkvarma24.qa Sep 23rd, 2008 If an application doesn't work properly after it is dispatched into the client environment then the application is said to be a failure.
srinivasulub1981 Profile Answers by srinivasulub1981 Questions by srinivasulub1981 Nov 28th, 2009 HI It may be due to the poor programming and poor testing.. CNU
What is a failure if a program doesn't work correctly?
Questions by surya singh