dsfasadf

profileebo
3-A.docx

There is a great job in businesses.  It is called a Business Systems Analyst.  What they basically do is receive from an internal client a request for a technology based solution to a business need.  This is normally prepared jointly with the customer on exactly how they want their processes to do to improve their operations.  Then the analyst does a process flow chart of what is being done now.  Reviews again with the customer and makes the changes to the "new process flow chart". 

Then comes the fun part.  How does the current process work with IT?  What changes have to be made within the IT world to support the new process flow chart.  It involves looking at the human/systems interface at every single step of both the old process and the new process.  Once that is done, it is back to IT to determine what specifically has to be changed.  A systems analyst gets to pickup the ball to prepare how the software, for sure, and maybe the hardware has to change. 

Lots of back and forth during this stage.  The easy ones are when there is no current IT support for the old process.  IT folks just love new stuff.  If IT was involved in the old process, then it becomes a lot more difficult to turn stuff off the old stuff and turn new stuff on.

So the question to all of you, have you ever been involved in changes to the work flow in your organization and how was IT

involved?

A student in a previous semester liked biology.  She came up with what came 1st.

It was the egg.  Reptiles, which pre-dated the chicken, their off springs were hatched from eggs.

.