0% found this document useful (0 votes)
11 views45 pages

Dbms Documentation

The document outlines a DBMS project titled 'Online Banking System' submitted by students from PSGR Krishnammal College for Women as part of their Bachelor of Computer Science degree requirements. It details the project's objectives, problem definitions, and the use of Oracle Database and Visual Basic .NET to create a secure online banking platform. The document also includes sections on normalization, ER diagrams, data manipulation, and integrity constraints, emphasizing the system's functionality and user-friendly design.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
11 views45 pages

Dbms Documentation

The document outlines a DBMS project titled 'Online Banking System' submitted by students from PSGR Krishnammal College for Women as part of their Bachelor of Computer Science degree requirements. It details the project's objectives, problem definitions, and the use of Oracle Database and Visual Basic .NET to create a secure online banking platform. The document also includes sections on normalization, ER diagrams, data manipulation, and integrity constraints, emphasizing the system's functionality and user-friendly design.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 45

NEWS PORTAL MANAGEMENT SYSTEM

DBMS PROJECT WORK SUBMITTED TO PSGR KRISHNAMMAL


COLLEGE FOR WOMEN IN PARTIAL FULFILLMENT OF THE
REQUIREMENTS
FOR THE AWARD OF THE DEGREE OF
BACHELOR OF COMPUTER
SCIENCE OF BHARATHIAR
UNIVERSITY, COIMBATORE – 641 046.

Submitted by

NAVYA SURESH (23BAI030)


NAVEENA SHREE A(23BAI029)
MONISHA M(23BAI028)

Guided by,
MRS.T.PRABHA KUMARI M.Sc.,M.Phil.,(Ph.D)
Assistant Professor, Department of BSC CS(AI),
PSGR Krishnammal College for Women,
Coimbatore – 641 004.

DEPARTMENT OF BSC CS(AI)


PSGR KRISHNAMMAL COLLEGE FOR WOMEN
College of Excellence
An Autonomous Institution, Affiliated to Bharathiyar University
Accredited with ‘A++’ Grade by NACC, An ISO 9001:2015 Certified Institution
Peelamedu, Coimbatore-641004. September 2024
CERTIFICATE

This is to certify that this DBMS project entitled “ONLINE BANKING SYSTEM” Submitted
to PSGR Krishnammal College for Women, Coimbatore in partial fulfillment of the requirement
for the award of the Degree of Bachelor of Computer Science is a record of original work done
by NAVYA SURESH (23BAI030),NAVEENA SHREE A(23BAI029),MONISHA
M(23BAI028) during her period of study in Department of BSC CS(AI), PSGR Krishnammal
College for Women, Coimbatore under my supervision and guidance and her DBMS Project has
not formed the basis for the award of any Degree/ Diploma/ Associate/ Fellowship or similar title
to any candidate of any university.

Forwarded by

Faculty Guide Head of the Department


MRS.T.PRABHA KUMARI Dr.M.MEERA
M. MCA., M Phil., B.Ed.,
DECLARATION

I hereby declare that the DBMS project entitled “ONLINE BANKING SYSTEM” submitted to
PSGR Krishnammal College for Women, Coimbatore for the award of the Degree of Bachelor
of Computer Science is a record of original work done by NAVYA SURESH (23BAI030)
under the guidance of MRS.T.PRABHA KUMARI Assistant Professor, Department of BSC
CS(AI), PSGR Krishnammal College for Women, Coimbatore and this project have not found
the basis for the award of any Degree/Diploma or similar title to any candidate of any university.

Place: Coimbatore NAVYA SURESH (23BAI030)


Date:

Endorsed by

Place: Coimbatore MRS.T.PRABHA KUMARI


Date:
TABLE OF CONTENTS
S.NO TITLE PAGE NO
CERTIFICATE i
DECLARATION ii
1
I CASE STUDY
1.1. Abstract 1
1.2. Problem Definition 1
1.3. Objective 1
1.4. Table Description 2
II NORMALIZATION
2.1. Entities and attributes
2.2. Cardinality and Relationships
2.3. Normal Forms Types
2.4. Normalized Table

III ER DIAGRAM
3.1 Description of ER diagram
3.2 Model of ER Diagram
3.3 Notations of ER Diagram
3.4 Primary Key Definition
3.5 Foreign Key Definition
3.6 Composite Key Definition
3.7Composite attributes
3.8 Simple attributes
3.9 Single valued attributes
3.10Multi valued attributes
3.11 Derived attributes
3.12Stored attributes
3.13 Complex attributes
3.14 Null value attributes
3.15 Key attributes
3.16 Value set of attributes
IV DATA DEFINITION LANGUAGE
4.1.Create
4.2.Alter
4.3. Drop
4.4. Truncate

