Art Gallery Report

VISVESVARAYA TECHNOLOGICAL UNIVERSITY
BELGAUM
DATABASE MANAGEMENT SYSTEM
LABORATORY MINI-PROJECT REPORT
ON
DEPARTMENT MANAGEMENT SYSTEM
SUBMITTED BY
VEDAVYAS PARITALA P VENKATACHALAPATHI
1AT16CS121 1AT16CS122
Submitted in partial fulfillment of the requirement for the award of the
Degree of Bachelor of Engineering
In
Computer Science &Engineering
UNDER THE GUIDANCE OF
Prof. Pradeep
XCELERATOR
Atria Institute of Technology
Anandanagar, Bangalore-560024
DBMS Lab Mini-Project Report DMS
Atria Institute of Technology Anandanagar, Bangalore-56002
CERTIFICATE
This is to certify that the project entitled DMS has been successfully completed by
VEDAVYAS PARITALA P VENKATACHALAPATHAI K V
1AT16CS121 1AT16CS122
In partial fulfillment for the data base management system laboratory with mini-project report
[15CSL58] –V semester, BE Computer Science during 2018-2019.
Signature of HOD Signature of guide
Dr.P.Aishwarya Prof. Ravi
External Viva:
(Name of Internal/External Examiner with signature & Date)
Examiner 1____________________________
Examiner 2____________________________
Atria Institute Of Technology 1

ACKNOWLEDGEMENT
Any achievement, be it scholastic or otherwise does not depend solely on the individual
efforts but on the guidance, encouragement and cooperation of intellectuals, elders and
friends, who believe that the individual can excel and put in their every bit in every
endeavor he/she embarks on, at every stage in life. And the success is derived when
opportunity meets preparation, also supported by a well-coordinated approach and
attitude.
The joy and satisfaction that accompanies the successful completion of any task would
be incomplete without mentioning the people who made it possible and also whose
efforts gave this project its final shape.
We would like to express our gratitude to our respected principal Dr. K V

Narayanaswamy for providing a congenial environment and surrounding to work in.
We would like to express our sincere gratitude to Dr. P. Aishwarya, Head of the
Department, Computer Science& Engineering, for his continuous support and
encouragement.
We are indeed indebted to Prof. Pradeep and Prof .Ravi Ranjan, project guide and lab in-charge, for
her support, advice and inputs in the course of this project. We would also like to thank various faculty
members of the Computer Science & Engineering Department for their valuable suggestions and inputs.
Last, but not the least we would like to thank our parents, who have acted as a beacon of
light throughout life.
Our sincere gratitude goes out to all our comrades and well-wishers who have supported us
through all our ventures.
VEDAVYAS PARITALA P VENKATACHALAPATHI K V
1AT16CS121 1AT16CS122

ABSTRACT
Online Art Gallery is an online application, which is used to display and sell art works of artist irrespective of
their nationality, gender and other narrow consideration, through auction. Artist can
register online for being a member in the art gallery and each artist can upload the digital copy of their art work
under the respective categories. They can host their art work either for auction or for
fixed price. The artist is liable to pay a fraction of the price of each art work to the web site to find the running
fund for site.
Art lovers
have to go to the art exhibition to collect their favorite arts or painting. But now-a-days they are not getting
enough time to go to the galleries and collect the arts and paintings
Existing System:
Customer can also register online and they can browse artworks that are arranged in different categories
scientifically. Each Customer can create their own gallery to see his favorite art works
without much difficult. And each user has the right to purchase an art work using the integrated payment
gateway and participate in auction by submitting their bids. Qualified bidder should remit the
amount using payment gateway and after each valid payment the art work will be shipped within some days.

