Query (Main)

From UG

Revision as of 22:14, 7 February 2010 (edit) Alex (Talk | contribs) (Created page with 'Category:Query') ← Older edit		Current revision as of 21:35, 18 December 2010 (edit) (undo) Alex (Talk | contribs)
(9 intermediate revisions not shown)
Line 1:		Line 1:
-	[[Category:Query]]	+	[[Category:XArc]]
		+
		+
		+	== General Info and Scope ==
		+
		+	* Classified As: [[component]]
		+	* Parent Mantis: [http://mantis.jaguarfreight.com/mantis/view.php?id=688 688]
		+	* Prerequisites: n/a
		+	* Related components:
		+
		+	== Analysis ==
		+
		+	=== Business Requirements (BR) ===
		+	see [[Query (Business Requirements)]]
		+
		+	=== Change Requests (CR) ===
		+	see [[Query (Change Requests)]]
		+
		+
		+	== 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 ===
		+
		+	see [[Query (User Guide)]]
		+
		+	=== Developer Guide ===
		+
		+	see [[Query (Developer Guide)]]
		+
		+	=== Test Plan ===
		+
		+	see [[Query (Test Plan)]]

---

Current revision as of 21:35, 18 December 2010

Contents 1 General Info and Scope 2 Analysis 2.1 Business Requirements (BR) 2.2 Change Requests (CR) 3 Design And Implementation 3.1 User Guide 3.2 Developer Guide 3.3 Test Plan

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