Scribd Logo
Upload

Welcome to Scribd!

  • 19 views

    Final Project

    Uploaded by

    rp7028694956
    The document outlines the requirements for a final project in a database systems course. Students must design a database for a given domain, including collecting requirements, creating an ER diagram with specific relationship types, normalizing the schema, implementing the database in SQL with stored procedures and triggers, and presenting their work.

    Copyright:

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

    Final Project

    Uploaded by

    rp7028694956
    19 views2 pages
    The document outlines the requirements for a final project in a database systems course. Students must design a database for a given domain, including collecting requirements, creating an ER diagram with specific relationship types, normalizing the schema, implementing the database in SQL with stored procedures and triggers, and presenting their work.

    Original Description:

    project

    Original Title

    Final-Project

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document outlines the requirements for a final project in a database systems course. Students must design a database for a given domain, including collecting requirements, creating an ER diagram with specific relationship types, normalizing the schema, implementing the database in SQL with stored procedures and triggers, and presenting their work.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    19 views2 pages

    Final Project

    Uploaded by

    rp7028694956
    The document outlines the requirements for a final project in a database systems course. Students must design a database for a given domain, including collecting requirements, creating an ER diagram with specific relationship types, normalizing the schema, implementing the database in SQL with stored procedures and triggers, and presenting their work.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    You are on page 1of 2

    CS 6360.

    002/003 - FINAL PROJECT

    Project Description:

    In this project, you need to design a database system for a given domain. For this, first you
    need to conduct research about the domain itself and collect data requirements (such as
    information about the main components of the system, how the system works, how
    different entities interact with each other etc.) Then you will try to design a system as
    practical as possible. This means, assumptions you make should comply well with real-
    world situations/scenarios.

    Tasks:

    Step 1: Write the data requirements for the system.

    Step 2: Draw the initial ER diagram for your system. ER diagrams should be drawn
    electronically. You can use any chart-drawing tool of your choice. (i.e. draw.io,
    lucidchart.com, etc.)

    A minimal system design should include at least:


    a. two one-to-one binary relationships.
    b. two one-to-many binary relationships.
    c. two many-to-many binary relationships.

    You can create more relationships if required.

    Indicate cardinality and participation constraints on ER diagram. You can use different
    notations to show cardinality ratios. (i.e. min-max notation, Crow’s Foot notation)

    Step 3: Map the ER diagram into relational schema. Show the resulting relational schema:
    show your tables, primary keys and foreign keys.

    Step 4: Discuss database normalization rules on your tables. Show the functional
    dependencies that violate 1st, 2nd and 3rd normal forms. Normalize your table(s) into 3NF.

    Step 5: Show the final relational schema after normalization.

    Step 6: Create tables using appropriate SQL command. Make sure to include primary key
    and foreign key definitions and triggered actions on foreign keys. Decide also about NOT
    NULL constraints and DEFAULT values for the attributes.

    Step 7: PL/SQL: Define two meaningful stored procedures and two triggers.
    Project Presentations:

    Project presentations should include an overview of the ER diagram, final relational


    schema, stored procedure and trigger definitions. In-class presentations will be conducted
    on December 4, 2019. All team members should be present during the presentation.

    Project Report:

    You will submit your final project report until December 4, 2019, 11:59pm.

    Only one member from each group is required to upload the project report through
    eLearning system.

    At the beginning of the project report, please make sure you include:

    o Project Title
    o Course number and section number
    o Team number
    o Team members (names and netids)

    Naming convention for project report file:


    CourseSectionNumber-Teamnumber-ProjectTitle.pdf

    Example: CS6360.002-Team4-ebay.pdf

    Evaluation:

    o Requirements collection: comprehensive, detail-oriented system (20 points)


    o ER/EER (20 points)
    o Mapping to relational model and normalization (20 points)
    o SQL (20 points)
    o PL/SQL (20 points)

    You might also like