TABLE OF CONTENTS
Certificate ....................................................................................................................................
1 Acknowledgement
...................................................................................................................... 2 Abstract
....................................................................................................................................... 3 1.
INTRODUCTION ................................................................................................................ 6
1.1 INTRODUCTION TO DBMS .......................................................................................... 6
1.1.1 SQL PROGRAMMING............................................................................................. 6
1.1.2 Working with SQL COMMANDS ............................................................................ 7 1.2
ORGANIZATION OF REST OF THE REPORT........................................................... 14 1.3
BRIEF OUTLINE OF THE PROJECT ........................................................................... 14 2.
LITERATURE SURVEY .................................................................................................. 15 3.
REQUIREMENT SPECIFICATIONS ............................................................................. 16 3.1
EXTERNAL INTERFACE REQUIREMENTS............................................................. 16 3.2
FUNCTIONAL REQUIREMENTS ............................................................................... 16 3.2
BROAD ARCHITECTURE ........................................................................................... 17 4.
SYSTEM DESIGN .............................................................................................................. 18
4.1 ER DIAGRAM ............................................................................................................... 18
4.2 APPLY ER-MAPPING RULES, .................................................................................... 19
4.3 NORMALIZATION ....................................................................................................... 20
4.4 USER INTERFACE DESIGN ........................................................................................ 21
5. DETAILED DESIGN ......................................................................................................... 22
5.1 DATABASE CREATION .............................................................................................. 22
5.1.1 Data Definitions ....................................................................................................... 22
5.1.2. Constraints…………………………………………………………….………….24
5.2.NORMAL FORMS………………………………………………………….………...24
5.2.1 First normal form………………………………………………………………..24
5.2.2 Second normal form…………………………………………………………..…24
5.2.3 Third normal form…………………………………………………………….…25
5.3.STORED PROCEDURES .............................................................................................. 26
6. DATABASE CONNECTIONS AND CODE IMPLEMENTATION………...……….28
6.1 Retrieving data from the database………………………………................................28
6.2 Inserting data into the database………………………………….................................28
6.3 Updating records into the database……………………………………………..…….28
6.4 Deleting data from the database…………………………………................................29
7. System and Database Testing ............................................................................................ 30

7.1 .2 TEST RESULTS/SNAPSHOTS ................................................................................. 30
8. CONCLUSION AND SCOPE FOR FURTHER ENHANCEMENTS .......................... 50 9.
APPENDIX .......................................................................................................................... 51
9.1APPENDIX-I ................................................................................................................... 51
9.1.1 Bibliography ............................................................................................................ 51 9.2
APPENDIX-II ................................................................................................................. 51 9.2.1
Development Tools .................................................................................................. 51 9.2.2
Software Environment ............................................................................................. 52 9.2.3
Hardware Environment ............................................................................................ 52
Front End AND Back End Softwares
Project Name : Art Gallery Management System

Technology Implemented : Apache Server
Language Used : PHP
Database : My SQL
User Interface Design : HTML, AJAX,JQUERY,JAVASCRIPT

Web Browser : Mozilla, Google Chrome, IE8,OPERA
Software : XAMPP Server
Modules of Tourism Management System in
php
 Admin
 Users
 Guest Users
Users—
 User can register yourself.
 User can login with valid email and password.
 Forgot Password(user Can recover own password)
 change Password
Admin–
 Admin can create product
 Manage product(Create,Update)
 Manage Users
 Manage Inquiries
 Manage issues
 Manage Pages
 Change Password
 Admin Dashboard
Guest users—
 Visit the Website
 Guest user can enquiry
Database Configuration
Open phpMyAdmin
Database Art
Open Your browser put inside browser “http://localhost/Art”

CHAPTER 2
Literature Survey
Online Attendance Management System
The objective of Online Attendance Management System is to go with computerized system,

instead of old-fashioned manual process. As compared to manual process, online system easily
helps management to analyze student’s attendance details as per requirement. Along with this,
it provides summarized attendance report very quickly at any point of time.
Advantages:
• User Friendly: User interface is very easy. Data storing and recovery is fast and secured. In
addition, application is provided with graphical representation for easier interpretation and
analysis.
• Reports are easily generated: Various reports such as Student wise attendance, Day wise
attendance, Class wise attendance, Month Wise Class Attendance etc can be easily generated.
Current and back-dated reports can be available instantly.
• No paperwork and no risk of errors which can be occurred while marking the attendance
manually.
Features:
• A simple online application designed for all attendance requirements
• Capable to store up maximum records
• Fully compatible - needs only internet connection compatible
The online attendance management system has been built to eliminate the time and effort
wasted in taking attendances. It is software that fulfills the requirement of the system for which
it has been developed. The system has reached at such a level where all bugs have been
eliminated and operated efficiently

