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 does a Buisness Analyst do? From:Win Day <winday -at- home -dot- com> To:"Anthony Markatos" <tonymar -at- hotmail -dot- com> Date:Wed, 12 Jan 2000 07:50:10 -0500
At 02:22 PM 1/11/00 -0800, Anthony Markatos wrote:
>Question to all listserv members:
>What does a Business Analyst (BA) REALLY do? I am considering a position
>I have read a lot of internet job ads for Business Analysts. Many say that
>the primary thing that BA's do is "Develop function models and functional
>requirements specifications." However, I have been in software for almost
>fifteenth years and have never seen anyone - including individuals with a BA
>title - create a data flow diagram (the most common formal functional
>model/specification tool). So I am mystified as to what BA's do.
I sure hope you're kidding about not seeing any data flow diagrams!
I spent yesterday afternoon with a couple of engineers creating flow
diagrams for manufacturing processes. I'm writing the FDA submission for a
medical device that has a lot of subcomponents, and this was the easiest
way for them to explain to me how they make all the widgets.
Today I'm off to head office. We'll repeat the exercise with the software
and chemistry kit people. When we're done, we'll create an overall flow
diagram of the whole shebang.
In all my years as an engineer and then a technical writer, I can't
remember ever NOT creating flow diagrams of the processes I was working on.
We'd start with overall block diagrams, and move to successively more
detailed drawings as the project progressed.