Nettippattam

BASELIOS POULOSE II CATHOLICOS COLLEGE
BASELIOS MOUNT, PIRAVOM
Accredited with ‘A’ Grade by NAAC
(Affiliated to Mahatma Gandhi University)
DEPARTMENT OF COMPUTER APPLICATIONS
2019-2020
Project Report
on
NETTIPPATTAM
PIRAVOM
2019-2020
Project Report
on
NETTIPPATTAM
Submitted in partial fulfilment of the
Requirements for the award of the degree of
BACHELOR OF COMPUTER APPLICATION
Guided by: Dr. Shaju Varhgese Submitted by:
(Dept. of Computer Applications) Bibin Sajeevan
(170021093014)
Alex George
(170021092991)
PIRAVOM

Certificate
This is to certify that the project entitled “NETTIPPATTAM”
submitted in partial fulfilment for the award of the degree of BACHELOR
OF COMPUTER APPLICATION is a bonafide report of the project
done by BIBIN SAJEEVAN (RegNo. 170021093014), ALEX GEORGE
(RegNo. 170021092991) during the year 2019-20.
Internal Guide Head of the Department

Dr. Shaju Varghese
Prof. Kurian M J
Examiners
Department Seal
College seal
DECLARATION
We hereby declare that this project work entitled “NETTIPPATTAM”

is a record of original work done by us under the guidance of Dr. Shaju
Varghese, Assistant Professor, Department of Computer Applications
and the work has not formed the basis for the award of any degree or
diploma or similar title to any candidate of any university subject.
Internal Guide Signature of Student
Dr. Shaju Varghese

ACKNOWLEDGEMENT
ACKNOWLEDGEMENT
At the outset, we thank God Almighty for making endeavour a success.
We express our gratitude to Dr. Tiji Zacharia, Principal,

Baselios Paulose II Catholicos College, for providing us with adequate facilities, ways
and means by which we were able to complete the project work .We express our
sincere thanks to our internal guide Dr. Shaju Varghese, Who guide us properly from
the beginning to the end of our project. With immense pleasure we take this
opportunity to record out sincere thanks to my Guide and Head of the Department
Prof. Kurian M J, Associate Professor, Department of Computer Applications in
examining the draft of this project and suggestions and modifications.
Last but not the least, we also express our gratitude to all other members of the faculty
and well-wishers who assisted us in various occasions during the project work.
:-Bibin Sajeevan
:-Alex George
ABSTRACT
ABSTRACT
Project 'Nettippattam' is an online platform for a variety of users who are related with
the Elephants of Kerala. This project is the first of its kind and a new breakthrough in
online booking, surveillance and assessment of Kerala elephants .It is a knowledge
repository for users to check and gather information about the elephants of Kerala all
in all at their fingertips.
OBJECTIVE:
This site is developed on the notion that elephants are to be handled properly by the
owners and the users in various jobs they are involved in. For executive administers,
DFO, they can make use of this web repository to gather information about their
concerned elephants at ease.
TABLE OF CONTENTS
PAGE NO
1. SYSTEM STUDY.............................................................................. 1
1.1 EXISTING SYSTEM………………………….……………………………….……2
1.1.1 DRAWBACKS……………………..……………………………………3
1.1.2 SYSTEM ANAYSIS……………………………………………….…...4
1.2 PROPOSED SYSTEM……………………………………………………….…….6
1.2.1 ADVANTAGE OF PROPOSED SYSTEM………..……..….….8
1.3 FEASIBILITY STUDY………………………………….……………………………9
1.3.1 ECONOMIC FEASIBILITY……………….…………………….……9
1.3.2 TECHNICAL FEASIBILITY……………….……………………….…10
1.3.3 BEHAVIOURAL FEASIBILITY………………..……………………10
2. SYSTEM SPECIFICATION………………………………………11
2.1 ABOUT FRONT END……………………………………………………………..12
2.2 ABOUT BACK END……………………………………………..…………..……14
2.3 ABOUT OPERATING SYSTEM…………………………………………..…..15
2.4 HARDWARE SPECIFICATION…………………………………..……………16
3. SYSTEM ANALYSIS AND DESIGN……………….……..……...17

3.1 DATA FLOW DIAGRAM………………………………………………………..18
3.2 TABLE DESIGN………………………………………………………………….….25
3.3 INPUT DESIGN…………………………………….……………………………….34
3.4 OUTPUT DESIGN………………………………………………………………….35
4. SYSTEM DESCRIPTION……………………….………………...36
5. SYSTEM TESTING AND IMPLEMENTATION……………….39
5.1 SYSTEM TESTING…………………………………….…………………………..40
5.1.1 UNIT TESTING…………………………………………………………40
5.1.2 INTEGRATION TESTING…………………………………………..41
5.1.3 VALIDATION TESTING……………………………………………..41
5.1.4 OUTPUT TESTING……………………………………………….…..42
5.2 SYSTEM IMPLEMENTATION…………………………………………………42
6. CONCLUSION……………………..……………………...……….44
7. BIBLIOGRAPHY………………...………………..…………….....46
8. APPENDIX……………………..…………………………….......... 48
8.1 INPUT FORMS…….…..….……………………………………………………….49
8.2 OUTPUT FORMS…………………………………………………………………..53

SYSTEM STUDY
1
1. SYSTEM STUDY
1.1 EXISTING SYSTEM