CHAPTER 3
REQUIREMENT SPECIFICATIONS
3.1 External Interface Requirements:
External interface requirements specify hardware, software, or database elements with which
a system or component must interface. This section provides information to ensure that the
system will communicate properly with external components. If different portions of the
product have different external interfaces, incorporate an instance of this section within the
detailed requirements for each such portion.
The project makes use of html,css,php to build up a user interactive pages for the website.Also
the data is stored in my sql from which we retrieve the details and display in the front end.
3.2 Functional Requirements

: A functional requirement defines a function of a system or its component. A function is
described as a set of inputs, the behaviour, and outputs. Functional requirements may be
calculations, technical details, data manipulation and processing and other specific
functionality that define what a system is supposed to accomplish.
This management system is supposed to take the user input in the form of the area in which
they are possibly looking for a land or a property and display the result of the search. Also the
system stores the details of the owners of the lands and the user details too who have logged in
which comes through the front end as the input and is stored in the database for future retrieval.
3.3 Broad Architecture:

CHAPTER 4

SYSTEM DESIGN
4.1 E-R Diagram
ER-Diagram is a visual representation of data that describes how data is related to each other.
4.2 Applying ER mapping rules

4.3 Normalization:
Database normalization, or simply normalization, is the process of organizing the columns

(attributes) and tables (relations) of a relational database to reduce data redundancy and
improve data integrity. Normalization is also the process of simplifying the design of a database
so that it achieves the optimal structure composed of atomic elements. It was first proposed by
Edgar F. Codd, as an integral part of a relational model.
Normalization involves arranging attributes in relations based on dependencies between

attributes, ensuring that the dependencies are properly enforced by database integrity
constraints. Normalization is accomplished by applying some formal rules either by a process
of synthesis or decomposition. Synthesis creates a normalized database design based on a
known set of dependencies. Decomposition takes an existing (insufficiently normalized)
database design and improves it based on the known set of dependencies.
First Normal Form (1NF)

As per First Normal Form, no two Rows of data must contain repeating group of information
i.e each set of column must have a unique value, such that multiple columns cannot be used to
fetch the same row. Each table should be organized into rows, and each row should have a
primary key that distinguishes it as unique.
The Primary key is usually a single column, but sometimes more than one column can be
combined to create a single primary key.
In First Normal Form, any row must not have a column in which more than one value is saved,
like separated with commas. Rather than that, we must separate such data into multiple rows.
Using the First Normal Form, data redundancy increases, as there will be many columns with
same data in multiple rows but each row as a whole will be unique.
Second Normal Form (2NF):

As per the Second Normal Form there must not be any partial dependency of any column on
primary key. It means that for a table that has concatenated primary key, each column in the
table that is not part of the primary key must depend upon the entire concatenated key for its
existence. If any column depends only on one part of the concatenated key, then the table fails
Second normal form.
In First Normal Form there are two rows ,included multiple values that were opted for. While
this is searchable, and follows First normal form, it is an inefficient use of space. Also in the
above Table in First Normal Form, while the candidate key of a table only depends on a
particular column, which is incorrect as per Second Normal Form. To achieve second normal
form, it would be helpful to split out the In
Although there are a few complex cases in which table in Second Normal Form suffers Update
Anomalies, and to handle those scenarios Third Normal Form is there.
Third Normal Form (3NF):
Third Normal form applies that every non-prime attribute of table must be dependent on
primary key, or we can say that, there should not be the case that a non-prime attribute is
determined by another non-prime attribute. So this transitive functional dependency should be
removed from the table and also the table must be in Second Normal form.
The advantage of removing transtive dependency is,
• Amount of data duplication is reduced.

• Data integrity achieved.
Boyce and Codd Normal Form (BCNF)

