Trucking Billing Manifest (main)

From UG

Revision as of 21:44, 27 February 2010 (edit) Alex (Talk | contribs) (→Design And Implementation) ← Older edit		Revision as of 18:49, 9 March 2010 (edit) (undo) Montira (Talk | contribs) (→General Info and Scope) Newer edit →
Line 7:		Line 7:
	* Prerequisites:		* Prerequisites:
	* Related components:		* Related components:
		+	* old: [[Trucking_Billing_Manifest_(M)_(xls)_(OLD)]]
	== Analysis ==		== Analysis ==

---

Revision as of 18:49, 9 March 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: 1581
• Prerequisites:
• Related components:
• old: Trucking_Billing_Manifest_(M)_(xls)_(OLD)

Analysis

Business Requirements (BR)

see Trucking Billing Manifest (BR)

Change Requests (CR)

see Trucking Billing Manifest (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.

After February IT restructuring I would like to change concept of User Guide and Developer Guide. Technical specification should be kept in Developer Guide. User Guide is to be created much later after component has been "stabilized" (no changes expected) .

User Guide

see Trucking Billing Manifest(User Guide)

Developer Guide

see Trucking Billing Manifest (Developer Guide)

Quality Assurance Plan

see Trucking Billing Manifest (QA Plan)