At the present no online platforms are available to handles the dealing with Kerala
Elephants. All the matters concerned with an elephant are done manually. People who
are in need of elephants for their use are approaching the owner or through dealers.
Booking elephants through dealers cost more money to the user. Elephants can be
hired at a high cost. Additional cost for this is not preferable for the users. The cost of
elephants can be also varied by the owners according to their wish. No records are
kept regarding this matter.
Harassment of the elephants can take place at any time. People are not taking
measures to avoid those situations .The complain about this harassment has to deals
with many legal issues and lots of time. No easy way is still available to report it
directly to higher officials.
Even if the people are aware about the elephants in Kerala, they are not provided with
enough information about them .People who wish to know about all the registered
elephants in Kerala has to go through many sources to acquire enough information.
An updated knowledge repository about the elephants in Kerala is still not available.
The facts and information about the elephants has to be acquired through the books
written about the elephants.
Temples those are hiring elephants has to cost a lot in it. A huge amount of money
has to be insured on the elephants along with the cost of hiring them. People can help
them by sponsoring the elephants during the festival occasions. But at the present
situation this has to be carried out manually.
2
Temples in need of help in money for hiring elephants has to now approach people
individually for gathering funds. No easy way to implement this process is available.
Owners are of in need of updating the medical certificate of the elephants after a given
period of time and to be approved it by DFO manually. Owners has to manually get
approved by DFO.
DFOs are responsible for surveillance and protection of elephants in their provisioned
region. They have to manually perform these actions. Even if the harassment of
elephants is taking place the reporting of this is not always happening.
As in the current situation people related with elephants have to perform lots of man
work and cost to perform various actions.
1.1.1 Drawbacks in existing system

1. Time consuming:-A lot of time is spent on the government procedures
associated with the elephants by various users. For example owners has to
update medical certificate of elephants after 15 days and to get approved by the
DFOs. DFOs has to approve the owners and to surveillance the elephants along
with other duties. Users has to check the availability of the elephants through
dealers or by contacting owners.
2. Manual record keeping:-The records regarding the elephants has to be kept
manually and to be updated manually. DFOs and owners has to manually create
records based on their concerned elephants.
3. Lack of participation from users:-in most of the cases due to various legal
procedures with regard of complaining about elephant harassment most people
are not willing to report complaints. Users are less interested in finding
sponsors for elephants due to inconvenience.
3
4. Inefficient information gathering:-Gathering of information about elephants
will take lot of work since it is not available at a single source. It is therefore
not easy to collect information about elephants.
5. Cost:-Elephants are costly and to keep or to use them a large sum of money has
to be spend. More money has to be spent on dealers to actually book elephants
and actually cost is not always revealed to the users.
6. Manual work:-The approval of government procedures takes up a lot of
manual work. Gathering funds for elephants is also done manually. No
digitalized form of booking elephants is available now.
7. Malpractices and harassment towards elephants:-Even though strict laws are
implemented for protection of elephants, harassment of elephants is taking
place. The manual records on the protection can be manipulated and the
elephants are sometimes used for more period than they are allowed.
1.1.2 System Analysis
1.1.2.1 Identifying Needs of the System
The work that was being carried out with the help of the manual system has to be
transferred to that of an advanced one for a variety of reasons,
1. The manual system is slowly being phased out and all the activities that are
being carried out by the manual system could easily and efficiently been alone
by our proposed system.
2. There are many functions that demanded computerization, but were not being
covered by the manual system.
4
3. The throughout time is high for processing
4. As information is very voluminous and it is not possible to run systematically

and accurately considering the time factor.
The system also needs easy access with a computer system we can easily access any
records in it. But when it is in manual systems it is difficult to find it using its serial
numbers or something like that. So now a day the need of the automated system is
important.
1.1.2.2 Preliminary Investigation
Visit to Kodanad Elephant training centre
While designing any system preliminary investigation is very important. It is the

essential part of the requirement analysis. The purpose of preliminary investigation is
to clarify the problems in existing system and strengthening the analyst’s idea and
background in the problem area. In our system investigation, we visited various
similar sites like our proposed system .It is seen that overall implementation of the
ideas of a user is not provided in those platforms.
5
For requirement elicitation purpose we have visited the Kodanad Elephant Training
Centre. Situated on the south bank of periyar river is a perfect spot in Ernakulum
district to train elephants. Many famous elephants like Chandrashekaran and all were
trained in this centre. When we visited the training centre there were a total of 6
elephants including 3 male elephants and 3 female elephants.2 of the male elephants
were baby elephants. The centre has large cages for the elephants training built on
wood. We interviewed the famous trainee Radhakrishnan who has written many
famous books on elephants. He taught us about the various ways elephants were
caught before the banning in Kerala and the current status of using elephants in
Kerala. He has conducted many classes in schools about elephants.
We also interviewed other elephant trainers of Kodanad training centre to gather

information about our project. The regular habits and robustness along with the food
habits of the elephants was taught to us.
The office of the research range officer Kodanad is also located inside Kodanad
training centre. The officer Madhavan Nair informed us about the various formalities
and papers required to own an elephant and to use elephants in festivals. We got the
information about the government procedures associated with elephant keeping. We
also visited some elephant lovers to know about the features that are to be included
for general users in our site
1.2 PROPOSED SYSTEM

An online platform for all the users creates a simplified environment for the users to
perform various tasks. The manual work that has to be deployed in various tasks can
be reduced considerably.
The project Nettippattam is a knowledge repository for all kinds of users. This
platform provides all the necessary details required by the users to implement their
6
operations. A user friendly all in all knowledge site about elephants is far easier and
useful for users to gather information about users.
Booking of elephants can be done directly between the users and the owners without
the need for any dealers in between them through online payment. Online payment is
cost effective and affordable way for booking elephants. The dates of the elephants
can be also verified and availability of elephants in the required period can be also
checked.
Complaints for reporting harassment against elephants can be directly reported to

