VISVESVARAYA TECHNOLOGICAL UNIVERSITY

BELAGAVI-590018

A MINI PROJECT REPORT

ON
FISHERIES MANAGEMENT

BY
AJAY SHETTY AKSHIRA
(4MT20CS008) (4MT20CS012)

In the partial fulfillment of the requirement for 5th semester

DBMS LABORATORY WITH MINI PROJECT

Under the guidance of

Mr. SUNIL KUMAR S Dr. DINESHA L

Senior Assistant Professor Associate Professor

Department of Computer Science and Engineering

(Accredited by NBA)

MANGALOREINSTITUTEOFTECHNOLOGY&ENGINEERING
Badaga, Mijar, Moodbidri-574225 2021-2022
 MANGALORE INSTITUTE OF TECHNOLOGY & ENGINEERING
Accredited by NAAC with A+ Grade, An ISO 9001: 2015 Certified Institution
(A Unit of Rajalaxmi Education Trust®, Mangalore - 575001)
Affiliated to V.T.U., Belagavi, Approved by AICTE, New Delhi.

Department of Computer Science & Engineering

(Accredited by NBA)

CERTIFICATE

This is to certify that the mini project entitled “PONDZILLA” is a bonafide work carried out by
AJAY SHETTY (4MT20CS008) and AKSHIRA (4MT20CS012) in partial fulfillment for the
requirement of 5th semester DBMS Laboratory with mini project (18CSL58). It is certified that all
the corrections / suggestions indicated for the Internal Assessment have been incorporated in the
report. The mini project has been approved as it satisfies the academic requirement in respect of
the 18CSL58 prescribed for the 5th Semester B.E in Computer Science & Engineering Program by
the Visvesvaraya Technological University, Belagavi, for the academic year 2021 – 2022.

………………………… ………………………… …………………………

Mr.Sunil Kumar S Dr. Dinesha L Dr. Ravinarayana B

Senior Assistant Professor Associate Professor Associate Professor & HOD

MITE, Moodabidri MITE, Moodabidri MITE, Moodabidri

Signature of the Examiners Signature with Date

1. ………………………….. ……………………………..

2. ………………………….. ……………………………..
 ABSTRACT

"Fisheries Management" is a web application. This system is developed to automate day to day
activity of fish vendors. This website is a link through which breeders dealers and owners of the pond
can interact. Fish is one of the favorite items in the food menu of almost 60% of Indians,So market
demand is always high for fish items. If we consider the global demand also,the total requirement
becomes very high.The overall goal of fisheries management is to produce sustainable biological,
social, and economic benefits from renewable aquatic resources. Fish farming involves raising fish
commercially in tanks or enclosures, usually for food.
The major freshwater farming environments in India are pond, cage, pen, rice field, sewage feed and
air breathing. Polyculture is the dominant culture system practiced. The major species are catla,
freshwater sardines and rohu. Basically India's aquaculture is carp-oriented and the contribution of
other species is marginal. Fish culture in India can be classified as extensive, semi-intensive or
intensive and stocking rate is high at 18,408 fish/ha. Both the central and state governments have
come up with schemes to help the cause of the farmers. India is a large producer of inland fish, ranking
next only to Japan. Out of the total inland fish production of over 3.6 million metric tons, more than
60% is contributed by fish culture in ponds and reservoirs. Fish farming is adopted by farmers on
commercial scale.
 ACKNOWLEDGEMENT

The successful completion of any significant task is the outcome of invaluable aggregate
combination of different people in radial direction explicitly and implicitly. We would therefore
take opportunity to thank and express our gratitude to all those without whom the completion of
project would not be possible.

We express our thanks to Mr. Sunil Kumar S, Senior Assistant Professor and Dr. Dinesha L,
Associate Professor Department of Computer Science and Engineering for having provided all
the facilities that helped us in timely completion of this report.

