TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: What is a business analyst From:"Lowe, Karen" <karen -dot- lowe -at- cgi -dot- com> To:<kmurri -at- comcast -dot- net> Date:Thu, 24 Aug 2006 11:22:36 -0400
Karen Murri asked: What does a business analyst do that's different from what a tech writer does? How is it different from systems analyst?
KL - BA comes into the process way earlier than a tech writer. The BA identifies the problem that the customer has, knowing that there is a system solution but not saying what exactly it will be. That's what the system analyst does. So the BA will say that the customer needs an application that lets them do x in their y process, and x has to do a, b, c and it would be great if it could address problem d. The BA details the issues, the customer's process and limitations, and the business requirements in one or more documents. These could include diagrams and functional specifications, but the BA doesn't propose the technical solution(s). That's up to the system people. Also, the BA acts as a 'translator' between the business people (who will use the system) and the development team (who build the system), so that the system build meets the needs of the people who use it.
KM - How did those of you with that title get into that work?
KL - not sure, but I think it's usually through the back door!