Requirement vs. QA / Tester

What is QA? What is Tester? I was being asked to deliver test cases, UAT and perform integration tests on the system. The reason is , I was the BA, a SA and so the best candidate to make sure the developed system maps the requirement being designed accordingly.

eehmmm ... i have been struggling of what's been said above. It does make sense theoritically. The best way to test the system is to identify the possible scenarios from the business process and test the situation with the system. Then i thought, what could possibly happen on the scope of work for a BA?

After each requirement workshop or session, I will start preparing for documents like business processes, requirement list, business rules and sometime scenarios and most of the time these information is being verified by the customer themselves and then this information will start to translate into the use case specs or functional specs (i don't like to work on functional specs and i always think the more appropriate person to work in should be the solution architect) but anyways, during the analysis and translation process, i thought, there should have a certain level of QA be inplaced, to check on standards, logic, etc and it should be not be done by the BA/SA alone, simple reason behind, when oneself is too into a certain work, they are tendencies of overlooking other aspect and also some important details that may be needed during the development cycle and therefore a QA is needed in here.

Not sure if it's a good or bad situation to bring in QA during documentatations, which ended up spending more time explaining the situation to the QA why certain work is being done accordingly and most of all the expectation is rather different when they start asking after this screen, where the cancel button will be leading to ? ...... The idea was, to let the QA check on the flow and i mean the business flow and how this is carry into the system, but so detail until how eash screen flow would be, if i would want to look into such details then i could be the solution architect and start designing each button, or link actions? .... hmmm is there a QA for business processes then ?

What about testers? the conflict starts during the interation testing. A lot of time, the tester or it could be the programmer himself doing testing in the development environement, test goes out well, when it comes into integration test, it always got haywired, so now the question comes back, who should do integration testing? the tester? the BAs? ...