Human Factors of XR: Using Human Factors to Design XR Systems
Workflow systems
1. Myths, Truths and Wishful Thinking Workflow Systems Brandon Satrom devLink2010 http://speakerrate.com/talks/4108
2. About Me Technology Evangelist @ Microsoft Software and Enterprise Architect Based in Austin, TX Husband and Father
3. Why are you here? What is "workflow"? What makes a “Workflow System” different? What kind of problem is workflow designed to solve? Can workflow problems only be solved by tools? Are workflows always visual? How do I design a “workflow system”?
17. A workflow is a depiction of a sequence of operations, declared as work of a person, a group of persons, an organization of staff, or one or more simple or complex mechanisms. Workflow may be seen as any abstraction of real work, segregated in workshare, work split or other types of ordering. For control purposes, workflow may be a view on real work under a chosen aspect, thus serving as a virtual representation of actual work. The flow being described often refers to a document that is being transferred from one step to another. – from http://en.wikipedia.org/wiki/Workflow Workflow: The Cure for Insomnia Definition
36. When Adopting Workflow, Consider… Complexity of the problem Skill level of development staff Who keeps it running? Value of a visual representation
37. Any GOOD system will encourage good design… Declaratively define the FLOW Define discrete, separate ACTIVITIES Keep the RULES out of code
38. What is "workflow"? What makes a “Workflow System” different? What kind of problem is workflow designed to solve? Can workflow problems only be solved by tools? Are workflows always visual? How do I design a “workflow system”? Did We Answer These?
We associate workflow not with what it does, or it’s value but with tools that label themselves as “Workflow”Expensive BPM suitesWindows Workflow Foundation
“abstraction of real work” describes all software"coodination of work“ describes every system Which might be why so much can "sound like workflow" if you let it
These are the problems Workflow is trying to solve? The reason systems like this exist
When humans are key to the process, and time between steps cannot be measured, Workflow systems are needed.This is why CM/Document Approval processes are so often used around WF systems. Human involvement is key in the process.
"coordination of RESUMABLE work" Needs to allow the system to run for an indeterminate amount of time To be responsive and reactive, instead of proactive
…Though not necessarily visual. Even though visual is usually stated
"Coordination of (long-running) work" is more than a problem solved just by workflowBack to Ruby statemachine… does it fit?
“A well traveled fable claims the Cyclops made a deal with Hades in which they traded an eye for the ability to see the future. Upholding his end of the bargain, Hades removed an eye and allowed the cyclops to foretell the day of their death.”- http://en.wikipedia.org/wiki/CyclopsTell the story of the trouble devs had working with WF 3.5 workflows to make minor changes…
Show off WebMatrix and Silicon Bakery siteShow OrderProcessor WFFlowchartActivitiesShow Baker WFShow Code-only Baker WFShow Workflow Service
Quickly-changing aspects of the system Design workflows so that Activities change the most, flows themselves change the least The over-arching process should be stable Steps in that process change the most Or even rules within those steps Visualization => Flows (most stable) => Activities (changing) => Rules (most fluid)