Mini Project

1. Do Mini project on Dispensary Patient name, with their contact details and treatment.
A unique ID can be given to each one. Also rooms, wards, nurses and doctor records
can be kept in DBMS.
2. Do a mini project to construct an E-R diagram for a hospital with a set of patients and
a set of medical doctors. Associate with each patient a log of the various tests and
examinations conducted.
3. Mini project on Design sort-based and hash-based algorithms for computing the
relational division operation (see Practise Exercises of Chapter 6 for a definition of
the division operation).
4. Develop a e-commerce platform, where a customer can register and buy a product.
(Mini Project)
5. Mini project - Create a simple web application to simulate SQL Injection attack. This
attack pattern is one of the most famous Application level attacks. So we can reduce
the risk or avoid this attack happening through optimizing our application code.
6.

Case Study

1. Case study on “workers behind the scene” of DBMS system design and
implementation.
2. Case study on the concept of functional dependencies, and used it to present two
normal forms, Boyce–Codd normal form (BCNF) and third normal form (3NF).
3. Case study on a recovery algorithm used in database systems.(Example: ARIES
algorithm)
4. Case study on “What is the effect on the cost of merging runs if the number of buffer
blocks per run is increased, while keeping overall memory available for buffering
runs fixed?”
5. Case study on Our description of static hashing assumes that a large contiguous
stretch of disk blocks can be allocated to a static hash table. Suppose you can allocate
only C contiguous blocks. Suggest how to implement the hash table, if it can be much
larger than C blocks. Access to a block should still be efficient.
6. The CAP theorem is a belief from theoretical computer science about distributed data
stores that claims, in the event of a network failure on a distributed database, it is
possible to provide either consistency or availability—but not both. Do complete case
study about this.
7. Identify all the important concepts represented in the library database case study described
below. In particular, identify the abstractions of classification (entity types and relationship
types), aggregation, identification, and specialization/generalization. Specify (min, max)
cardinality constraints whenever possible. List details that will affect the eventual design but
that have no bearing on the conceptual design. List the semantic constraints separately.
Draw an EER diagram of the library database.
 Case Study: The Georgia Tech Library (GTL) has approximately 16,000 members, 100,000
titles, and 250,000 volumes (an average of 2.5 copies per book). About 10% of the volumes
are out on loan at any one time. The librarians ensure that the books that members want to
borrow are available when the members want to borrow them. Also, the librarians must
know how many copies of each book are in the library or out on loan at any given time. A
catalog of books is available online that lists books by author, title, and subject area. For
each title in the library, a book description is kept in the catalog; the description ranges from
one sentence to several pages. The reference librarians want to be able to access this
description when members request information about a book. Library staff includes chief
librarian, departmental associate librarians, reference librarians, check-out staff, and library
assistants. Books can be checked out for 21 days. Members are allowed to have only five
books out at a time. Members usually return books within three to four weeks. Most
members know that they have one week of grace before a notice is sent to them, so they try
to return books before the grace period ends. About 5% of the members have to be sent
reminders to return books. Most overdue books are returned within a month of the due
date. Approximately 5% of the overdue books are either kept or never returned. The most
active members of the library are defined as those who borrow books at least ten times
during the year. The top 1% of membership does 15% of the borrowing, and the top 10% of
the membership does 40% of the borrowing. About 20% of the members are totally inactive
in that they are members who never borrow. To become a member of the library, applicants
fill out a form including their SSN, campus and home mailing addresses, and phone numbers.
The librarians issue a numbered, machine-readable card with the member’s photo on it. This
card is good for four years. A month before a card expires, a notice is sent to a member for
renewal. Professors at the institute are considered automatic members. When a new faculty
member joins the institute, his or her information is pulled from the employee records and a
library card is mailed to his or her campus address. Professors are allowed to check out
books for three-month intervals and have a two-week grace period. Renewal notices to
professors are sent to their campus address. The library does not lend some books, such as
reference books, rare books, and maps. The librarians must differentiate between books
that can be lent and those that cannot be lent. In addition, the librarians have a list of some
books they are interested in acquiring but cannot obtain, such as rare or outof-print books
and books that were lost or destroyed but have not been replaced. The librarians must have
a system that keeps track of books that cannot be lent as well as books that they are
interested in acquiring. Some books may have the same title; therefore, the title cannot be
used as a means of identification. Every book is identified by its International Standard Book
Number (ISBN), a unique international code assigned to all books. Two books with the same
title can have different ISBNs if they are in different languages or have different bindings
(hardcover or softcover). Editions of the same book have different ISBNs. The proposed
database system must be designed to keep track of the members, the books, the catalog,
and the borrowing activity.
8. A Case Study of Faculty of Open Education
9. A case study of comparative analysis of RDBMS and OODBMS
10. Case Study: AWS Relational DB service for a leading transportation company
11. Case Study
 Consider the following database scenario for a Career Advising Website.

The Career Advising Center at a University would like a “Career Advising Website” to be
created so they can better manage the student requests for career advising appointments.
The Career Advising Center would like to assign appropriate Industry Advisors with students
based on career area.

 Every Industry Advisor has an area (or areas) of expertise, that is, they are
knowledgeable in providing career advice for particular career areas (e.g. Arts,
Education, Engineering, Healthcare, Marketing, etc…)
 Students come to the Career Advising Center to get career advice in a particular
career area. Students who log into the system will have a profile with their basic
information — first name, last name, studentID, phone number, email, and a career
area which they select from a list of career areas.
 Industry Advisors also have their basic information — first name, last name,
facultyID, office location, phone, email, and area(s) of expertise (area of expertise
taken from the same list of career areas the Students have.)
 Let’s assume each student is interested in only one career area (e.g. Engineering)
whereas Industry Advisors can have more than one career area listed as their areas
of expertise.
 Students can request an advising session and based on their career area an
appropriate Industry Advisor will be assigned.
 An advising session will be scheduled between the student and an Industry Advisor
at a specific date and time, in a particular location (either Room 100, Room 200, or
Room 300), and for a specific career area (for example, to indicate this advising
session is to discuss the Engineering career area.) At the end of the advising session
the student has the opportunity to rate their experience with a simple numeric
rating (e.g. 1 to 10) and a free-form text box.
At various times, the Career Advising Center would want to gather information about the
number of advising sessions that took place, the number of advising sessions that took place
per career area, the total number of unique students who requested advising sessions
(students can request multiple advising sessions during an academic year), the average
rating given, or the Industry Advisor who was rated the highest, etc.
i. Discuss about E-R diagram.
ii. Create an E-R diagram for the database scenario. Make sure to include an indication
of the cardinality of relationships and specify any mandatory relationship (total
participation). State any assumptions that you make.
iii. Convert the E-R diagram to tables, using schema statements.
12. DATABASE MANAGEMENT SYSTEM APPLICATION (CASE STUDY: TWISBLESS)
13. Case Study of Computerized cab service management system
14. A Case Study of A.T.E.C Central Library
15. Data management issues in vehicle control system: a case study
16. A real-time database management system for logistics systems: A case study
17. Case Study: A scalable SQL Database Powers Real-time Analytics at Uber
18. Research issues in real time database systems
19. Parliament’s IT Systems
20. Case Study on active database applications