Query (Main)

From UG

(Difference between revisions)
Jump to: navigation, search
(General Info and Scope)
 
(4 intermediate revisions not shown)
Line 1: Line 1:
-
[[Category:Query]]
+
[[Category:XArc]]
Line 11: Line 11:
== Analysis ==
== Analysis ==
-
=== Business Requirements ===
+
=== Business Requirements (BR) ===
-
see [[TBD]]
+
see [[Query (Business Requirements)]]
-
=== Change Requests ===
+
=== Change Requests (CR) ===
-
see [[TBD]]
+
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.
+
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 ===
Line 28: Line 30:
=== Developer Guide ===
=== Developer Guide ===
-
see [[TBD]]
+
see [[Query (Developer Guide)]]
=== Test Plan ===
=== Test Plan ===
-
see [[TBD]]
+
see [[Query (Test Plan)]]

Current revision as of 21:35, 18 December 2010


Contents

[edit] General Info and Scope

  • Classified As: component
  • Parent Mantis: 688
  • Prerequisites: n/a
  • Related components:

[edit] Analysis

[edit] Business Requirements (BR)

see Query (Business Requirements)

[edit] Change Requests (CR)

see Query (Change Requests)


[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.

[edit] User Guide

see Query (User Guide)

[edit] Developer Guide

see Query (Developer Guide)

[edit] Test Plan

see Query (Test Plan)

Personal tools