Main Sample

CHAPTER NO. TITLE PAGE NO.
1.1 Database Environment System 4

1.2 Advantages of Using DBMS Approach 5
1.3 Architecture of Database 7

2. INTRODUCTION TO PROJECT 8
2.1 Brief Description 8
2.2 Scope 9
2.3 Table Description 10
2.3.1 Users 10
2.3.2 Admin 10
2.3.3 Courses 10
3. DESIGN 11
3.1 ER Diagram 11
3.2 Normalization 12
3.3 Schema Diagram 13

4. HARDWARE AND SOFTWARE REQUIREMENTS 14
4.1 Functional and non-functional requirements 14
4.1.1 Functional or specific requirements 14
4.1.2 Non-functional Requirements 14

4.2 Hardware Requirements 14
4.3 Software requirements 15

4.3.1 Server side 15
4.3.2 Client side 15
4.3.1.1 PHP 15
4.3.1.2 Web Server: Apache
4.3.1.3 HTML
4.3.1.4 Xampp
CONCLUSION
FUTURE ENHANCEMENT
REFERENCES
APPENDIX „A‟ – CODE SNIPPETS
A.1 Database Connection
A.2 Insert Query
A.3 Fetch Query
A.4 Delete Query
APPENDIX „B‟ – SCREENSHOTS
B.1 Home Page
B.2 Login Page
B.3 Dashboard Page
B.4 Student List Page
B.5 Courses List Page
B.6 Teachers ListPage
COLLEGE DATABASE MANAGEMENT SYSTEM 2022-23
INTRODUCTION
The college data management contains data related to the
college, i.e. various departments in the college, courses in a
department, the instructors teaching that course and the
students studying various courses. The E-R Diagram and the
Relational Schema for the college data has also been made.
The preceding definition of a database is quite general, for

example, we may consider the collection of words that make up
this page of text to be related data and hence to constitute a
database. However, the common use of the term database is
usually more restricted. A database has the following properties.
A database is a logically coherent collection of data with some

inherent meaning. A random assortment of data cannot correctly
be referred to as a database.
A database is designed, built and populated with data for a
specific purpose. It has an intended group of users and some
preconceived applications in which these users are interested.
.A database can be of any size and complexity. A database may

SIET
be generated and maintained manually or computerized. For

example, a library card catalogue is a database thatmay be
created and maintained manually. A computerized database may
be created and
maintained either by a group of application programs written
specifically for that task or by a database management system.
A database is a collection of data, typically describing the
activities of one or more related organizations. For example, a
university database might contain information about the
following
Entities such as students, faculty, courses, and classrooms.

Relationships between entities, such as student’s enrolment in
courses, faculty teaching courses, and the use of rooms for
courses
File system versus DBMS
To understand the need for a DBMS, let us consider a motivating

scenario: a company has a large collection (say 500 GB) of data
on employees, departments, products, sales, and so on. This data
is accessed concurrently by several employees. Questions about
the data must be answered quickly, changes made to the data by
different users must be applied consistently and access to certain
parts of the data must be restricted. We can try to manage the
data by storing it in operating system files. This approach has
many drawbacks, including the following
● We probably do not have 500GB of main memory to hold all
the data. We must, therefore, store data in a storage device such
as a disk or tape and bring relevant parts into the main memory
for processing as needed.
● Even if we have 500 GB of main memory, on computer
SIET
systems with 32 bit addressing, we cannot refer directly to more

than about 4 GB of data. We have to program some method of
identifying all data items.
● We have to write special programs to answer each question
a user may want to ask about the data. These programs are likely
to be complex because of the large volume of data to be
searched.
● We must protect the data from the inconsistent changes
made by different users accessing the data concurrently. If
applications must address the details of such concurrent access,
this adds greatly to their complexity.
● We must ensure that the data is restored to a consistent
state if the system crashes while changes are being made.
● Operating systems provide only a password mechanism for
security. This is not sufficiently flexible to enforce security
policies in which different users have permission to access
different subsets of the data.
A DBMS is a piece of software designed to make the preceding
tasks easier. By storing data in DBMS rather than as a collection
of operating system files, we can use the DBMS’s features to
manage the data in a robust and efficient manner. As the volume
of data and the number of users grow hundreds of gigabytes of
data and thousands of users are common in current corporate
database DBMS support becomes indispensable.
1.1 DATABASE ENVIRONMENT SYSTEM

