information gathered previously to a system, the final product which is a

report of yearly sales, profits, etc. The first thing a Systems Analyst does is to

interview the company which wants the report, (called the user) to find out

what kind of report they want, format, etc. They must find whether the report

is feasible or not, and to find out, they do an analysis of the project. To

analyze the project, they must find out where are they going to get the

information, how, when is the project going to be done, etc. They then design

the system, which is to make a 'skeleton' of the project. They write

specifications, of what is to be in the final report. They do flowcharting,

specifications for the programmers of the report, and development control.

Development control is where the Systems Analyst works with the

programmers along a critical path. A critical path is like a due date, if the

program for bugs. This is similar to quality control. The Systems Analyst

the final report is finished and free of bugs, it is sent to the user. The Systems

Analyst has a big job to do, he/she is responsible for the design, the

report is to be done in thirty days, the Systems Analyst makes sure the report

development, and implementation of the report, ie: what purpose will it serve,

product, making all the specifications and charts for what is to be done. A

end of a project, and they must implement the system to good use. The

man hours it will take to finish, etc. A critical path flowchart also helps the

Some common words found in the essay are:
Systems Analyst, systems analyst, critical path, final report, thirty days systems, systems analyst helps, report thirty days, development control, etc systems analyst, control systems analyst, control systems, report thirty, analysis project, etc systems, thirty days, job he/she,
Approximate Word count = 1018
Approximate Pages = 4 (250 words per page double spaced)