We express our sincere gratitude to Dr. Ravinarayana B, Associate Professor, Head of the
Department, Computer Science and Engineering for his support and guidance.

We are grateful to Dr. Ganesh Prasad, Principal, Mangalore Institute of Technology and
Engineering, Moodabidri for his support and encouragement.

I express my sincere gratitude to our institution and management for providing us with good
infrastructure, laboratory facilities, qualified and inspiring staffs, and whose guidance was of
immense help in completion of this seminar successfully.

AJAY SHETTY ( 4MT20CS008)

AKSHIRA( 4MT20CS012)
 TABLE OF CONTENTS
Abstract…...................................................................................................i
Acknowledgement…...................................................................................ii
CONTENT PAGE NO
1. INTRODUCTION 1-2
1.1 Problem Statement 1
1.2 Objective 1
1.3 SQL 1
1.4 NODE JS 1
1.5 HTML 2
1.6 CSS3 2

2. REQUIREMENT ANALYSIS AND SPECIFICATION 3-5

2.1 Functional Requirements 3
2.1.1 Users 3
2.1.2 Dealers 3
2.1.3 Admin 3
2.2 Non-Functional Requirements 3

3. SYSTEM DESIGN 5-10

3.1 ER Diagram 5
3.2 Schema diagram 6
3.3 Description of Tables 6

4. IMPLEMENTATION 9-14
4.1 Code Snippets 10-14

5. TESTING 15-17
5.1 Testing Process 15
5.1.1 Unit testing 15
5.1.2 Integration testing 15
5.1.3 System testing 16
5.2 Test Cases 16

6. Snapshots 18-23
7. Conclusion 24
References 25

LIST OF FIGURES
Sl. No TITLE PAGE NO.
Figure 3.1 ER Diagram of PONDZILLA 5
Figure 3.2 Schema Diagram of PONDZILLA 6
Figure 4.1.1 Code Snippet of Connection Module 9
Figure 4.1.2 Code Snippet of Registration Module 10
Figure 4.1.3 Code Snippet of Login Module 11
Figure 4.1.4 Code snippet of View Module 12
Figure 4.1.5 Code Snippet of Delete Module 12
Figure 6.1 Screenshot of Home page 18
Figure 6.2 Screenshot of User Register page 18
Figure 6.2 Screenshot of Owner page 19
Figure 6.3 Screenshot of Dealer page 19
Figure 6.4 Screenshot of Breeder page 20
Figure 6.5 Screenshot of Species page 20
Figure 6.6 Screenshot of Pond page 21
Figure 6.7 Screenshot of Contact Us page 21
Figure 6.8 Screenshot of deals page 22
Figure 6.9 Screenshot of Buying page 22
Figure 6.10 Screenshot of Update page 23
Figure 6.11 Screenshot of Selling Page 23

LIST OF TABLES 7

Table 5.1 Test Case for Login 16

Table 5.2 Test Case for Register 17

Table 5.3 Test Case for Update 17

Chapter 1 INTRODUCTION

The objective of the application is to develop a system using which the fish breeder’s and buyers can
communicate with each other. Pondzilla is an application where the users can register themselves at the
website as breeders dealers or the owners. Pondzilla is an online fish marketplace System which is a
package to be used by people to acess it online. The system provides information regarding the type of
species that are being breeded and also give us the information regarding the ponds in which they are
breeded for sale. The buyers and sellers can keep the fish catalogue detailed. The purpose of Pondzilla is
to automate the manual work of looking out for dealers. The required software and hardware are easily
available and it is easy to work with. Pondzilla, as described above, can lead to error free, secure, reliable
and fast management system.

1.1 Problem Statement

To develop an online fisheries management system where the owners buys species from breeders and
sells it to the dealers and also to manage pond fish cultivation.

1.2 Objective
⚫ To buy species from breeders and sell it to the dealers
⚫ To allow the admin to view and update the species that are available.

