Trucking Billing Manifest (main)
From UG
(Difference between revisions)
Alex (Talk | contribs)
(Created page with 'Category:Trucking Billing Manifest (M) (xls) == General Info and Scope == * Classified As: component * Parent Mantis: [http://mantis.jaguarfreight.com/mantis/view.php?i…')
Newer edit →
(Created page with 'Category:Trucking Billing Manifest (M) (xls) == General Info and Scope == * Classified As: component * Parent Mantis: [http://mantis.jaguarfreight.com/mantis/view.php?i…')
Newer edit →
Revision as of 02:25, 13 February 2010
Contents |
General Info and Scope
Analysis
Business Requirements (BR)
see Trucking Billing Manifest (BR)
Change Requests (CR)
see Trucking Billing Manifest (CR)
Design And Implementation
- It is suggested to define major functionality in #User Guide and additional / "technical details" in #Developer Guide.
- Dividing line between them is not exact. In general audience for #Developer Guide is more technical.
- Ideally most information presented in #User Guide should not be repeated again in #Developer Guide.
- Do not overwhelm user with details in User Guide. Delegate details into Developer Guide.
User Guide
see Trucking Billing Manifest(User Guide)
Developer Guide
see Trucking Billing Manifest (Developer Guide)