File Upload (main)

From UG

Revision as of 22:11, 5 February 2010 (edit) Alex (Talk | contribs) ← Older edit		Current revision as of 18:27, 11 February 2010 (edit) (undo) Alex (Talk | contribs)
(6 intermediate revisions not shown)
Line 7:		Line 7:
	* Prerequisites: n/a		* Prerequisites: n/a
-	=== Scope ===
-	* ''List what it covers and what it does not''
-	== Business Requirements ==	+	== Analysis ==
-	see [[File Upload (BR)]]	+
-	== Systems Design ==	+	=== Business Requirements (BR) ===
		+	see [[File Upload (Business Requirements)]]
-	see [[File Upload sdd]]	+	=== Change Requests (CR) ===
		+	see [[File Upload (Change Requests)]]
-	== QA ==	+	== Design And Implementation ==
-	see [[File Upload qa]]	+	*  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 [[File Upload (User Guide)]]
-	== Look and Feel ==	+	=== Developer Guide ===
-	see [[File Upload lf]]	+
-	== Link to User Guide ==	+	see [[File Upload (Developer Guide)]]
-	see [[File Upload ug]]	+	=== Test Plan ===
-	== Changes ==	+	see [[Query (Test Plan)]]
-		+
-	see [[File Upload chg]]	+

---

Current revision as of 18:27, 11 February 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: 814
• Prerequisites: n/a

[edit] Analysis

[edit] Business Requirements (BR)

see File Upload (Business Requirements)

[edit] Change Requests (CR)

see File Upload (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 File Upload (User Guide)

[edit] Developer Guide

see File Upload (Developer Guide)

[edit] Test Plan

see Query (Test Plan)