1.3 SQL
SQL (Structured Query Language) is the language which is used to communicate to our database. It’s
used on the back-end of website to provide access to user data. A web framework is used to display SQL
data on web page and write simple SQL query to link a website to a database.

1.4 NODE JS

Node.js is an open source server environment.It is free.Node.js runs on various platforms

(Windows, Linux, Unix, Mac OS X, etc.) Node.js uses JavaScript on the server. Node.js runs

single-threaded, non-blocking, asynchronous programming, which is very memory

efficient.Node.js can collect form data and can add, delete, modify data in your database

1.5 HTML5

Dept of CS&E, MITE, Moodabidri 1

HTML (Hyper Text Markup Language) is used to create the physical structure of the website. It provides
necessary tags for setting up a foundation for the website to be created. It is assisted by CSS in the
designing section. Web browsers receive HTML documents from a web server or from local storage and
render the documents into multimedia web pages. HTML describes the structure of a web page
semantically and originally included cues for the appearance of the document. HTML can embed
programs written in a scripting language such as JavaScript, which affects the behavior and content of
web pages.

1.6 CSS3
CSS (Cascading Style Sheets) is used to design the web page that is created through HTML. CSS is used
here to style the web pages. It describes the look and formatting of a document which is written in markup
language. CSS is designed to enable the separation of presentation and content, including layout, colors,
and fonts .This separation can improve content accessibility; provide more flexibility and control in the
specification of presentation characteristics; enable multiple web pages to share formatting by specifying
the relevant CSS in a separate .css file, which reduces complexity and repetition in the structural content;
and enable the .css file to be cached to improve the page load speed between the pages that share the file
and its formatting.

Dept of CS&E, MITE, Moodabidri 2

Chapter 2 REQUIREMENT ANALYSIS AND SPECIFICATION

2.1 Functional Requirements

These are statements of services the system should provide, how the system should react to particular
inputs and how the system should behave in particular situations. In some cases, the functional
requirements may also explicitly state what the system should not do. The functional requirements for a
system describe what the system should do. These requirements depend on the type of software being
developed, the expected users of the software and the general approach taken by the organization when
writing requirements. When expressed as user requirements, the requirements are usually described in an
abstract way. However, functional system requirements describe the system function in detail, its inputs
and outputs, exceptions, and so on. Functional requirements for a software system may be expressed in a
number of ways. The main users c of the system are three types:

1. Owner : The person who owns the pond and buys species from the breeders in the system.

2. Dealer : The person who deals with buying and viewing of species.

3. Breeder : The person who provides species information through the system.

2.1.1 Owner
The user can login to the system as the owner. They are also provided with the feature of buying the
species from the breeder’s. The users can check the species which are sold and the details of the dealers,
and are able to contact the dealers based on the provided details. Further owner can edit the cars details
at any time. The can buy species based on the provided specification.

2.1.2 Dealers
The dealer can login and buy the species available from the owner . Users can also just register
themselves as breeder and view the species that are available to buy from the owners page.

2.1.3 Breeder
Users can register themselves as the breeders and they can sell the species that are breeded to the owners.
Breeder breeds different species in the pond and can update the species available in the view.

Dept of CS&E, MITE, Moodabidri 3

2.2 Non-Functional Requirements

Non-functional requirements are requirements that are not directly concerned with the specific
functions delivered by the system. They may relate to emergent system properties suchas reliability,
response time and occupancy. Alternatively, they may define constraints on the system such as the
capabilities of I/O devices and the data representations used in system interfaces. The plan for
implementing functional requirements is detailed in the system design. The plan for implementing non-
functional requirements is detailed in the system architecture. Non-functional requirements are often
called qualities of a system. Other terms for non-functional requirements are "constraints", "quality
attributes", "quality goals", "quality of service requirements" and "non-behavioral requirements".
Qualities, that are non-functional requirements, can be divided into two main categories: Execution
qualities, such as security and usability, which are observable at run time.