SIET
A database management system (DBMS) is a collection of

programs that enables users to create and maintain a database.
The DBMS is a general-purpose software system that facilities the
processes of defining, constructing, manipulating and sharing
databases among
various users and applications. Defining a database involves
specifying the data types, structures and constraints of the data
to be stored in the database.
The database definition or description information is also stored

by the DBMS in
the form of a database catalogue or dictionary, it is called
Metadata. Constructing the database is the process of storing the
data on some storage medium that is controlled by the DBMS.
Manipulating a database includes functions such as querying the
database to retrieve specificdata, updating the database to
reflect changes in the mini world and generating reports from the
data. Sharing a database allows multiple users and programs to
access the database simultaneously.
An application program accesses the database by sending queries

or requests for data
to DBMS. A query typically causes some data to be retrieved; a
transaction may cause some data to be read and some data to be
written into the database.
Other important functions provided by DBMS include protecting

the database and maintaining it over a long period of time,
protection includes system protection against hardware or
software malfunction and security protection against
SIET
unauthorized or malicious access. A typical large database may

have a life cycle of many years, so the DBMSmust be able to
maintain the database system by allowing the system to evolve
as requirements change over time.
It is not absolutely necessary to use general-purpose DBMS

software to implement a computerized database. We could write
our own set of programs to create and maintain the database, in
effect creating our own special purpose DBMS software. In either
case, whether we use a general-purpose DBMS or not we usually
have deployed a considerable amount of complex software. In
fact, most DBMSs are very complex software systems. Fig 1.1
shows a simplified database environment system
1.2 ADVANTAGES OF USING DBMS APPROACH
Using a DBMS to manage data has many advantages:

● Data independence: application program should not, ideally,
be expected to details of data representation and storage, the
DBMS provides an abstract view of the data that hides such
details.
● Efficient Data Access: A DBMS utilizes a variety of
sophisticated techniques to store and retrieve data efficiently.
This feature is especially important if the data is to be stored on
an external device.
● Data integrity and security: if data is always accessed
through DBMS, the DBMS can enforce integrity constraints. For
example, before inserting salary information for an employee,
the DBMS can check that the department budget is not
exceeded.
Also, it can enforce access controls that govern what data is
SIET
visible to different classes of users.

● Data Administration: when several users share data,
centralizing the administration of data can offer significant
improvements. Experienced professionals who understand the
nature of the data being managed, and how different groups of
users use it, it can be responsible for organizing the data
representation to minimize redundancy and for fine-tuning the
storage of the data to make retrieval efficient.
● Concurrent Access and Cash Recovery: A DBMS schedules
concurrent accesses to the data in such a manner that users can
think of the data as being accessed by only one user at a time.
Further, the DBMS protects users from the effects of system
failures.
● Reduced Application Development Time: clearly, the DBMS
supports important functions that are common to many
applications accessing data in the DBMS. This, in conjunction with
the high-level interface to data, facilities quick application
development. DBMS applications are also likely to be more
robust than a similar stand-alone application because many
important tasks are handled by the DBMS.
1.3 ARCHITECTURE OF DATABASE Three-Schema Architecture

The goal of the three-schema architecture illustrated in the figure
SIET
is to separate the user application from the physical database. In

this architecture, schemas can be defined at the following three
levels:
● The internal level has an internal schema, which describes

