Question: You are designing a database for an application that manages academic papers . The program will handle information about academic papers , authors and their
You are designing a database for an application that manages academic papers. The program will handle information about academic papers, authors and their institutes, and application domains. The basic business rules for the data:
- A paper is written by one to many authors, and an author writes one to many papers
- A paper cites other papers, and can be cited by other papers as well
- A paper can have many application domains, and a domain can have many papers
- Example: Paper 1 has application domains of database, E/R model, information retrieval; Domain database has 10 papers
- An author must belong to one institute, one institute can have multiple authors
- An application domain can have zero to many subdomains, a subdomain belongs to zero or one domain
- Example: database domain has subdomains of E/R model, RDM model, SQL. Computing domain does not belong to any parent domain.
Now you will move on to design the EER model for this data. Below are more requirements
- Institute should have institute name, department, detailed address
- Author should have name, academic degree
- Application domain should have the domain name
- Paper should have title, abstract, URL, and has three disjoint types:
- Proceedings paper is published from a conference with conference name, ordinal number, organizer, and location (e.g. paper 1 is published from IEEE Big Data, 5th, IEEE, Seattle WA US)
- One conference may have many proceedings papers, one proceedings paper belongs to one conference
- Journal paper is published from a journal with journal name, volume, and publisher
- One journal paper belongs to one journal, a journal may have many papers
- White paper is not published, so there is no further information
- Proceedings paper is published from a conference with conference name, ordinal number, organizer, and location (e.g. paper 1 is published from IEEE Big Data, 5th, IEEE, Seattle WA US)
Please draw the detailed EER diagram that
- Has all entities, their attributes, and relationships
- Resolves all Many to-Many relationships
- Has specialized supertypes into subtypes
- Remember to add an attribute in the supertype to represent subtypes
This lab does not include contents from module 4 (RDM), so you dont need to include foreign keys in the entities.
Step by Step Solution
There are 3 Steps involved in it
Get step-by-step solutions from verified subject matter experts
