RFD Spec Template

From UG

(Difference between revisions)
Jump to: navigation, search
Alex (Talk | contribs)
(Created page with 'Category:Spec Templates == General Info and Scope == * Classified As: component * Parent Mantis: [http://mantis.jaguarfreight.com/mantis/view.php?id=xx xx] * Prerequi…')
Newer edit →

Revision as of 22:13, 24 February 2010



Contents

General Info and Scope

  • Classified As: component
  • Parent Mantis: xx
  • Prerequisites:
  • Related components:


Who is Who

  • Requested by:
  • Module Owner:
  • Business Analyst:
  • Systems Analyst:
  • Developer:
  • QA:
  • Review Group:

Analysis

Business Requirements (BR)

xx (BR)

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.

Notes From Lead Systems Architect

None.

User Guide

see xx (User Guide)

Developer Guide

see xx (Developer Guide)

Quality Assurance Plan

see xx (QA Plan)

Change Requests (CR)

see xx (CR)

Personal tools