STUDENT DATABASE PROPOSAL

BY

TO BULID A DATABASE OF STUDENT MANAGEMENT

TITLE:

TO BUILD A DATABASE OF STUDENT MANAGEMENT FOR A UNIVERSITY

SUBMITTED BY:

ARSHAD AHMED M. ZIL-E-SUBHAN M. ZULQARNAIN

SUPERVISOR:

MR. MEHAR ABBAS

COURSE:

PGD-IT
DEPARTMENT:

COMPUTER CENTER

QUAID-E-AZAM UNIVERSITY, ISLAMABAD

2

TO BULID A DATABASE OF STUDENT MANAGEMENT

TABLE OF CONTENTS
1. INTRODUCTION .............................................................................................................................. 5 1.1. BACKGROUND ...................................................................................................................... 5 1.2. GOALS................................................................................................................................... 6 1.3. REQUIREMENTS ................................................................................................................... 6 2. 3. IDENTIFICATION OF THE PROBLEM ............................................................................................... 7 PROPOSED SYSTEM ........................................................................................................................ 8 3.1. BENEFITS .............................................................................................................................. 8 3.1.1. EASY DATA CONTROL .................................................................................................... 8 3.1.2. ACCURACY ..................................................................................................................... 8 3.1.3. DATA SECURITY ............................................................................................................. 8 3.1.4. BETTER PROCESSING SPEED .......................................................................................... 9 3.1.5. REUSE OF DATA CODE ................................................................................................... 9 3.2. FUNCTIONS .......................................................................................................................... 9 3.2.1. DATA DICTIONARY MANAGEMENT............................................................................. 10 3.2.2. DATA STORAGE MANAGEMENT ................................................................................. 10 3.2.3. DATA TRANSFORMATION AND PRESENTATION ......................................................... 10 3.2.4. SECURITY MANAGEMENT ........................................................................................... 10 3.2.5. MULTIUSER ACCESS CONTROL .................................................................................... 10 3.2.6. BACKUP AND RECOVERY MANAGEMENT ................................................................... 11 3.2.7. DATA INTEGRITY MANAGEMENT ................................................................................ 11 3.2.8. DATABASE ACCESS LANGUAGES AND APPLICATION INTERFACE ............................... 11 3.2.9. DATABASE COMMUNICATION INTERFACES ............................................................... 11 3.3. ENTITIES ............................................................................................................................. 12 3.4. ATTRIBUTES ........................................................................................................................ 12 4. ER DIAGRAM ................................................................................................................................. 15 4.1. ONE-TO-ONE ...................................................................................................................... 15 4.2. ONE-TO-MANY ................................................................................................................... 15 4.3. MANY-TO-MANY ................................................................................................................ 15 3

TO BULID A DATABASE OF STUDENT MANAGEMENT 5. NORMALIZATION.......................................................................................................................... 18 5.1. FORMS OF NORMALIZATION ............................................................................................. 19 6. 7. SCREENSHOTS OF TABLES ............................................................................................................ 20 CONCLUTION...............................................................................................................................25

ACKNOWLEDGEMENT
We feel great pleasure in acknowledging our indebtedness to all those who have been of substantial help and support to us during the preparation of this manuscript. The work presented in this manuscript was accomplished under the inspiring guidance and enlightened supervision of Sir. Mehar Abbas. His efforts towards the instructions of the spirit of constant work and maintenance of professional integrity besides other valuable words of advice encouraged us to keep on fighting against all over whelming odds till success was ensured. We avail this opportunity to express our deepest sense of gratitude and thankfulness to him. We deem it utmost pleasure to express our heartiest gratitude and deep sense of obligation to him for his guidance, co-operation, encouragement and invaluable suggestions whenever we had any problem regarding this project throughout the course of this project. We thank all the staff of the computer center for their cooperation and assistance during the performance of our experimental work. The completion of this project was a long term task and needed an ideal atmosphere for its completion. We pay tribute to all ourwell-wishers and class fellows specially Tahir & Raza for their cooperation and sincere help.

TO BULID A DATABASE OF STUDENT MANAGEMENT

