AGRICULTURE MANAGEMENT SYSTEM

The Project Report is submitted in partial fulfillment of the

requirements for the award of the degree of
Master of Computer Applications

Submitted by:
MOGALIKUDURU SOWJANYA
2385351073

Under the Esteemed Guidance of

K.R.Rajeswari
B.V. Raju College
Vishnupur::Bhimavaram

Submitted to
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
COLLEGE OF ENGINEERING
ADIKAVI NANNAYA UNIVERSITY
RAJAHMAHENDRAVARAM
2024-2025
 B.V. RAJUCOLLEGE (AUTONOMOUS)
(Re-Accredited with ‘B++’ Grade by NAAC)

Department of MCA
Vishnupur :: Bhimavaram

CERTIFICATE
This is to certify that this project entitled “AGRICULTURE MANAGEMENT
SYSTEM” submitted in partial fulfillment of the degree of MASTER OF
COMPUTER APPLICATIONS to Adikavi Nannaya University from 7itech
solutions through B.V. Raju College, done by Ms. MOGALIKUDURU SOWJANYA
Regd. No. 2385351073 is an authentic work carried out by her during the Academic
Year 2024-2025 at under my guidance. The matter embodied in this project work has not
been submitted earlier for award of any degree or diploma to the best of my knowledge
and belief.

Internal Guide Head of the Department

External Examiner Principal

 ACKNOWLEDGEMENTS
The satisfaction and euphoria that accompany the successful completion of any task
would be incomplete without the mention of people who made it possible, whose constant
guidance and encouragement crowned our efforts with success. It is a pleasant aspect that I have
now the opportunity to express my gratitude for all of them.

The first person I would like to thank Dr. I.R.krishnam Raju, Principal MCA,

B V Raju College, Bhimavaram. His wide knowledge and logical way of thinking have
made a deep impression on me. His understanding, encouragement and personal guidance have
provided the basis for this thesis. He is a source of inspiration for innovative ideas and his kind
support is well known to all his students and colleagues.

I wish to thank Dr. V. BHASKARA MURTHY, Professor& HOD, Dept of MCA.

His support and valuable suggestions for the successful completion of this project.

I wish to thank my guide Ms.K.R.Rajeswari, Assistant Professor, Dept. of MCA his

support and valuable suggestions for the successful completion of this Project.

MOGALIKUDURU SOWJANYA

2385351073
 DECLARATION

This is to certify that the project report entitled “AGRICULTURE MANAGEMENT

SYSTEM” is done by me is an authentic work carried out for the partial fulfillment of
the requirements for the award of the degree of Master of Computer Applications
under the guidance of Ms.K.R.Rajeswari, Assistant Professor, Dept. of MCA. The
matter embodied in this project work has not been submitted earlier for award of any
degree or diploma to the best of my knowledge and belief.

Signature of the student

MOGALIKUDUR SOWJANYA

2385351073

B.V.Raju College.
1. INTRODUCTION 1

1.1. INTRODUCTION TO PROJECT

1.2. PURPOSE OF THE PROJECT
1.3 EXISTING SYSTEM & ITS DISADVANTAGES
1.4 PROPOSED SYSTEM & ITS ADVANTAGES

2. SYSTEM ANALYSIS 2-6

2.1. STUDY OF THE SYSTEM

2.2. INPUT & OUTPUT REPRESENTATION
2.3. PROCESS MODELS USED WITH JUSTIFICATION
2.4. SYSTEM ARCHITECTURE

3. FEASIBILITY STUDY 7-9

3.1. TECHNICAL FEASIBILITY

3.2. OPERATIONAL FEASIBILITY
3.3. ECONOMIC FEASIBILITY

4. REQUIREMENT SPECIFICATIONS 10-16

4.1. FUNCIONAL REQUIREMENTS

4.2. PERFORMANCE REQUIREMENTS
4.3. SOFTWARE REQUIREMENTS
4.4. HARDWARE REQUIREMENTS
 5. SYSTEM DESIGN 17-24

