Addressbook (component)
From UG
(Difference between revisions)
(→History of Updates) |
|||
Line 19: | Line 19: | ||
* ''The purpose of this section is to give direction to System Analysts who will write detailed specification.'' | * ''The purpose of this section is to give direction to System Analysts who will write detailed specification.'' | ||
- | == | + | == Design == |
- | + | ||
- | + | ||
=== Address Profile Fields === | === Address Profile Fields === | ||
Line 49: | Line 47: | ||
==== Fax ==== | ==== Fax ==== | ||
- | == | + | == Version 2 == |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
== Figures == | == Figures == | ||
- | === Figure 1 | + | === Figure 1 === |
- | + | [[File:Addrbook v2.JPG]] | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | === | + | === Figure 2 === |
- | + | [[File:Addrbook v2 combined profile.JPG]] | |
- | + | ||
== History == | == History == | ||
Line 101: | Line 61: | ||
* [http://mantis.jaguarfreight.com/mantis/view.php?id=901 (*ph1)(Admin AddrBook) Re-design: Address Profile should include all categories: Transportation, Vendors, Bill To] | * [http://mantis.jaguarfreight.com/mantis/view.php?id=901 (*ph1)(Admin AddrBook) Re-design: Address Profile should include all categories: Transportation, Vendors, Bill To] | ||
+ | * see [[#Version 2]] |
Revision as of 16:45, 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.