1. INTRODUCTION
In the proposed database, users will be able to access information about students, faculty and various departments of a university . SQL Plus has been used as the main tool for storing data and for development of the database. A database is a tool for collecting and organizing information. Our Databases will store information about students, teachers, subjects, departments etc. Many databases start as a list in a word-processing program or spreadsheet. As the list grows bigger, redundancies and inconsistencies begin to appear in the data. The data becomes hard to understand in list form, and there are limited ways of searching or pulling subsets of data out for review. Once these problems start to appear, it's a good idea to transfer the data to a database created by a database management system (DBMS), such as SQL plus.

1.1. BACKGROUND
In the XYZ University, tracking a student's progress and gaining information about departments and faculty through manual registers or word processing programms and worksheets. However, as multiple aspects of the students data must be shared for various tasks, this data is often shared via email and stored redundantly in excel spreadsheets across the department. This manner of storage often leads to hardships with regards to how the data was managed, updated, and shared; when data needs to be updated, all copies must be updated manually with great care so that out of date information is not kept and recirculated through the system. Currently, this is done by sifting through hundreds of papers for all the students and counting them manually. With a centralized system, it could potentially take a single query to count the students on a moments notice.

TO BULID A DATABASE OF STUDENT MANAGEMENT

1.2. GOALS
To replace the current paper-based or simple word documents with database management system so that users will be benefited from data collection and information sharing efficiently. To create a database to centrally handle the information of all the students in the university, and to provide access to this information with an easy to use web-based interface that can be accessed by any device with basic html rendering capabilities.

1.3. REQUIREMENTS
Requirements for the system fall into three categories, those tending towards the usability of the system, those towards the maintenance and alteration of the system, and those towards the security of the system. For the first requirement, accessibility was addressed by making the system accessible from the web via a standard web browser, and no required extensions, such as java, javascript, or flash. The system was also designed so that the users would be able to complete the repeatable tasks in a streamlined manner to cut down on wasted time, and in a concise way to switch between tasks. To address the maintenance of the system, a modular design was used. This was done so that bugs can easily be found and additional features can easily be added to the system. To address the security of the system, users are required to run sessions over Hypertext Transfer Protocol over Secure Socket Layer, https.

TO BULID A DATABASE OF STUDENT MANAGEMENT

2. IDENTIFICATION OF THE PROBLEM

Organization is key for business as well as personal use. No matter who you are, it is important to have excellent organizational skills, especially when dealing with vital documents. In today's world, organization is made simple for us through the use of computers and electronic filing systems. Although this tool is available to us, we may still require a little assistance using it to the greatest benefit. If this describes your relationship with electronic filing, the project might prove beneficial. Furthermore, this project will assist us how to create and manage student records using a student database.

Currently the XYZ university was using sipmle word files or spreadsheets for storing data. Which has following problems:

Data redundancy(duplication) Inconsistency Program data interdependency Lack of flexibility Poor security Lack of data sharing and availability

TO BULID A DATABASE OF STUDENT MANAGEMENT

3. PROPOSED SYSTEM
Our propsed system is DATA BASE MANAGEMENT SYSTEM.

3.1. BENEFITS
Database management system simply refers to handling and managing of data. It is commonly used in small and large organizations to allow the collection of data, as well as background integration. Not only do they ensure information is easily accessed by users, but also help to facilitate data duplication.

3.1.1. EASY DATA CONTROL Since all the information is centralized, you dont need to duplicate data. Unlike traditional paper systems, all users can get the data firsthand without making new copies. Likewise, data base management system helps to remove the cost of duplication resulting from single application programs.

3.1.2. ACCURACY Because data is stored on multiple computers using database management software, handling data becomes easier. In addition, organizations use database management system to maintain accuracy of information. By doing so, they are able to enforce high standards.

3.1.3. DATA SECURITY Of all the benefits, this is one of the most important features of database management system. Data is restricted only to those who are certified to manipulate it, therefore preventing breach of information by unscrupulous individuals.

TO BULID A DATABASE OF STUDENT MANAGEMENT

3.1.4. BETTER PROCESSING SPEED The responsiveness of data management using computer systems is better with a wellversed DBMS, as compared to linear computer applications. For instance, functions such as sum, calculate, and count are automated with ease. In a data management system, the applications to report, store, and update the data are planned in an orderly manner.

3.1.5. REUSE OF DATA CODE The best thing about data management system is that each part can reuse code from other modules or sections. For instance, inventory data is stored in a section that is separate from another set of data. Nevertheless, queries are combined from all the modules without having to change their structure. Since all the data is combined into one single database, power outage or corrupted database may result in loss of information.

