MATSYA BAIBHAV

A PROJECT REPORT
Submitted to

JORHAT ENGINEERING COLLEGE

By

JASPREET SINGH
(200720014012)

In partial fulfillment for completion of Major Project

of

FOURTH SEMESTER
OF
MASTERS OF COMPUTER APPLICATION

UNDER THE GUIDANCE OF

Dr. Siddhartha Baruah,
Professor

Department of Computer Application,

Jorhat Engineering College, Jorhat, Assam

BATCH (2020 - 2022)

 JORHAT ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER APPLICATION
JORHAT, ASSAM

CERTIFICATE

This is to certify that the Project Report entitled “Matsya Baibhav” submitted by
Jaspreet Singh bearing Roll No- 200720014012, Registration No-344807220 to the
Jorhat Engineering College, Jorhat, Assam, in partial fulfillment of the requirement for
Major Project of 4th semester of Masters of Computer Application. It is a bona fide record
of the project work carried out by them under my supervision during the semester. I wish
him success in the future.

(Signature of the Head of the Department)

DR. RUPAM BARUAH,

Head of the Department/Principal,
Department of Computer Application,
Jorhat Engineering College

Date: ………………………
 JORHAT ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER APPLICATION
JORHAT, ASSAM

CERTIFICATE

This is to certify that the Project Report entitled “Matsya Baibhav” submitted by
Jaspreet Singh bearing Roll No- 200720014012, Registration No-344807220 to the
Jorhat Engineering College, Jorhat, Assam, in partial fulfillment of the requirement for
Major Project of 4th semester of Masters of Computer Application. It is a bona fide record
of the project work carried out by him under my supervision during the semester.

(Signature of the Internal Guide)

Internal Guide:
DR. SIDDHARTHA BARUAH,
Professor,
Department of Computer Application
Jorhat Engineering College

Date: ………………
 JORHAT ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER APPLICATION
JORHAT, ASSAM

CERTIFICATE

This is to certify that the Project Report entitled “Matsya Baibhav” submitted by
Jaspreet Singh bearing Roll No- 200720014012, Registration No-344807220 to the
Jorhat Engineering College, Jorhat, Assam, in partial fulfillment of the requirement for
Major Project of 4th semester of Masters of Computer Application. It is a bona fide record
of the project work carried out by him under my supervision during the semester.

(Signature of the Internal Co-Guide)

Internal Co-Guide:
ABINASH BORAH,
Assistant Professor
Department of Computer Application
Jorhat Engineering College

Date: …………………………
 JORHAT ENGINEERING COLLEGE
DEPARTMENT OF COMPUTER APPLICATION
JORHAT, ASSAM

EXAMINATION CERTIFICATE

This is to certify that the Project Report entitled “Matsya Baibhav” submitted by
Jaspreet Singh bearing Roll No- 200720014012, Registration No-344807220 to the
Jorhat Engineering College, Jorhat, Assam, in partial fulfillment of the requirement for
Major Project of 4th semester of Masters of Computer Application have carried out the
Project Work in a manner satisfactory to warrant its acceptance and also defended it
successfully.
I wish him all the success in his future endeavors.

Examiners:

(Signature of the External Examiner)

Date: …………………………
 DECLARATION

We hereby declare that the project work entitled “Matsya Baibhav” submitted to the
Jorhat Engineering College, Jorhat, Assam, in partial fulfilment of the requirement for
Major Project of 4th semester of Masters of Computer Application. It is a record of an
original work done by me under the guidance of Dr. Siddhartha Baruah (Professor,
Dept. of Computer Application, Jorhat Engineering College) and Abinash Borah
(Assistant Professor, Dept. of Computer Application, Jorhat Engineering College).

I also declare that no part of this project has been submitted in any form for the award
of any degree or diploma from any university/institute.

(Signature of the student)

JASPREET SINGH
(Roll No-200720014012)
Department of Computer Application
Jorhat Engineering College
 ACKNOWLEDGEMENT

The success and final outcome of this project required a lot of guidance and I am
extremely privileged to have got this all along the completion of my project.

I respect and thank Mrs. Hiranmayee Goswami (Scientist-F), Senior Technical

Director for providing me an opportunity to do the project work in National
Informatics Centre (NIC), Assam State Centre, Guwahati and giving all support and
guidance which made me complete the project duly. I am extremely thankful to her for
guiding me and providing such a nice guidance.

It is a genuine pleasure to express our deep sense of thanks and gratitude to my guide and
supervisor Dr. Siddhartha Baruah (Professor, Department. Of Computer Application,
Jorhat Engineering College) and Abinash Borah (Assistant Professor, Department Of
Computer Application, Jorhat Engineering College) who took keen interest on my project
work and guided me all along, till the completion of my project work by providing all the
suggestions for developing a good system.

