User Tools

Site Tools


middleware:devel:ed:address-manage

Address Management Bean

Author David Hawes
Date 2008/09/02

Requirements

Problem Statements

  • There exists no programmatic method to manage addresses and phone numbers in the Registry.

Functional Requirements

  1. Ability to create addresses in the Registry for specific people
    • Mail stop must be valid per the regular expression:
      [\\p{Digit}]{4}
    • State prov code must exist in the Registry
    • Country code must exist in the Registry
    • A person can only have one local address, one office address, and one home address
    • If the address is unlisted, add a corresponding suppressed attribute
  2. Ability to modify specific addresses in the Registry
    • Mail stop, state prov codes, and country codes must be valid
    • Add, remove suppressed attributes as appropriate
  3. Ability to remove specific addresses from the Registry
    • Associated phone numbers will be removed
    • Suppressed attributes will be removed
  4. Ability to create phone numbers in the Registry
    • Phone numbers must be valid per the regular expression:
      [\\p{Digit}]{10}
    • If the phone number is unlisted, add a corresponding suppressed attribute
    • For each type of address, a phone number can be of that type, or one of the following: mobile, pager, fax
  5. Ability to modify phone numbers in the Registry
    • Phone number must be valid
    • Add, remove suppressed attributes as appropriate
  6. Ability to remove phone numbers from the Registry
    • Suppressed attributes will be removed
  7. Ability to return a List of StateProv objects from the Registry
  8. Ability to return a List of Country objects from the Registry

Nonfunctional Requirements

  1. Must be implemented as a clustered stateless session bean.
  2. Methods that modify the Registry must be sure to replicate the person whose information was updated.

Comments

middleware/devel/ed/address-manage.txt · Last modified: 2015/06/01 12:02 (external edit)