appropriate DFOs with digital proofs like image/video. This method is more
approachable and preferable by the users to report their complaints. This digitalized
way of reporting complaints ensures the safe keeping and handling of elephants.
Funding or sponsorship of elephants provides a great help in temples for conducting

the festivals in apt manner without compromising in facilities provided to the
elephants. Various items like food, water, palm leaves etc. can be sponsored by the
users to the temples they are wishing to provide. Records will be kept on these funds
allocated as a proof.
In this digitalized era the updating of medical license can be done by the owner
according to periods of updating without the need to manually get certified by the
DFO. This make ease of formalities involved in this matter. DFO can accept the
owners according to the proofs and license submitted to them by the owners.
DFOs can monitor and view the booking details of each elephants. DFO can also
approve owners based on their license and proof submitted. He can also reject owners
easily according to the proofs submitted and expired medical certificate of elephants.
DFO can also view and verify the complaints reported through the online submission.
7
Thus the proposed system eases the way in which elephants are handled by the users.
This recordical methodology ensures the safety of the elephants.
1.2.1 Advantages of Proposed System

 Convenience in information gathering:-The proposed system works as a
knowledge repository about elephants. All the required information about the
elephants can be viewed and gathered from this online site easily.
 User Interface:-A user friendly user interface is incorporated in the proposed
system to conveniently and efficiently perform various tasks offered by the
system.
 More participation:-An online complaint reporting system will encourage
people to report complaints about harassment of elephants. The users can easily
offer funds to elephants they are wishing to sponsor.
 Handles records on elephants:-Digitalized records are easier to handle and to
store it for future references. These records will be available to the users who
are authorised to access them.
 Digitalize government procedures:-The government procedures associated
with elephants needs lot of time and paper works. These procedures can be
implemented at ease through the digitalized way of conducting them, like
updating of medical certificate by owners.
 Minimise cost:-The avoiding of dealers in between users and owners saves a
lot of cost. The users can get to know about the actual cost of an elephant
through the proposed system. The temples can also reduce the burden on cost
through the funds they receive.
 Efficient surveillance and protection:-Protection of elephants is the main
notion of the proposed system. This is implemented through the complaint
section and through monitoring the booking of elephants by DFO. The actual
usage of elephants is recorded and can be viewed later. The government
8
documents are also approved through the digital platform by authorized
authorities.
1.3 FEASIBILITY STUDY

During the system analysis, a feasibility study of the proposed system was carried out
to see whether it was beneficial to the organization or not. The existing system is
manual. Some data are currently recorded in books. The books have to be referred
every time when a new item is added or an item is removed. The existing system is
compared with the merits of the new system. If there is no loss for the organization
then the proposed system is considered as financially
The results of the feasibility study are:-
1. Economic feasibility
2. Technical feasibility
3. Behavioural feasibility
Economic Feasibility
Economic analysis is the most frequently used method for evaluating the effectiveness
of the proposed system. It is more commonly known as cost benefit analysis, the
procedure is to determine the benefit and saving that are expected from the proposed
system and compare them with the cost of the existing system. If the benefits
outweigh cost then a decision is made to design and implement the system. Otherwise
make alterations in the proposed system.
The system can be developed technically and if installed would still be good for the
society. The cost is found to be lesser as compared to the benefits of the proposed
9
system. The work load of the user will decrease to half of the current work load. Hence
the proposed system is found to be economically feasible.
Technical Feasibility
Technical study is a study of hardware and software requirements. Technical
feasibility concentrates on the organization to what extend it and support the proposed
system. The question to be answered is whether the organization is technically
capable to operate the system
Hardware Requirements:
 Pentium IV
 256MB RAM
 500MB HDD
Software Requirements:
 Windows 2000 or above

 Web Browser
 Wamp server
Behavioural Feasibility
The developed system is completely driven and user friendly. Also the system is
developed using HTML, CSS and JavaScript as front end, which is user interface.
There is no need of skill for new user to open this Website and use it.
10
SYSTEM SPECIFICATION
11
2. SYSTEM SPECIFICATION
2.1 ABOUT THE FRONT END