the physical storage structure of the database. The internal
schema uses a physical data model and describes the complete
details of data storage and access paths for the database.
● The conceptual level has a conceptual schema, which
describes the structure of the whole database for a community of
users. The conceptual schema hides the details of physical
storage structures and concentrates on describing entities, data
types, relationships, user operations, and constraints. Usually, a
representational data model is used to describe the conceptual
schema when a database system is implemented. This
implementation conceptual schema is often based on a
conceptual schema design in a high-level data model.
● The external or view level includes a number of external
schemas or user views. Each external schema describes the part
of a database that a particular user group is interested in and
hides the rest of the database from that user group. As in the
previous level, each external schema is typically implemented
using a representational data model, possibly based on external
schema design in a high level data model.
Fig 1.2 shows the architecture of DBMS.
CHAPTER 2
SIET
INTRODUCTION TO PROJECT
STUDENT INFORMATION MANAGEMENT SYSTEM
2.1 Brief description
● The mini-project entitled “Student Information management

system” is developed as a partof the fifth semester DBMS
laboratory, for the partial fulfilment of the
requirement for the BE(Computer Science and Engineering)
course.
● Student Information Management System can be used by

education institutes to maintain the records of students easily.
Achieving this objective is difficult using a manual system as the
information is scattered, can be redundant and collecting
relevant information may be very time consuming. All these
problems are solved using this project.
Objectives
The objective of the Student Information management system

Project is to design to fully automate the process of managing
the student information.That is:-
▪ Online registration of students
▪ Maintenance of student records
▪ Searching student records
▪ Delete the student record if necessary
SIET
2.2 Scope
• Without Student information System, managing and
maintaining the details of the student is a tedious job for any
organization.
• Student Information system will store all the details of the
students including their background information, personal details
and all the information related to them
• Login module: Login module will help in authentication of
user accounts
.Users who have valid login id and password can only login into
their respective accounts.
• Registration Module and Account Management: This
module will help the student get registered from anywhere if
internet is present .This module will really simplify the task of on
paper registration. Also after successful registration the user can
update information and change their password as and when
required
• Purpose of project is to maintain details of the students such
as storing information about:
 Student name
 Student phone
 Courses
 Teacher name
Analysis
Student Information management system is an online student
website. This website is mainly created to store the student
details, it comprises of the following properties:-
● A central database that will store all information.
● An online website that will provide real- time information
about the student details and dashboard.
SIET
● Every registered user is able to view his dashboard that

contains all the details of courses and teachers name.
● Every registered user can delete the his/her information any
time he/she wants to change.
2.3 Table description
2.3.1 USERS
USERS table has a attributes id,username,password,email is

shown in table 2.1
TABLE 2.1 STRUCTURE OF USERS
2.3.2 ADMIN
ADMIN table has attributes tid,name,phone,subject, and tid is

used as a primary key as shown in table 2.
SIET
TABLE 2.2 STRUCTURE OF ADMIN
2.3.3 COURSES
COURSES table has the attribute cid,cname,code and cid is used

as primary key is shown in the table 2.
TABLE 2.3 STRUCTURE OF COURSES
SIET
Chapter 3
ER DIAGRAM
The E-R data model employs three basic concepts: entity sets,
relationship sets, and attributes
1. ENTITY SETS
An entity is a “thing” or “object” in the real world that is
distinguishable from all other objects. An entity has a set of
properties, and the values for some set of properties may uniquely
identify an entity. An entity set is a set of entities of the same type
that share the same properties, or attributes. Each entity has a
value for each of its attributes. A database thus includes a
collection of entity sets, each of which contains any number of
entities of the same type.
2. RELATIONSHIP SETS
A relationship is an association among several entities. A
relationship set is a set of relationships of the same type. The
association between entity sets is referred to as participation. A
relationship instance in an E-R schema represents an association
between the named entities in the real-world enterprise that is
being modeled. The function that an entity plays in a relationship
is called that entity’s role. A relationship may also have attributes
called descriptive attributes. The number of entity sets that
participate in a relationship set is the degree of the relationship
set. A binary relationship set is of degree 2; a ternary relationship
SIET
set is of degree 3.
3. ATTRIBUTES
An attribute of an entity set is a function that maps from the entity
set into a domain. For each attribute, there is a set of permitted
values, called the domain, or value set, of that attribute. The
attribute values describing an entity constitute a significant
portion of the data stored in the database. An attribute, as used in
the E-R model, can be characterized by the following attribute
types:
 Simple and composite attributes. Simple attributes cannot be

