Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 18K views

    Micro Project On DBMS

    Uploaded by

    Yogesh Raut
    This document contains a micro project on normalizing a bank database up to the third normal form (3NF). It includes: 1) An ER diagram of a hospital management system with entities like hospitals, patients, doctors, etc. and relationships between them. 2) Conversion of the ER diagram into database tables, defining primary and foreign keys. 3) Identification of different types of attributes and relationships like one-to-many and many-to-one. The micro project aims to represent the database design of a hospital management system using an ER diagram and normalize the database structure up to 3NF.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Micro Project On DBMS

    Uploaded by

    Yogesh Raut
    18K views12 pages
    This document contains a micro project on normalizing a bank database up to the third normal form (3NF). It includes: 1) An ER diagram of a hospital management system with entities like hospitals, patients, doctors, etc. and relationships between them. 2) Conversion of the ER diagram into database tables, defining primary and foreign keys. 3) Identification of different types of attributes and relationships like one-to-many and many-to-one. The micro project aims to represent the database design of a hospital management system using an ER diagram and normalize the database structure up to 3NF.

    Original Description:

    information about DBMS project

    Original Title

    micro project on DBMS

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document contains a micro project on normalizing a bank database up to the third normal form (3NF). It includes: 1) An ER diagram of a hospital management system with entities like hospitals, patients, doctors, etc. and relationships between them. 2) Conversion of the ER diagram into database tables, defining primary and foreign keys. 3) Identification of different types of attributes and relationships like one-to-many and many-to-one. The micro project aims to represent the database design of a hospital management system using an ER diagram and normalize the database structure up to 3NF.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    18K views12 pages

    Micro Project On DBMS

    Uploaded by

    Yogesh Raut
    This document contains a micro project on normalizing a bank database up to the third normal form (3NF). It includes: 1) An ER diagram of a hospital management system with entities like hospitals, patients, doctors, etc. and relationships between them. 2) Conversion of the ER diagram into database tables, defining primary and foreign keys. 3) Identification of different types of attributes and relationships like one-to-many and many-to-one. The micro project aims to represent the database design of a hospital management system using an ER diagram and normalize the database structure up to 3NF.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 12

    MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

    VIDYA VARDINI’S
    BAHUSAHEB VARTAK POLYTECHNIC

    MICRO PROJECT
    ACEDEMIC YEAR: 2019-20

    NORMALIZE THE DATABASE OF


    BANK UPTO 3 NF

    PROGRAM/CODE: COMPUTER ENG (CO) SEMESTER: 3


    COURSE/CODE: DATABASE MANAGEMENT SYSTEM (22319)
    NAME OF STUDENT:
    ROLL NO.

    NAME OF FACULTY: PROF. PREETI AWARE


    MAHARASHTRA STATE
    BOARD OF TECHNICAL EDUCATION
    CERTIFICATE

    THIS IS TO CERTIFY THAT MR./MS.


    ........................................................................................................................…………
    ROLL NO. .............. OF THIRD SEMESTER OF DIPLOMA IN COMPUTER ENGINEERING
    OF INSTITUTE, B.V.POLYTECHNIC (CODE: 0093) HAS COMPLETED THE MICRO PROJECT
    SATISFACTORILY IN SUBJECT- DATABASE MANAGEMENT SYSTEM (22319) FOR THE
    ACEDEMIC YEAR 2019-20 AS PRESCRIBED IN THE CURRICULUM.

    PLACE: .......................... ENROLLMENT NO. :


    ........................................
    DATE: ............................ EXAM. SEAT NO. :
    ..........................................

    SUBJECT TEACHER HEAD OF THE DEPARTMENT PRINCIPAL

    Seal of institution
    WEEKLY ACTIVITY SHEET

    INSTITUTE CODE:0093/ ACADEMIC YEAR: 2019-20


    PROGRAM: SYCO1 ENGINEERING ROLL N0.
    COURSE &CODE: DATABASE MANAGEMENT SYSTEM (22319)
    NAME OF CANDIDATE :

    SEMESTER: III NAME OF FACULTY: PROF.PREETI AWARE


    SR. WEEK ACTIVITY PERFORMED DATE SIGN OF
    NO FACULTY
    1 1st Discussion and finalization of
    topic
    2 2nd Literature review
    3 3rd Collection of data
    4 4th Collection of data
    5 5th Discussion and outline of
    content
    6 6th Formulation of content
    7 7th Editing and proof reading of
    content
    8 8th Compilation of report
    9 9th Report presentation
    10 10th Final submission of micro
    project
    RUBRIC FOR EAVLUATION ON MICRO PROJECT

    INSTITUTE CODE: 0093 ACADEMIC YEAR: 2019-20

    PROGRAM: SYCO1 COURSE CODE: 22319

    SEMSTER: 3 NAME OF FACULTY: PROF. PREETI AWARE

    SR. CHARACTERISTICS TO BE ASSESSED POOR AVERAGE GOOD


    NO (1-2) (3-4) (5-6)

    01 LITERATURE SURVEY/REFERENCE

    02 PROJECT PROPOSAL/REPORT/CONTENT

    03 RELEVANCE TO THE COURSE


    04 PLANNING AND TIMELY COMPLETION OF
    TARGET

    05 ANALYSIS OF DATA/REPRESENTATION

    06 QUALITY OF PROTOTYPE/MODEL

    07 TOTAL MARKS FORM ASSESMENT OF MICRO PROJECT (OUT OF


    6)

    08 MARKS OBTAINED IN INDIVISUAL PRESENTATION (OUT OF 4)

    09 TOTAL MARKS(OUT OF 10)

    SIGNATURE OF FACULTY SIGNATURE OF STUDENT


    ANNEXTURE-II
    EVALUATION SHEET FOR THE MICRO PROJECT

    ACADEMIC YEAR: 2018-19 NAME OF FACULTY: PROF. PREETI AWARE


    COURSE CODE: 22319 SEMESTER: 3
    COURSE: DATABASE MANAGEMENT SYSTEM.
    TITLE OF PROJECT : ER Diagram for Hospital Management System.

    CO’s addressed by the Micro Project

    Outcomes in affective domain:

    A. ER Diagram for Hospital Management System.

    Comments/suggestions about team work/leadership/inter personal communication (IF ANY)

    Roll. Enrollment Student name Marks out of 6 Marks out of 4 Total out
    no No. for performance for of 10
    in group activity performance
    in group
    activity

    1257 1900930115 Yogesh Vasant Raut


    1258 1900930117 Vaibhav Dinesh Gawad
    1259 1900930116 Vishal Arun Chaudhary
    1260 1900930020 Sahil Rajesh Pawar
    INDEX

    SR. PAGE
    NO. CONTENT NO.

    1 Introduction of Hospital ER Diagram 1

    2 ER Diagram Hospital Management 2


    System

    3 ER Diagram into Data tables 3,4

    4 Entity Relationships 5

    5 Conclusion 6

    6 References 7
    INTRODUCTION

    This ER (ENTITY RELATIONSHIP) Diagram represents the model of Hospital Management

    System Entity. The entity-relationship diagram of Hospital Management System shows all the

    visual instrument of database tables and the relations between Patient,

    Nurses,Hospitals,Medicines etc. It used structure data and to define the relationships

    between structured data groups of Hospital Management System functionalities. The main

    entities of the Hospitals, Patient ,Doctors, Nurses, Appointments and Medicines.


    Step 2: Converting the E-R Diagram into Tables
    b. Converting entity to table and attribute to columns
    Hospital

    Hosp-id Primary Key


    HCity
    HAddress
    Hos-Name
    Pat-id Foreign key refernces to Pat-id of Patient table
    Doc-id Foreign key refernces to Doc-id of Doctor table
    Patient

    Pat-id Primary Key


    Medical Record

    PName
    Record-id Primary Key

    PAddress
    Problem

    PDiagnosis
    Date_of_examination

    Record-id
    Pat-id Foreign Foreign
    key references to Record-id
    key references of Medical
    to Pat-id Record
    of Patient
    table table

    Hosp-id Foreign key references to Hosp-id of Hospital table

    Doctor

    Doc-id Primary Key

    DName

    Qualification

    Salary

    Hosp-id Foreign key references to Hosp-id of Hospital table


    Step 3: Mapping of Attributes
     Simple Attributes
    Simple Attributes which can not be divided into subparts.
    Example: Salary of Doctor

     Composite Attributes
    Composite Attributes which can be divided into subparts.
    Example: Patient Name, Doctor Name

    Step 4: Mapping of Relationships


    b. Foreign Key approach
    Hosp_patient

    Pat-id Hospital table makes foreign key references to Pat-id of Patient table

    Hosp-id Patient table makes foreign key references to Hosp-id of Hospital table

    Hosp_Doctor

    Hosp- Doctor table makes foreign key references to Hosp-id of Hospital


    id table

    Doc-id Hospital table makes foreign key references to Doc-id of Doctor table
    Hosp- Doctor table makes foreign key references to Hosp-id of Hospital
    id table

    PatiPPatient_MedicalRecord

    Pat-id Medical Record table makes foreign key references to Pat-id of


    Patient table

    Record- Patient table makes foreign key references to Record-id of Medical


    id Record table

    step 5: Identifying the relationships


    a. Hospital has a set of patients.
    Therefore the relations is 1……..N.
    b. Hospital has a set of doctors.
    Therefore the relations is 1……..N.
    c. Doctor are associated with each patient.
    Therefore the relations is N……..1.
    d. Each patient has record of various test and examination conducted.
    Therefore the relations is 1……..N.

    Conclusion

    We can represent a database that conforms to an E-R database schema by a


    collection of tables. For each entity set and for each relationship set in database,
    there is a unique table to which we can assign the name of the corresponding entity
    set and relationship set. Each table has multiple columns, each of which has a
    unique name. Both the E-R model and the relational-database model are abstract,
    logical representations of real-world enterprises. Because the two models employ
    similar design principles, we can convert an E-R design into a relational design.
    Converting a database representation from an E-R diagram to a table format is the
    way we arrive at a relational-database design from an E-R diagram. Informally, a
    relation can be considered to be a table of values.

    References

    https://www.ques10.com/p/9489/draw-e-r-diagram-for-hospital-management-system-1/
    https://www.geeksforgeeks.org/introduction-of-er-model/

    You might also like