Understanding Work Flow Analysis For Projects
In my previous article, I have looked at some of the facts that you need to know about cost-benefit analysis for projects. In this article, I want to look at all that you need to know about workflow analysis for projects. Follow me as we are going to look at it together in this article.
Work Flow Analysis is a technique that formally documents the manner in which work gets done and displays that work in a flowchart. This type of analysis can be helpful in breaking down large or complex jobs into discrete tasks and decisions, but it requires that you already know how to do the work.
Sometimes, you may encounter situations where you have limited experience with the problem at hand. In these cases, you need help to precisely determine the functional requirements.
Once the discrete steps involved in getting a piece of work completed are identified, technology can be applied to improve efficiency.
Every day, people go to the bank to make deposits. Million of people automated the process of making deposits, which is a form of Electronic Fund Transfer. The automation of this business process means that those bright and sunny Saturday mornings no longer need to be spent at the bank.
in the same way, automating business process can free up time spent on tore activity so that more important issues can be addressed.
Also, increased efficiency that comes with business process automation is usually accomplished by automating redundant tasks within the workflow that require complex calculations. The most common task automated in our everyday working environment is information retrieval.
Use cases and prototype
Use cases, prototypes and scenarios are tools that are used to create or refine functional requirements by providing a prospective or point of interaction that did not previously exist. this newly created point of interaction allows for more detailed input to the design process
Some of the tools…
#1 Use case analysis
This is a method for designing information systems by breaking down requirements into user functions. Each use case is an event or sequence of actions performed by the user.
This is a simulated version of a new system, essential for clarifying information elements for the project.
A method for developing potential or likely eventualities for different situations.
Imagine for a moment that you have been told to mow a lawn and that although you have a vague understanding of the process, you have never done this before. A business Analyst, Samson, show up and questions you about how you will like to cut the grass. he performs a use case analysis by breaking down the larger task of cutting grass into a sequence of actions, such as start the mower, push over grass, stop the mower and empty the bag.
A day later an engineer shows up in your driveway with a prototype lawn-mower on a trailer. The engineer patiently spends about an hour explaining the power operation of the mower and answering any question that you have. Without really knowing what to expect, you start the mower and begin to cut the grass.
Hours later, you complete the task and the Business Analyst returns to ask you how the mowing went. You inform him that the mower too was bad, it stalled in thick grass and was very difficult to push.
The interaction with the prototype lawn-mower succeeded in providing concrete feedback that otherwise will not have been possible. Based on the feedback given, the analyst decides to perform further testing using other scenarios such as mowing is very thick grass, wet grass, and on uneven terrain.
I know you might agree with some of the points that I have raised in this article. You might not agree with some of the issues raised. Let me know your views about the topic discussed. We will appreciate it if you can drop your comment. Thanks in anticipation.
Become Part Of our Fan Base on Facebook. Click Here.
Follow Us on Twitter. Click Here.
Have a deeper understanding of Google Search Console. Join SEOPOZ for free