divided into subparts. Composite attributes can be divided
into subparts (that is, other attributes).
 Single-valued and multivalued attributes. Singled value
attributes are attributes having a single value. Attributes that
have more than one value are called multivalued attributes.
Where appropriate, upper and lower bounds may be placed
on the number of values in a multivalued attribute.
 Derived attribute. The value for this type of attribute can be
derived from the values of other related attributes or entities.
The value of a derived attribute is not stored but is computed
when required.
E-R diagram can express the overall logical structure of a
database graphically. E-R diagrams are simple and clear—
qualities that may well account in large part for the widespread
use of the E-R model.
An E-R diagram consists of the following major components:
 Rectangles divided into two parts represent entity sets.
 Diamonds represent relationship sets.
SIET
 Undivided rectangles represent the attributes of a relationship

set. Attributes that are part of the PRIMARY KEY are
underlined.
 Lines link entity sets to relationship sets.
SIET
Entities and their attributes used in this E-R diagram are:

 STUDENT
- USN NUMBER
- NAME
- DATE OF BIRTH
SIET
- MOBILE NUMBER
- ADDRESS
 INSTRUCTOR
- ID
- NAME
- DATE OF BIRTH
- MOBILE NUMBER
- ADDRESS
 DEPARTMENT
- NAME
- HOD
- NUMBER OF STUDENTS
- NUMBER OF COURSES
 COURSES
- COURSE ID
- COURSE NAME
RELATIONAL SCHEMA
A relational schema is a set of relational tables and associated

items that are related to one another. It is the basic information
SIET
describing a table and its relation. It is the logical definition of a

table. Relation schema defines what the name of the table is. This
includes the attributes of the table, the PRIMARY KEY, the
referenced Foreign Keys of the table and the relations of the table.
Tables used in Relational Schema:
 STUDENT(USNNO, NAME, DATE_OF_BIRTH,

MOBILENO, ADDRESS, DEPARTMENT)
 COURSES(ID, NAME, INSTRUCTOR, DEPARTMENT)
 ATTENDS(USNNO, COURSE_ID)
 INSTRUCTOR(ID, NAME, DATE_OF_BIRTH,
MOBILENO, ADDRESS, DEPARTMENT)
 TEACHES(USNNO, INSTRUCTOR_ID)
 DEPARTMENT(NAME, HOD, NUMBER_OF_STUDENTS,
NUMBER_OF_COURSES)
DESIGN
An entity–relationship model describes inter-related things
SIET
of interest in a specific domain of knowledge. An ER model is

composed of entity types and specifies relationships that can
exist between instances of those entity types.
This ER Diagram gives a brief idea about the relations existing

between the tables and
tells about the primary and the foreign keys being used in this
Database.
Figure 3.1 E R Diagram name
username email
students
USER name
teachers
subject
password courses
cname
code
3.2 NORMALIZATION
3.3.1 First Normal Form (1NF)

SIET
As the domain of all attributes of all relations in the database has

atomic value and no tuples can have a set of these values, all
relations are in 1NF.
3.3.2 Second Normal Form (2NF)

As there is no partial dependency in the database, i.e. all
nonprime attributes of a relation are fully functionally dependent
on the primary key of the relation schema, all relations are in
2NF.
3.3.3 Third Normal Form (3NF)

As all relations are in 2NF and no non-prime attribute of a
relation schema is transitively dependent on the primary key, all
relations are in 3NF.
3.3 SCHEMA DIAGRAM

SIET
A database schema can be represented in a visual diagram, which