I am thankful to and fortunate enough to get constant encouragement, support and

guidance from all Teaching staffs of Jorhat Engineering College which helped me in
successfully completing our project work.

Finally, it is a great pleasure to acknowledge my friends/team members for co-operating

with each other to finalizing this project and proceeding successfully.

THANKING YOU

JASPREET SINGH
(Roll No-200720014012)
Department of Computer Application
Jorhat Engineering College, Jorhat
 CONTENTS

Chapter 1: ABSTRACT …………………………………………………………..…… 1

Chapter 2: INTRODUCTION …………………………………………………..…….. 2

2.1 About the Project

2.2 Aims and Objective of the Project

Chapter 3: FEASIBILTY STUDY ………………………………………………….… 3

3.1 Technical Feasibility

3.2 Financial Feasibility
3.3 Operational Feasibility
3.4 Schedule Feasibility

Chapter 4: REQUIREMENT ANALYSIS AND REQUIREMENT GATHERING. 5

4.1 Hardware and software requirement

4.2 About the technologies
4.3 Requirement Gathering

Chapter 5: SYSTEM STUDY …………………………………………………….....… 9

5.1 Study of the Existing System

5.2 Drawback of the Existing System
5.3 Study of the proposed System
5.4 Advantages of the proposed System
5.5 Modules included in the proposed system

Chapter 6: SYSTEM DESIGN ………………………………………………….…….. 11

6.1 ER Diagram
6.2 Data Flow Diagram
6.3 Relational Schema

Chapter 7: SYSTEM IMPLEMENTATION …………………………………….……22

Chapter 8: TESTING ……………………………………………………………….…. 33

Chapter 8: CONCLUSION …………………………………………………….……… 35

References …………………………………………………………………………….… 36
 ABSTRACT

'Matsya Baibhav’ is a mobile application developed by the National Informatics Center

(NIC), the Assam State Center for the Department of Fisheries, Assam for geotagging
property created under GGPGGM. The project 'Ghare Ghare Pukhuri Ghare Ghare
Maach' (GGPGGM) aims to build 1000 hectares of ponds for individual farmers and 430
hectares of community tanks to cover all LACs across the province. The project was intended
and agreed upon using geo-tagging.

In addition, beneficiaries were given support for incorporating fish culture as fish seeds and
fish feed for 2 consecutive years under Chief Minister’s Samagra Grammya Unnayan Yojana
(CMSGUY). In addition, beneficiaries were provided with support and hands-on training and
training through the College of Fisheries, Raha and Krishi Vigyan Kendras under Assam
Agricultural University, Jorhat in phases.

1
 INTRODUCTION

This chapter outlines the overview about the project, its aims and objectives and operation
environment used for developing the system.

ABOUT THE PROJECT

Fishery is considered to be an important economic activity in Assam's socio-economic

environment. The sector has registered an average growth rate of 6% per annum in
respect of fish production. Total fish production in the Province has reached 3.93 Lakh
Ton in 2020-21 compared to 2.94 Lakh Ton in 2015-16. At the same time fish seed
production has also increased from 5678 million in 2015-16 to 9886 million by 2020-21.
Despite this encouraging situation, the growing demand for fish in Assam is yet to be met.
Large quantities of fish come from other countries to meet the economic need every year.
To reduce government spending in other parts of the country through the arrival of fish,
the Government considered a major project in 2017-18 for the Department of Fisheries to
increase local fish production and employment opportunities for rural youth, popularly
known as Ghare Ghare Pukhuri Ghare Ghare Maach (GGPGGM) under RIDF-XXIII with
a total project amount of Rs. 12 155 lakh. The sharing pattern contains Rs. 9509.50 lakh
as a loan allocation from NABARD, Rs. 500.50 lakh as Government allocation and Rs.
2145 lakh as beneficiaries share. The project was expected to add more than 5000 MT of
fish per year to the state fish basket.

The GGPGGM project has directed the construction of 1000 hectares of individual
farmers' ponds and 430 hectares of community tanks covering all LACs across the
province. It was intended and agreed upon to take details of the property created and its
beneficiaries under the project using geo-tagging. The Honorable Prime Minister, Assam,
at a meeting on 15-06-2021 also emphasized the geo-tagging of all lakes and tanks
created under the 'Ghare Ghare Pukhuri Ghare Ghare Ghare Maach' (GGPGGM) project
by the Department of Fisheries. , Assam.

AIMS AND OBJECTIVES OF THE PROJECT