The system is created using HTML, CSS and JavaScript as front end.
HTML
HTML is a computer language devised to allow Website creation. These Websites
can then be viewed by anyone else connected to the Internet. It is relatively easy to
learn, with the basics being accessible to most people in one sitting; and quite
powerful in what it allows you to create. It is constantly undergoing revision and
evolution to meet the demands and requirements of the growing Internet audience
under the direction of the W3C, the organization charged with designing and
maintaining the language.
HTML consists of a series of short codes typed into a text-file by the site author —
these are the tags. The text is then saved as an html file, and viewed through a browser,
like Internet Explorer or Netscape Navigator. This browser reads the file and
translates the text into a visible form, hopefully rendering the page as the author had
intended. Writing your own HTML entails using tags correctly to create your vision.
You can use anything from a rudimentary text-editor to a powerful graphical editor
to create HTML pages.
CSS
Stands for "Cascading Style Sheet." Cascading style sheets are used to format the
layout of Web pages. They can be used to define text styles, table sizes, and other
aspects of Web pages that previously could only be defined in a page's HTML.
12
CSS helps Web developers create a uniform look across several pages of a Web site.
Instead of defining the style of each table and each block of text within a page's
HTML, commonly used styles need to be defined only once in a CSS document. Once
the style is defined in cascading style sheet, it can be used by any page that references
the CSS file. Plus, CSS makes it easy to change styles across several pages at once.
For example, a Web developer may want to increase the default text size from 10pt
to 12pt for fifty pages of a Web site. If the pages all reference the same style sheet,
the text size only needs to be changed on the style sheet and all the pages will show
the larger text.
While CSS is great for creating text styles, it is helpful for formatting other aspects of
Web page layout as well. For example, CSS can be used to define the cell padding of
table cells, the style, thickness, and colour of a table's border, and the padding around
images or other objects. CSS gives Web developers more exact control over how Web
pages will look than HTML does. This is why most Web pages today incorporate
cascading style sheets.
JavaScript
JavaScript is a dynamic computer programming language. It is lightweight and most
commonly used as a part of Web pages, whose implementations allow client-side
script to interact with the user and make dynamic pages. It is an interpreted
programming language with object-oriented capabilities.
JavaScript was first known as LiveScript, but Netscape changed its name to
JavaScript, possibly because of the excitement being generated by Java. JavaScript
made its first appearance in Netscape 2.0 in 1995 with the name LiveScript. The
general-purpose core of the language has been embedded in Netscape, Internet
Explorer, and other Web browsers.
13
2.2 ABOUT THE BACK END
The system is created with PHP and MySQL as backend.
PHP
PHP started out as a small open source project that evolved as more and more people
found out how useful it was. Rasmus Lerdorf unleashed the first version of PHP way
back in 1994.
PHP is a MUST for students and working professionals to become a great Software
Engineer especially when they are working in Web Development Domain. The key
advantages of learning PHP are:
PHP is a recursive acronym for "PHP: Hypertext Pre-processor".
PHP is a server side scripting language that is embedded in HTML. It is used to

manage dynamic content, databases, session tracking, even build entire e-commerce
sites. It is integrated with a number of popular databases, including MySQL,
PostgreSQL, Oracle, Sybase, Informix, and Microsoft SQL Server.
PHP is pleasingly zippy in its execution, especially when compiled as an Apache

module on the UNIX side. The MySQL server, once started, executes even very
complex queries with huge result sets in record-setting time. PHP supports a large
number of major protocols such as POP3, IMAP, and LDAP. PHP4 added support for
Java and distributed object architectures (COM and CORBA), making n-tier
development a possibility for the first time. PHP is forgiving: PHP language tries to
be as forgiving as possible. PHP Syntax is C-Like.
14
MYSQL
MySQL is an open-source relational database management system (RDBMS).Its

name is a combination of "My", the name of co-founder Michael Widenius's
daughter, and "SQL", the abbreviation for Structured Query Language.
MySQL is free and open-source software under the terms of the GNU General Public
License, and is also available under a variety of proprietary licenses. MySQL was
owned and sponsored by the Swedish company MySQL AB, which was bought
by Sun Microsystems (now Oracle Corporation). In 2010, when Oracle acquired Sun,
Widenius forked the open-source MySQL project to create Maria DB.
2.3 ABOUT THE OPERATING SYSTEM

The OS used is Windows Operating System.
WINDOWS OS
Windows 10 is a series of personal computer operating systems produced by
Microsoft as part of its Windows NT family of operating systems. It is the successor
to Windows 8.1, and was released to manufacturing on July 15, 2015, and broadly
released for retail sale on July 29, 2015. Windows 10 receives new builds on an
ongoing basis, which are available at no additional cost to users, in addition to
additional test builds of Windows 10 which are available to Windows Insiders. The
latest stable build of Windows 10 is Version 1909 (November 2019-20 Update).
Devices in enterprise environments can receive these updates at a slower pace, or use
long-term support milestones that only receive critical updates, such as security
patches, over their ten-year lifespan of extended support.
15
2.4 HARDWARE SPECIFICATION
Selection of hardware configuration is very important task related to the software

development. The processor should be powerful to handle all the operations. The hard
disk should have the sufficient capacity to solve the database and the application.
Processor Minimum: 1 GHz (x86 processor or x64 processor)
Recommended: 2 GHz or faster (dual-core or quad-core will be much faster)
Memory Minimum: 1 GB RAM for 32-bit system, 2 GB RAM for 64-bit systems
Recommended: 2 GB RAM or greater
Available Disk Space Minimum: 16 GB for 32-bit systems, 20 GB for 64-bit

systems
Recommended: 40 GB or greater
Recommended Monitor Resolutions: 1920 x 1080 or 1366 x 768
16
SYSTEM ANALYSIS
AND
DESIGN
17
3. SYSTEM ANALYSIS AND DESIGN
System design’s main aim is to identify the modules that should be in the system, and
the specifications of these modules and how they interact with each other to produce
the desired results. At the end of the system design all the major data structures, file
formats and the major modules in the system and their specification are decided.
3.1 DATA FLOW DIAGRAM

A DFD has the purpose of clarifying system requirements and identifying major
transformations that will become programs in system design.
These symbols are used in the DFD:
Source or destination of data
Data Flow
Process that transforms data flow
Data store
18
Level 0 (Context Diagram)
Level 1 Users
19
Level 2 Admin
20
Level 2 User
21
Level 2 Owner
22
Level 2 DFO
23
Level 2 Temple
24
3.2 TABLE DESIGN
The general theme behind a database is to handle information as an integrated whole.

A database is a collection of interrelated data stored with minimum redundancy to
serve quick access and effective storage. The database is a collection of stored data
organized in such a way that all the data requirements are satisfied by the database.
The aim of database design is to improve the existing system situation. A number of
database files were designed to hold the data requirements for running their systems.
Here we have 16 major tables, described below:
1. TABLE NAME: tbl_admin

PRIMARY KEY: username
DESCRIPTION: ADMIN DETAILS
SL.NO FIELD NAME FIELD TYPE FIELD SIZE CONSTRAINS DESCRIPTION

