Freight Release (main)

From UG

Revision as of 00:51, 17 February 2010 (edit) Alex (Talk | contribs) (Created page with 'Category:Freight Release') ← Older edit		Revision as of 00:53, 17 February 2010 (edit) (undo) Alex (Talk | contribs) Newer edit →
Line 1:		Line 1:
	[[Category:Freight Release]]		[[Category:Freight Release]]
		+
		+	== General Info and Scope ==
		+
		+	* Classified As: [[component]]
		+	* Parent Mantis: [http://mantis.jaguarfreight.com/mantis/view.php?id=583 583]
		+	* Prerequisites:
		+	* Related components:
		+	* Old spec: [[Freight Release]]
		+
		+	== Analysis ==
		+
		+	=== Business Requirements (BR) ===
		+	see [[Freight Release (BR)]]
		+
		+	=== Change Requests (CR) ===
		+	see [[Freight Release (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 [[Freight Release (User Guide)]]
		+
		+	=== Developer Guide ===
		+
		+	see [[Freight Release (Developer Guide)]]
		+
		+	=== Quality Assurance Plan ===
		+
		+	see [[Freight Release (QA Plan)]]

---

Revision as of 00:53, 17 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

General Info and Scope

• Classified As: component
• Parent Mantis: 583
• Prerequisites:
• Related components:
• Old spec: Freight Release

Analysis

Business Requirements (BR)

see Freight Release (BR)

Change Requests (CR)

see Freight Release (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 Freight Release (User Guide)

Developer Guide

see Freight Release (Developer Guide)

Quality Assurance Plan

see Freight Release (QA Plan)