3.2. FUNCTIONS
The Database Management System performs the following functions.

Data Dictionary Management Data Storage Management Data Transformation and Presentation Security Management Multi User Access Control Backup and Recovery Management Data Integrity Management Database Access Languages and Application Interface Database Communication Interface

TO BULID A DATABASE OF STUDENT MANAGEMENT

3.2.1. DATA DICTIONARY MANAGEMENT The data dictionary stores the definitions of data elements and their relationships.This information is termed as metadata.The metadata includes definition of data, data types, relationship between data, integrity constraints etc. Any changes made in a database structure are automatically reflected in the data dictionary. In short the DBMS provides data abstraction and it removes structural and data dependency from the system.

3.2.2. DATA STORAGE MANAGEMENT The DBMS creates the complex structures required for data storage. The users are freed from defining,programming and implementing the complex physical data characteristics.

3.2.3. DATA TRANSFORMATION AND PRESENTATION DBMS supports data independence. Hence the DBMS translate logical request into commands that physically locate and retrieve the requested data. The DBMS formats the physically retrieved data according to the logical data format specifications.

3.2.4. SECURITY MANAGEMENT The DBMS creates a security system that enforces user security and data privacy within the database. Security rules determine the access rights of the users. Read/write access is given to the user is specified using access rights.

3.2.5. MULTIUSER ACCESS CONTROL The DBMS ensures that multiple users can access the database concurrently without compromising the integrity of the database. Hence the database ensures data integrity and data consistency.

10

TO BULID A DATABASE OF STUDENT MANAGEMENT

3.2.6. BACKUP AND RECOVERY MANAGEMENT The DBMS provide backup and data recovery procedures to ensure data safety and integrity. DBMS system provide special utilities which allow the DBA to perform routine and special backup and restore procedures. Recovery Management deals with the recovery of the database after a failure.

3.2.7. DATA INTEGRITY MANAGEMENT The DBMS promotes and enforce integrity rules to eliminate data integrity problems, thus minimizing the data redundancy and maximizing data consistency.

3.2.8. DATABASE ACCESS LANGUAGES AND APPLICATION INTERFACE The DBMS provides data access via query language. A query language is a nonprocedural language, that is the user only need to specify what must be done without specifying how it is to be done. The DBMS's query language contains two components: a data definition language(DDL) and a data manipulation

language(DML). The DBMS also provide data access to programmers via programming languages.

3.2.9. DATABASE COMMUNICATION INTERFACES Different users may access the database through a network environment.So the DBMS provide communication functions to access the database through computer network environment.

11

TO BULID A DATABASE OF STUDENT MANAGEMENT

3.3. ENTITIES
An entity is an object that exists and is distinguishable from other objects. An entity may be concrete (a person or a book, for example) or abstract. An entity is represented by a set of attributes. Entities to be used in our project of student database are: 1. Computer Students 2. Economic Students 3. IT Students 4. Student record 5. Subjects 6. Faculty 7. Designation 8. City 9. Department 10. Department Details 11. Students Details 12. Faculty Details

3.4. ATTRIBUTES
An attribute is a function which maps an entity set into a domain. One can characterize a DBMS as an "attribute management system" where attributes are small chunks of information that describe something. Attributes to be used against each entity in our project are:

1. Computer Students
a) b) c) d) e) f) g) COM_ST_ID COM_ST_NAME COM_ST_AGE COM_ST_FATHER COM_ST_CONTACT COM_ST_DOMICILE COM_ST_SEMESTER
12

TO BULID A DATABASE OF STUDENT MANAGEMENT

2. Economics Students
a) b) c) d) e) f) g) ECO_ST_ID ECO_ST_NAME ECO_ST_AGE ECO_ST_FATHER ECO_ST_CONTACT ECO_ST_DOMICILE ECO_ST_SEMESTER

3. IT Students
a) b) c) d) e) f) g) IT_ST_ID IT_ST_NAME IT_ST_AGE IT_ST_FATHER IT_ST_CONTACT IT_ST_DOMICILE IT_ST_SEMESTER

4. Student record
a) ST_ID b) GPA c) CGPA

5. Subjects
a) SUBJECT_ID b) SUBJECT_NAME c) CREDIT_HRS

6. Faculty
a) b) c) d) e) f) g) h) FAC_NAME FAC_ID QUALIFICATION DOB CITY_ID PAY FAC_EMAIL FAC_CONTACT