1 admin_id int 11 NOT NULL Admin id
2 username varchar 500 NOT NULL Admin username
3 password varchar 500 NOT NULL Admin password
2. TABLE NAME: tbl_booking

PRIMARY KEY: booking_id
DESCRIPTION: BOOKING DETAILS

1 booking_id int 11 NOT NULL Elephant booking
2 user_id int 11 NOT NULL User id
3 elephant_id int 11 NOT NULL Elephant id
4 amount int 11 NOT NULL Elephant amount
5 start_date date 11 NOT NULL Start date
6 end_date date 11 NOT NULL End date
7 hours int 11 NOT NULL hours
25
3. TABLE NAME: tbl_complaint
PRIMARY KEY: complaint_id
DESCRIPTION: COMPLIANT BOX
1 compliant_id int 11 NOT NULL Compliant id

2 district_id int 11 NOT NULL District id
3 subject varchar 500 NOT NULL Compliant subject
4 description varchar 500 NOT NULL Compliant description
5 photo varchar 500 NOT NULL Compliant photo
7 date date 500 NOT NULL Compliant date
8 status int 11 NOT NULL Compliant status
4. TABLE NAME: tbl_dfo

PRIMARY KEY: dfo_id
DESCRIPTION: DISTRICT FOREST OFFICER
1 dfo_id int 11 NOT NULL DFO id

2 name varchar 11 NOT NULL DFO name
3 gender varchar 500 NOT NULL DFO gender
4 dob date 500 NOT NULL DFO dob
5 contact varchar 500 NOT NULL DFO contact
6 district_id int 11 NOT NULL DFO district id
7 address varchar 500 NOT NULL DFO address
8 email varchar 500 NOT NULL DFO email
9 user_name varchar 500 NOT NULL DFO user name
10 password varchar 500 NOT NULL DFO password
11 proof varchar 500 NOT NULL DFO proof
12 status int 11 NOT NULL DFO status
13 place_id int 11 NOT NULL DFO Place id
14 photo varchar 500 NOT NULL DFO photo
15 squetion1 int 11 NOT NULL Security Question 1
17 sanswer1 varchar 500 NOT NULL Security Question
Answer 1
26
Answer 2
5. TABLE NAME: tbl_district

PRIMARY KEY: district_id
DESCRIPTION: DISTRICT DETAILS

1 district_id varchar 500 NOT NULL District id
2 name varchar 500 NOT NULL District name
6. TABLE NAME: tbl_elephant

PRIMARY KEY: elephant_id
DESCRIPTION: DETAILS OF ELEPHANT

2 name varchar 500 NOT NULL Elephant name
3 type_id int 11 NOT NULL Elephant type id
4 height int 11 NOT NULL Elephant height
5 medical_proof varchar 500 NOT NULL Medical proof
6 gender int 11 NOT NULL Elephant gender
7 age int 11 NOT NULL Elephant age
8 microchipno int 11 NOT NULL Elephant microchip no
9 licence_proof varchar 500 NOT NULL Licence proof
10 owner_id int 11 NOT NULL Owner id
11 status varchar 500 NOT NULL Status
12 photo varchar 500 NOT NULL Elephant photo
13 honor varchar 500 NOT NULL Elephant honor
14 amount int 11 NOT NULL Elephant amount
27
7. TABLE NAME: tbl_elephantdesign
PRIMARY KEY: elephantdesign_id
DESCRIPTION: ELEPHANT DESIGNATION
SL.NO FIELD NAME FIELD TYPE FIELD SIZE

CONSTRAINS DESCRIPTION
1 elephantdesign_id int 11 NOT NULL Elephant designation id
2 elephantdesign_name varchar 500 NOT NULL Elephant
designation name
8. TABLE NAME: tbl_elephanttype

PRIMARY KEY: type_id
DESCRIPTION: ELEPHANT TYPE

1 type_id int 50 NOT NULL Elephant type
2 type_name varchar 500 NOT NULL Elephant type name
9. TABLE NAME: tbl_feedback

PRIMARY KEY: feedback_id
DESCRIPTION: FEEDBACKS FROM USERS

1 feedback_id int 11 NOT NULL Feedback id
4 description varchar 500 NOT NULL Description
5 date date 11 NOT NULL Date
6 status date 11 NOT NULL Status
7 subject varchar 500 NOT NULL Subject
8 status int 11 NOT NULL Status
28
10. TABLE NAME: tbl_festival
PRIMARY KEY: festival_id
DESCRIPTION: DETAILS OF FESTIVAL

1 district_id int 11 NOT NULL District id
2 place_id int 11 NOT NULL Place id
3 location varchar 500 NOT NULL Festival location
4 end_date date 11 NOT NULL Festival end date
5 description varchar 500 NOT NULL Festival description
6 elephants varchar 500 NOT NULL Elephants
7 festival_photo varchar 500 NOT NULL Festival photos
8 festival_id int 11 NOT NULL Festival id
9 temple_id int 11 NOT NULL Temple id
11 status varchar 500 NOT NULL Elephant proof
12 start_date date 500 NOT NULL Festival start date
11. TABLE NAME: tbl_fund

PRIMARY KEY: fund_id
DESCRIPTION: ELEPHANT FUND

1 fund_id int 11 NOT NULL Fund id
2 type_id int 11 NOT NULL Fund type id
3 description varchar 500 NOT NULL Fund description
5 status int 11 NOT NULL Fund status
6 festival_id int 11 NOT NULL Festival id
12. TABLE NAME: tbl_fundtype

PRIMARY KEY: type_id
DESCRIPTION: ELEPHANT FUND TYPE

