· Miscommunication or no communication – about the details of what an application should or shouldn't do.
· Programming errors – in some cases the programmers can make mistakes.
· Changing requirements – there are chances of the end-user not understanding the effects of changes, or may understand and request them anyway to redesign, rescheduling of engineers, effects of other projects, work already completed may have to be redone or thrown out.
· Time force - preparation of software projects is difficult at best, often requiring a lot of guesswork. When deadlines are given and the crisis comes, mistakes will be made.
good post
ReplyDeleteit was realy wonderful blog..!
ReplyDeletehey dude this is really very nice and also great helpful for me.please continue posted this type of another blog.and thanks for sharing information
ReplyDeleteTry out edition is a stabilizing stage, so during this edition, it is possible to make only bug solving, interpretation upgrade or design upgrade. For this reason, the Try out Version has significance for the venture.
ReplyDeleteSWIFT Interview questions on
ReplyDeletehttp://testwithus.blogspot.in/p/swift.html
For selenium solution visit
http://testwithus.blogspot.in/p/blog-page.html
For QTP interview questions
http://testwithus.blogspot.in/p/qtp-questions.html
www.searchyourpolicy.com