Use Cases for EDI to TMS

From UG

Revision as of 00:16, 17 July 2010 (edit) Alex (Talk | contribs) (→Business story) ← Older edit		Revision as of 17:09, 21 July 2010 (edit) (undo) Denise (Talk | contribs) (→Use Cases) Newer edit →
Line 18:		Line 18:
	== Use Cases ==		== Use Cases ==
		+	== Use case 1. Shipper Creates CT via Web Portal ==
		+
		+	=== Normal Flow of Events ===
		+
		+	1) Shipper logs into the web portal to enter all new products that are ready to ship and Upon clicking save, they create 1 CT per line item
		+
		+	2) Planner logs into the web portal to view all new records created by shipper and sets an "Approval status" to "Approved"
		+
		+	3) Jaguar operator logs into CT2 internal application in the morning to find these "Approved" records
	== Use case. ==		== Use case. ==

---

Revision as of 17:09, 21 July 2010

Contents 1 Business story 2 Use Cases 3 Use case 1. Shipper Creates CT via Web Portal 3.1 Normal Flow of Events 4 Use case.

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 case 1. Shipper Creates CT via Web Portal

Normal Flow of Events

1) Shipper logs into the web portal to enter all new products that are ready to ship and Upon clicking save, they create 1 CT per line item

2) Planner logs into the web portal to view all new records created by shipper and sets an "Approval status" to "Approved"

3) Jaguar operator logs into CT2 internal application in the morning to find these "Approved" records

Use case.