Database Management 

System – Project

Project Members – 
1. Rajasimmavarman A (2009506086)
2. Raju N (2009506087)
3. Ram Sr ivatsa K (2009506088)

Project guide – 
Mrs A. Anusooya devi
 Database Management system
Project
Definition –

A Database Management System (DBMS) is a set of computer programs that

controls the creation, maintenance, and the use of a database. It allows organizations
to place control of database development in the hands of database
administrators (DBAs) and other specialists. A DBMS is a system software package
that helps the use of integrated collection of data records and files known as
databases. It allows different user application programs to easily access the same
database. DBMSs may use any of a variety of database models, such as the network
model or relational model. In large systems, a DBMS allows users and other software
to store and retrieve data in a structured way. Instead of having to write computer
programs to extract information, user can ask simple questions in a query language.
Thus, many DBMS packages provideFourth-generation programming language (4GLs)
and other application development features. It helps to specify the logical organization
for a database and access and use the information within a database. It provides
facilities for controlling data access, enforcing data integrity, managing concurrency,
and restoring the database from backups. A DBMS also provides the ability to logically
present database information to users.

DBMS building blocks

A DBMS includes four main parts: modeling language, data structure, database
query language, and transaction mechanisms:
Components of DBMS
 DBMS Engine accepts logical request from the various other DBMS
subsystems, converts them into physical equivalents, and actually
accesses the database and data dictionary as they exist on a storage
device.
 Data Definition Subsystem helps user to create and maintain the data
dictionary and define the structure of the files in a databDBMS
Engine accepts logical request from the various other DBMS subsystems,
converts them into physical equivalents, and actually accesses the
database and data dictionary as they exist on a storage device.
 Data Definition Subsystem helps user to create and maintain the data
dictionary and define the structure of the files in a database.
 Data Manipulation Subsystem helps user to add, change, and delete
information in a database and query it for valuable information. Software
tools within the data manipulation subsystem are most often the primary
interface between user and the information contained in a databaseDBMS
Engine accepts logical request from the various other DBMS subsystems,
converts them into physical equivalents, and actually accesses the
database and data dictionary as they exist on a storage device.
 Data Definition Subsystem helps user to create and maintain the data
dictionary and define the structure of the files in a databDBMS
Engine accepts logical request from the various other DBMS subsystems,
converts them into physical equivalents, and actually accesses the
database and data dictionary as they exist on a storage device.
 Data Definition Subsystem helps user to create and maintain the data
dictionary and define the structure of the files in a database.
 Data Manipulation Subsystem helps user to add, change, and delete
information in a database and query it for valuable information. Software
tools within the data manipulation subsystem are most often the primary
interface between user and the information contained in a databaseDBMS
Engine accepts logical request from the various other DBMS subsystems,
converts them into physical equivalents, and actually accesses the
database and data dictionary as they exist on a storage device.
 . It allows user to specify its logical information requirements.. It allows
user to specify its logical information requirements.
 Application Generation Subsystem contains facilities to help users to
develop transaction-intensive applications. It usually requires that user
perform a detailed series of tasks to process a transaction. It facilitates
easy-to-use data entry screens, programming languages, and interfaces.
 Data Administration Subsystem helps users to manage the overall
database environment by providing facilities for backup and recovery,
security management, query optimization, concurrency control, and
change management.
Modeling language
A data modeling language to define the schema of each database hosted in
the DBMS, according to the DBMS database model. The four most common
types of models are the:
 hierarchical model,
 network model,
 relational model, and
 object model.
