Skip to main content

CallAir case study - SQL queries, SQL reports, ERD

Your group is responsible for developing a database to support the fundamental data requirements of a customer call center for an established network service provider (includes landline, mobile and internet (broadband) services) - CallAir.  Due to increased competition in the market, CallAir.

Due to increase competition in the market, CallAir is under increasing pressure to remain competitive and to rebuild its waning customer base. In order to do this, CallAir requires a unified view of all its customer data including customer personal information, bill details, marketing preferences, history with the organization providing CallAir with the ability to target customers with the right product/service offers.

The following are the minimum project requirements:

You are required to create a REPORT for CallAir documenting the database design and some preliminary results once the database is developed.

This should include:
  1. 1.  Draw an Entity Relationship Diagram (ERO). This should include: 
    1. Primary keys 
    2. Foreign keys 
    3. Attributes (at least 2) 
    4. Relationship cardinality
    5. Include any assumptions you make about the problem scenario 
  2. Using Oracle (or another RDBMS) and SQL, create the database tables required to support the data storage needs of the database outlined above
    1. Populate each table with a minimum of 10 records 
  3. Knowing more about CallAir customers and their personal data, preferences, bills, complaints etc. will help the CallAir to identify customers who are at risk of cancelling their CallAir services as well targeting the right customers with new products and services. As part of this report, the team must use SQL (using at least five SQL statements} to provide management with a report highlighting this information.

Get your solution now

Buy now

Comments

Popular posts from this blog

Are you looking for the article. Congratulations! you are at the right place

Please comment on this post for Article requests Kindly Write Following things in comment: 1)  Name 2)  Article Link 3)  Your Email Id We will process your request as soon as possible. Note: Share this post with friends to help them.

Human Physiology by Stuart Ira Fox [PDF] (12th edition) free download

The Zoo Management System - entity relationship diagram & MS Access Database

Zoo Management System - Project Details: You are the employee of a big, worldwide working Zoo Management Company. Your company is responsible for the Zoo management. Your boss thinks it would be a great idea to store all data for each Zoo in a brand new self-developed ZOO Management System. Up to now, the ZOO management company has maps of each ZOO available. Your boss knows that you took a course in introduction on an ERP system, so he asks you if you could help designing such a system. Each ZOO must have the same organizational structure, which should look like this: Each Zoo has a Zoo-Address. Each Zoo has many visitors (Visitor Ticket Process (VTP). Many Zoo-Attractions belong to a Zoo. Module 1: Entity Relationship Diagram Design a ER (entity-relationship) diagram for your ZOO Management System. Use the information provided below with the entities and its attributes. Put the entities in the correct relationship to each other (organizational structure). Module 2: DB Implem...