Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  General  Documenting Process flow for existing system
Previous Previous
 
Next Next
New Post 3/1/2011 7:20 AM
User is offline srikanth
33 posts
9th Level Poster


Documenting Process flow for existing system 

Hi All,

There is a eprocurement system that exists in our company and there has been problems with that system and the support team was given training to resolve the problems. The training was a failure because they don't understand the workflow. Now, I have been tasked to document process flow or work flow for the existing eprocurement system. Can you please guide me how to start this. Buy reading the user guide I get an idea how to use but doesn't give any idea of process flow.

Please post comments.

Regards,

Srikanth

 

 

 
New Post 3/1/2011 7:55 PM
User is offline KJ
243 posts
6th Level Poster


Re: Documenting Process flow for existing system 

 

In the ‘old’ DFD days, you’d ignore the design features and create the “essential” process, defining what needs to be done, rather than how its done. Because you working with an existing system its “hard” to extricate yourself from how the system does things; and therein is your challenge!
 
So for procurement you’d start with the “essential” processes: (borrowed the following from (scm.ncsu.edu)
1.                  Identify or anticipate material or service needs.
2.                  Evaluate potential suppliers.
3.                  Select suppliers.
4.                  Release and receive purchase requirements.
5.                  Continuously measure and manage supplier performance.
 
You’d flowchart steps 1-5 (high-level); then you’d work on each step providing more detail. For example, step1, you’d identify what is needed to identify “service needs” etc. You'd match the SCM site's processes to suit yours (provide the appropriate acknowledgements) .Note the diagrams at http://scm.ncsu.edu/public/procurement/index.html.
 
Once there’s understanding of these “essential” processes; then you apply your systems Functions/Screens to each of the processes.
 
Warm regards,
Keith
Ps. I have no association with scm.ncsu.edu
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  General  Documenting Process flow for existing system

Community Blog - Latest Posts

As Business Analysts in Agile teams, we often hear about Definition of Ready (DOR) and Definition of Done (DOD). But beyond the buzzwords, these two concepts are powerful tools to drive clarity, consistency, and quality in our work. Definition of Ready ensures a user story is truly ready for development. It answers: Is this story clear, feasible...
In today's fast-paced digital world, successful projects aren't just built on great code—they're built on clarity. And that clarity often comes from one key player: the Business Analyst. At the heart of every great product or system is a need—a business goal, a customer pain point, or a regulatory requirement. But busines...
I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...

 






 

Copyright 2006-2025 by Modern Analyst Media LLC