Query (Main)
From UG
(Difference between revisions)
(→Design) |
|||
| (6 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | [[Category: | + | [[Category:XArc]] |
| Line 5: | Line 5: | ||
* Classified As: [[component]] | * Classified As: [[component]] | ||
| - | * Parent Mantis: [http://mantis.jaguarfreight.com/mantis/view.php?id= | + | * Parent Mantis: [http://mantis.jaguarfreight.com/mantis/view.php?id=688 688] |
* Prerequisites: n/a | * Prerequisites: n/a | ||
| + | * Related components: | ||
== Analysis == | == Analysis == | ||
| - | === Business Requirements === | + | === Business Requirements (BR) === |
| - | see [[ | + | see [[Query (Business Requirements)]] |
| - | === Change Requests === | + | === Change Requests (CR) === |
| - | see [[ | + | see [[Query (Change Requests)]] |
== Design And Implementation == | == 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 information presented in #User Guide could be clarified, elaborated adding more details but should not be repeated. | ||
| + | * Do not overwhelm user with details in User Guide. Delegate details into Developer Guide. | ||
=== User Guide === | === User Guide === | ||
| - | see [[ | + | see [[Query (User Guide)]] |
=== Developer Guide === | === Developer Guide === | ||
| - | see [[ | + | see [[Query (Developer Guide)]] |
=== Test Plan === | === Test Plan === | ||
| - | see [[ | + | see [[Query (Test Plan)]] |
Current revision as of 21:35, 18 December 2010
Contents |
[edit] General Info and Scope
[edit] Analysis
[edit] Business Requirements (BR)
see Query (Business Requirements)
[edit] Change Requests (CR)
[edit] 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 information presented in #User Guide could be clarified, elaborated adding more details but should not be repeated.
- Do not overwhelm user with details in User Guide. Delegate details into Developer Guide.