5.1. INTRODUCTION
5.2 UML DIAGRAMS
5.3 NORMALIZATION
5.4 DATA DICTIONARY

6. SCREENS
25-31

7. SYSTEM
TESTING 32-36

7.1 INTRODUCTION TO TESTING

7.2 TESTING STRATEGIES

8SYSTEM SECURITY 37-38

8.1 INTRODUCTION

8.2 SECURITY IN SOFTWARE

9. CONCLUSION 38-40

10. BIBLIOGRAPHY 41-42

1. INTRODUCTION
 1. INTRODUCTION

The processes for access and use of information and technology by individuals and organizations as
a whole constitute the Information Technologies and define the main foundations of what is
currently named the Information Society. Castells points out that we are in a society whose
economy is dominated by a technological paradigm in which information is its raw material.
That is, the information is critical to the day-to-day organization of all the different tasks that
constitute their work processes. It is expected that a relationship exists between the effective
management of organizations and how they treat and manage information . Gonçalves states that
people, information and knowledge are key assets that differentiate organizations, and success is
increasingly the result of the ability of its management. Find the best ways to do this
management requires a proactive and persistent attitude in the pursuit of improving posture,
which includes having openness to innovate

Information technologies has been of utmost importance in Geospatial management. In the last
years we've seen the growth of a special relevance to the agricultural Information systems

This importance is reflected in the implementation of systems for the processing and handling of
agricultural land and products and the use of information systems to influence agricultural
productivity. It can help to take better decisions regarding land, labor, livestock, capital and
management. Agricultural productivity can undoubtedly be improved by relevant, reliable and
useful data, information and knowledge. Hence, the creation of agricultural information (by
extension services, research, education plans and others) is now often managed by agricultural
organizations that create information systems to disseminate information to farmers so that
farmers can make better decisions in order to take advantage of market opportunities and manage
continuous changes in their production systems

In this article, in a more limited aspect, we describe the implementation of an innovative system
architecture for the management of agricultural properties which allows a more agile and
efficient land and crop management, aiming towards an enhanced productivity and
competitiveness

The Agrifootprint system allows us to build a strong, feature-rich management system for every
available and applicable property and its cultures. The user uploads the geographic
representation of a unity’s parcels and then assigns a culture for that parcel. The system keeps
track of the expenditure and resources consumption, as well as the resulting products of the given
parcel, for the given period of time. Reports can be generated in several formats, making it easier
to control and manage production costs. Graphical representations of data from the cultures are
also added to the reports so the user gets a more immediate view of the plantation’s information.

1
2. SYSTEM ANALYSIS

2
 2. SYSTEM ANALYSIS

INPUT DESIGN

Input design is part of overall system design that requires special attention designing input data
is to make the data entered easy and free from errors. The input forms are designed using the
controls available in .NET framework. Validation is made for each and every data that is entered.
Help information is provided for the users during when the customer feels difficult.

Input design is the process of converting the user originated inputs to a computer based format. A
system user interacting through a workstation must be able to tell the system whether to accept
the input to produce reports. The collection of input data is considered to be most expensive part
of the system design. Since the input has to be planned in such a manner so as to get relevant
information, extreme care is taken to obtain pertinent information.

This project first will entered to the input of allocation forms it will be created on student details
form and subject entry form, time table form .it will helps to calculate subject wise attendance
system. Next one if u wants any verification on your data’s also available in details show forms.
Attendance to entered single subject wise or all subject wise attendance system available in this
project

3
 OUTPUT DESIGN

Output design this application “Student Attendance management system”generally refers to

the results and information that are generated by the system for many end-users; output is the
main reason for developing the system and the basis on which they evaluate the usefulness of the
application.

The output is designed in such a way that it is attractive, convenient and informative. Forms
are designed with various features, which make the console output more pleasing.

As the outputs are the most important sources of information to the users, better design
should improve the system’s relationships with us and also will help in decisionmaking. Form
design elaborates the way output is presented and the layout available for capturing information.