V DATA MANIPULATION LANGUAGE


5.1. Select
5.2. Insert
5.3. Update
5.4. Delete

VI DATA CONTROL LANGUAGE


6.1. Grant
6.2. Revoke

VII TRANSACTION CONTROL LANGUAGE


7.1. Commit
7.2. Rollback
7.3. Savepoint
VIII DATA INTEGRITY CONSTRAINTS
8.1. Primary Key
8.2. Foreign Key
8.3. Not Null
8.4. Unique
8.5. Check
IX AGGREGATE FUNCTIONS AND SORTING
9.1. Count()
9.2. Sum()
9.3. Avg()
9.4. Min()
9.5. Max()
9.6. Ascending
9.7. Descending
X JOIN OPERATIONS
10.1. Left Join
10.2. Right Join
10.3. Inner Join
10.4. Full Join
10.5. Left Outer Join
10.6. Right Outer Join
10.7. Full Outer Join

XI SUB QUERIES
11.1. Inserting Values In a Table
11.2. Select, Displaying Values In a Table
11.3. Using Where Clause
11.4. Aggregate Functions With Select
11.5. Deleting A Row

XII VB.NET
12.1. Form Design
12.2. Connectivity
12.3. Result

XIII CONCLUSION AND SCOPE FOR FUTURE ENHANCEMENT


12.1 Conclusion
12.2 Scope For Future Enhancement

XIV BIBLIOGRAPHY
13.1 Book References
13.2 Website References
CHAPTER 1
CASE STUDY

1.1. ABSTRACT

This project focuses on the development of an Online Banking System


utilizing Oracle Database and Visual Basic .NET (Vb.Net) as the primary technologies.
The system is designed to offer users a secure and efficient platform for managing
banking activities, including account registration, balance inquiries, fund transfers, and
transaction history retrieval.

Oracle Database provides a robust and scalable environment for data storage and
management, leveraging advanced features for complex queries and data manipulation.
The integration of Vb.Net allows for the creation of an intuitive graphical user interface,
enhancing user interaction and experience.

Key features of the system include stringent security measures, such as data encryption
and user authentication, ensuring the protection of sensitive financial information.
Additionally, the project emphasizes best practices in database normalization and
transaction management to maintain data integrity. Overall, this Online Banking System
serves as a practical application of Oracle and Vb.Net, demonstrating their effectiveness
in delivering a reliable and user-friendly banking solution.

1.2. PROBLEM DEFINITION


The increasing demand for convenient banking solutions has led to the need for
an efficient Online Banking System that addresses various user requirements. Traditional
banking methods often involve time-consuming processes, limited accessibility, and
potential security risks. Key problems that this project aims to address include
Accessibility, User Management, Transaction Management and Efficiency. By addressing
these challenges, the Online Banking System aims to provide a secure, accessible, and
user-friendly solution for modern banking needs.
1.3. OBJECTIVE
Develop a web-based platform to grant users the opportunity for making
transactions at any time and from wherever, thereby ensuring continuous service around
the clock.Put in place next-level security methods like encoding and multifactor
authentication to stop hackers from looking through or tampering with user data.The task
should involve the creation of an easily operating and friendly design that would not only
make navigation between web pages a less complicated task but would also promote
customer involvement by means of user-friendly interface which allows clients to be in
control of the information that is accessible on their account.Automate circulation of
transactions in real-time, where stable amount transfers and balance verifications are
included; thus, correctness and efficiency are assured.Users can use a single one-point
access platform as well as see their account transactions and statements. Also, the bank
administrators use the functionalities offered to them to monitor transactions and generate
reports for a better operational oversight by implementing the remote management
function. Give thought to a system that allows the addition of more features and grows
according to the need of the bank and its customers. The platform should provide
educational resources to help users understand better the banking services and effective
financing management.

1.4. TABLE DESCRIPTION

The Online Banking System is designed to provide a secure platform for