the mobile app ‘Matsya Baibhav’ has been developed by the National Informatics Center
(NIC), Assam State Center for the Department of Fisheries, Assam to tag the assets
created under GGPGGM in the first phase for the following objectives:

 To enable a secure JWT Token based authentication system.

 To store the beneficiary and pond details and capture images with geotagging.
 To allow the district level users to accept/reject beneficiaries after due verification.
 To enable users to view geotagged locations on maps.
 To provide up to date status of GGPGGM scheme to the Fishery department.

2
 FEASIBILTY STUDY
Feasibility study could be a vital stage during system design. Feasibility study evaluates
the practicality of our project plan so as to judge whether or not we are able to move
forward with the project. It also decides whether the system is correctly developed or not.

The main aim of the feasibility study is to check whether the project is financially,
economically and technically feasible or not.

Types of feasibility study: -

1. Technical feasibility.
2. Financial Feasibility.
3. Operational Feasibility.
4. Schedule Feasibility

1. Technical Feasibility:

The feasibility of technology is reviewed by the technical resources available for our project.
It means that the processing system meets all current requirements or not. This study
determines whether we have the right tools, the right tools and the right technical knowledge
to complete our project goals.
This project is technically viable as it is independent because it can work on any mobile
devices.

2. Financial Feasibility:

Being financially viable means that if the system is efficient and should not be cheap in the
sense that the system should not be too expensive.
As this program is not affiliated with any third party company, it is therefore exempt from
costs.

3. Operational Feasibility:

This program is very easy to use, and will require a short time to understand the operation of
the program even for someone with very little knowledge of smart phones. Therefore, the
system is operational. Also, the user will have no problems accessing any area provided on
the mobile app. Also, since a smart phone is more accurate than a human, system reliability
will be improved.

The proposed plan is possible for the following reasons:

3
 • It is easy to keep all records in an orderly manner.
• Reduces user (administrator) workload.
• Easy to use due to friendly UI (User Interface).

4. Schedule Feasibility:

The feasibility of the schedule determines whether the proposed project can be completed
in a given time or not.
The project is completed within the stipulated time given by my external guide.

4
 REQUIREMENT ANALYSIS

During this phase, the requirement of the project is pointed out. We performed the
system software and hardware requirement for the project.

For Application:
 HARDWARE REQUIREMENT: -
o Processor : Quad core (1.2 Ghz)
o RAM : 416 MB (minimum)
o Secondary Storage : 832MB (minimum)
o Screen Resolution : 426 dp x 320 dp (minimum)
o Touch, Monitor, Keyboard and mouse

 SOFTWARE REQUIREMENT: -

o Operating System : Android 5.0 +

o Language : Dart, PHP

o Framework : Flutter

o Tools : 1. pgAdmin server

2. Android Studio or Visual

Studio Code.

3. Postman

4. XAMPP server

o Database : PostgreSQL, SQLite

o Browser : Chrome

5
ABOUT THE TECHNOLOGIES

FLUTTER:
• Flutter is a mobile UI (User Interface) framework which is free and open source.
• This framework is created by Google in 2017.
• It allows us to make native mobile application with just one codebase. It simply implies
that it makes two different app (for iOS and Android) just by using one programming
language and one codebase.
• To developer applications in flutter, we have to learn a programming language called
Dart.
• Flutter has two main parts: SDK (Software Development Kit) and framework (based on
Widgets).

DART:
• Dart is a programming language which is used for developing fast apps on any
platform.
• Google created it in 2011.
• It is a client optimized language.
• Dart is object oriented and open-source programming language.
• The main motive of this programming language is to create a frontend UI both for
mobile apps and web.

PHP:
• PHP is a programming language which is used for creating interactive and dynamic
websites. Its codes are executed by the server.

POSTGRESQL:
• PostgreSQL is a free, open-source relational database system that extends the SQL
language used to store the complicated data workloads.

SQLITE:
• SQLite is free, highly reliable and full-featured database engine. It is inbuilt all mobile
phones.

6
 REQUIREMENT GATHERING

Requirements analysis is an activity that records requirements in one or more formats, usually
software requirements specifications (SRS) documents. Software requirements specifications are the
starting point for software development activities.

The main goal of SRS (Software Requirements Specification) is to create a communication gap
between developers and customers. SRS is a medium for specifying customers and users.

The following 6-step process continued to collect the requirements:

 Step 1: Assign Roles

The first step in collecting requirements is to assign roles in your project. At
this point, you have identified the project stakeholders (external
guides, project managers, project management). Identifying these roles
helped us later determine who needed to analyze the scope of the project).

 Step 2: Meet with Stakeholders:

