|GDB Topic||Dated: Feb 08, 16|
GDB topic has been announced for CS504. You can prepare your reply meanwhile and post on GDB from 19th February to 22nd February.
Software Verification and validation are the processes in which we check a product against its specifications and the expectations of the users who will be using it.
It is possible that software is verified but not validated because during the requirements engineering phase, user needs might not have been captured precisely or the analyst might have missed a major stakeholder in the analysis.
Now, let’s suppose during requirement engineering phase, users requirements are captured precisely and comprehensively. Do you think there is a need of validation? Is it a wastage of resources if we perform validation in said scenario? Justify your answer with very solid reasons (3-5) in either case.
Best of Luck
The validation at that point would consist of going back and making sure that change the specifications are met. To change the specifications, if users rerquirements are fully met by the implemented product. Always validate requirements with clients requirements, if your project deviates from clients requirements the client will sure you for delievering a useless project. You may have the same requirements in writing but your understanding of what they mean could be off. Clients also don’t understanding fully what they want you need to pretty much interrogate them on everything . if a client just want to give you a project and disapear for 6 monthes drop the project. It is not worth the headache, you will need constant communicate with the client. Yes validation is necessary because, it is the proof that the requirements are all met sufficiently.
here is the right solution
ek Allah ky bandy ny dea