13

TO BULID A DATABASE OF STUDENT MANAGEMENT

7. Designation
a) DESG_NAME b) DESG_ID c) DESG_TYPE

8. City
a) CITY_ID b) CITY_NAME c) CITY_PSTLCODE

9. Department
a) b) c) d) e) f) DEPT_ID DEPT_NAME DEPT_ADDRESS DEPT_CONTACT DEPT_EMAIL DEPT_HOD

10. Department Details

a) b) c) d) e) DEPT_ID ECO_STUDENT_IDD IT_STUDENT_IDD COM_STUDENT_IDD FCT_IDD

11. Faculty Details

a) FACT-DET_ID b) FACT_CITY c) FACT_DESG

12. Final Details

13. ST_DETAIL_DD 14. DEPT_DETAIL_DD 15. DEPARTMENT_DD

14

TO BULID A DATABASE OF STUDENT MANAGEMENT

4. ER DIAGRAM
Also called an entity-relationship model, a graphical representation of entities and their relationships to each other, typically used in computing in regard to the organization of data within databases or information systems. An entity is a piece of data-an object or concept about which data is stored. A relationship is how the data is shared between entities. There are three types of relationships between entities:

4.1. ONE-TO-ONE
This type of relationship takes place when a single occurrence of an entity is related to just one occurrence of a second entity.

For example, a roof covers one building; a building is covered by one roof. A One-to-One relationship is shown on the diagram by a line connecting the two entities.

4.2. ONE-TO-MANY
This type of relationship takes place when a single occurrence of an entity is related to many occurrences of a second entity. For example, an employee works in one department; a department has many employees. A One-to-Many relationship is shown on the diagram by a line connecting the two entities with a 'crow's foot' symbol denoting the 'many' end of the relationship.

4.3.

MANY-TO-MANY

This type of relationship takes place when multiple occurrences of an entity are related to multiple occurrences of a second entity. For example, many employees can be involved in many projects at a given time.

15

TO BULID A DATABASE OF STUDENT MANAGEMENT

ST_NAME SUBJECT_ID CITY_ID ST_SEMESTER

ST_CONTACT

ST_TYPE DESG_ID ST_DOB SUBJECT_ID

STUDENTS

ST_GENDER
OPT

SUBJECT
SUBJECT_NAME

ST_EMAIL ST_ID
STUDY IN HAVE

ST_ADDRESS

CREDIT_HR S

GPA

DEPT_CONTACT

DEPT_ID

DEPARTMENT
DEPT_NAMEE HOD_NAME DEPT_EMAIL ST_ID

STUDENT RECORD

CGPA DEPT_ADDRESS

WORKS 4

DESG_ID

PAY

FACULTY
FAC_ID QUALIFICATION

FAC_EMAIL

DESIGNATION

FAC_CONTACT

DESG_ID

DESG_NAME

TYPE

FAC_NAME

DOB

CITY_ID

CITY

CITY_PSTLCODE

ER-DIAGRAM
16

CITY_NAME

CITY_ID

TO BULID A DATABASE OF STUDENT MANAGEMENT

COM_ST_ID

COM_ST_NAM

ECO_ST_ID ECO_ST_CON T ECO_ST_DO M

ECO_ST_NAM

IT_ST_NAM IT_ST_CONT

IT_ST_ID

COM_ST_CON T COM_ST_DOM COM_ST_FAT

M

ECO_ST_FAT

IT_ST_DOM

IT_ST_FAT

COMP_STUDENT

ECNOMIC_STUDENT
IT_ST_SEM

IT_STUDENT
IT_ST_AGE

COM_ST_SEM

COM_ST_AGE

ECO_ST_SEM

ECO_ST_AGE

FAC_ID DOB

FAC_NAME

DEPT_NAM E DEPT_HOD

DEPT_ID
CGPA GPA

FACULTY
PAY QUALIFICATION FAC_CONTACT

DEPARTMENT
DEPT_CONT
DEPT_EMAIL

STUDNT RECORD

ST_ID

ECO_ST_IDD

IT_ST_IDD

FINAL_DET_DD

ST_DETAIL_DD

FACULTY DETAIL

DEPARTMENT DETAIL

FINAL DETAIL