Reliability

⚫ The system could produce required result in terms of the species sold.
⚫ It provides correct result with minimum expenditure if time and effort.

Consistency

⚫ The system can update the list of species sold without any error.
⚫ There’s no case of redundancy in the database, so it will be not take any extra memory space.

Performance

⚫ Better component design to get better performance at peak time.

⚫ The database used is robust, reliable and fast. So user will not have to wait long time for output.

Security

⚫ Secure access to confidential data by username and password provided by the user.
⚫ The password is encrypted and stored in the database such that users confidentiality is achieved.

Hardware requirements
⚫ Processor : Intel i3/i5,1.8GHz machine or above.

⚫ Main memory : 4GB RAM or more.

⚫ Hard disk drive : 1TB

⚫ Input Output Console for interaction.

Dept of CS&E, MITE, Moodabidri 4

Software requirements

⚫ Operating System : Windows 7 and higher.

⚫ Front end : HTML5 , CSS3 , JavaScript.

⚫ Back end : NODE JS , SQL.

⚫ Software : Visual Studio Code , XAMPP.

Dept of CS&E, MITE, Moodabidri 5

Chapter 3

SYSTEM DESIGN

System Design process partitions the system into subsystems based on the requirements. It establishes
overall system architecture and is concerned with identifying various components, specifying
relationships among components, specifying software structure, maintaining a record of design decisions
and providing a blue print for the implementation phase. Design consists of architecture design and
detailed design is concerned with the details of how to package processing modules and how to implement
the processing algorithms, data structures and interconnections among modules and data structures.

3.1 ER DIAGRAM
An entity-relationship diagram describes interrelated things of interest in a specific domain of knowledge.
A basic ER diagram is composed of entity types and specifies relationships that can exist between entities.

Figure 3.1 ER Diagram of Fisheries Management system

Entity-Relation diagram for Fisheries Management System has 5 entities namely, Owner, Dealers,
Breeder, Species and Pond. Owner and Breeder entities have 1: N Relationship ratio due to 1 owner can
buy species from N breeders. Owner and Pond entities have 1: N Relationship ratio due to 1 owner can
own N ponds . Owner and Dealers have N: N Relationship due to number of dealers can buy number of

Dept of CS&E, MITE, Moodabidri 6

species from the owner. Owner and Species has a 1: N Relationship since for each bought there one entry
in the table.

3.2 SCHEMA DIAGRAM

A schema diagram is a diagram which contains entities and the attributes that will define that schema.
A schema diagram only shows the database design. It does not show the actual data of the database.
Schema can be a single table or more than one table which is related.

Figure 3.2 Schema Diagram of Fisheries Management system

In the figure 3.2, Schematic representation of Fisheries Management System is given. It has 5 entities
namely, Owner, Dealers, Breeder, Species and Pond. Breeders and Dealers have Email as a primary key.
Species has Car_id as primary key and Seller_email as foreign key referencing Users. Species also has
S_id as combination of primary key and Dealer_email as foreign key referencing Dealers. Deal has
Buyer_email as it foreign key that references Users.

3.3 DESCRIPTION OF TABLES

The database consists of five tables
1. Owners: Stores the Owner details.

Dept of CS&E, MITE, Moodabidri 7

 o O_email :Email id of the database and primary
key.
o O_phone: phone of the owner.
o O_name: name of the owner.
o O_address: address of the owner.
2. Breeder: Stores details of breeder users registered.
o B_email : Email id of the user and primary key.

o B_phone: phone of the user.

o B_address: Breeder address.

o B_name:Breeder name

3. Dealers: Stores details of the dealers.

O D_Email : Email id of the dealer and primary

key.
o B_phone: phone of the user.

o B_address: Breeder address.

o B_name:Breeder name

4. Pond : Stores the pond details entered by users.

o P_id: Unique id given to each pond and

primary key
o P_type: type of pond.

