A BA colleague said that if requirements have been wriiten in sufficient detail that requirements acceptance criteria is not required? As a Tester I find that writing acceptance criteria for each requirement adds value as it makes the user re-examine there requirements and help clarify them.
Software has been proposed to solve a business problem in my company. After investigating the existing process, I discovered that for the proposed commercial off-the-shelf software to work -- some additional work would have to be done to it. What I'm confused about is what specification I should...