Dock Receipt (M) (main)

From UG

Revision as of 22:47, 11 February 2010 (edit) Alex (Talk | contribs) (Created page with 'Category:Dock Receipt (M)') ← Older edit		Current revision as of 23:04, 11 February 2010 (edit) (undo) Alex (Talk | contribs) (→General Info and Scope)
(One intermediate revision not shown)
Line 1:		Line 1:
	[[Category:Dock Receipt (M)]]		[[Category:Dock Receipt (M)]]
		+
		+	== General Info and Scope ==
		+
		+	* Classified As: [[component]]
		+	* Parent Mantis: [http://mantis.jaguarfreight.com/mantis/view.php?id=975 975]
		+	* Prerequisites:
		+	* Related components:
		+	* Old spec: [[Dock Receipt (M)]] (just a draft, before [[BR]] stage)
		+
		+	== Analysis ==
		+
		+	=== Business Requirements (BR) ===
		+	see [[Dock Receipt (M) (BR)]]
		+
		+	=== Change Requests (CR) ===
		+	see [[Dock Receipt (M) (CR)]]
		+
		+
		+	== 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 most information presented in [[#User Guide]] should not be repeated again in [[#Developer Guide]].''
		+	* ''Do not overwhelm user with details in User Guide. Delegate details into Developer Guide.''
		+
		+	=== User Guide ===
		+
		+	see [[Dock Receipt (M) (User Guide)]]
		+
		+	=== Developer Guide ===
		+
		+	see [[Dock Receipt (M) (Developer Guide)]]
		+
		+	=== Quality Assurance Plan ===
		+
		+	see [[Dock Receipt (M) (QA Plan)]]

---

Current revision as of 23:04, 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 Quality Assurance Plan

[edit] General Info and Scope

• Classified As: component
• Parent Mantis: 975
• Prerequisites:
• Related components:
• Old spec: Dock Receipt (M) (just a draft, before BR stage)

[edit] Analysis

[edit] Business Requirements (BR)

see Dock Receipt (M) (BR)

[edit] Change Requests (CR)

see Dock Receipt (M) (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 most information presented in #User Guide should not be repeated again in #Developer Guide.
• Do not overwhelm user with details in User Guide. Delegate details into Developer Guide.

[edit] User Guide

see Dock Receipt (M) (User Guide)

[edit] Developer Guide

see Dock Receipt (M) (Developer Guide)

[edit] Quality Assurance Plan

see Dock Receipt (M) (QA Plan)