Our experiences with Workflow over the next period of time have the potential to significantly change our thinking about workflow. We should consider what impact this change in audience suggests for our documents. One possible product of the team would be the tools for understanding the different types of workflow and placing a one's application within the appropriate category. This led to a discussion of the team doing more than just functional requirements for workflow. A decision process to use in considering Workflow purchase or design decisions.
Similar questions exist about APIs.
Following this round table, the team generated ideas about specific tasks and grouped those tasks against the items above. In the discussion which ensued the team decided that it was important to share the knowledge we've already developed, but that there was definitely more work to be done. A list of issues needing further inquiry Additional information. This statement of direction would have a relatively short life span with review in 3-6 months. The list of major campus systems and projects which will constrain workflow options Case studies of campus systems and their workflow elements Developing the list of difficult questions for vendors More detailed examination of product specifics.