After identifying the stakeholders in the project, we met them

to understand what they are looking for in the project. Ultimately, it's the
stakeholders who we create the project for, so it's important to
understand what the stakeholders want.

 Step 3: Gather and Document

Step 3 in the process is done at the same time as step 2. The main goal of this
step is to ask stakeholders and document all the answers needed to start the
project.

 Step 4: List assumptions and Requirements

Based on the information collected, we have created a requirements
management plan that looks like this:

1. The length of the project timeline

2. People involved in the project
3. Project Risk

 Step 5: Get Approval

After formalizing the project requirements, approval from the project guide
was required to ensure that the requirements were met.

7
 Step 6: Monitor Progress
After completing a part of the project, we ask the
project guide for approval, and after approval, proceed to the next part and
finally meet all the requirements and complete the project within the
stipulated time.

8
 SYSTEM STUDY

STUDY OF THE EXISTING SYSTEM:

In the existing system, the Block Development Officers used to fill hand written forms
for beneficiaries which would then have to be verified by the District Level Officers.
There was no way to verify the details without being physically present in that location.
This method required huge amount of labour for District Level Officers as they would
need to physically be present at each and every beneficiary location within the district for
verification purposes.

DRAWBACKS OF EXISTING SYSTEM:

 Pen and paper is used to manage the existing system.
 It is time and labour intensive.
 The work efficiently is reduced to excessive travel time.
 Required huge efforts if a particular beneficiary detail is required to be viewed.

STUDY OF PROPOSED SYSTEM:

The purpose of the proposed system is to develop a system with improved equipment. The proposed
system overcomes all the limitations of existing systems. Existing systems have drawbacks and
many other difficulties in functioning well. The proposed system attempts to overcome these
difficulties to some extent by mitigating these difficulties.

In proposed system, all beneficiary details will get digitally stored in the web and hence
would greatly improve accessibility of the records. With the help of geo tagging, the need of
physical verification would be mitigated and hence reduce lots of human effort.

ADVANTAGES OF PROPOSED SYSTEM:

 User friendly.
 Easier to keep vast records at the same time.
 Minimum time required.
 Increases Efficiency.
 Fast and convenient.

9
MODULES IN THIS PROJECT:
This project “Matsya Baibhav” has three modules:

1. Admin.
2. District level.
3. Block level.

1. ADMIN MODULE:
 JWT Token based authentication login feature for Admin.
 Admin can manage all the districts and blocks in the database.
 He/she can add, update and view beneficiaries.
 He/she can also approve/reject beneficiaries.

2. DISTRICT LEVEL MODULE:

 JWT Token based authentication login feature for District level user.
 District level user can manage only a particular district and all blocks in that
district in the database.
 He/she can add, update and view beneficiaries.
 He/she can also approve/reject beneficiaries.

3. BLOCK LEVEL MODULE:

 JWT Token based authentication login feature for Block level user.
 Block level user can manage only a particular block(s) in the database.
 He/she can add, update and view beneficiaries.

10
 SYSTEM DESIGN

Entity-Relationship Diagram:
The Entity-Relationship Diagram, also known as Entity-Relationship-model, is a specialized graphic
that illustrates the interrelationships between entities in a database. ER diagrams often use symbols to
represent three different types of information:

 Boxes are commonly used to represent entities

 Diamonds are normally used to represent the relationships

 Ovals are used to represent attributes

 An entity is a piece of data– an object or concept about which data is stored

A relationship is how the data is shared between entities. There are three types of relationships
between the entities:

 One-to-One One instance of an entity (A) is associated with zero, one or more instances of
another entity (B).

 Many-to-Many One instance of an entity (A) is associated with zero, one or many instances
of another entity (B); and one instance of an entity (B) is associated with zero, one or many
instances of another entity (A).

Symbols used in ER:

11
ER DIAGRAM:

12
DATA FLOW DIAGRAM:

The formal analysis of the Data Flow diagram has the following characteristics:
 It always is pictorial. DFD represents the image of what is being said and in theory it
is easy to understand the presentation of the application.
 The whole process is divided so that we have a clear picture of the process from
normal to direct system flow
 Logical rather than physical. Defined in a clear, concise and concise manner in a
legible way so that one can express the effectiveness of the system well.

Symbols and notation used in DFD:

13
Level 0

14
 Level 1

For Admin

15
For District level user

16
For Block level user

17
 Level 2

For Admin

Admin manages Beneficiaries:

Admin manages Beneficiary History:

18
For District level user

District level user manages beneficiaries:

District level user manages beneficiaries_history:

19
For Block level user

Block level user manages beneficiaries:

