File Upload (main)

From UG

Revision as of 23:15, 5 February 2010 (edit) Alex (Talk | contribs) (→Link to User Guide) ← Older edit		Revision as of 18:13, 11 February 2010 (edit) (undo) Alex (Talk | contribs) Newer edit →
Line 34:		Line 34:
-	== Questions ==	+	== xxxxxxxxxxxxxxxxxxxxxxx ==
-	see [[File Upload q]]	+	== 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)]]

---

Revision as of 18:13, 11 February 2010

Contents 1 General Info and Scope 1.1 Scope 2 Business Requirements 3 Changes 4 Systems Design 5 QA 6 Look and Feel 7 Link to User Guide 8 xxxxxxxxxxxxxxxxxxxxxxx 9 Analysis 9.1 Business Requirements (BR) 9.2 Change Requests (CR) 10 Design And Implementation 10.1 User Guide 10.2 Developer Guide 10.3 Test Plan

General Info and Scope

• Classified As: component
• Parent Mantis: 814
• Prerequisites: n/a

Scope

• List what it covers and what it does not

Business Requirements

see File Upload (BR)

Changes

see File Upload chg

Systems Design

see File Upload sdd

QA

see File Upload qa

Look and Feel

see File Upload lf

Link to User Guide

see File Upload ug

xxxxxxxxxxxxxxxxxxxxxxx

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)