DEPT_ID FACT_DET_ID FACT_CITY FACT_DESG COM_ST_IDD D FCT_IDD

DEPT_DETAIL_D

DEPT_DD

SUBJECT

DESIGNATION

CITY

SUBJECT_ID

DESG_TYPE DESG_ID DESG_NAME

CITY_NAME

SUBJECT_NAME

EA

CREDIT_HR

CITY_ID

CITY_PSTLCD

ER-DIAGRAM
17

TO BULID A DATABASE OF STUDENT MANAGEMENT

5. NORMALIZATION
Database normalization is the process of organizing the fields and tables of a relational database to minimize redundancy and dependency. Normalization usually involves dividing large tables into smaller (and less redundant) tables and defining relationships between them. The objective is to isolate data so that additions, deletions, and modifications of a field can be made in just one table and then propagated through the rest of the database via the defined relationships. While designing a database out of an entityrelationship model, the main problem existing in that raw database is redundancy. Redundancy is storing the same data item in more one place. A redundancy creates several problems like the following: Extra storage space: storing the same data in many places takes large amount of disk space. Entering same data more than once during data insertion. Deleting data from more than one place during deletion. Modifying data in more than one place. Anomalies may occur in the database if insertion, deletion, modification etc are no done properly. It creates inconsistency and unreliability in the database. To solve this problem, the raw database needs to be normalized. This is a step by step process of removing different kinds of redundancy and anomaly at each step. At each step a specific rule is followed to remove specific kind of impurity in order to give the database a slim and clean look. Database designed based on ER model may have some amount of inconsistency, ambiguity and redundancy. To resolve these issues some amount of refinement is required. This refinement process is called as Normalization. Normalization Avoids: Duplication of Data - The same data is listed in multiple lines of the database Insert Anomaly - A record about an entity cannot be inserted into the table without first inserting information about another entity - Cannot enter a customer without a sales order Delete Anomaly - A record cannot be deleted without deleting a record about a related entity. Cannot delete a sales order without deleting all of the customer's information.

18

TO BULID A DATABASE OF STUDENT MANAGEMENT

Update Anomaly - Cannot update information without changing information in many places. To update customer information, it must be updated for each sales order the customer has placed.

5.1. FORMS OF NORMALIZATION

Normalization is a Six stage process - After the first stage, the data is said to be in first normal form, after the second, it is in second normal form, after the third, it is in third normal form and so on.

Let us finally summarize the normalization steps we have discussed so far. Input Transformation Output Relation Relation All Relations 1NF Relation 2NF 3NF Eliminate variable length record. Remove multi-attribute lines in table. Remove dependency of non-key attributes on part of a multi-attribute key. Remove dependency of non-key attributes on other non-key attributes. Remove dependency of an attribute of a multi attribute key on an attribute of another (overlapping) multi-attribute key. Remove more than one independent multivalued dependency from relation by splitting relation. Add one relation relating attributes with multivalued dependency. 1NF 2NF 3NF BCNF

BCNF

4NF

4NF

5NF

19

TO BULID A DATABASE OF STUDENT MANAGEMENT

6. SNAPSHOTS OF TABLES 6.1. ALL ENTITIES

6.2. FACULTY

20

TO BULID A DATABASE OF STUDENT MANAGEMENT

6.3. DEPARTMENT

6.4. DESIGNATION

21

TO BULID A DATABASE OF STUDENT MANAGEMENT

6.5. ECONOMICS STUDENT

6.6. COMPUTER STUDENT

22

TO BULID A DATABASE OF STUDENT MANAGEMENT

6.7. FACULTY DETAIL

6.8. DEPARTMENT DETAIL

23

TO BULID A DATABASE OF STUDENT MANAGEMENT

6.9. FINAL DETAIL

6.10.DESC QUERY

24

TO BULID A DATABASE OF STUDENT MANAGEMENT

7. CONCLUTION
In conclusion, a database is a far more efficient mechanism to store and organize data than spreadsheets; it allows for a centralized facility that can easily be modified and quickly shared among multiple users. Having a web based front end removes the requirement of users having to understand and use a database directly, and allows users to connect from anywhere with an internet connection and a basic web browser. It also allows the possibility of queries to obtain information for various surveys. Due to the number of users reading and modifying student data in the department, it is an ideal use for such a system. While this project has supplied the basics for a system to keep track of students, many further enhancements are desired for greater control of the information.

25