Use Cases for EDI to TMS
From UG
(Difference between revisions)
(→Business story) |
|||
| Line 2: | Line 2: | ||
== Business story == | == Business story == | ||
| + | |||
| + | This needs to reflect typical and some exceptional workflows | ||
| + | |||
| + | * 3 CTs get approved | ||
| + | * CT2 sends data to TMS | ||
| + | * Jag oper discovers new approved CTs (how?) | ||
| + | * a) Jag oper manually processes CT | ||
| + | * updates | ||
| + | * docs | ||
| + | * etc | ||
| + | * b) Jag oper uses optimization to handle CT | ||
| + | * updates | ||
| + | * docs | ||
| + | * etc | ||
== Use Cases == | == Use Cases == | ||
== Use case. == | == Use case. == | ||
Revision as of 00:16, 17 July 2010
Business story
This needs to reflect typical and some exceptional workflows
- 3 CTs get approved
- CT2 sends data to TMS
- Jag oper discovers new approved CTs (how?)
- a) Jag oper manually processes CT
- updates
- docs
- etc
- b) Jag oper uses optimization to handle CT
- updates
- docs
- etc
