| || |
could you pl. help me out in below query, I was asked in an interview :
1.What are the things that we need to implement in the product which are not defined in the Requirements(which are not asked by client)
clue / Note : This question was asked during the discussion of Forward / Backward Traceability matrix.
Thanks for your Answers, similarly I have come up with the same question could you pl. help me out..
2) What are the situations where code needs to be changed without change of Business Requirement.
Thanks for your Answers, similarly I have come up with the Question 2) above, could you pl. help me out..
Last edited by testerboy1; 08-28-2013 at 01:07 AM.
Did you see/review any requirements documentation during the interview?
Requirements can come from internal stakeholders as well.
For example, say you're working on a back end server, and hardware is starting to become too expensive to keep purchasing faster and faster hard drives. You might have a new project to shard the back end server so it can run across multiple machines. This isn't asked for by the clients, but it creates requirements, project items, and deliverables that need to be managed as well.
The product can meet all of the requirements and still not be useful.
Maybe it does everything that it is supposed to, but it has extra objects or graphics that have nothing to do with the application.
Tags for this Thread