Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

cse 2nd year dmcedmcl;d;mcdemwckjjevjwfnv, Exercises of Applications of Computer Sciences

ndkenkl'ddnclkdkdenckldnkjfevnjfeijfeknekwnkjenvkjewfvnjkfev

Typology: Exercises

2019/2020

Uploaded on 04/02/2020

mknknknknknjkm
mknknknknknjkm 🇺🇸

1 document

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
CS/SE 6360.002 - 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. Erwin,
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 NULL/
NOT NULL and DEFAULT values for the attributes.
Step 7: PL/SQL: Define two different stored procedures and two triggers.
pf3

Partial preview of the text

Download cse 2nd year dmcedmcl;d;mcdemwckjjevjwfnv and more Exercises Applications of Computer Sciences in PDF only on Docsity!

CS/SE 6360.002 - 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. Erwin, 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 NULL/ NOT NULL and DEFAULT values for the attributes. Step 7: PL/SQL: Define two different stored procedures and two triggers.

Step 8: Implement CRUD operations (Create, Read, Update and Delete) for one of your tables by using PHP or Python. You can use MAMP application package for implementation. It includes Apache Server, PHP/Python and MySQL database. Project Presentations: Project presentations should include an overview of the ER diagram, final relational schema, stored procedures and triggers and a demo for the website that shows CRUD operations. The in-class presentations will be conducted on April 26, 2017. All team members should be present during the presentation. Project Report: You will submit your final project report on April 26 , 2017 until midnight. Only one member from each group is required to upload the project reports 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 members (names and netids) Naming convention for project report file: SectionNumber-Teamnumber-ProjectTitle (doc, docx, pdf) Example: CS6360.002-Team4-LibraryManagementSystem Source code: Along with the project report also send your zipped source code and screenshots for each major operation. Due date for source code submission is April 26, 2017.