Business requirements analysis

For Black Box Testing you need to read & Analyze the requirement documents.

Let's get a few things straight here. Black box testing has nothing specifically to do with reading requirements or writing tests based on them. In fact, neither development nor black box testing need formal requirements to proceed. With that said, if you are using a development model that relies on requirements, and then yes, read them, and yes, use them to create your tests.

If you go Analyze the requirement documents you would get a clear picture of the Project & the Test Coverage would be good.

2. According to me, Master Test Plan should be written based on the Project Plan and it could be revised as and when needed.

Again, no test plans need to be written. In fact test plans, and written test cases do not have to write any formal testing documents. I have seen perfectly good "test suites" written on sticky notes or a white board.

As I have said many times before, don't waste time on documents that are not

demanded by your management, clients, or development model.

3. To determine whether a requirement is Testable or not is only by participating in the Requirement review / discussion meeting. The Reason is that after getting signoff from the Customer its not good to go back & say this requirement is not testable etc... Example: Scenario 1. Data for a Transactions should come from an external application like SAP / HL7 messaging etc. So, what we need to do is that create a Text file or XML file in that format and feed it as data for Transactions as we don't have SAP / HL7 messaging.