Boyce and Codd Normal Form is a higher version of the Third Normal form. This form
deals with certain type of anomaly that is not handled by 3NF. A 3NF table which does not
have multiple overlapping candidate keys is said to be in BCNF. For a table to be in BCNF,
following conditions must be satisfied:
• R must be in 3rd Normal Form and, for each functional dependency ( X → Y ), X should
be a super Key.
4.4 User Interface Design
User interface design (UI) or user interface engineering is the design of user interfaces for
machines and software, such as computers, home appliances, mobile devices, and other
electronic devices, with the focus on maximizing usability and the user experience. The goal
of user interface design is to make the user's interaction as simple and efficient as possible, in
terms of accomplishing user goals (user-centered design).
Good user interface design facilitates finishing the task at hand without drawing unnecessary
attention to itself. Graphic design and typography are utilized to support its usability,
influencing how the user performs certain interactions and improving the aesthetic appeal of
the design; design aesthetics may enhance or detract from the ability of users to use the
functions of the interface. The design process must balance technical functionality and visual
elements (e.g., mental model) to create a system that is not only operational but also usable and
adaptable to changing user needs.
Interface design is involved in a wide range of projects from computer systems, to cars, to
commercial planes; all of these projects involve much of the same basic human interactions yet
also require some unique skills and knowledge. As a result, designers tend to specialize in
certain types of projects and have skills centered on their expertise, whether that be software
design, user research, web design, or industrial design.
CHAPTER 5
DETAILED DESIGN
5.1 Database Creation
CREATE DATABASE Statement
The CREATE DATABASE statement is used to create a new SQL database.
Syntax:
CREATE DATABASE databasename;
We should have the admin privilege before creating any database. Once a database is created,
we can check it in the list of databases as follows –
SHOW DATABASES;

5.1.1 Data Definitions Entity
types and Attributes:
Students:
Field Type Null Key Default Extra

Usn varchar(20) NO PRI NULL
Sem int(11) NO NULL

Sec varchar(15) NO NULL
Name varchar(45) NO NULL
Phone int(11) NO NULL
Address varchar(50) NO NULL
Email varchar(45) NO NULL
Subjects:

Subcode varchar(20) NO PRI NULL
sub_name varchar(45) NO MUL NULL
Fid varchar(45) YES MUL NULL
Tracker:

Fkusn varchar(20) NO MUL NULL
Fksubcode varchar(20) NO Attend: MUL NULL

usn_fk varchar(20) YES MUL NULL
subcode_fk varchar(20) YES MUL NULL
Sec varchar(15) YES NULL
Hours int(11) YES NULL
Date Date YES NULL
Attendance varchar(10) YES NULL
Writes_internals_for_:

Usn varchar(20) NO MUL NULL
Subcode varchar(20) YES MUL NULL
test1 Float YES NULL
assign1 Float YES NULL
total1 Float YES NULL
Avg Float YES NULL
Faculty_memebers:
Faculty_id varchar(45) NO PRI NULL
Password varchar(45) NO NULL
f_name varchar(45) NO NULL
f_email varchar(45) NO NULL
5.1.2. Constraints:
1. A student studies 8 subjects each semester

2. Each student may or may not have internal marks record created
3. Each student may or may not have attendance records created for classes of one or more
subjects
4. Each subject must have one or more faculty members and each faculty member must teach
one or more subjects
5. Each student may or may not have a personal detail record created
6. Each student must have only one personal details record but a personal details record may
belong to one more students
5.2. Normal Forms
5.2.1. First normal form:
First normal form (1NF) sets the very basic rules for an organized database:
• Eliminate duplicative columns from the same table.

• Create separate tables for each group of related data and identify each row with a
unique column or set of columns (the primary key).
• Remove repetitive groups
• Create Primary Key
5.2.2. Second Normal Form (2NF)
Second normal form (2NF) further addresses the concept of removing duplicative data:
• Meet all the requirements of the first normal form.
• Remove subsets of data that apply to multiple rows of a table and place them in separate
tables.
· Create relationships between these new tables and their predecessors through the use of
foreign keys.
Remove columns which create duplicate data in a table and related a new table with Primary
Key – Foreign Key relationship’
5.2.3. Third Normal Form (3NF)

Third normal form (3NF) goes one large step further:
• Meet all the requirements of the second normal form.
• Remove columns that are not dependent upon the primary key