users to manage their banking needs remotely. This system leverages modern
technology to offer a wide range of banking services through an intuitive web
interface and a robust backend powered by a relational database.
The Accounts table maintains record of all users account. It includes attributes like
Account ID, User ID, Account Number, Account Type, Account Balance and Created
Date.
The Transaction table logs all financial transaction made by users. It consists of
attributes like Account ID, Transaction ID, Transaction Type, Amount, Transaction
Date, Recipient Account, User ID.
The User Details table stores information about each table in the online banking
system. It includes attributes like User ID, Password, Username, Email, Phone,
Created Date.
CHAPTER II
NORMALIZATION

2.1 ENTITIES AND ATTRIBUTES

An entity type typically corresponds to one or several related tables in the


database.
Example: User, Article, Category, Comment, Advertisement, Subscription.
Attribute is defined as a characteristic or trait of an entity type that describes the
entity.
Example:
 User table: User id, Name, Email, Password, Role.
 Comment table: Comment id, Content, Comment date, Article id, User
id.
 Advertisement table: Advertisement id, Advertiser, Advertisement
Content
2.2 CARDINALITY AND RELATIONSHIP

Cardinality refers to the relationships between tables and the number of


instances of one entity that can relate to instances of another.
Types of Cardinality:
One-to-One (1:1): Each record in Table A is associated with one record in Table B.
Example: Each employee has a unique ID and one corresponding entry in a details
table.

One-to-Many (1:N): A record in Table A can be related to multiple records in Table B.


Example: A customer can have multiple orders, but each order belongs to one customer.

Many-to-One (N:1): Multiple records in Table A can relate to a single record in Table B.
Example: Many students can be enrolled in one class.

Many-to-Many (M:N): Records in Table A can relate to multiple records in Table B and
vice versa.
Example: Students and courses where each student can enroll in multiple courses, and
each course can have multiple students. This typically requires a junction table to
manage the relationships.
Relationships are defined by the cardinality and the type of relationship between two
entities. They can be used to enforce data integrity and ensure that data is consistent
across multiple tables.

2.3 NORMAL FORMS TYPES

Normal forms are guidelines for structuring a relational database to reduce


redundancy and improve data integrity.
First Normal Form (1NF) Definition: A table is in 1NF if it contains only atomic
(indivisible) values and each entry in a column is of the same data type.
Second Normal Form (2NF) Definition: A table is in 2NF if it is in 1NF and all non-key
attributes are fully functionally dependent on the primary key.
Third Normal Form (3NF) Definition: A table is in 3NF if it is in 2NF and there are no
transitive dependencies between non-key attributes.

2.4. NORMALIZED TABLE

The Online Banking System is designed to provide a secure platform for users to
manage their banking needs remotely. This system leverages modern technology to
offer a wide range of banking services through an intuitive web interface and a robust
backend powered by a relational database.

COLUMN DATA TYPE CONSTRAINTS