shows the database object and their relationship which
represents the logical view of the database and how the
relationships among them are represented.
SIET
1. PURPOSE OF THE PROJECT

This project is built to keep a record of a college, the departments
of the college, the courses associated, and the information
regarding instructors and students of that college gets stored.
Information regarding the subject studied by a student, courses
taught by a instructor, number of students in a department is
stored. The project is meant to easily and efficiently access,
update, view, delete and create records of a student. Also, it
displays a list and accessing information of an instructor. The
website uses:
o HTML
o CSS
o JavaScript
o PHP
o MySQL
2. WEBSITE STRUCTURE
The website contains a homepage, which leads to a student menu page
and to another teacher menu page. The student menu contains
options to add a record, delete a record, edit existing record,
search a record using roll number and show a list of students
which can be filtered according to a department. The teacher’s
menu contains options to search a teacher using his id and view a
full teacher’s list, which can be filtered department-wise.
SIET
3. PAGE DESCRIPTIONS
i. HOME
Home page contains links to go to access student’s menu or
teacher’s menu.
ii. STUDENT MENU

This page contains options to Add a student record, search a
student record, edit an existing student record, delete a student
record and show a list of students. It also contains links to go
back to home page or go to the Teacher’s Menu.
iii. ADD A STUDENT

This page contains a form which requires the basic information
of a student, his name, roll number, date of birth, mobile
number(optional), address(optional), department, and his 5
subjects. A front-end validation is done using HTML to check
format of Name, roll number and mobile number, and also to
ensure required fields are not empty. A back-end validation is
done to ensure none of the fields is empty, and also to check
whether the record being added already exists (using roll
number). If the data doesn’t exist, it displays an alert box
showing message “data entered successfully”. An arrow button
is provided to go back to Student Menu.
iv. SEARCH STUDENT

This page contains a search bar to retrieve information of a student,
using his roll number. A front-end validation is done using
HTML to ensure the roll number is in correct format (6 digits).
A back-end validation is done to ensure the student being
searched exists. If the student doesn’t exist, an error message is
shown in the same page. Else, redirection to another page is
done which displays all the information of student, Name, Roll
Number, Department, Date of Birth, Mobile, Address, Subjects
studying and corresponding instructor. Both these pages
SIET
contain an arrow to go back to previous page (Student Menu

and Search Page respectively).
v. EDIT STUDENT
This page contains an interface similar to the search page button. It
searches the entered value, with front end validation. If the
student does not exist, it displays an error message. Else, we
get redirected to another page which contains a form with
checkboxes to tick which values need to be edited, and an input
field to input the aforementioned values, using front end
validation. After submitting the form, we are redirected to a
page which gives a list of changes done.
vi. DELETE STUDENT

This page contains an interface similar to the search button. A
front-end validation is done to check whether data is entered in
correct format. A back-end validation is done to ensure that the
data entered exists. If it exits, a message confirming the
deletion is shown. Else, an error message showing data doesn’t
exist is shown.
vii. SHOW STUDENT LIST

This page displays a list of students in tabular form. It displays their
Roll Number, Name, Date of Birth, Mobile, Address and
Department using columns of a table. A student record is
displayed in row. A filter button is provided at top which can
filter out the records according to the department of a student.
viii. TEACHER MENU

This page contains record to search a teacher according to his id,
and display a list of all instructors, which can be filtered
according to their department. This page also contains links to
go back to home page or to Student’s Menu.
SIET
ix. SEARCH TEACHER

This page contains a search bar to search a teacher using his id. A
front-end validation is done using HTML to ensure correct id
format is entered (2 to 3 lowercase alphabets). A back-end
validation is done to ensure teacher with the inputted it exists.
If it exists, we are redirected to a page displaying the
information of the required teacher (Name, ID, Department,
Date of Birth, Mobile Number, Address, and a list of courses
taught).
x. SHOW TEACHER LIST

