Designing a Relational Database Model for a Research Publication Management System

User Requirements

Elicit requirements for, and model a relational database using Entity Relationship and Normalisation techniques

Use SQL in the construction, testing, manipulation and documentation of a small relational database for a business scenario

Explain and apply aspects of database management to a database scenario;

Identify and explain different types of database technologies and information systems;

Based on the case study provided at the end of this coursework specification,You need to submit:

A single REPORT containing the following

1. User requirements: Identify two possible stakeholders in the scenario and three functional requirements for each stakeholder, that your database system must be able to meet. These should be outputs linked to your stakeholders. As the case study contains only an outline of a business scenario, you will also need to state any business rules, assumptions, etc, that you have made in the course of putting together the database design. These need to be submitted with your design.

2. An ER diagram covering the data requirements of the scenario

3. A completed entity specification form for each entity shown on your ER diagram. The entity specification template can be found on Blackboard.

Have you identified meaningful functional requirements that can be met by the database, and associated each with appropriate stakeholders? Can each output be generated by your database design?

ER Model design Have you provided a comprehensive ER diagram that meets the requirements of the case study? Are all attributes, PKs and FKs correctly identified? Are all relationships named?

ER Model documentation Are all entities correctly and comprehensively documented? Have you chosen appropriate data types, data widths; are all constraints noted?

Either during, or at the end of the project, the research team publish various scholarly articles based on their research. Usually the articles will be based on one research project, but a single research project can generate a number of publications in variousscholarly journals. The aim of the team is to try to get their research published in highly rated scholarly journals (each journal is rated from 1 to 4 stars, with 4 star being the  quality).

A particular journal article can be written by one or more members of the research team. The research director now wishes to set up database information system which it hopes will provide the following:

• A list of the projects that are running, along with their start and projected end dates and the size of the sample of patients taking part in the project (but details of the patients are not required)

• Information on which researcher(s) are running each project;

• Information on what which articles have been published for each project and which journals they have been published in

• Information on which researchers have written which articles.

The above is a basic outline of the scenario for the new system.

The new system must be able to produce a number of useful reports to satisfy the requirements of its stakeholders. You may make any reasonable assumptions in the course of constructing your database model for the proposed system, eg on what attributes might be needed in each entity.