1 type_id int 11 NOT NULL Fund type id
2 type_name varchar 500 NOT NULL Fund type name
29
13. TABLE NAME: tbl_gallery
PRIMARY KEY: elephantgallery_id
DESCRIPTION: ELEPHANT GALLERY

1 elephantgallery_id varchar 500 NOT NULL Elephant gallery
3 description varchar 500 NOT NULL Description
4 date date NOT NULL Date
5 type varchar 500 NOT NULL Type
6 image/video varchar 500 NOT NULL Images and videos
14. TABLE NAME: tbl_owner

PRIMARY KEY: owner_id
DESCRIPTION: OWNER
1 owner_id int 11 NOT NULL Owner id

2 name varchar 11 NOT NULL Owner name
3 gender varchar 500 NOT NULL Owner gender
4 dob date 500 NOT NULL Owner dob
5 contact varchar 500 NOT NULL Owner contact
6 district_id int 11 NOT NULL Owner district id
7 address varchar 500 NOT NULL Owner address

8 email varchar 500 NOT NULL Owner email
9 user_name varchar 500 NOT NULL Owner user name
10 password varchar 500 NOT NULL Owner password
11 proof varchar 500 NOT NULL Owner proof

12 status int 11 NOT NULL Owner status
13 place_id int 11 NOT NULL Owner place id
14 photo varchar 500 NOT NULL Owner photo
Answer 1
Answer 2
30
15. TABLE NAME: tbl_place
PRIMARY KEY: place_id
DESCRIPTION: PLACE DETAILS

1 place_id int 11 NOT NULL Place id
2 place_name varchar 500 NOT NULL Place name
3 district_id int 50 NOT NULL District
16. TABLE NAME: tbl_elephantreview

PRIMARY KEY: review_id
DESCRIPTION: ELEPHANT REVIEW DETAILS

1 review_id int 11 NOT NULL Review id
2 review varchar 500 NOT NULL User review
5 date date 500 NOT NULL Review date
17. TABLE NAME: tbl_temple

PRIMARY KEY: temple_id
DESCRIPTION: TEMPLE DETAILS

1 temple_id int 11 NOT NULL Temple id
2 name varchar 11 NOT NULL Temple name
3 contact varchar 500 NOT NULL Temple contact
4 district_id int 11 NOT NULL Temple district id
5 address varchar 500 NOT NULL Temple address

6 email varchar 500 NOT NULL Temple email
7 user_name varchar 500 NOT NULL Temple user name
8 password varchar 500 NOT NULL Temple password
9 proof varchar 500 NOT NULL Temple proof

10 status int 11 NOT NULL Temple status
31
11 place_id int 11 NOT NULL Temple place id
12 photo varchar 500 NOT NULL Temple photo
Answer 1
Answer 2
18. TABLE NAME: tbl_user

PRIMARY KEY: user_id
DESCRIPTION: USER DETAILS

2 name varchar 11 NOT NULL User name
3 gender varchar 500 NOT NULL User gender
4 dob date 500 NOT NULL User dob
5 contact varchar 500 NOT NULL User contact
6 district_id int 11 NOT NULL User district id
7 address varchar 500 NOT NULL User address
8 email varchar 500 NOT NULL User email
9 username varchar 500 NOT NULL User name
10 password varchar 500 NOT NULL User password
12 status int 11 NOT NULL User status
13 place_id int 11 NOT NULL User place id
14 photo varchar 500 NOT NULL User photo
Answer 1
Answer 2
32
19. TABLE NAME: tbl_squestion
PRIMARY KEY: squestion_id
DESCRIPTION: SECURITY QUESTIONS

1 squestion_id int 11 NOT NULL Security Question id
2 squestion varchar 500 NOT NULL Security Question
33
3.3 INPUT DESIGN
Input is the process of converting user inputs computer based format. The project
requires a set of information from the user to prepare a report. In the order, when
organized input data are needed.
In the system design phase, the expanded DFD identifies logical data flow, data stores
and destination. Input data is collected and organized into groups of similar data. The
goal behind designing input data is to make the data entry easy and make it free from
logical error .So the input screens in the system should be really flexible and faster to
use. The input entry to all type of clients is the Username and password. If they are
valid the User is allowed to enter into the software. The input design determines
whether the user can interact directly with the computer.
Objectives
  To produce a cost-effective method of input
 To achieve the highest possible level of accuracy.
  To ensure that the input is acceptable and understandable
  To make clutter free screens

  The prevention of irrelevant data entry
 To make user friendly input screen
Here in our system, ‘NETTIPPATTAM’, interactive input screens ensure the

reliability and accuracy of the system. The intended input details, Account details,
posting details etc. For example like the below login form.
34
3.4 OUTPUT DESIGN
Outputs are the most important direct source of information to the user and to the
management. Efficient and eligible output design should improve the system’s
relationship with the user and help in decision making. The system mainly consists of
outputting the posts and messages. For example like the admin home page shown
below.
35
SYSTEM DESCRIPTION
36
4. SYSTEM DESCRIPTION
The new system is intended to perform the following tasks,

 Knowledge repository:-The site acts as a knowledge repository to various users
who need information about the elephants. The information is recorded and
viewed in precise and validated manner such that correct information is
provided to the users.
 Register accounts:-The various users- DFO, user, temple & owner can register
and create accounts to access various tasks they need to perform.
 Report complaints:-The users can report complaint about the harassment of
elephants through valid digital evidence to DFO directly with ease.
 Manage DFO:-The DFO is accepted or rejected by the admin after checking
the valid proof and licence submitted. After acceptance DFO can perform
various tasks through the site.
 Manage temple:-The user temple is also accepted or rejected by the admin after
