Case Study: Personnel

 [R_a] 

• What problems can occur calling address fields "Suburb", "City" ?
  • Not all addresses have Suburb, City. People live in towns, have rural codes for addresses or use PO Box numbers.
  • This causes confusion for a data entry operator as to where to enter the data.
• What problems can occur if the addresses are called Address1, Address2, Address3 ?
  • The data entry operator may enter the town/city in either Address2 or Address3 creating problems when searching for people who live in a particular Town/City.
• Why is phone number not usually entered in as a number ?
  • phone numbers are not used in calculations (normally), and often inclde alphanumeric character
    eg. (09) 123-456, 123-444 ex 123 or word numbers may be given 0800 ringme

• Why would weekly pay NOT be included in the database table ?
  • It is a calculated field made up of HourlyRate times the HrsPerWeek.
• Why problems could a field called "Hrs/Week" cause?
  • The "/" could be interpreted as a division sign.
• Some people only have one name. Should this be put in the FirstName or LastName field ?
  • From experience this is really a first name. Make sure your reports handle this problem. One solution that really annoyed the person was to place the name in both fields! (This was because the database required data in both fields!).