One of the most important factors of the system is the output it produces. This system
refers to the results and information generated. Basically the output from a computer system is
used to communicate the result of processing to the user.

Attendance management system to show the report subject wise attendance maintaining by
staffs. Taken as a whole report obtain on a administrator privileges only. this forms will show
weekly report and consolidate report generated date, batch, and class wise to our end user. we
want to change our report to convert Excel format .if you want change any modification.

4
 2.3 PROCESS MODEL USED WITH JUSTIFICATION

SDLC (Umbrella Model):

DOCUMENT Umbrella
CONTROL

Umbrella
Business
Requirement
Documentation

Requiremen
• Feasibility Study
• TEAM
ts
FORMATION ANALYSIS & CODE UNIT TEST
Gathering
• Project
Specificatio
n

INTEGRATIO
N& ACCEPTAN
SYSTEM DELIVERY/ CE TEST
TESTING INS

Umbrella
TRAINING

SDLC is nothing but Software Development Life Cycle. It is a standard which is used by
5
software industry to develop good software.

6
Stages in SDLC:

 Requirement Gathering
 Analysis
 Designing
 Coding
 Testing
 Maintenance

2.4 SYSTEM ARCHITECTURE

Architecture flow:
Below architecture diagram represents mainly flow of requests from users to database through
servers. In this scenario overall system is designed in three tires separately using three layers
called presentation layer, business logic layer and data link layer. This project was developed
using 3-tire architecture.

User

SERVER
Request Response

Data
Base

7
3. FEASIBILITY STUDY

8
 3. FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put
forth with a very general plan for the project and some cost estimates. During system analysis the
feasibility study of the proposed system is to be carried out. This is to ensure that the proposed
system is not a burden to the company. For feasibility analysis, some understanding of the major
requirements for the system is essential.

Three key considerations involved in the feasibility analysis are

 ECONOMICAL FEASIBILITY
 TECHNICAL FEASIBILITY
 SOCIAL FEASIBILITY

ECONOMICAL FEASIBILITY

This study is carried out to check the economic impact that the system will have on the
organization. The amount of fund that the company can pour into the research and development
of the system is limited. The expenditures must be justified. Thus the developed system as well
within the budget and this was achieved because most of the technologies used are freely
available. Only the customized products had to be purchased.

TECHNICAL FEASIBILITY

9
 This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the available
technical resources. This will lead to high demands on the available technical resources. This
will lead to high demands being placed on the client. The developed system must have a modest
requirement, as only minimal or null changes are required for implementing this system.

SOCIAL FEASIBILITY

The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the user about the system and
to make him familiar with it. His level of confidence must be raised so that he is also able to
make some constructive criticism, which is welcomed, as he is the final user of the system.

10
4. SYSTEM REQUIREMENTS

11
 4. SYSTEM REQUIREMENTS
HARDWARE REQUIREMENTS:

 System : Pentium Dual Core.

 Hard Disk : 120 GB.
 Monitor : 15’’ LED
 Ram : 1 GB

SOFTWARE REQUIREMENTS:

 Operating system : Windows 7/10.

 Coding Language : JAVA/J2EE
 Tool : Net Beans.
 Database : MYSQL

The proposed system buyers or sellers can directly register in the site and sell the product otherwise
they can contact with a seller directly. Buyers can open the site and register with it and sell their
products online.

The products will be selled online with full information, instructions and descriptions so that the
users can use the products with a good manner.

SOFTWARE ENVIRONMENT

Java Technology
Java technology is both a programming language and a platform.

12
The Java Programming Language
The Java programming language is a high-level language that can be characterized by all
of the following buzzwords:

 Simple
 Architecture neutral
 Object oriented
 Portable
 Distributed
 High performance
 Interpreted
 Multithreaded
 Robust
 Dynamic
 Secure

With most programming languages, you either compile or interpret a program so that you can run it on
your computer. The Java programming language is unusual in that a program is both compiled and
interpreted. With the compiler, first you translate a program into an