From the above definitions of 1NF,2NF,3NF it can be concluded that the above 6 tables are
normalised , that is they are in 1NF,2NF,3NF.hence it
a. Eliminates data redundancy

b. Improves performance
c. Query optimization
d. Faster update due to less number of columns in one table
e. Index improvement
5.3 Stored Procedure
A stored procedure termed proc, storp, sproc, StoPro, StoredProc, StoreProc, sp, or SP)
is a subroutine available to applications that access a relational database management system
(RDBMS). Such procedures are stored in the database data dictionary.
Uses for stored procedures include data-validation (integrated into the database) or
accesscontrol mechanisms. Furthermore, stored procedures can consolidate and centralize
logic that was originally implemented in applications. To save time and memory, extensive or
complex processing that requires execution of several SQL statements can be saved into stored
procedures, and all applications call the procedures. One can use nested stored procedures by
executing one stored procedure from within another.
Stored procedures may return result sets, i.e., the results of a SELECT statement. Such result
sets can be processed using cursors, by other stored procedures, by associating a result-set
locator, or by applications. Stored procedures may also contain declared variables for
processing data and cursors that allow it to loop through multiple rows in a table.
Storedprocedure flow-control statements typically include IF, WHILE, LOOP, REPEAT, and
CASE statements, and more. Stored procedures can receive variables, return results or modify
variables and return them, depending on how and where the variable is declared.

CHAPTER 6 DATABASE CONNECTIONS AND CODE

IMPLEMENTATION
6.1 Retrieving data from the database:
6.2 Inserting data into the database:
6.3 Updating records into the database:

6.4 Deleting data from the database:

CHAPTER 7
SYSTEM AND DATABASE
TESTING
7.1 Snapshots:




















CHAPTER 8 CONCLUSION AND SCOPE FOR FURTHER

ENHANCEMENTS
To conclude, DMS is a web application which can access all the databases and picks up
different functions. It overcomes the many limitations incorporated in the attendance.
• Easy implementation Environment
• Generate report Flexibly
The project has a very vast scope in future. The project can be implemented on intranet in
future. Project can be updated in near future as and when requirement for the same arises, as it
is very flexible in terms of expansion. Department Management System is ready and fully
functional. The client is now able to manage and hence run the entire department in a much
better, accurate and error free manner. The following are the future scope for the project.
• Bar code Reader based attendance system.

• Image capture based attendance system
• Make notes during class hours and share with classmates
• Apply to all departments of a college
CHAPTER 9
APPENDIX
9.1 Appendix-I

9.1.1 Bibliography
• https://en.wikipedia.org/wiki/Stored_procedure
• https://www.w3schools.com/
• https://www.tutorialspoint.com/
• https://stackoverflow.com/
• https://www.wikipedia.org/
• https://www.youtube.com/
• http://www.inmotionhosting.com/support/edu/website-design/using-php-
andmysql/grab-all-comments-from-database
• https://www.edureka.co
• https://www.udemy.com
• https://www.google.co.in/
9.2 Appendix-II:
9.2.1 Development Tools:
1. MYSQL Workbench:
MySQL Workbench is a unified visual tool for database architects, developers, and DBAs.
MySQL Workbench provides data modeling, SQL development, and comprehensive
administration tools for server configuration, user administration, backup, and much more.
MySQL Workbench is available on Windows, Linux and Mac OS X
MySQL Workbench simplifies database design and maintenance, automates time-consuming