verification of licence proof.
 Provide Fund:-The funds can be provided by the users to the temples they are
wishing to donate. These fund type can be palm leaves, water, food etc. to the
elephants.
 Provide Feedback:-Users can also provide feedback to the owners whose
elephants where used by the user. Feedback helps owners to know the opinions
about the users about their elephants.
 Book Elephants:-Elephants can be booked through this online platform after
checking all the details about the elephants. The dates in which elephants will
be available for booking can also be verified.
 Rate elephants: - There is also the facility to rate the elephants by the users.
Star rating is used to rate the elephants. Users can rate and write a review about
the elephants.
37
 Register Elephants:-Elephant accounts are created by the owners after
submitting proper certificates digitally.
 Add festival details:-Temples can add festival details so that the users can get
to know about the festivals that are about to take place in their locality.
 Surveillance of elephants:-The DFO can check every booking details of the
elephants so that he can make sure that elephants are not over used by the
owner.
38
SYSTEM TESTING
AND
IMPLEMENTATION
39
5. SYSTEM TESTING AND IMPLEMENTATION
Software testing is a critical element of system quality assurance and represents the
ultimate reviews of specification, design and coding. Testing presents an interesting
anomaly for the software. Testing is vital to the success of the system. Errors can be
injected at any stage during development. System testing makes a logical assumption
that if all the parts of the system are correct, the goal will be successfully achieved.
During testing, the program to be tested is executed with set of test data and output of
the program for the test data is evaluated to determine if the program is performing as
expected. A series of testing are performed for the proposed system before the system
is ready for the user acceptance testing.
TYPES OF TESTING
* Unit Testing
* Integration Testing
* Validation Testing
* Output Testing
5.1 SYSTEM TESTING

5.1.1 UNIT TESTING
Unit testing focuses verification effort on the smallest unit of the software design, the
module this is known as module testing. Since the proposed system has modules the
testing is individually performed on each module.
Using the details description as a guide, important control paths are tested to uncover
errors within the boundary of the modules. This testing was carried out during
programming stage itself. In this testing step each module is found to be working
40
satisfactorily as regards to the expected output from the module. In our system, we
want to check the information like whether the inputs are saved to back end correctly.
So every form includes this testing because we want to maintain our database because
information like document to be saved, the personal information, security features are
so sensitive and should check it perfectly by each module from the beginning. These
are checked in the programming step itself.
5.1.2 INTEGRATION TESTING

Data can be test across an interface, one module can have adverse effect on another,
and sub function when combined may not produce the desired function. Integration
testing is a systematic technique for constructing the program structure while at the
same time conducting test to uncover errors associated within the interface.
The objective is to take unit tested modules and built a program structure that has
been dictated by design. All modules are combined in this testing step. The entire
program is tested as a whole. Correction is difficult at this stage because the isolation
of causes is complicated by the vast expense of the program. Thus in the integration
testing step all the errors uncover are corrected for the next testing step. Primarily we
have met with several errors like data save and table linking. These are corrected well.
5.1.3 VALIDATION TESTING

At the culmination of integration testing, software is completely assembled as a
package. Interfacing errors have been uncovered and corrected and a final series of
software test-validation testing begins. Validation testing can be defined in many
ways, but a simple definition is that validation succeeds when the software functions
in manner that is reasonably expected by the user. Software validation is achieved
through a series of tests that demonstrate conformity with requirement. After
validation test has been conducted, one of two conditions exist.
41
• The function or performance characteristics confirm to specifications and are
accepted.
• A validation from specification is uncovered and a deficiency created .Deviation
or error discovered at this step in this project is corrected prior to completion of the
project with the help of the user. Thus the proposed system under consideration has
been tested by using validation testing and found to be working satisfactorily.
5.1.4 OUTPUT TESTING

After performing the validation testing, the next step is output testing of the proposed
system since no system could be useful if it does not produce the required output in
the specific format. The output generated or displayed by the system under
consideration is tested asking the users about the format required by them.
In the first test, we saw that our services are disordered and not interactive. We made
it in this step. The output format on the screen is found to be correct as the format
designed according to the user needs. For the hard copy also, the output comes out as
specified by the user. Hence output testing doesn’t result in any connection in the
system.
5.2 SYSTEM IMPLEMENTATION

Implementation is the stage in the project where the theoretical design is turned into
a working system and is giving confidence on the new system for the users that it will
work efficiently and effectively. It involves careful planning, investigation of the
current system and its constraints implementation, design of methods to achieve the
changeover, an evaluation, of change over methods.
42
Implementation is the final and important phase. The most critical stage in achieving
a successful new system and in giving the users confidence that the new system will
work and be effective. The system can be implemented only after through testing is
done and if it found to working according to the specification. This method also offers
the greatest security since the old system can take over if the errors are found or
inability to handle certain type of transactions while using the new system.
At the beginning of the development phase a preliminary implementation plan is

created to schedule and manage the many different activities must be integrated into
plan. The implementation plan is updated throughout the development phase,
culminating in a changeover plan for the operation phase. The major elements of
implementation plan are test plan, training plan, equipment installation plan and a
conversion plan.
There are three types of implementation:
• Implementation of a computer system to replace a manual system.
• Implementation of a new computer system to replace an existing one.
• Implementation of a modified application to replace an existing one, using the
same computer.
43
CONCLUSION
44
6. CONCLUSION
The project entitled “NETTIPPATTAM” was completed on time. This project

provided maximum interaction and flexibility. The system was tested and the
performance of the system was provided to be much efficient and data maintenance
is achieved partially. The system has been developed in attractive fashion.
The modules in the system help in faster development, implementation and

