Database Design and Implementation for Delphi Marketing

Information Requirements

As previously mentioned, Delphi have a permanent staff of over 40 people.   Every member of staff has a role (for example, account manager, campaign manager, graphic designer, etc), a salary grade and a corresponding charge-out rate at which clients are charged.  Staff names should also be recorded together with the telephone number, fax number and email.  There are members of staff with the same name therefore a staff number will also be required for identification purposes.

Clients and Campaigns

Each client company is asked to nominate two members of staff to act as contacts for each campaign.  The information requested is the person’s name, position, email address and telephone number.  Delphi allocate an account manager to each client no matter how many campaigns the client is involved in.  The account manager is responsible for maintaining contact with the client after campaigns have finished as part of the marketing activities for Delphi.

The Campaign Process

The initial stages of a campaign will involve a number of meetings with the client and the design of the campaign.  These processes will involve staff members who will be involved in the campaign.  The system needs to keep a record of all meetings held for a campaign.  The date, time and duration of each meeting should be recorded along its purpose and the internal staff attending.  Whilst specific details of the room used for the meeting are not required, a record of where the meeting was held is necessary.  Meetings will either be held at Delphi or at the client’s offices.  

Once a campaign starts, its first day is known as rollout day, the purchasing assistants are responsible for checking that the adverts do appear as planned – for each placement they check to see that the advert was presented in the place and on the dates expected.  A note is made of any placements that do not occur as planned.  

System Requirements

Delphi require a database to support their key activities in a campaign, this includes the recording of:

·Staff details and their involvement in campaigns

·Client details including contacts for particular campaigns

·Campaign details

·Meeting details

·Advert and placement details

Details of the contents of actual documentation produced during a campaign is part of the campaign documentation and is not regarded as relevant information for the database which is essentially concerned with recording the information necessary to track the progress of a campaign.

Conceptual Design Stage

Design a class diagram that will capture the data and links capable of supporting the requirements outlined above.  The figures provide some sample data to give you additional information on the kind of data you will need to store.   The model needs to capture the data requirements in order for the system to work.  You also need to develop a list of constraints and a list of assumptions.

Implementation Stage

This stage will be to implement your design, using Oracle.

·Convert your model into an SQL database.

·Populate your database with some sample data

·Test your database.  You will need to consider testing the database to ensure that the database meets the information requirements of the system.  You need to create and run SQL queries that produce the information required.  

The report will require the following chapters:

Chapter 1: Introduction – one page description of the aims and objectives of the report.

Chapter 2: The Class Diagram with constraints and assumptions.

Chapter 3: Implementation.  Provide a listing of the SQL table definitions.

Chapter  4: Six queries that demonstrate that your database meets the requirements of the system.

Chapter 5: Conclusion.  A critical evaluation of your final product and a review of the entire exercise.