Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Google is your friend, but on a slightly more helpful note, there are a whole heap of distinctions and IMO and experience one is definitely not interchangeable for the other.
In a very brief summary:
BA - document the business requirements, i.e. what business benefit(s) the user wants the project to deliver.
SA - document how the system will function and what functionality, rules, system resources etc. will be required to deliver the business benefits as described by the BA.
In reality what usually happens is a "BA" is asked to fulfil all of their role and part of the SA role, subsequently the developers are asked to fulfil the residual part of the SA's role.
Hmm, I think this IT malarky might be a bit too much for you Mike.. Having had a quick look at your previous posts, you need not have resorted to Google to answer your question, but rather, you could have simply looked at the responses to YOUR thread that you posted in general YESTERDAY
If Sockie 0/10, if genuine you really need to consider a career outside of contracting...
Comment