maintenance of the software. This system has been developed as versatile and user
friendly as possible keeping in mind the advanced features. Using HTML, CSS,
JavaScript, PHP and MYSQL, the system was developed and tested with all possible
samples of data. As a whole, the system was well planned and designed. The
performance of the system is proved to be efficient. And it already provide all the
objectives we have identified before.
All modules are tested separately and put together to form the main system. Finally
the system is tested with the real data and everything worked successfully. Thus the
system has fulfilled the entire objective identified. The system required least hardware
requirement to work on. So we can state, we have developed such a good environment
for communication, to connect with more people. And it provides a number of
advantages too as we described in the previous sections.
To conclude this, we thank all people who help us to complete this project work
successfully.
45
BIBLIOGRAPHY
46
7. BIBLIOGRAPHY
SYSTEM ANALYSIS AND DESIGN

Elias M Award,
Second Edition, 1999,
Galgotia Publications, Delhi.
DATABASE SYSTEM CONCEPTS

Silberschatz,
Korth, Sudarshan,
Fourth Edition.
WEB PROGRAMMING USING PHP
Jeeva Jose
Kalyani publications
HTML 5 BLACK BOOK
Steven Holzner
Dreamtech Press
47
APPENDIX
48
8. APPENDIX
LAUNCHING PAGE
USER HOMEPAGE
49
8.1 INPUT FORMS DESIGN
FORM 1 - LOGIN PAGE
FORM 2 -CREATE NEW ACCOUNT
50
FORM 3 -CHANGE PASSWORD
FORM 4 -ENTER FUND TYPE
51
FORM 5 -COMPLAINT
FORM 6-ELEPHANT BOOKING
52
8.2. OUTPUT FORMS DESIGN
FORM 1 –VIEW PROFILE
FORM 2–DFO ACCEPTED LIST
53
FORM 3 –TEMPLE DETAILS
FORM 4 –ELEPHANT DETAILS
54
FORM 5 –COMPLAINTS
FORM 6– FESTIVAL DETAILS
55

Nettippattam

Uploaded by

Copyright:

Available Formats

You might also like

Nettippattam

Uploaded by

Document Information

Original Description:

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

Nettippattam

Uploaded by

Copyright:

Available Formats

BASELIOS POULOSE II CATHOLICOS COLLEGE

BASELIOS MOUNT, PIRAVOM

Accredited with ‘A’ Grade by NAAC

(Affiliated to Mahatma Gandhi University)

DEPARTMENT OF COMPUTER APPLICATIONS

(Affiliated to Mahatma Gandhi University)

DEPARTMENT OF COMPUTER APPLICATIONS

Accredited with ‘A’ Grade by NAAC

(Affiliated to Mahatma Gandhi University)

DEPARTMENT OF COMPUTER APPLICATIONS

Internal Guide Head of the Department

We hereby declare that this project work entitled “NETTIPPATTAM”

Internal Guide Signature of Student

Dr. Shaju Varghese

At the outset, we thank God Almighty for making endeavour a success.

We express our gratitude to Dr. Tiji Zacharia, Principal,

1.1 EXISTING SYSTEM………………………….……………………………….……2

1.1.2 SYSTEM ANAYSIS……………………………………………….…...4

1.2 PROPOSED SYSTEM……………………………………………………….…….6

1.2.1 ADVANTAGE OF PROPOSED SYSTEM………..……..….….8

1.3 FEASIBILITY STUDY………………………………….……………………………9

1.3.1 ECONOMIC FEASIBILITY……………….…………………….……9

1.3.2 TECHNICAL FEASIBILITY……………….……………………….…10

1.3.3 BEHAVIOURAL FEASIBILITY………………..……………………10

2.1 ABOUT FRONT END……………………………………………………………..12

2.2 ABOUT BACK END……………………………………………..…………..……14

2.3 ABOUT OPERATING SYSTEM…………………………………………..…..15

2.4 HARDWARE SPECIFICATION…………………………………..……………16

3. SYSTEM ANALYSIS AND DESIGN……………….……..……...17

3.2 TABLE DESIGN………………………………………………………………….….25

3.3 INPUT DESIGN…………………………………….……………………………….34

3.4 OUTPUT DESIGN………………………………………………………………….35

5. SYSTEM TESTING AND IMPLEMENTATION……………….39

5.1 SYSTEM TESTING…………………………………….…………………………..40

5.1.1 UNIT TESTING…………………………………………………………40

5.1.2 INTEGRATION TESTING…………………………………………..41

5.1.3 VALIDATION TESTING……………………………………………..41

5.1.4 OUTPUT TESTING……………………………………………….…..42

5.2 SYSTEM IMPLEMENTATION…………………………………………………42

8.1 INPUT FORMS…….…..….……………………………………………………….49

8.2 OUTPUT FORMS…………………………………………………………………..53

1.1 EXISTING SYSTEM

1.1.1 Drawbacks in existing system

1.1.2 System Analysis

1.1.2.1 Identifying Needs of the System

4. As information is very voluminous and it is not possible to run systematically

1.1.2.2 Preliminary Investigation

Visit to Kodanad Elephant training centre

While designing any system preliminary investigation is very important. It is the

We also interviewed other elephant trainers of Kodanad training centre to gather

1.2 PROPOSED SYSTEM

Complaints for reporting harassment against elephants can be directly reported to

Funding or sponsorship of elephants provides a great help in temples for conducting

1.2.1 Advantages of Proposed System

1.3 FEASIBILITY STUDY

The results of the feasibility study are:-

 Windows 2000 or above