DO Ocean (main)
From UG
(Difference between revisions)
(→Design And Implementation) |
(→Design And Implementation) |
||
| Line 21: | Line 21: | ||
* ''It is suggested to define major functionality in [[#User Guide]] and additional / "technical details" in [[#Developer Guide]]. '' | * ''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 information presented in [[#User 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.'' | * ''Do not overwhelm user with details in User Guide. Delegate details into Developer Guide.'' | ||
Revision as of 02:41, 10 February 2010
Contents |
General Info and Scope
- Classified As: component
- Parent Mantis: 583
- Prerequisites:
- Related components:
- Old spec: Delivery Order Ocean
Analysis
Business Requirements (BR)
see DO Ocean (BR)
Change Requests (CR)
see DO Ocean (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
Developer Guide
see DO Ocean (Developer Guide)