This page displays a list of teachers in tabular form. It displays their
ID, Name, Date of Birth, Mobile, Address and Department
using columns of a table. A teacher record is displayed in row.
A filter button is provided at top which can filter out the
records according to the department of a teacher.
SIET
4. REQUIREMENTS
This project is expected to run on all modern web browsers. No
responsive design has been added as yet.
4.3.1 Server side

1. Programming language: PHP 5.6.31
2. Web Server: Apache 2.4.27
3. Database: SQL 5.7.19
4.3.2 Client side

1. Programming language: JAVASCRIPT, HTML, CS
2. OS: windows7/8/10
3. MYSQL server
SIET
4.3.1.1 PHP
PHP is a server-side scripting language designed primarily for

web development but also used as a general programming
language PHP code may be embedded into HTML or HTML5
mark-up or it can be used in combination with various web
template systems, web content management systems, and web
frameworks. PHP code is usually processed by a PHP interpreter
implemented as a module in the web server. The web server
software combines the results of the interpreted and executed PHP
code, which may be any type of data, including images, with the
generated webpage.
4.3.1.2 WEB SERVER: APACHE
Apache is the most widely used web server software. Developed

and maintained by Apache Software Foundation, Apache is open-
source software available for free. It runs on 67% of all web
servers in the world. It is fast, reliable, and secure. It can be highly
customized to meet the needs of many different environments by
using extensions and modules. Most WordPress hosting providers
use Apache as their web server software. However, WordPress
can run on other web server software as well.
4.3.1.3 HTML
HTML is an acronym that stands for HyperText Markup

SIET
Language.
HyperText: HyperText simply means "Text within Text". A text
has a link within it, is a hypertext. Every time you click on a word
that brings you to a new webpage, you have clicked on a
hypertext.
Markup language: A markup language is a programming language
that is used to make text more interactive and dynamic. It can turn
a text into images, tables, links, etc. An HTML document is made
of many HTML tags and each HTML tag contains different
content.
4.3.1.5 XAMPP
XAMPP is a small and light Apache distribution containing

the most common web development technologies in a single
package. Its contents, small size, and portability make it the ideal
tool for students developing and testing applications in PHP and
MySQL. XAMPP is available as a free download in two specific
packages: full and lite. While the full package download provides
a wide array of development tools, XAMPP Lite contains the
necessary technologies that meet the Ontario Skills Competition
standards.The light version is a small package containing Apache
HTTP Server, PHP, MySQL, phpMyAdmin, Openssl, and SQLite.
SIET
CONCLUSION
Student information management system lead to a better

organization structure since the information management of the
students is well structured and also lead to better as well as
efficient utilization of resources.
Student Information Management System can be used by

education institutes to maintain the records of students easily.
Achieving this objective is difficult using a manual system as the
information is scattered, can be redundant and collecting relevant
information may be very time consuming. All these problems are
solved using this project.
SIET
FUTURE ENHANCEMENT
● We can even further make it private and secured by

implementing Log- in IDs and encrypting them with passwords.
● We can give away this software for more number of
institutes and organizations to conduct a Beta Testing and based
upon the results we can just make those changes and be assured of
the application developed.
● We can make it more space and resource efficient so that this
application consumes lesser RAM and ROM and battery power (if
available).
SIET
REFERENCES
[1] http://php.net/
[2] https://www.http://en.wikipedia.org/wiki/PHP
[3] https://www.w3shools.com
APPENDIX „A‟- CODE SNIPPETS
A.1 DATABASE CONNECTION

The connect() / mysqli_connect() function opens a new
connection to the MySQL server with the following syntax :
mysqli_connect($DATABSE_HOST,$DATABASE_USER,
$DATABASE_PASS,$DATABA SE_NAME)
FIG A.1 DATABASE CONNECTION
A.2 INSERT QUERY

This query is used to insert a course .
SIET
A.3 FETCH QUERY

In this query,all the details are fetched
FIG A.3 FETCH QUERY
A.4 DELETE QUERY

