Sales Contact Database Design

Paper Summary:

This paper explains that the purpose of this database is to provide a means by which sales-persons can track contact information about potential customers including the history for each customer contact. The author relates that this database will be relational, using the Oracle database and will be interfaced with other existing database systems, primarily the employee database. The paper states that the data consistency is maintained in this system by means of the system assignment of values, validation of entries and limitations on access. Charts and diagram.

Table of Contents
Database Overview
Business Requirements
Interfaces
Consistency and Validation
Screens and Reports
Tables
1. Customer
2. Customer History
3. Employee
4. Sales Territories
5. City
6. State
7. Phone Number
Entity Relationship Diagram

From the Paper:

"The main business requirement is to allow salespersons access to customer information. Salespersons need to be able to find the customer's phone number and address, but they will have only the authority to add to the Phone Number table, if the customer's number is not already in the table. They also need to be able to view and update the Customer History. Employees may add customers and phone numbers, but they may not delete them. They will not have update authority on sales territories. They also will have no authority to update the City or State tables, except to relate a Customer to City."

More papers on Sales Contact Database Design:

• Analytical Essay # 22805 : "Case Analysis: Barnes & Noble's Database Design and Implementation"
• Research Paper # 149739 : "Assessing Database Administration Today"
• Business Plan # 94485 : "Costco Solution Design"

APA Citation:

MLA Citation: