User Tools

Site Tools


middleware:devel:ed:person-manage

Person Management Bean

Author Daniel Fisher
Date 2005/04/19

Requirements

Problem Statements

  • There exists no programmatic method to create people in the registry, modify attributes about them in a controlled manner, or expire them.
  • There exists no programmatic method to suppress a person's LDAP attributes.

Functional Requirements

  1. Ability to create a person record in the registry with the following information:
    • First and last name – given by user
    • Social Security Number, must be unique – given by user
    • List of affiliations – given by user
    • Date of birth – given by user
    • Creation date – set to current system date
    • Deceased flag – set to 0
  2. Ability to modify any of the following pieces of data about an existing person, reasonable format checking should be applied to fields where applicable:
    • Name; first, middle (if the person has one), last, suffix, and prefix
    • Social Security Number
    • Affiliations
    • Date of birth
    • Addresses
    • Phone numbers
    • Preferred name
    • Deceased flag
  3. Ability to suppress any LDAP attribute in a person's record

Nonfunctional Requirements

  1. Must be implemented as a clustered stateless session bean.
  2. All methods must accept UIDs as input, not UUPIDs.

Name Requirements

A well-formed name must meet the following requirements:

  • last name cannot be null
  • first and middle names can be null, but if they exist must meet requirements
  • must start with an alphabetical character
  • can contain only alphabetical characters, spaces( ), apostrophes('), dashes(-), and dots(.)

SSN Requirements

A well-formed SSN must meet the following requirements:

  • must be exactly 9 digits long

Phone Number Requirements

A well-formed phone number must meet the following requirements:

  • must be exactly 10 digits long

Comments

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