Entity relationship diagrams
- Design an entity-relationship model for concierge desk in PJAIT, which will be used to create a database to facilitate the issuance of the keys for lecture rooms. Each room has its unique symbol. For each of the rooms may be many of keys (i.e. multiple copies – we do not take into account a number of castles). We have to remember information about teachers (name, surname) and each key issue (who and when took it, when the key has returned).
- The company needs a database to record customers (name, surname, address). Each client is supported by one representative (name) – the representative can support multiple clients. Each representative is assigned to one of the many branches of the company. Each customer has a specific status (active client/former client/potential client etc.). The database has to keep information about all contact events between representative and customer. We must remember the date of contact, description and type of contact (email/phone/fax etc.).
- Design an entity-relationship model for the company, which organizes the conferences. The company wants to store data about customers (companies), data about people with the company they work in and the data on organized conferences (date, subject). We assume, that each conference is organized by only one company. We need to keep the information of the speakers (people from the company) – there are many speakers on each conference. For each speech we need to remember the title.
Entity Relationship Diagrams
Task 1 – beer and beer drinkers
Create an entity relationship diagram which will be used to collect data about pubs and beer drinkers. We will store information about beer drinkers, names and addresses of pubs. For each beer drinker we want to remember what kind of beer he likes and which pubs he often visits. We want to know in which pub we can drink specific beer and what is the price of this beer in those places. Of course, each beer drinker may like different types of beer and go to different pubs (more than one). Create an entity relationship diagram, without redundancy (III normal form).
Task 2 - philharmonic
The philharmonic requires new database which will be used to achieve two interrelated objectives:
Database should allow us to gather the information about specific pieces, their composers and musicians. We should also remember how many specific types of musicians/instruments are required to play specific piece. We want to remember what kind instrument is used by each musician and what kind of pieces he is able to perform. We assume that each piece has one composer, but may require participation of many different instruments/musicians. Composers may be an author of more than one piece. Each musician specializes in playing on one specific instrument, but he can play more than one piece.
Should enable us to remember which piece is played in specific days and which musicians takes part in specific concerts.
Create an entity relationship diagram for philharmonic without redundancy (III normal form)
Task 3 - SPO
State Protection Office wants to create a top-secret database of its operations. We must remember carried out actions, their code name, purpose, area of operation and date. We want to know the personal details of every agent, his military rank, in which actions they took part and what kind of nickname was assigned to them during those actions. From each action we want to remember numbered notes with timestamp which apply to specific agents. Database should allow us to easily find notes about the specific agent or action. Create an entity relationship diagram without redundancy (in III normal form).
jaki koszt rozwiazania zadan?