Академический Документы
Профессиональный Документы
Культура Документы
T.E. (CIS)
Batch: 2009-10
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 projects 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-
Project Title
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. Name Signature
Group Members
1. 2. 3. 4.
-3-
Abstract
Roll No.
Group Members
Name
Signature
1. 2. 3. 4.
-4-
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.
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.
-5-
CERTIFICATE
Certified that following students have successfully completed the DBMS project titled <<PROJECT TITLE>> as assigned by Course Incharge, Mr. Kashif Asrar.
<Name1>
<Rollno>
____________________________ <signature>
<Name2>
<Rollno>
____________________________ <signature>
<Name3>
<Rollno>
____________________________ <signature>
<Name4>
<Rollno>
____________________________ <signature>
-6-
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 FDs 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. b. c. StudID, Course_ID Grade (Full) StudID StudName (Partial) CourseID CourseTitle (Partial)
Now the reduced tables are CourseInfo (CourseID, CourseTitle) SutdentInfo (StudID, StudName) GradeInfo (StudID, CourseID, Grade)
-7-