Workflow, Process and Use Cases: Setting the Record Straight |
||||||||||
|
|
Home > Articles > Workflow, Process and Use Cases: Setting the Record Straight February 29, 2000 I am hearing lots of talk about workflow methods, process modeling and use cases. Are they all referring to the same thing, or are they distinct concepts? Allow me to clarify this confusion. A workflow is a description of the work being done in an organization from a document flow perspective. For example, when an insurance claim is received, workflow refers to the journey of the claim through the insurance company that ultimately produces a check to pay the claim. There are numerous steps in that workflow. The physical claim will be received by mail, inspected by a claims officer, then a claims adjuster, then policy rules are checked to validate the claim and finally when all is okay, a check is issued and all the appropriate accounting is done. The workflow for this identifies all the actors in this scenario, their points of contact with the organization, the various forms required by the organization and the connectivity of the flow of the documents. There are many workflow tools that let you model the visual flow, the document capture and the sequence of steps. A process is slightly different. A process is an activity or function of the organization that brings value to the organization and mostly to the clients of the organization. Please login/register to read the entire article.
sponsored announcements and special offers
You can do this!
Earn your master's degree in project management without putting your life on hold at GoUWP.com! Apply today at GoUWP.com for 100% online courses, 45 PDUs each. No entrance exam. University of Wisconsin- Platteville’s MS in Project Management is globally accredited by PMI. Combine academics and real-world scenarios for a 360-degree education. If you have a distributed team, what are you trying to achieve with Agile approaches? Isn't Agile more for co-located teams? There are eight key benefits to working in a distributed Agile environment. A new report from ProjectsAtWork looks at each of those benefits – and how you can achieve them.
Most business and IT executives agree that any company able to rapidly deliver software of high and predictable quality with minimum budgets enjoys a significant advantage. However, practical experience shows that the challenges associated with software quality remain largely unsolved. Download the white paper Uplift Quality with Requirements Driven Testing to learn fundamental principles of Requirements Driven Testing.
|
| ||||||||
|
| ||||||||||