intermediate language called Java byte codes —the platform-independent codes interpreted by
the interpreter on the Java platform. The interpreter parses and runs each Java byte code
instruction on the computer. Compilation happens just once; interpretation occurs each time the
program is executed. The following figure illustrates how this works.

You can think of Java byte codes as the machine code instructions for the Java Virtual
Machine (Java VM). Every Java interpreter, whether it’s a development tool or a Web browser

13
that can run applets, is an implementation of the Java VM. Java byte codes help make “write
once, run anywhere” possible. You can compile your program into byte codes on any platform
that has a Java compiler. The byte codes can then be run on any implementation of the Java VM.
That means that as long as a computer has a Java VM, the same program written in the Java
programming language can run on Windows 2000, a Solaris workstation, or on an iMac.

The Java Platform

A platform is the hardware or software environment in which a program runs.
We’ve already mentioned some of the most popular platforms like Windows 2000,
Linux, Solaris, and MacOS. Most platforms can be described as a combination of the
operating system and hardware. The Java platform differs from most other platforms in
that it’s a software-only platform that runs on top of other hardware-based platforms.

The Java platform has two components:

 The Java Virtual Machine (Java VM)
 The Java Application Programming Interface (Java API)
You’ve already been introduced to the Java VM. It’s the base for the Java platform
and is ported onto various hardware-based platforms.

The Java API is a large collection of ready-made software components that provide
many useful capabilities, such as graphical user interface (GUI) widgets. The Java API is
grouped into libraries of related classes and interfaces; these libraries are known as

14
 packages. The next section, What Can Java Technology Do? Highlights what
functionality some of the packages in the Java API provide.
The following figure depicts a program that’s running on the Java platform. As the
figure shows, the Java API and the virtual machine insulate the program from the
hardware.

Native code is code that after you compile it, the compiled code runs on a specific
hardware platform. As a platform-independent environment, the Java platform can be a
bit slower than native code. However, smart compilers, well-tuned interpreters, and just-
in-time byte code compilers can bring performance close to that of native code without
threatening portability.
To gain a wider acceptance of JDBC, Sun based JDBC’s framework on ODBC. As you
discovered earlier in this chapter, ODBC has widespread support on a variety of platforms.
Basing JDBC on ODBC will allow vendors to bring JDBC drivers to market much faster than
developing a completely new connectivity solution.
JDBC was announced in March of 1996. It was released for a 90 day public review that
ended June 8, 1996. Because of user input, the final JDBC v1.0 specification was released soon
after.
The remainder of this section will cover enough information about JDBC for you to know what
it is about and how to use it effectively. This is by no means a complete overview of JDBC. That
would fill an entire book.

JDBC Goals
Few software packages are designed without goals in mind. JDBC is one that, because of
its many goals, drove the development of the API. These goals, in conjunction with early
reviewer feedback, have finalized the JDBC class library into a solid framework for building
database applications in Java.

15
 The goals that were set for JDBC are important. They will give you some insight as to why
certain classes and functionalities behave the way they do. The eight design goals for JDBC are
as follows:

1. SQL Level API

The designers felt that their main goal was to define a SQL interface for Java. Although
not the lowest database interface level possible, it is at a low enough level for higher-level
tools and APIs to be created. Conversely, it is at a high enough level for application
programmers to use it confidently. Attaining this goal allows for future tool vendors to
“generate” JDBC code and to hide many of JDBC’s complexities from the end user.

2. SQL Conformance
SQL syntax varies as you move from database vendor to database vendor. In an effort to
support a wide variety of vendors, JDBC will allow any query statement to be passed through
it to the underlying database driver. This allows the connectivity module to handle non-
standard functionality in a manner that is suitable for its users.

3. JDBC must be implemental on top of common database interfaces

The JDBC SQL API must “sit” on top of other common SQL level APIs. This goal
allows JDBC to use existing ODBC level drivers by the use of a software interface. This
interface would translate JDBC calls to ODBC and vice versa.
4. Provide a Java interface that is consistent with the rest of the Java system
Because of Java’s acceptance in the user community thus far, the designers feel that they
should not stray from the current design of the core Java system.

