please masters , i need help or any link has descripes these things to me.

Let me first admit that I have an immense respect for the role of SME on a project. I totally respect their knowledge/contribution in drafting a solution to a business problem associated with their domains. However I just get into clueless state when I am expected to provide SME inputs when actually I am a BA. Be it Business BA or IT BA , both carry same passion to meet with the end to end solution. Yes, We have our own set of strengths/weaknesses. But we belong to same fraternity at the end of day. Being SME is altogether different thing. I feel that I do not carry that authority as a BA to dictate/guide on domain knowledge. I might do my research/analyse/suggest ; but I am not a SME.
We can plan to become a SME as our next career move if we want. But it is strictly a personal choice. I think floating across into different domains to get diverse exposure would suit my career goals better.
Michelle, you are right in guessing (:-)…)that I could be termed as IT BA as I evolved into this role but originally came from technical background.
Pushpak , You are correct that in many cases solutions are just ready and what you needs is customization from new client perspective. But I am not quite sure,how come a SME would be able to guide the system customizations considering all the Interfaces/aligned systems impacts/system architectures etc. It is not what they design daily. It is not what they read about on their weekends.
I totally Second CJ Allen on his/her views.
So ideally I would say that every role contributes to a project to make it successful. Hope we all can make significant contributions with our own strengths rather than having preference of one group over the another. Hope I am on right track 🙂
…It is interesting to discuss this… I appreciate diverse views…It helps me grow.

Regards.

Yes, as Pdt mentioned, in India most of the time (at least for most of the Medium and small projects) the BA role is dome by SME. The main reason from my experience for this is that normally the solution is already sold when the project is started like the customer has already decided which modules and what product it want to use and the work left is to map the business process with the system and implement. In-fact most of the BA work at least at the high level is done during the pre-sales time and the solution demo etc is also completed at that time.

As Michelle pointed out, knowledge, whether from previous experience or from other sources is helpful for BA and for some cases for IT analysis it may be essential also. For a pure business BA role perspective, I feel knowledge of best practices and experience in similar business process is really helpful,more where there is a need for re-engineering or designing of new business processes.