RFD Spec Template

From UG

---

Revision as of 22:13, 24 February 2010

Contents 1 General Info and Scope 2 Who is Who 3 Analysis 3.1 Business Requirements (BR) 4 Design And Implementation 4.1 Notes From Lead Systems Architect 4.2 User Guide 4.3 Developer Guide 4.4 Quality Assurance Plan 5 Change Requests (CR)

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)