5. Keep it simple
This goal probably appears in all software design goal listings. JDBC is no exception.
Sun felt that the design of JDBC should be very simple, allowing for only one method of
completing a task per mechanism. Allowing duplicate functionality only serves to confuse
the users of the API.

6. Use strong, static typing wherever possible

16
 Strong typing allows for more error checking to be done at compile time; also, less error
appear at runtime.

7. Keep the common cases simple

Because more often than not, the usual SQL calls used by the programmer are simple
SELECT’s, INSERT’s, DELETE’s and UPDATE’s, these queries should be simple to
perform with JDBC. However, more complex SQL statements should also be possible.

Java Program Interpreter

Compilers My Program

17
5. SYSTEM DESIGN

18
 5. SYSTEM DESIGN

5.1. INTRODUCTION

Systems design

Introduction: Systems design is the process or art of defining the architecture, components,
modules, interfaces, and data for a system to satisfy specified requirements. One could see it as
the application of systems theory to product development. There is some overlap and synergy
with the disciplines of systems analysis, systems architecture and systems engineering.

5.2.UML DIAGRAMS

UML stands for Unified Modelling Language. UML is a standardized general-purpose modelling
language in the field of object-oriented software engineering. The standard is managed, and was
created by, the Object Management Group.

The goal is for UML to become a common language for creating models of object-oriented
computer software. In its current form UML is comprised of two major components: a Meta-
model and a notation. In the future, some form of method or process may also be added to; or
associated with, UML.
The Unified Modelling Language is a standard language for specifying, Visualization, Constructing
and documenting the facts of software system, as well as for business modelling and other non-
software systems.
GOALS:
The Primary goals in the design of the UML are as follows:
 Provide users a ready-to-use, expressive visual modelling Language so that they can
develop and exchange meaningful models.
 Provide extendibility and specialization mechanisms to extend the core concepts.
 Be independent of particular programming languages and development process.

19
  Provide a formal basis for understanding the modelling language.
 Encourage the growth of OO tools market.

5.3. NORMALIZATION

A Database is a collection of interrelated data stored with a minimum of redundancy to serve

many applications. The database design is used to group data into a number of tables and
minimizes the artificiality embedded in using separate files. The tables are organized to:

Reduced duplication of data.

Simplify functions like adding, deleting, modifying data etc.,

Retrieving data

Clarity and ease of use

More information at low cost

5.4 DATA DICTIONARY

Source code

* java.lang

* java.io

* java.util

* javax.microedition.io

* javax.microedition.lcdui

* javax.microedition.midlet

20
* javax.microedition.rms

Sample Code

Dbconnection.java

package dbcon;

import java.sql.Connection;

import java.sql.DriverManager;

/**

* @author java2

*/