Block level user manages beneficiaries_history:

20
RELATIONAL SCHEMA:

21
 SYSTEM IMPLEMENTATION

User Interface of the Portal:

Login Page:

Dashboard:

22
Beneficiary form:

Geo-tagging:

23
Pond Details:

Incomplete Entries:

24
Beneficiary Data:

25
Pending Beneficiaries:

Approved Beneficiaries:

26
Rejected Beneficiaries:

Map view:

27
Profile:

Change Password:

28
Database Table:

beneficiaries Table

villages Table

29
beneficiaries_history Table

blocks Table

categories Table

30
districts Table

gaon_panchayat Table

genders Table

lacs Table

police_stations Table

31
roles Table

user_blocks Table

users Table

versions Table

32
 TESTING TECHNIQUES AND STRATEGIES

Testing is an important step in the success of an application. Application testing involves

providing the app with a set of test inputs (test conditions) and checking if the system
behaves as expected. The purpose of the test is to identify and correct errors in the system
being developed. System testing ensures that every part of the system is operating properly
and the purpose is successfully executed.

There are two software testing strategies. They are:

1. Code Testing: Code testing is a testing strategy that tests the core thinking of a
program.

Project codes have been tested manually. Any errors found in the code have been
corrected.

2. Specification Testing: In order to perform specific tests, the analyst examines

specifications that describe what the system is trying to do and how it should work
under a variety of conditions.

The application was tested under various circumstances in several phones.

LEVEL OF TESTING:

The following are the different levels of testing:

1. Unit Testing:

Unit testing is testing performed by developers. Here the analyst examines the system
that builds the system. Unit testing is focused on verifying code integrity, fixing bugs
in the system ahead of the development cycle and helping the developer understand
the basics of the code.

2. System Testing:

System testing begins with testing system modules separately, followed by integrated
modules as a unit. System modules may work well on their own but fail when
connected to other modules. The test method is to evaluate each major business
successfully, up to system level testing.

The system test consists of the following tests:

 Program Testing: A program testing represents the
rationale for the system. For the system to work
efficiently, it must integrate test data efficiently and
effectively with other systems. System test check two
types of errors - syntax errors and logical errors

33
  String testing: Systems are constantly connected and
interact with the complete system.

 User acceptance testing: An acceptance test aims to

market the user to the efficiency and reliability of the
system.
3. Output Testing:

The process simultaneously checks both the system and its output. The output
generated by the system is compared to the output you want. Thus, each program is
evaluated separately with performance data. In fact, it turns out to be the same.

4. Recovery and system security test:

Without the backup copy protection service, the system is disabled. Even in some
cases it can cause many problems such as loss of data. Mandatory system failures
check the security of stored information.

5. Documentation Testing:

A sufficient number of components or messages are provided in each program to help

the user take the wrong position and easily use the system. User was asked about the
understanding of those messages; user feedback was considered to make the system
more user-friendly like them

SUMMARY OF TESTING:

The “MATSYA BAIBHAV” project is in the development phase and therefore the testing
methods and techniques are designed to be implemented within the proposed system so
that the user can get the most effective information using the system.

34
 CONCLUSION

The program defines a project-based perspective and describes the technology and method
used. Finally, it shows the result and the output you want. Using Flutter has made it easier for
system upgrades. This system will provide less error in keeping beneficiary records than the
error made in the normal pen and paper system.

Conventional pen and paper methods are highly inefficient and inconvenient. Therefore this
application will help the Fishery Department in removing the inefficiencies and provide and
solution that is error resistant. It will let the Director, Department of Fisheries to view any
details of any beneficiary at the click of a button.

The District level fishery officers will get an easy access the beneficiary details and they can
accurately verify the authenticity of the data using the provided maps option where the geo
tagged location is viewed on a map.

The Block level officers will no longer need to maintain huge paperwork related to the
beneficiaries as now it will fit in the palm of their hands in the form of smart phones.

Moreover, the system is very basic, effective and easy to use.

35
 WEB REFERENCES

Book References:

1. PostgreSQL 11 by Simon Riggs ,2019.

2. PHP: A Beginner's Guide – by Vikram Vaswani.
3. Relational Database Systems by Dan A. Simovici, Richard L. Tenney

Web References:
 https://pg-sql/com
 https://www.flutter.dev
 https://docs.flutter.dev
 https://getbootstrap.com
 https://dart.dev
 https://stackoverflow.com
 https://w3schools.com
 https://youtube.com
 https://fontawesome.com
 https://SQlite-query.com
 https://arstechnica.com/gadgets/2018/02/google-starts-a-push-for-cross-platform-app-
development-with-flutter-sdk/

36