Addressbook (component)

From UG

Contents 1 General Info and Scope 1.1 Scope 2 Business Requirements 3 Notes from Systems Architect 4 Design 4.1 Address Profile Fields 4.1.1 Company City 4.1.2 Remark 4.1.3 Address 1 4.1.4 Address 2 4.1.5 Address 3 4.1.6 City 4.1.7 Zip 4.1.8 Country 4.1.9 State 4.1.10 Contact Person 4.1.11 Tel 4.1.12 Fax 5 Version 2 5.1 Filter by category 6 Figures 6.1 Figure 1 6.2 Figure 2 7 History 7.1 m901

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.

See #Figure1 and #Figure2.

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

Figures

Figure 1

Figure 2

History

m901

• (*ph1)(Admin AddrBook) Re-design: Address Profile should include all categories: Transportation, Vendors, Bill To
• see #Version 2