DBMS Mini Project

NED UNIVERSITY OF ENGINEERING AND TECHNOLOGY, KARACHI DEPARTMENT OF COMPUTER AND INFORMATION SYSTEMS ENGINEERING

T.E. (CIS)

Batch: 2009-10

Session: Fall Term 2012

CS-306: DATABASE MANAGEMENT SYSTEMS (DBMS)

MINI Project GUIDLINE

BY Kashif Asrar Lecturer (CIS) & Course Teacher

MINI PROJECT  A database application system is to be developed with a database at back-end (Oracle, SQL-Server, MySQL etc) and an application at the front-end (VB.Net, ASP.Net, C#.Net, PHP, Oracle Developer, Java etc).  The front-end GUI-based application should manipulate and present the database data to users using forms and help prepare important reports.  The students are required to submit a project proposal (see page 3). The students must also submit a Gantt Chart or use other project management tool to show the various activities of the project.  Deadline for submitting project proposal is MON 30th July, 2012 (Max. four members per group)  A Project Progress Report is also required to be submitted (see page 7)  Last date for project progress report is MON 26th Sept, 2012 which has 5 marks. More guidance will be provided in the class.  The project’s final report (see page 5) should indicate all the necessary steps in database design. Detailed report format is also being provided with this guideline.  The project may also cover the aspects of recovery and security of the database.

-2-

DBMS PROJECT PROPOSAL (SAMPLE)

Project Title

HOSPITAL INFORMATION SYSTEM Description

This project will involve developing a database to store information about patients, doctors, medicines, hospital departments and other facilities available. This will help in managing the patients, doctors and hospital facilities. It will include patient appointment, patient category, history, visits and billing; doctor availability, experience, field of specialization and salaries. Moreover, it would also provide information about different department in the hospital. Roll No.

Group Members

Name

Signature

1. 2. 3. 4.

Tools to be used (both front end and back end)

FRONT END : C#.NET BACK END : ORACLE 9i

Date of submission: 30-07-2012

-3-

DBMS PROJECT PROPOSAL Project Title

Abstract

Roll No. Group Members

Name

Signature

1. 2. 3. 4.

Tools to be used (both front end and back end)

FRONT END : BACK END :

Date of submission: ____________

-4-

DBMS MINI-PROJECT-REPORT FORMAT TITLE PAGE: The title page should mention the project title, student names, roll no, course name i.e. DBMS, batch, submitted to whom, date of submission.

CERTIFICATE: A certificate to be signed at the end by course teacher. The certificate is on the next page. Each student will have to sign it personally against his/her name.

ACKNOWLEDGEMENTS: Acknowledgements may be included as well. ABSTRACT: 10 to 20 lines TABLE OF CONTENTS: SN, topic, page number (page number should be at bottom-centre) REPORT BODY Chapter 1: The report should begin with a brief overview of the project, telling the source from which the project was taken (if fictitious organization, then mention it also) and describe the problems of the organization that would be solved by the database system developed.

Chapter 2: Requirement Formulation and Analysis (A handout can be provided with the title Database Design that will serve as guidance for this chapter)

Chapter 3: (Conceptual Design) E-R Model, its description and mapping the E-R model to tables. ER model may be drawn by hand or with software.

Chapter 4: (Logical Design) Normalization of tables upto BCNF. Show the functional dependencies on the pattern of your lesson in the text book. Even if you are sure that tables are already normalized, then you should perform validation to ensure that there are no partial or transitive dependencies and all dependencies are on candidate keys. Guidance for normalization is provided at the end of this document.

Chapter 5: (Implementation Design) 

Show conceptual schema in terms of CREATE TABLE, CREATE SEQUENCE and other DDL statements.  Show external schema in terms of CREATE VIEW statement.  Also show the necessary indexes created. (part of internal schema) Chapter 6 and onwards: Describe the implementation of front-end application using front-end tools (i.e. VB, Oracle Developer, Php, Java, .net, ASP/JSP etc.). Describe about the different forms and reports included in the software. Mention the different features of front-end tools used for forms and reports. This section should include snapshots of some important forms and reports generated by the software.

Last Chapter: Describe how security of database is implemented. Suggest further improvements to be made in future. It would be very advantageous to include some recovery controls and measures to be taken.

Bibliography Index is optional NOTE i. THE REPORT SHOULD NECESSARILY INCLUDE A PAPER AT THE END INDICATING THE CONTRIBUTION OF EACH STUDENT IN THE PROJECT. (i.e. problem finding, designing, implementing, report preparation etc.) ii. Line spacing should be 1.5. iii. The report body should have 1" margins of top, bottom, left, right iv. Suggested Font is Times New Roman/Book Antiqa/Sylfaen, Font size 11 or 12 v. Report should be ring-binded

-5-

CERTIFICATE Certified that following students have successfully completed the DBMS project titled as assigned by Course Incharge, Mr. Kashif Asrar.





____________________________





____________________________





____________________________





____________________________

_____________________ Kashif Asrar Lecturer & Project Incharge

-6-

PROJECT PROGRESS REPORT The Project Progress Report should cover the following work:1. Requirement Formulation and Analysis (A handout will be provided) 2. ER-Model of the database (along with transformation to tables) 3. Normalization of the tables

Guidance for Normalization Consider the relation produced after transformation from ER-Model:Course (CourseID, StudID, CourseTitle, StudName, Grade)  Now consider all CKs and the PK  Identify all FD’s  If there is partial or transitive dependency or a dependency on non-CK, then remove it. Otherwise show that there the relation is in BCNF.  Repeat the above procedure for all relations. e.g. Following are the partial and full dependencies in above relation. a.

StudID, Course_ID  Grade (Full)

b.

StudID  StudName (Partial)

c.

CourseID  CourseTitle (Partial)

Now the reduced tables are CourseInfo (CourseID, CourseTitle) SutdentInfo (StudID, StudName) GradeInfo (StudID, CourseID, Grade)

-7-