Here the update query is called to Delete the course of an already
existing based on its id using DELETE command.
FIG A.4 DELETE QUERY
SIET
APPENDIX „B‟- SCREENSHOTS
B.1 HOME PAGE
B2 STUDENT DASHBOARD PAGE
SIET
This page allows student to visit their dashboard and see the details and make
changes to data base as shown in Fig B.3
B2 TEACHER DASHBOARD PAGE
This page allows teacher to visit their dashboard and see the
details and make changes to data base as shown in Fig B.3
B.4 STUDENT LIST PAGE

This page allows admin to find the students and delete if
necessary as shown in the FigB.4
SIET
FIG B.4 STUDENT LIST PAGE
B.5 TEACHER LIST PAGE

This page allows admin to see courses available as show in the
Fig B.5
SIET
B.6 SEARCH STUDENT BY USN NUMBER
B.7 SEARCH STUDENT BY USN NUMBER
SIET
B.8 EDIT STUDENT BY USN NUMBER
SIET

Main Sample

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Main Sample

Uploaded by

Copyright:

Available Formats

CHAPTER NO. TITLE PAGE NO.

1.1 Database Environment System 4

1.3 Architecture of Database 7

3.3 Schema Diagram 13

4.1.2 Non-functional Requirements 14

4.3 Software requirements 15

The preceding definition of a database is quite general, for

A database is a logically coherent collection of data with some

.A database can be of any size and complexity. A database may

be generated and maintained manually or computerized. For

Entities such as students, faculty, courses, and classrooms.

File system versus DBMS

To understand the need for a DBMS, let us consider a motivating

systems with 32 bit addressing, we cannot refer directly to more

1.1 DATABASE ENVIRONMENT SYSTEM

A database management system (DBMS) is a collection of

The database definition or description information is also stored

An application program accesses the database by sending queries

Other important functions provided by DBMS include protecting

unauthorized or malicious access. A typical large database may

It is not absolutely necessary to use general-purpose DBMS

1.2 ADVANTAGES OF USING DBMS APPROACH

Using a DBMS to manage data has many advantages:

visible to different classes of users.

1.3 ARCHITECTURE OF DATABASE Three-Schema Architecture

is to separate the user application from the physical database. In

● The internal level has an internal schema, which describes

STUDENT INFORMATION MANAGEMENT SYSTEM

2.1 Brief description

● The mini-project entitled “Student Information management

● Student Information Management System can be used by

The objective of the Student Information management system

▪ Maintenance of student records

▪ Searching student records

▪ Delete the student record if necessary

● Every registered user is able to view his dashboard that

USERS table has a attributes id,username,password,email is

TABLE 2.1 STRUCTURE OF USERS

ADMIN table has attributes tid,name,phone,subject, and tid is

TABLE 2.2 STRUCTURE OF ADMIN

COURSES table has the attribute cid,cname,code and cid is used

TABLE 2.3 STRUCTURE OF COURSES

 Simple and composite attributes. Simple attributes cannot be

 Undivided rectangles represent the attributes of a relationship

Entities and their attributes used in this E-R diagram are:

A relational schema is a set of relational tables and associated

describing a table and its relation. It is the logical definition of a

 STUDENT(USNNO, NAME, DATE_OF_BIRTH,

of interest in a specific domain of knowledge. An ER model is

This ER Diagram gives a brief idea about the relations existing

Figure 3.1 E R Diagram name

3.3.1 First Normal Form (1NF)

As the domain of all attributes of all relations in the database has

3.3.2 Second Normal Form (2NF)

3.3.3 Third Normal Form (3NF)

3.3 SCHEMA DIAGRAM

A database schema can be represented in a visual diagram, which

1. PURPOSE OF THE PROJECT

ii. STUDENT MENU

iii. ADD A STUDENT

iv. SEARCH STUDENT

contain an arrow to go back to previous page (Student Menu

vi. DELETE STUDENT

vii. SHOW STUDENT LIST