Student Database Proposal
-
Upload
syed-zile-subhan -
Category
Documents
-
view
223 -
download
0
Transcript of Student Database Proposal
-
8/13/2019 Student Database Proposal
1/25
BY
STUDENT DATABASE PROPOSAL
-
8/13/2019 Student Database Proposal
2/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
2
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
-
8/13/2019 Student Database Proposal
3/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
3
TABLE OF CONTENTS
1. INTRODUCTION.............................................................................................................................. 5
1.1. BACKGROUND ...................................................................................................................... 5
1.2. GOALS ................................................................................................................................... 6
1.3. REQUIREMENTS ................................................................................................................... 6
2. IDENTIFICATION OF THE PROBLEM............................................................................................... 7
3. 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
-
8/13/2019 Student Database Proposal
4/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
4
5. NORMALIZATION.......................................................................................................................... 18
5.1. FORMS OF NORMALIZATION ............................................................................................. 19
6. SCREENSHOTS OFTABLES............................................................................................................ 20
7. 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 andenlightened 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 ofour 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.
-
8/13/2019 Student Database Proposal
5/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
5
1.INTRODUCTIONIn 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. BACKGROUNDIn 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.
-
8/13/2019 Student Database Proposal
6/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
6
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 inthe university, and to provide access to this information with an easy to useweb-based interface that can be accessed by any device with basic html
rendering capabilities.
1.3. REQUIREMENTSRequirements 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 doneso 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.
-
8/13/2019 Student Database Proposal
7/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
7
2.IDENTIFICATION OF THE PROBLEMOrganization 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
-
8/13/2019 Student Database Proposal
8/25
-
8/13/2019 Student Database Proposal
9/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
9
3.1.4. BETTER PROCESSING SPEEDThe responsiveness of data management using computer systems is better with a well-
versed 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 CODEThe 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 inloss of information.
3.2. FUNCTIONSThe 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
http://benefitof.net/benefits-of-weight-loss/http://benefitof.net/benefits-of-weight-loss/ -
8/13/2019 Student Database Proposal
10/25
-
8/13/2019 Student Database Proposal
11/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
11
3.2.6. BACKUP AND RECOVERY MANAGEMENTThe 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 MANAGEMENTThe 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 INTERFACEThe DBMS provides data access via query language. A query language is a non-
procedural 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 INTERFACESDifferent users may access the database through a network environment.So the
DBMS provide communication functions to access the database through computer
network environment.
-
8/13/2019 Student Database Proposal
12/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
12
3.3. ENTITIESAn 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 isrepresented by a set of attributes.
Entities to be used in our project of student database are:
1. Computer Students2. Economic Students3. IT Students4. Student record5. Subjects6. Faculty7. Designation8. City9. Department10.Department Details11.Students Details12.Faculty Details
3.4. ATTRIBUTESAn 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 Studentsa) COM_ST_ID
b) COM_ST_NAMEc) COM_ST_AGEd) COM_ST_FATHERe) COM_ST_CONTACTf) COM_ST_DOMICILEg) COM_ST_SEMESTER
-
8/13/2019 Student Database Proposal
13/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
13
2. Economics Studentsa) ECO_ST_ID
b) ECO_ST_NAMEc) ECO_ST_AGEd) ECO_ST_FATHERe) ECO_ST_CONTACTf) ECO_ST_DOMICILEg) ECO_ST_SEMESTER
3. IT Studentsa) IT_ST_ID
b)
IT_ST_NAMEc) IT_ST_AGEd) IT_ST_FATHERe) IT_ST_CONTACTf) IT_ST_DOMICILEg) IT_ST_SEMESTER4. Student recorda) ST_ID
b) GPAc) CGPA5. Subjectsa) SUBJECT_ID
b) SUBJECT_NAMEc) CREDIT_HRS6. Facultya) FAC_NAME
b) FAC_IDc) QUALIFICATIONd) DOBe) CITY_IDf) PAYg) FAC_EMAILh) FAC_CONTACT
-
8/13/2019 Student Database Proposal
14/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
14
7. Designationa) DESG_NAME
b) DESG_IDc) DESG_TYPE8. Citya) CITY_ID
b) CITY_NAMEc) CITY_PSTLCODE9. Departmenta) DEPT_ID
b) DEPT_NAMEc)
DEPT_ADDRESS
d) DEPT_CONTACTe) DEPT_EMAILf) DEPT_HOD10.Department Detailsa) DEPT_ID
b) ECO_STUDENT_IDDc) IT_STUDENT_IDDd) COM_STUDENT_IDDe) FCT_IDD11.Faculty Detailsa) FACT-DET_ID
b) FACT_CITYc) FACT_DESG12.Final Details13.ST_DETAIL_DD14.DEPT_DETAIL_DD15.DEPARTMENT_DD
-
8/13/2019 Student Database Proposal
15/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
15
4. ER DIAGRAMAlso 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 ofdata withindatabases or information systems. An entity is a piece of
data-anobject 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-ONEThis 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-MANYThis 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-MANYThis 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.
http://www.webopedia.com/TERM/D/data.htmlhttp://www.webopedia.com/TERM/D/database.htmlhttp://www.webopedia.com/TERM/O/object.htmlhttp://www.webopedia.com/TERM/O/object.htmlhttp://www.webopedia.com/TERM/D/database.htmlhttp://www.webopedia.com/TERM/D/data.html -
8/13/2019 Student Database Proposal
16/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
16
STUDENTS
DEPARTMENT
FACULTY
CITY
DESIGNATION
SUBJECT
STUDENT
RECORD
ER-DIAGRAM
DEPT_ID
SUBJECT_ID
ST_NAME
ST_DOB
ST_GENDER
ST_TYPEST_CONTACT
ST_ID
CITY_ID
ST_SEMESTER
ST_ADDRESS
ST_EMAIL
DEPT_CONTACT
DEPT_NAMEE
DEPT_ADDRESS
DEPT_EMAIL
HOD_NAME
FAC_ID
QUALIFICATION
TYPE
DOBCITY_ID
FAC_NAME
FAC_CONTACT
FAC_EMAIL
PAY
DESG_ID
CITY_PSTLCODE
CITY_NAMECITY_ID
DESG_ID DESG_NAME
SUBJECT_IDDESG_ID
SUBJECT_NAME
CREDIT_HR
GPA
ST_ID
CGPA
STUDY
IN
HAVE
OPT
WORKS 4
-
8/13/2019 Student Database Proposal
17/25
-
8/13/2019 Student Database Proposal
18/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
18
5. NORMALIZATIONDatabase normalization is the process of organizing thefields andtables of
arelational database to minimizeredundancy 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 dataitem 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 diskspace.
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 arelated entity. Cannot delete a sales order without deleting all of the customer's
information.
http://en.wikipedia.org/wiki/Field_(computer_science)http://en.wikipedia.org/wiki/Table_(database)http://en.wikipedia.org/wiki/Relational_databasehttp://en.wikipedia.org/wiki/Data_redundancyhttp://en.wikipedia.org/wiki/Data_redundancyhttp://en.wikipedia.org/wiki/Relational_databasehttp://en.wikipedia.org/wiki/Table_(database)http://en.wikipedia.org/wiki/Field_(computer_science) -
8/13/2019 Student Database Proposal
19/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
19
Update Anomaly- Cannot update information without changing information in manyplaces. To update customer information, it must be updated for each sales order the
customer has placed.
5.1. FORMS OF NORMALIZATIONNormalization 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
Relation
Transformation Output
Relation
All
Relations
Eliminate variable length record. Remove
multi-attribute lines in table.
1NF
1NF
Relation
Remove dependency of non-key attributes on
part of a multi-attribute key.
2NF
2NF Remove dependency of non-key attributes on
other non-key attributes.
3NF
3NF Remove dependency of an attribute of a multi
attribute key on an attribute of another
(overlapping) multi-attribute key.
BCNF
BCNF Remove more than one independent multi-
valued dependency from relation by splitting
relation.
4NF
4NF Add one relation relating attributes with multi-
valued dependency.
5NF
-
8/13/2019 Student Database Proposal
20/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
20
6. SNAPSHOTS OF TABLES6.1.ALL ENTITIES
6.2.FACULTY
-
8/13/2019 Student Database Proposal
21/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
21
6.3.DEPARTMENT
6.4.DESIGNATION
-
8/13/2019 Student Database Proposal
22/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
22
6.5.ECONOMICS STUDENT
6.6.COMPUTER STUDENT
-
8/13/2019 Student Database Proposal
23/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
23
6.7.FACULTY DETAIL
6.8.DEPARTMENT DETAIL
-
8/13/2019 Student Database Proposal
24/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
24
6.9.FINAL DETAIL
6.10.DESC QUERY
-
8/13/2019 Student Database Proposal
25/25
TO BULID A DATABASE OF STUDENT MANAGEMENT
7. CONCLUTIONIn 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.