Inverted lists and other methods are also used. A given database
management system may provide one or more of the four models. The
optimal structure depends on the natural organization of the application's
data, and on the application's requirements (which include transaction rate
(speed), reliability, maintainability, scalability, and cost).
The dominant model in use today is the ad hoc one embedded in SQL,
despite the objections of purists who believe this model is a corruption of
the relational model, since it violates several of its fundamental principles
for the sake of practicality and performance. Many DBMSs also support
the Open Database Connectivity API that supports a standard way
for programmers to access the DBMS.
Before the database management approach, organizations relied on file
processing systems to organize, store, and process data files. End users
became aggravated with file processing because data is stored in many
different files and each organized in a different way. Each file was
specialized to be used with a specific application. Needless to say, file
processing was bulky, costly and nonflexible when it came to supplying
needed data accurately and promptly. Data redundancy is an issue with the
file processing system because the independent data files produce duplicate
data so when updates were needed each separate file would need to be
updated. Another issue is the lack of data integration. The data is
dependent on other data to organize and store it. Lastly, there was not any
consistency or standardization of the data in a file processing system which
makes maintenance difficult. For all these reasons, the database
management approach was produced. Database management systems
(DBMS) are designed to use one of five database structures to provide
simplistic access to information stored in databases. The five database
structures are hierarchical, network, relational, multidimensional and object-
oriented models.
The hierarchical structure was used in early mainframe DBMS. Records’
relationships form a treelike model. This structure is simple but nonflexible
because the relationship is confined to a one-to-many relationship. IBM’s
IMS system and the RDM Mobile are examples of a hierarchical database
system with multiple hierarchies over the same data. RDM Mobile is a newly
designed embedded database for a mobile computer system. The
hierarchical structure is used primary today for storing geographic
information and file systems.
The network structure consists of more complex relationships. Unlike the
hierarchical structure, it can relate to many records and accesses them by
following one of several paths. In other words, this structure allows for
many-to-many relationships.
The relational structure is the most commonly used today. It is used by
mainframe, midrange and microcomputer systems. It uses two-dimensional
rows and columns to store data. The tables of records can be connected by
common key values. While working for IBM, E.F. Codd designed this
structure in 1970. The model is not easy for the end user to run queries with
because it may require a complex combination of many tables.
The multidimensional structure is similar to the relational model. The
dimensions of the cube looking model have data relating to elements in
each cell. This structure gives a spreadsheet like view of data. This structure
is easy to maintain because records are stored as fundamental attributes,
the same way they’re viewed and the structure is easy to understand. Its
high performance has made it the most popular database structure when it
comes to enabling online analytical processing (OLAP).
The object oriented structure has the ability to handle graphics, pictures,
voice and text, types of data, without difficultly unlike the other database
structures. This structure is popular for multimedia Web-based applications.
It was designed to work with object-oriented programming languages such
as Java.
Data structure
Data structures (fields, records, files and objects) optimized to deal with
very large amounts of data stored on a permanent data storage
device (which implies relatively slow access compared to volatile main
memory).
Database query language
A database query language and report writer allows users to interactively
interrogate the database, analyze its data and update it according to
the users privileges on data. It also controls the security of the
database. Data security prevents unauthorized users from viewing or
updating the database. Using passwords, users are allowed access to the
entire database or subsets of it called subschemas. For example, an
employee database can contain all the data about an individual employee,
but one group of users may be authorized to view only payroll data, while
others are allowed access to only work history and medical data.
If the DBMS provides a way to interactively enter and update the database,
as well as interrogate it, this capability allows for managing personal
databases. However, it may not leave an audit trail of actions or provide the
kinds of controls necessary in a multi-user organization. These controls are
only available when a set of application programs are customized for each
data entry and updating function.
Transaction mechanism
A database transaction mechanism ideally guarantees ACID properties in
order to ensure data integrity despite concurrent user
accesses (concurrency control), and faults (fault tolerance). It also maintains
the integrity of the data in the database. The DBMS can maintain the
integrity of the database by not allowing more than one user to update the
same record at the same time. The DBMS can help prevent duplicate
records via unique index constraints; for example, no two customers with
the same customer numbers (key fields) can be entered into the database.
See ACID properties for more information (Redundancy avoidance).
Aim –
This project is aimed at creating a database which maintains the
batting, bowling and other essential statistics of a cricket player.

Project details –
• Many tables are created one for the personal details and the other for the
cricketing details of the player.

• The personal details include name, date of birth, age, weight, height and
s.no.

• The cricketing details include total runs, 50s, 100s, wickets, 5-wicket hauls,
st rate, run rate, s.no.

• The cricketing details are further classified into many types -

➢ First class career

➢ Test match career

➢ One day international career

➢ International teams database

➢ club teams database

• The first table and the second table are related to each other by the use of a
foreign key s.no which individually acts as the primary key to each and every
table.

• Various datatypes which are used for different attributes are shown in the
main project.

Uses -
• It can be used to access the personal details of the cricket players.
• It gives the full appropriate details of the batsman whenever he is new in the
crease.

• This project is easy to use as it requires instant updation of data after every
match played by the players.

• This project is very useful for cricket statisticians who analyze the statistics
of individual players performance before every match.