o P_temp: specifies temperature of the pond

o P_species:gives information about the species in the pond

5. Species : Stores the species details.

o S_id : Unique id given to each specie and

primary key.
o S_food: The type of food given to species

o S_grade: The grade of the species

o S_size :The size of the specise
o S_name :Name of the species

Dept of CS&E, MITE, Moodabidri 8

Chapter 4 IMPLEMENTATION

Node JS: Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. It allows developers
to run JavaScript on the server side, creating server-side applications with JavaScript. Node.js is popular
for building web servers, real-time applications, and other network-dependent applications. It also
provides a rich library of modules for performing various tasks such as handling HTTP requests and
working with databases. Node.js is open-source and has a large and active community of developers
This project uses HTML as front-end tool. Hypertext Mark-up Language (HTML) is the standard markup
language for creating web pages and web applications. With Cascading Style Sheets (CSS) and
JavaScript, it forms a triad of cornerstone technologies for the world wide web. Web browser receive
HTML documents from a web server or from local storage and render the documents into multimedia
web pages.HTML describes the structure of a web page semantically and originally included cues for the
appearance of the document.HTML elements are the building blocks of HTML pages. With HTML
constructs, images and other objects such as interactive forms may be embedded into the rendered
page.HTML provides a means to create structured documents by structural semantics for text such as
headings, paragraphs, lists, links, quotes and other items.HTML elements are delineated by tags, written
using angle brackets. Browsers do not display the HTML tags, but use them to interrupt the content of
the page.

Dept of CS&E, MITE, Moodabidri 9

4.1 Code Snippet

//code snippet of connection module

const mysql = require("mysql");

const con = mysql.createConnection({

host:"localhost",

user:"root",

password:"",

database:"user_info"

});

module.exports = con;

Fig 4.1.1 code snippet for connection module

The above code snippet in Figure 4.1.1 is used for connecting purpose. This is used to connect back end
and front end. If the connection fails then a message occurs saying connection failed. This connection
establishment is required for storing the details entered by the users in the HTML form to the database
and also to retrieve the stored information from the database. Connection establishment is required for
all database access operations

Dept of CS&E, MITE, Moodabidri 10

 //code snippet for registration module

app.post('/signup',function(req,res){

var Name = req.body.name;

var email = req.body.email;

var password = req.body.password;

var role = req.body.role;

var sql = "INSERT INTO info_db(name,email,password,designation)

VALUES('"+Name+"','"+email+"','"+password+"','"+role+"')";

con.query(sql,function(error){

if(error) throw error;

res.redirect('../login');

})

});

Fig 4.1.2 Code snippet for Registration Module

The above code snippet in Figure 4.1.2 is used for Registration purpose. This is used to store the values
inserted by user into the Users table of database. If user already exists in table, it returns appropriate
message saying user exists.
//code snippet for login module