public class Dbconnection {

public static Connection getConnection()

{ Connection con = null;

try {

Class.forName("com.mysql.jdbc.Driver");

con = DriverManager.getConnection("jdbc:mysql://localhost:3306/agriculture",
"root", "");

} catch (Exception ex) {

ex.printStackTrace();

21
 return con;

AddProduct.java

package com.register;

import java.io.IOException;

import java.io.InputStream;

import java.sql.Connection;

import java.sql.DriverManager;

import java.sql.PreparedStatement;

import java.sql.SQLException;

import java.util.logging.Level;

import java.util.logging.Logger;

import javax.servlet.ServletException;

import javax.servlet.annotation.MultipartConfig;

import javax.servlet.annotation.WebServlet;

import javax.servlet.http.HttpServlet;

import javax.servlet.http.HttpServletRequest;

import javax.servlet.http.HttpServletResponse;

import javax.servlet.http.HttpSession;

import javax.servlet.http.Part;

import java.sql.*;

@WebServlet("/AddProduct")

22
@MultipartConfig(maxFileSize = 16177215)

public class AddProduct extends HttpServlet {

private String dbURL = "jdbc:mysql://localhost:3306/agriculture";

private String dbUser = "root";

private String dbPass = "";

protected void doPost(HttpServletRequest request,

HttpServletResponse response) throws ServletException, IOException

{ String pid = request.getParameter("iid");

String username = request.getParameter("username");

String pname = request.getParameter("pname");

String pdec = request.getParameter("pdec");

String pcost = request.getParameter("pcost");

InputStream inputStream = null;

Part filePart = request.getPart("image");

if (filePart != null) {

System.out.println(filePart.getName());

System.out.println(filePart.getSize());

System.out.println(filePart.getContentType());

inputStream = filePart.getInputStream();

23
 Connection conn = null;

String message = null;

try {

Class.forName("com.mysql.jdbc.Driver");

conn = DriverManager.getConnection(dbURL, dbUser, dbPass);

String sql = "INSERT INTO Addproducts (pid, username, pname,pdec,

pcost,image) values (?,?, ?, ?, ?,?)";

PreparedStatement statement = conn.prepareStatement(sql);

statement.setString(1, pid);

statement.setString(2, username);

statement.setString(3, pname);

statement.setString(4, pdec);

statement.setString(5, pcost);

if (inputStream != null) {

statement.setBlob(6, inputStream);

int row = statement.executeUpdate();

if (row > 0) {

System.out.println("image upload sucess");

response.sendRedirect("Addproducts.jsp?reg=Product Added

Successfully");

24
 } else {

response.sendRedirect("Addproducts.jsp?reg= Prduct Adding Failed");

} catch (SQLException ex) {

ex.printStackTrace();

} catch (ClassNotFoundException ex)

{ Logger.getLogger(AddProduct.class.getName()).log(Level.SEVERE, null, ex); }

25
 6. SCREENS

26
6. SCREENSHOTS

Home Page

27
Admin Login

Admin Home

28
Registration Screen

Post Idea

View Idea

29
 Add product

Add product Details

30
 User Login

User Home

View Ideas

31
View Products

Place Order

32
7. SYSTEM TESTING

33
 7. SYSTEM TESTING

The purpose of testing is to discover errors. Testing is the process of trying

to discover every conceivable fault or weakness in a work product. It provides a
way to check the functionality of components, sub assemblies, assemblies and/or a
finished product It is the process of exercising software with the intent of ensuring
that the

Software system meets its requirements and user expectations and does not fail in
an unacceptable manner. There are various types of test. Each test type addresses a
specific testing requirement.

TYPES OF TESTS

Unit testing
Unit testing involves the design of test cases that validate that the internal
program logic is functioning properly, and that program inputs produce valid
outputs. All decision branches and internal code flow should be validated. It is the
testing of individual software units of the application .it is done after the
completion of an individual unit before integration. This is a structural testing, that
relies on knowledge of its construction and is invasive. Unit tests perform basic
tests at component level and test a specific business process, application, and/or
system configuration. Unit tests ensure that each unique path of a business process
performs accurately to the documented specifications and contains clearly defined
inputs and expected results.

34
Integration testing

Integration tests are designed to test integrated software components to

determine if they actually run as one program. Testing is event driven and is more
concerned with the basic outcome of screens or fields. Integration tests
demonstrate that although the components were individually satisfaction, as shown
by successfully unit testing, the combination of components is correct and
consistent. Integration testing is specifically aimed at exposing the problems that
arise from the combination of components.

Functional test

Functional tests provide systematic demonstrations that functions tested are

available as specified by the business and technical requirements, system
documentation, and user manuals.

Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to
identify Business process flows; data fields, predefined processes, and successive
processes must be considered for testing. Before functional testing is complete,
additional tests are identified and the effective value of current tests is determined.

35
System Test
System testing ensures that the entire integrated software system meets
requirements. It tests a configuration to ensure known and predictable results. An
example of system testing is the configuration oriented system integration test.
System testing is based on process descriptions and flows, emphasizing pre-driven
process links and integration points.

White Box Testing

White Box Testing is a testing in which in which the software tester has
knowledge of the inner workings, structure and language of the software, or at
least its purpose. It is purpose. It is used to test areas that cannot be reached from a
black box level.

Black Box Testing

Black Box Testing is testing the software without any knowledge of the inner
workings, structure or language of the module being tested. Black box tests, as
most other kinds of tests, must be written from a definitive source document, such
as specification or requirements document, such as specification or requirements
document. It is a testing in which the software under test is treated, as a black box
.you cannot “see” into it. The test provides inputs and responds to outputs without
considering how the software works.

6.1 Unit Testing:

36
 Unit testing is usually conducted as part of a combined code and unit test
phase of the software lifecycle, although it is not uncommon for coding and unit
testing to be conducted as two distinct phases.

6.2 Integration Testing

Software integration testing is the incremental integration testing of two or

more integrated software components on a single platform to produce failures
caused by interface defects.

The task of the integration test is to check that components or software

applications, e.g. components in a software system or – one step up – software
applications at the company level – interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

6.3 Acceptance Testing

User Acceptance Testing is a critical phase of any project and requires

significant participation by the end user. It also ensures that the system meets the
functional requirements.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

37
8. SYSTEM SECURITY

38
 8. SYSTEM SECURITY

8.1 INTRODUCTION

System Security:

Setting Up Authentication for Web Applications:

Introduction:
To configure authentication for a Web Application, use the <login-config> element of the web.xml
deployment descriptor. In this element you define the security realm containing the user
credentials, the method of authentication, and the location of resources for authentication.

8.2 SECURITY IN SOFTWARE

To set up authentication for Web Applications:

1. Open the web.xml deployment descriptor in a text editor or use the Administration
Console. Specify the authentication method using the <auth-method> element. The
available options are:

BASIC

Basic authentication uses the Web Browser to display a username/password dialog box. This
username and password is authenticated against the realm.

FORM

Form-based authentication requires that you return an HTML form containing the username
and password. The fields returned from the form elements must be username and
password, and the action attribute must be security check.

39
9. CONCLUSION

40
 9. CONCLUSION
The Agrifootprint system with its integrated, centralized and web-accessible database of spatial and
related alphanumerical data, allowed non-GIS-users to Perform CRUD (Create, Read, Update
and Delete) operations of both spatial and alphanumerical data, by using near real-time data, and
also allowed spatial and alphanumerical analysis through the use of maps, charts, tables and KPI
(Key Performance Indicators) Dashboard, and produce preformatted reports. Information system
like the one that was developed, are built in accordance to customer requirements from the very
beginning and include our last research results in the field, which results in far fewer
complications that arise in comparison to the commonly seen ones in ready- made software [19].
Custom business applications are equipped with features that only the client requires which
makes it incredibly easy to use, requiring little training to learn how to use the software, being
easy and inexpensive to maintain. The development of a custom-made application and its
interface required a stringent examination, in order to verify the correct comprehension, analysis
and exact implementation of thoughts of the client into the definite product. Some future work,
could include the development and implementation of a mobile application designed towards
geospatial data collection to update the Agrifootprint database, with a complete and customized
interface

41
10. BIBLIOGRAPHY

42
 10. BIBLIOGRAPHY

Re fer ences fo r t he Pro ject Deve lo pme nt Wer e T aken Fr o m t he fo l lo w ing

Boo ks and Web Sit es.

JAVA Technologies

JAVA Complete Reference

Java Script Programming by Yehuda Shiran

Mastering JAVA Security

JAVA2 Networking by

Pistoria JAVA Security by

Scotl oaks Head First EJB

Sierra Bates

J2EE Professional by Shadab siddiqui

JAVA server pages by Larne

Pekowsley JAVA Server pages by Nick

Todd

HTML

HTML Black Book by Holzner

JDBC

Java Database Programming with JDBC by Patel moss.

Software Engineering by Roger Pressman

43