Field Definitions and Naming Conventions: Selecting Proper Field Names Is Very Important

You might also like

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 5

Field

Definitions and Naming Conventions

Selecting proper field names is very important.

Names must be as descriptive as possible within restrictions.

Naming must reflect designers documentation

needs and users reporting and processing requirements.

Data

Redundancy:

Uncontrolled data redundancy sets the stage for

Data Inconsistency (lack of data integrity) Data anomalies Modification anomalies

Insertion anomalies
Deletion anomalies

Data

consistency Controlled redundancy Program-Data Independence Integrity enforcement Concurrency control Backup and recovery Security and Privacy Multiple views of data

CUSTOMERS Name Smith Shiver Shiver Hughes Hughes


Street Maple North North Sidehill Sidehill

City Queens Bronx Bronx Brooklyn Brooklyn

Number 900 556 647 801 647

Balance 55 100000 896 9867 203

1. What if savings and checking account records are managed in separate files? 2. How does one retrieve customers living within 78733 zip code? 3. First of all how do we include zip code in the database? 4. What happens if two customers withdraw funds from an account at the same time 5. Why should payroll personnel have access to customer accounts? 6. How do we make sure that the balance in checking accounts never goes below $25? 7. What if the system goes down while you are depositing into your account? 8. Customer is always interested in his/her own account, manager is always interested in the total assets, ....

You might also like