TYPE
User ID INT Primary Key
User Name VARCHAR(15) Unique, Not null
Password VARCHAR(15) Not Null
Email VARCHAR(15 Unique, Not null
Phone Number VARCHAR(10)
Created date DATETIME Default to
CURRENT_TIMESTAMP
CHAPTER III
ER DIAGRAM

3.1 DESCRIPTION OF ER DIAGRAM

An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how entities or
concepts relate to each other within a system. This model is used to define the data elements and
relationship for a specified system. An ER Diagram explains the logical structure and the flow of
information within a data model. An entity-relationship diagram highlights entities,attributes,and
relationships through predefined symbols for effective visualization of the architecture.

ENTITIES: Article, Author, Category, and comments. Each entity has its own set of
attributes. For example, the Article entity has attributes such as Title, Content, and Publish Date. The
Author entity has attributes such as Name, Email, and Bio.

The relationships between entities are represented by lines connecting the entities. For
example, the relationship between Article and Author is represented by a line connecting the two
entities. This relationship indicates that each article is written by one author, and each author can write
multiple articles.

Similarly, the relationship between Article and Category is represented by a line connecting
the two entities. This relationship indicates that each article can belong to one category, and each
category can have multiple articles.
3.2 NOTATIONS OF ER DIAGRAM
3.3 PRIMARY KEY DEFINITION

A primary key is an attribute or set of attributes that uniquely identifies each record in a
table. Primary keys are used to enforce data integrity and ensure that each record in a table is unique.
They can be composed of one or more attributes, and they must be unique for each record in the table.
Primary keys are used to link tables together and create relationships between them. They are an
essential part of any database management system.

S. No TABLE NAME PRIMARY KEYS

1. User UserID
2. Article ArticleID
3. Category CategoryID
4. Comment CommentID
5. Advertisement AdvertisementID
6. Subscription SubscriptionID
3.4 FOREIGN KEY DEFINITION

A foreign key is a key that links two tables together. It is a field in one table that refers to
the primary key in another table. The foreign key establishes a relationship between the two tables and
ensures referential integrity.

Foreign keys are used to enforce data integrity and ensure that data is consistent across multiple tables.
They can be used to create relationships between tables, enforce referential integrity, and improve query
performance.

S. No TABLE NAME FOREIGN KEYS

1. Comments ArticleID
UserID
2. Subscription SubscriberID

3.5 COMPOSITE KEY DEFINITION

A composite key is a key that consists of two or more attributes that uniquely identify each
record in a table. It is also known as a compound key. Composite keys are used when a single attribute
cannot uniquely identify each record in a table. Composite keys can be used to enforce data integrity and
ensure that each record in a table is unique. They can also be used to link tables together and create
relationships between them.

3.5 COMPOSITE ATTRIBUTES

Composite attributes are attributes that can be broken down into smaller sub-attributes.
They are also known as complex attributes. Composite attributes are used to represent complex data
types that cannot be represented by a single attribute.

Composite attributes can be used to improve data organization and reduce redundancy in a database
management system. They can also help improve query performance by allowing for more efficient
indexing and searching of data.
3.6 SINGLE VALUED ATTRIBUTES

Single-valued attributes are attributes that can have only one value for a single record. They
are also known as simple attributes. Single-valued attributes are the most common type of attribute in a
database management system. They are used to represent simple data types that can be represented by a
single attribute.

3.7 MULTI VALUED ATTRIBUTES

Multi-valued attributes accept one or more values that are separated with spaces
and enclosed in braces. Multi-valued attributes are attributes that can have multiple values for
a single record. They are also known as repeating groups. Multi-valued attributes can be
problematic when designing a database management system. They can lead to data redundancy
and inconsistency. To avoid these issues, it is recommended to use a separate table to store the
multi-valued attribute and link it to the original table using a foreign key.

3.8 DERIVED ATTRIBUTES

A derived attribute is an attribute or property in a table that has been calculated or


derived using other attributes in the database.Derived attributes are attributes that are calculated based
on other attributes in the same table or related tables. They are also known as virtual attributes. Derived
attributes are used to represent data that can be calculated from other data in the same table or related
tables. Derived attributes can be used to improve data organization and reduce redundancy in a database
management system. They can also help improve query performance by allowing for more efficient
indexing and searching of data.

3.9 STORED ATTRIBUTES


Stored attributes are those attributes that are stored in the physical database.
stored attributes are attributes that are derived from other attributes in the same table. They are also
known as computed attributes. Computed attributes are used to represent data that can be calculated
from other data in the same table.Computed attributes can be used to improve data organization and
reduce redundancy in a database management system. They can also help improve query performance
by allowing for more efficient indexing and searching of data.

3.10 COMPLEX ATTRIBUTES

Those attributes, which can be formed by the nesting of composite and multi-valued
attributes, are called “Complex Attributes" .Complex attributes are attributes that can be
broken down into smaller sub-attributes. They are also known as composite attributes.
Composite attributes are used to represent complex data types that cannot be represented by a
single attribute. Composite attributes can be used to improve data organization and reduce
redundancy in a database management system. They can also help improve query performance
by allowing for more efficient indexing and searching of data.

3.11 NULL VALUE ATTRIBUTES

Null value attributes are attributes that do not have a value or contain no data. They are
used to represent missing or unknown data. Null values can be assigned to any attribute in a table,
including primary keys. However, it is generally not recommended to assign null values to primary keys
as they are used to uniquely identify each record in a table . A null value is a special indicator that
represents the absence of a value.

3.12 KEY ATTRIBUTES

Key attributes are the attributes that uniquely identify each record in a table. They are also
known as primary keys. Primary keys are used to enforce data integrity and ensure that each record in a
table is unique. They can be composed of one or more attributes, and they must be unique for each
record in the table. Primary keys are used to link tables together and create relationships between them.
They are an essential part of any database management system .

3.13 VALUE SET OF ATTRIBUTES

Attributes are the characteristics that describe an entity. They are also known as
fields or columns. Attributes can be of different types such as single-valued, multi-valued,
composite, stored, and derived attributes.
CHAPTER IV

DATA DEFINITION LANGUAGE

4.1 CREATE

Create database defines a logical database under the active location root directory. The database
normally consists of a subdirectory of the same name that holds the physical table and index
files. Users can use stogroups to implicitly specify different storage directories for individual
database objects. Create table creates a table by defining its columns and each column's data type
and field length. The command can also be used to create primary and foreign keys for the table.

figure 4.1 creating database and table for user


4.2 ALTER

figure 4.2 : altering table user

Alter table adds, removes or alters columns and their data types. It can also enforce referential
and domain integrity by creating or dropping unique, primary key , foreign key and check constraints in
mode. Alter Tablespace changes the specifications of a tablespace within the current location.Alter view
uses an existing view definition at the current server to regenerate a view.Alter sequence changes
sequence attributes at the current server.

4.3 DROP

Drop database does the exact opposite of the create database It deletes a database
defined at a certain location, along with all the objects logically associated with it. It also
deletes the database subdirectory even if it is empty and contains no objects logically associated
with the database.DROP STOGROUP deletes a stogroup by severing the logical connection
between data objects defined using the stogroup and the directory path specified in the deleted
stogroup definition. It doesn't delete the objects associated with the stogroup. As with other
DROP commands, the DROP STOGROUP command should be used sparingly and with
caution.
figure 4.3 : dropping table user

4.4 TRUNCATE

figure
4.4 : to truncate the table article

The truncate table statement is a Data Manipulation Language (DML) operation


that deletes all rows of a table without causing a triggered action. The result of this
operation quickly removes all data from a table, typically bypassing a number of integrity
enforcing mechanisms.The TRUNCATE command is used to remove all of the rows from
a table, regardless of whether or not any conditions are met and resets the table definition.
4.5 RENAME

The rename operator ρ is one of the unary operators in relational algebra and is used to
rename relations in a DBMS.The RENAME TABLE statement can be used to rename a table in
SQL. We use the RENAME keyword followed by the old name of the table followed by the To
keyword followed by the new name of the table.

figure 4.5: Renaming article


CHAPTER V

DATA MANIPULATION LANGUAGE

5.1 SELECT

figure 5.1 : selecting user_id and name from user table

The SELECT Statement in SQL is used to retrieve or fetch data from a database.
We can fetch either the entire table or according to some specified rules. The data returned
is stored in a result table. This result table is also called the result set.A select query helps
you retrieve only the data that you want, and also helps you combine data from several data
sources.
5.2

INSERT

Insert command is data manipulation commands, which is used to manipulate data by inserting
the information into the tables. This command is used to add records to a table. While inserting a
record using the insert statement, the number of records being entered should match in the columns
of the table.Use the insert command to enter data into a table. Insert one row at a time, or select
several rows from an existing table and insert them all at once.

figure 5.2: inserting values into user table


UPDATE

Update command is a data manipulation command which is used to edit the records
of a table. It may be used to update a single row based on a condition, all rows or sets of
rows based on the condition given by the user.UPDATE statement changes the data of one
or more records in a table. Either all the rows can be updated, or a subset may be chosen
using a condition.
5.3

figure 5.3: updating user

DELETE

Delete command is a data manipulation command which is used to remove records


from a table. All records may be removed in one go, or a set of records may be deleted
based on a condition. The Delete command in SQL is a part of the Data Manipulation
Language, a sub-language of SQL that allows modification of data in databases. This
command is used to delete existing records from a table.

figure 5.4 : deleting user_id from user


5.4
CHAPTER VI

TRANSACTION CONTROL LANGUAGE

6.1 BEGIN

figure 6.1 : Beginning transaction

Begin SQL is the keyword that is used to mark up and specify the beginning of the
transaction or stored procedure or functions or simply the collection of multiple statements inside
the logical block whose body starts from the specification of the BEGIN keyword and stops with
the use of END keyword.
6.2 COMMIT

figure 6.2: committing transaction for user

The COMMIT command is a fundamental transactional command used to save changes made
by a particular transaction in a database management system. It ensures that all changes made
before committing are permanent and cannot be rolled back. The COMMIT command is the
transactional command used to save changes invoked by a transaction. It saves all the transactions
that occurred on the database since the last COMMIT.

6.3 ROLLBACK

The rollback statement undoes part or all of the current transaction. If you omit the to
save_point_name clause, the statement terminates the transaction and rolls back any changes
made by the transaction.If you use the to save_point_name clause, the transaction is not
terminated, and only those changes made after the specified savepoint are rolled back.
Processing resumes with the statement following the rollback statement. A rollback statement
also closes any open cursors.
figure 6.3: rollback

6.4 SAVEPOINT

A savepoint is a way of implementing subtransactions (also known as nested transactions)


within a relational database management system by indicating a point within a transaction that
can be "rolled back to" without affecting any work done in the transaction before the
savepoint was created.

figure 6.4 : Savepoint of user


CHAPTER VII

DATA CONTROL LANGUAGE

7.1 GRANT

This is a SQL command which is used to provide privileges/permissions to


modify and retrieve database objects like tables, views, sequences, indexes, and
synonyms.This command also gives privileges like providing the same permissions to
some third user as well.
figure 7.1 : granting permission to table

7.2 REVOKE

figure 7.2: revoking permission to the table

The revoke command functions as the opposite of the grant command. It is used to remove
the privileges on user accounts for access to a database object. It revokes permission granted to a
user on a database object and also revokes the access rights assigned to users.
CHAPTER VIII

DATA INTEGRITY FUNCTION

8.1 UNIQUE KEY

figure 8.1 : unique key of table news

A unique key is a candidate key. All the candidate keys of a relation can uniquely identify
the records of the relation, but only one of them is used as the primary key of the relation. A
unique key is used to remove the duplicity of values in a table. However, the usage of a primary
key is the same, but there is a difference between both keys. A primary key cannot take a null
value, but a unique key can have one null value as its value.
8.2 PRIMARY KEY

figure 6.2:
primary key for table news

A Primary Key is the minimal set of attributes of a table that has the task to uniquely identify
the rows, or we can say the tuples of the given particular table.A primary key of a relation is one
of the possible candidate keys which the database designer thinks it's primary. It may be selected
for convenience, performance and many other reasons.

8.3 FOREIGN KEY

A foreign key is the one that is used to link two tables together via the primary key. It means the
columns of one table point to the primary key attribute of the other table. It further means that if
any attribute is set as a primary key attribute will work in another table as a foreign key attribute.
But one should know that a foreign key has nothing to do with the primary key.
figure 8.3: foreign key for table news

8.4 NOT NULL


figure 8.4: Notnull for table news

The NOT NULL constraint is used to ensure that a given column of a table is never assigned the
null value. Once a NOT NULL constraint has been defined for a particular column, any insert or
update operation that attempts to place a null value in that column will fail.The NOT NULL
constraint enforces a column to not accept NULL values, which means that you cannot insert or
update a record without adding a value to this field.
8.5 CHECK

figure 8.5 : check for table checking

Check constraint ensures that the data entered by the user for that column is within the range
of values or possible values specified.The CHECK constraint is used to limit the value range
that can be placed in a column. If you define a CHECK constraint on a column it will allow
only certain values for this column. If you define a CHECK constraint on a table it can limit
the values in certain columns based on values in other columns in the row.

CHAPTER XIII

CONCLUSION AND SCOPE FOR FUTURE


ENHANCEMENT
12.1 CONCLUSION

The Student Management System (SMS) is a comprehensive software solution


designed to streamline and optimize the management of students within educational
institutions, such as schools, colleges, and universities. This system leverages modern
technology to simplify administrative tasks, enhance communication between stakeholders,
and improve overall operational efficiency. The Student Management System (SMS) is a
comprehensive software solution designed to streamline and optimize the management of
students within educational institutions, such as schools, colleges, and universities. This
system leverages modern technology to simplify administrative tasks, enhance
communication between stakeholders, and improve overall operational efficiency.

The Student Management System (SMS) is a comprehensive software solution


designed to streamline and optimize the management of students within educational
institutions, such as schools, colleges, and universities. This system leverages modern
technology to simplify administrative tasks, enhance communication between stakeholders,
and improve overall operational efficiency. The Student Management System (SMS) is a
comprehensive software solution designed to streamline and optimize the management of
students within educational institutions, such as schools, colleges, and universities. This
system leverages modern technology to simplify administrative tasks, enhance
communication between stakeholders, and improve overall operational efficiency. This
system leverages modern technology to simplify administrative tasks, enhance
communication between stakeholders, and improve overall operational efficiency.
12.2 SCOPE FOR FUTURE ENHANCEMENT

The Student Management System (SMS) is a comprehensive software solution


designed to streamline and optimize the management of students within educational
institutions, such as schools, colleges, and universities. This system leverages modern
technology to simplify administrative tasks, enhance communication between stakeholders,
and improve overall operational efficiency. The Student Management System (SMS) is a
comprehensive software solution designed to streamline and optimize the management of
students within educational institutions, such as schools, colleges, and universities. This
system leverages modern technology to simplify administrative tasks, enhance
communication between stakeholders, and improve overall operational efficiency. This
system leverages modern technology to simplify administrative tasks, enhance
communication between stakeholders, and improve overall operational efficiency.

The Student Management System (SMS) is a comprehensive software solution


designed to streamline and optimize the management of students within educational
institutions, such as schools, colleges, and universities. This system leverages modern
technology to simplify administrative tasks, enhance communication between stakeholders,
and improve overall operational efficiency. The Student Management System (SMS) is a
comprehensive software solution designed to streamline and optimize the management of
students within educational institutions, such as schools, colleges, and universities. This
system leverages modern technology to simplify administrative tasks, enhance
communication between stakeholders, and improve overall operational efficiency. This
system leverages modern technology to simplify administrative tasks, enhance
communication between stakeholders, and improve overall operational efficiency.

CHAPTER XI

PL/SQL FUNCTIONS

Function can be used as a part of SQL expression. We can use them with select/update/merge
commands. One most important characteristic of a function is that, unlike procedures, it must return
a value
figure 11.1: Multiplication in function

figure 11.2: Subtraction in function


CHAPTER XII

PL/SQL PROCEDURE

A procedure in PL/SQL is nothing but a series of declaration SQL statements which can be stored in the
database catalog. A procedure can be thought of as a function or a method. A news portal management system
implemented in PL/SQL can utilize the COUNT function to efficiently gather critical information.A news
portal management system implemented in PL/SQL can utilize the MAX function.We have created procedures
namely article.PL/SQL procedure could be designed to find maximum salary from the table. Then call the
procedure article.
figure 12.1: Count in procedure

figure 12.2:Maximum in procedure


CHAPTER XIII

TRIGGERS IN PL/SQL

Trigger is a statement that a system executes automatically when there is any modification
to the database. In a trigger, we first specify when the trigger is to be executed and then the action to
be performed when the trigger executes.

13.1 STATEMENT LEVEL TRIGGERS:

Statement level triggers executes only once for each single transactions.

ROLL LEVEL TRIGGERS


Row level triggers executes once for each and every row in the transactions.
CHAPTER XIV

CURSOR IN PL/SQL

To execute SQL statements a work area is used by the Oracle engine for its internal
processing and storing the information. This work area is private to SQL’s operations. The ‘Cursor’
is the PL/SQL construct that allows the user to name the work area and access the stored
information in it.

IMPLICIT CURSOR

Implicit cursors are automatically created when select statements are executed.
CHAPTER IV

BIBLIOGRAPHY

13.1 BOOK REFERENCES

1. Mischel, W., & Baker, N. (1975). Cognitive transformations of reward objects through
instructions. Journal of Personality and Social Psychology, 31, 254-261.
2. Mischel, W., & Baker, N. (1975). Cognitive transformations of reward objects through
instructions. Journal of Personality and Social Psychology, 31, 254-261.
3. Mischel, W., & Baker, N. (1975). Cognitive transformations of reward objects through
instructions. Journal of Personality and Social Psychology, 31, 254-261.
4. Mischel, W., & Baker, N. (1975). Cognitive transformations of reward objects through
instructions. Journal of Personality and Social Psychology, 31, 254-261.
5. Mischel, W., & Baker, N. (1975). Cognitive transformations of reward objects through
instructions. Journal of Personality and Social Psychology, 31, 254-261.

13.2 WEBSITE REFERENCES

1. https://www.sourcecodester.com/php/16525/lost-and-found-information-system- using-php-
and-mysql-db-source-code-free-download.html
2. https://www.sourcecodester.com/php/16525/lost-and-found-information-system- using-php-
and-mysql-db-source-code-free-download.html
3. https://www.sourcecodester.com/php/16525/lost-and-found-information-system- using-php-
and-mysql-db-source-code-free-download.html
4. https://www.sourcecodester.com/php/16525/lost-and-found-information-system- using-php-
and-mysql-db-source-code-free-download.html
5. https://www.sourcecodester.com/php/16525/lost-and-found-information-system- using-php-
and-mysql-db-source-code-free-download.html

You might also like