app.post("/login",function(req,res){

const Email =req.body.email;

var Password=req.body.password;

console.log(Email,Password)

Dept of CS&E, MITE, Moodabidri 11

 con.query("SELECT * FROM `info_db` WHERE `email` = ? AND `password` = ?"
,[Email,Password],function(error,results,fields){

console.log(results.length)

if(results.length > 0 ){

const token = jwt.sign({email: Email, password:Password},"AjayHacker",{ expiresIn : "1d"});

console.log(token)

const cookieOptions = {

expires : new Date(Date.now() + 1*24*60*60*1000),

httpOnly : false

res.cookie("Registered",token,cookieOptions);

res.redirect('../' + results[0].designation + "home" );}

else{ res.redirect('../login?status=1');

}});});

Fig 4.1.3 Code snippet of Login Module

The above code snippet in Figure 4.1.3 is used for Login purpose. This is used to check the mail and
password inserted by user with the Users table of database. If mail and password inserted by user is in
the table, it returns appropriate message saying incorrect values.

//code snippet of view module

app.get('/getdetailsa',(req,res)=>
{
const token = jwt.verify(req.cookies.Registered,'AjayHacker');

const Email = token.email;

console.log(Email)

Dept of CS&E, MITE, Moodabidri 12

 con.query("SELECT * FROM owner O,owner_add OA WHERE O.O_email=OA.O_email
AND O.O_email=?",[Email],(err,results)=>
{

if(err) console.log(err)

else

{
console.log(results[0])

res.send(results)

})

})

Figure 4.1.4 Code Snippet of view module

The above code snippet in Figure 4.1.4 is used for View purpose. This is used to provide a view of the
species that owners have posted for sale. If there are no species available , the same will be updated in
the view to the buyers.

//code snippet for delete module

app.get('/delete',(req,res)=>
{
const B_email = req.query.B_email

console.log(B_email)

con.query("DELETE FROM breeder WHERE B_email =?",[B_email],(err,results)=>{

if(err)
{
console.log(err)
res.status(404).send("Error Occured")
}
else{

Dept of CS&E, MITE, Moodabidri 13

 res.redirect('/breeder?message=Deleted_Succesfully')
}
})
})
Figure 4.1.5 Code Snippet of delete module

The above code snippet in Figure 4.1.5 is used for Deletion purpose. This is used by owner to delete the
species posted by them for sale. On successful deletion the same will be updated in the view table.

Dept of CS&E, MITE, Moodabidri 14

Chapter 5
TESTING
Software testing is the process of used to identify the correctness, security, completeness and quality of
developed computer software. This includes the process of executing the program or applications with
the intent of finding errors. An individual unit, functions or procedures of developed project is verified
and validated and these units are fit for use.

5.1 Testing process

Best testing process is to test each subsystem separately, as we have done in project. Best done during
implementation. Best done after small sub-steps of the implementation rather than large chunks. Once
each lowest level unit has been tested, units are combined with related units and retested in combination.
This proceeds hierarchically bottom-up until the entire system is tested as a whole. Typical levels of
testing:
⚫ Module- package, abstract data type, class
⚫ Sub-system- collection of related modules, cluster of classes, method-message paths
⚫ Acceptance testing- whole system with real data (involve customer, user, etc)

Alpha testing is acceptance testing with a single client (common for bespoke systems).
Beta testing involves distributing system to potential customers to use and provide feedback. In this
project, beta testing has been followed. This exposes system to situations and errors that might not be
anticipated by us.

5.1.1 Unit testing

Unit testing is the process of testing individual software components unit or modules. Since it needs the
detailed knowledge of the internal program design and code this task is done by the programmer and not
by testers.

5.1.2 Integration Testing

Integration testing is another aspect of testing that is generally done in order to uncover errors associated
with the flow of data across interfaces. The unit-tested modules are grouped together and tested in small
segment, which makes it easier to isolate and correct errors. This approach is continued until we have

Dept of CS&E, MITE, Moodabidri 15

integrated all modules to form the system as a whole. After the completion of each module, it has been
combined with the remaining module to ensure that the project is working properly as expected.

5.1.3 System Testing

System testing tests a completely integrated system to verify that it meets its requirements. After the
completion of the entire module, they are combined together to test whether the entire project is working
properly.

5.2 Test Cases

A Test Case is a software testing document, which consists of events, action, input, output, expected
result and actual result. Technically a test case includes test description, procedure, expected result and
remarks. Test cases should be based primarily on the software requirements and developed to verify
correct functionality and to establish conditions that reveal potential errors.

Test cases no Test Case Expected results Status

1 Logging into website Successful

Email and password
provided correct

2 Logging into website Email incorrect Unsuccessful

3 Logging into website Password Incorrect Unsuccessful

4 Logging into website Any field left empty Unsuccessful

Table 5.1 Test Case for Login

Table 5.1 represents the test case for login module. It shows both successful result in case the user enters
correct email and password and unsuccessful results for the test cases where the user enters incorrect
password , incorrect email or leaves any field empty.

Dept of CS&E, MITE, Moodabidri 16

 Test cases no Test Case Expected results Status

1 Successful

Registration for new All details provided

user correctly

2 Registration for new Unsuccessful

user
Confirm password field
and password field do
not match

3 Any field left empty Unsuccessful

Registration for new

user
Table 5.2 Test Case for Register

Figure 5.2 represents the test case for register module. It shows both successful and unsuccessful results
for the test cases.

Test cases no Test Case Expected results Status

1 Buying species Species available Successful

2 Required species are Unsuccessful

Buying species not available

3 Buying species Any field left empty Unsuccessful

Figure 5.3 represents the test case for buying species. It shows both successful and unsuccessful results
for the test cases.

Dept of CS&E, MITE, Moodabidri 17

Chapter 6
SNAPSHOTS

Figure 6.1 Screenshot of Home page

Figure 6.1 indicates the home page. This contains navigation bar, through which you can navigate to other
pages. It also contains some details about the website at the home page.

Figure 6.2 Screenshot of User register

Dept of CS&E, MITE, Moodabidri 18

Figure 6.2 indicates the user register page. This contains registration form, through which new user is
able to become a member of the platform.

Figure 6.3 Screenshot of Owner Page

Figure 6.3 indicates the owner information page. Here the owner can mention the species available with
him

Dept of CS&E, MITE, Moodabidri 19

 Figure 6.4 Screenshot of Dealer page

Figure 6.4 indicates the dealer page. This contains the dealer information and species id of species they
wish to buy

Fig 6.4 Screenshot of Breeder Page

Figure 6.4 indicates the Breeder page. It includes the breeder information along with the species they
breed.

Figure 6.5 Screenshot of Species page

Dept of CS&E, MITE, Moodabidri 20

Figure 6.5 indicates the species view page. User is able to view all the species and its information to buy
them.

Figure 6.7 Screenshot of Pond page

Figure 6.5 indicates the Pond page. User is able to view all the information regarding the pond.

Figure 6.6 Screenshot of Contact Us page

Figure 6.6 indicates the Contact Us page. It is a User support Page to deliver their queries

Dept of CS&E, MITE, Moodabidri 21

 Figure 6.8 Screenshot of Deals Page

Figure 6.8 indicates Deals Page.Here deals can be specified.

Figure 6.9 Screenshot of Buying Page

Figure 6.9 Indicates the screenshot of Buying Page.

Dept of CS&E, MITE, Moodabidri 22

 Figure 6.10 Screenshot of Update Page

Figure 6.10 Indicates the screenshot of Update page where the owner can add his species and ponds

Figure 6.11 Screenshot of Selling Details

Figure 6.11 indicates the Selling details.Here the owner will enter all the selling details of the species
that are available with him

Dept of CS&E, MITE, Moodabidri 23

Chapter 7

CONCLUSION

The project titled “PONDZILLA” is only a humble venture to fulfil the requirements of a people in
finding species to buy and also for finding buyers for their species. Several user-friendly coding has been
developed. This package shall prove to be a powerful package in satisfying all the requirements of the
user. The objective of making a blueprint is to provide a framework that enables the programmer to make
reasonable estimates made within a limited time frame at the beginning of the software project which is
updated regularly as the project progresses. This project can be developed into full-fledged software and
can be extended according to the specifications of the end user. Various attributes in each frame can be
added according to the needs of the client.

Dept of CS&E, MITE, Moodabidri 24

 REFERENCES

[1] Fundamentals of database system, Ramez elmarsri Shamkanth b 7th edition,2017, Pearson.
[2] www.w3schools.com/sql/
[3] https://nodejs.org/en/docs/guides/

Dept of CS&E, MITE, Moodabidri 25

Dept of CS&E, MITE, Moodabidri 26