You are on page 1of 4

NAME :JESSICA GONSALVES ROLL NO: 71 CLASS: SECMPNA

ST. FRANCIS INSTITUTE OF TECHNOLOGY


MT. POINSUR, BORIVALI (W), MUMBAI

LAB MANUAL

EXPERIMENT NO. 1

Aim: Identify the case study and detailed statement of the problem. Design an
Entity-Relationship (ER) / Extended Entity-Relationship (EER) Model.

Theory:
1. Features of Database system

● Reduced amount of space and money spent on storage


All database management systems must save a large amount of data. However,
proper data integration saves a lot of space in the database management
system.
● Data Organization
In a Database Management system, a digital repository’s information is
structured in a clear hierarchical structure using records, tables, and objects.
Every piece of information which we enter into our database will be
structured in a catalog, making it easy to search and edit our records later.
● Multi User Access
Multiple users can access all forms of information contained in the same data
store with a Multi-User Access Database Management System.
● Maintenance of a Large Database
Only a database management system can keep large databases of large
corporations up to date. These databases necessitate a high level of security as
well as backup and recovery capabilities. Database Management System
includes all of these functionalities.
● Data Durability
All data files are permanently stored by Database Management System , so
there is no risk of data loss. If the data is lost, the organization’s data files can be
saved using a backup and recovery procedure.
● Data Retrieval
Data Retrieval becomes a big advantage of the database management systems as
only authenticated users can fetch data from the database and unauthenticated users
NAME :JESSICA GONSALVES ROLL NO: 71 CLASS: SECMPNA

are denied access, thus improving the security of the data. ● Saves Storage Space
and Cost
All the Database management systems have a lot of data to save. But proper
integration of data saves much more space in DBMS. Companies are paying so much
money to store data. If they have managed data to store then it will save their cost of
storing data and data entry.
● Provides High Level of Security
Security is a very big concern for all the organizations who are handling a large
amount of data. DBMS doesn’t give full access to the database except to the DBA or
head of the department. They are able to alter the database and all the users are
created by them so the security level of DBMS becomes so high.

2. Explain ER & EER- Entities, Attributes, Relationship, Specialization,


generalization

ER- An entity-relationship (ER) diagram, also called an entity-relationship model, is


aptly named: It shows the relationships between entities. It is most commonly used to
organize data within databases or information systems.There are two kinds of ER
diagrams: conceptual and physical. Conceptual diagram models can be used as the
foundation for logical data models or to form commonality relationships between ER
models as a basis for data-model integration.with notations.

EER- Enhanced entity-relationship (EER) diagrams are basically an expanded upon


version of ER diagrams. EER models are helpful tools for designing databases with
high-level models. With their enhanced features, you can plan databases more
thoroughly by delving into the properties and constraints with more precision.

1. Entities: are objects or concepts that represent important data. Also known as
strong entities or parent entities, these entities will often have weak entities that
depend on them.
2. Attributes :are characteristics of an entity, i.e. many-to-many or one-to-one.
3. Relationships: are associations between entities.Relationships are typically
shown as diamonds or labels directly on the connecting lines.
4. Generalization is a bottom-up approach in which two lower level entities
combine to form a higher level entity. In generalization, the higher level entity
can also combine with other lower level entities to make further higher level
entities. For Example, STUDENT and FACULTY can be generalized to a
higher level entity called PERSON
5. Specialization is opposite to Generalization. It is a top-down approach in
which one higher level entity can be broken down into two lower level entity.
NAME :JESSICA GONSALVES ROLL NO: 71 CLASS: SECMPNA

In specialization, a higher level entity may not have any lower-level entity sets,
it's possible.For Example, EMPLOYEE entity in an Employee management
system can be specialized into DEVELOPER, TESTER etc.

Implementation:
1. Identify Case study and write detailed problem statements.

Design a DB for Western India medical clinic located in Mangalore. The clinic
has a number of regular patients and new patients that come to the clinic regularly.
Patients make appointments to see one of the doctors. Several doctors attend the
clinic and they each have their own hours when they attend the clinic. Some
doctors are general practitioners while others are specialists eg. cardiologists,
dermatologists, endocrinologists, etc. Doctors' hours are defined and fixed by each
doctor but can be changed if necessary. Different doctors may charge different
fees. Doctors send patients to clinics for X-rays and blood tests. These reports are
sent from the clinics to the doctors electronically. Doctors write medical
certificates. Patients have families and their family relationships are important.
Medical records of each patient need to be maintained. Information on
prescriptions, issurances, allergies,etc need to be maintained.
2. Draw Entity Relationship diagram

3. If EER concept available, then extent ER to EER Diagram


NAME :JESSICA GONSALVES ROLL NO: 71 CLASS: SECMPNA

Conclusion:
Your understanding about the experiments and lab Outcomes attained.

In this experiment, we have seen the components of an ER Diagram such as Entities,


Attributes,Relationships and also the types of attributes. We have drawn an ER
Diagram of a college using online tools and were able to successfully show the
relationships between the various entities of the ER Diagram. Thus we have
successfully studied and drawn an Entity-Relationship Diagram.

You might also like