and error-prone tasks, and improves communication among DBA and developer teams. It
enables data architects to visualize requirements, communicate with stakeholders, and resolve
design issues before a major investment of time and resources is made. It enables modeldriven
database design, which is the most efficient methodology for creating valid and wellperforming
databases, while providing the flexibility to respond to evolving business requirements. Model
and Schema Validation utilities enforce best practice standards for data modeling, also enforce
MySQL-specific physical design standards so no mistakes are made when building new ER
diagrams or generating physical MySQL databases..
MySQL Workbench delivers visual tools for creating, executing, and optimizing SQL queries.
2. Sublime Text 3:
Sublime Text is a proprietary cross-platform source code editor with a Python application
programming interface (API). It natively supports many programming languages and markup
languages, and functions can be added by users with plugins, typically community-built and
maintained under free-software licenses.
Version 3 entered beta on 29 January 2013. At first available only for registered users who
have purchased Sublime Text 2, on 28 June 2013 it became available to the general public.
However, the very latest development builds still required a registration code.[12] Sublime Text
3 was officially released on 13 September 2017.[13]
Two of the main features that Sublime Text 3 adds include symbol indexing and pane
management. Symbol Indexing allows Sublime Text to scan files and build an index to
facilitate the features Goto Definition and Goto Symbol in Project. Pane Management allows
users to move between panes via hotkeys.[14]
9.2.2 Software Environment
1. Html
2. Php
3. My Sql
4. Java Script
5. Css
9.2.3 Hardware Environment:
System
Manufacturer DELL,,Mac
Model DELL Pavilion g6 Notebook PC
Total amount of system memory 4.00 GB RAM
System type 64-bit Operating System
Processor Intel® Core i5-3230 CPU 4 x 2.60 GHz
Storage
Total size of hard disk 500 GB
Disk partition (C:) 40.8 GB Free (371 GB Total)
Disk partition (D:) 2.10 GB Free (16.7 GB Total)
Disk partition (H:) 5 GB Free (34 GB Total)

Art Gallery Report

Uploaded by

Document Information

Original Title

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

Art Gallery Report

Uploaded by

Copyright:

Available Formats

VISVESVARAYA TECHNOLOGICAL UNIVERSITY

DATABASE MANAGEMENT SYSTEM

LABORATORY MINI-PROJECT REPORT

DEPARTMENT MANAGEMENT SYSTEM

VEDAVYAS PARITALA P VENKATACHALAPATHI

Degree of Bachelor of Engineering

Computer Science &Engineering

UNDER THE GUIDANCE OF

Atria Institute of Technology

Atria Institute of Technology Anandanagar, Bangalore-56002

VEDAVYAS PARITALA P VENKATACHALAPATHAI K V

Signature of HOD Signature of guide

Dr.P.Aishwarya Prof. Ravi

(Name of Internal/External Examiner with signature & Date)

Atria Institute Of Technology 1

We would like to express our gratitude to our respected principal Dr. K V

VEDAVYAS PARITALA P VENKATACHALAPATHI K V

Atria Institute Of Technology 2

Atria Institute Of Technology 3

6.2 Inserting data into the database………………………………….................................28

DBMS Lab Mini-Project Report DMS

Atria Institute Of Technology 5

6.3 Updating records into the database……………………………………………..…….28

6.4 Deleting data from the database…………………………………................................29

7. System and Database Testing ............................................................................................ 30

Front End AND Back End Softwares

Project Name : Art Gallery Management System

User Interface Design : HTML, AJAX,JQUERY,JAVASCRIPT

Atria Institute Of Technology 6

The objective of Online Attendance Management System is to go with computerized system,

Atria Institute Of Technology 7

3.1 External Interface Requirements:

3.2 Functional Requirements

3.3 Broad Architecture:

Atria Institute Of Technology 8

Atria Institute Of Technology 9

4.2 Applying ER mapping rules

Atria Institute Of Technology 10

Database normalization, or simply normalization, is the process of organizing the columns

Normalization involves arranging attributes in relations based on dependencies between

First Normal Form (1NF)

Second Normal Form (2NF):

The advantage of removing transtive dependency is,

• Amount of data duplication is reduced.

Boyce and Codd Normal Form (BCNF)

4.4 User Interface Design

The CREATE DATABASE statement is used to create a new SQL database.

Atria Institute Of Technology 13

types and Attributes:

Field Type Null Key Default Extra

Sem int(11) NO NULL

Field Type Null Key Default Extra

Field Type Null Key Default Extra

Field Type Null Key Default Extra

Field Type Null Key Default Extra

Atria Institute Of Technology 14

1. A student studies 8 subjects each semester

5.2. Normal Forms

5.2.1. First normal form:

• Eliminate duplicative columns from the same table.

5.2.2. Second Normal Form (2NF)

5.2.3. Third Normal Form (3NF)

Atria Institute Of Technology 16