Addressbook (component)
From UG
(Difference between revisions)
(→Version 2) |
(→Version 2) |
||
Line 69: | Line 69: | ||
* V4 | * V4 | ||
* ... all V- cats | * ... all V- cats | ||
+ | |||
+ | === Data Migration === | ||
+ | |||
+ | All existing data must be of course migrated into this new format. | ||
== Figures == | == Figures == |
Revision as of 16:53, 1 April 2010
Contents |
General Info and Scope
- Classified As: (small) (large) component / common feature / misc
- Parent Mantis: tbd
- Prerequisites: any articles that must be read before to understand this?
Scope
- List what it covers and what it does not
Business Requirements
- This section is defined by Business Analyst
- In this section this component/feature is defined from the business standpoint. All important points are listed. It could include some design details if business insists on specific design.
Notes from Systems Architect
- This section is defined by Systems Architect. It is written after #Business Requirements are defined.
- The purpose of this section is to give direction to System Analysts who will write detailed specification.
Design
Address Profile Fields
Company City
Remark
Address 1
Address 2
Address 3
City
Zip
Country
State
Contact Person
Tel
Fax
Version 2
In this version any address may be classified under any Transportation or Vendor or Bill To category.
3 top category tabs are merged into one.
Filter by category
Contains:
- [Any]
- [Transportation]
- [Vendors]
- [Bill To]
- T1
- T2
- ... all T- cats
- V3
- V4
- ... all V- cats
Data Migration
All existing data must be of course migrated into this new format.