Trucking Billing Manifest (main)
From UG
(Difference between revisions)
(→Design And Implementation) |
(→Design And Implementation) |
||
| Line 26: | Line 26: | ||
</strike> | </strike> | ||
| - | '''After [[February IT restructuring]] I would like to change concept of [[User Guide]] and [[Developer Guide]]. Technical specification should be kept in [[Developer Guide]]. [[User Guide]] is to be created much later after component has been stabilized.''' | + | '''After [[February IT restructuring]] I would like to change concept of [[User Guide]] and [[Developer Guide]]. Technical specification should be kept in [[Developer Guide]]. [[User Guide]] is to be created much later after component has been "stabilized" (no changes expected) .''' |
=== User Guide === | === User Guide === | ||
Revision as of 21:44, 27 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.
After February IT restructuring I would like to change concept of User Guide and Developer Guide. Technical specification should be kept in Developer Guide. User Guide is to be created much later after component has been "stabilized" (no changes expected) .
User Guide
see Trucking Billing Manifest(User Guide)
Developer Guide
see Trucking Billing Manifest (Developer Guide)
