8

CHAPTER 1
OVERVIEW
1.1 INTRODUCTION
Modern agricultural systems have been developed with two related goals in mind: to obtain the
highest yields possible and to get the highest economic profit possible. In pursuit of these goals,
six basic practices have come to form the backbone of production: intensive
tillage, monoculture , application of inorganic fertilizer, irrigation, chemical pest control, and
genetic manipulation of crop plants. Each practice is used for its individual contribution to
productivity, but when they are all combined in a farming system each depends on the others and
reinforces the need for using the others. The work of agronomists, specialists in agricultural
production, has been key to the development of these practices.Depression.The fruitless chasing
of subsidies, and ultimately the elimination of subsidies. Bad answer for a Creed question
thought. For the FFA Creed contest the answer: Agriculture holds the promise of innovation The
future is exciting. As we begin to integrate more and more technology in agriculture the
possibilities are endless. What I do know of agriculture is that it will continue on through out the
future, providing for those who need us most.

MODULE DESCRIPTION:

1. User

2. Officer

3. Admin.

4. Use of Machines on Farms

5. Modern Transportation.

6. Irrigation of plants
 9

1.2 INPUT DESIGN

The input design is the link between the information system and the user. It comprises the
developing specification and procedures for data preparation and those steps are necessary to put
transaction data in to a usable form for processing can be achieved by inspecting the computer to
read data from a written or printed document or it can occur by having people keying the data
directly into the system. The design of input focuses on controlling the amount of input required,
controlling the errors, avoiding delay, avoiding extra steps and keeping the process simple. The
input is designed in such a way so that it provides security and ease of use with retaining the
privacy. Input Design considered the following things:

 What data should be given as input?

 How the data should be arranged or coded?
 The dialog to guide the operating personnel in providing input.
 Methods for preparing input validations and steps to follow when error occur.

1.2.1 OBJECTIVES

1. Input Design is the process of converting a user-oriented description of the input into a
computer-based system. This design is important to avoid errors in the data input process and
show the correct direction to the management for getting correct information from the
computerized system.

2. It is achieved by creating user-friendly screens for the data entry to handle large volume of
data. The goal of designing input is to make data entry easier and to be free from errors. The data
entry screen is designed in such a way that all the data manipulates can be performed. It also
provides record viewing facilities.

3. When the data is entered it will check for its validity. Data can be entered with the help of
screens. Appropriate messages are provided as when needed so that the user will not be in maize
of instant. Thus the objective of input design is to create an input layout that is easy to follow.
 10

1.3 OUTPUT DESIGN

A quality output is one, which meets the requirements of the end user and presents the
information clearly. In any system results of processing are communicated to the users and to
other system through outputs. In output design it is determined how the information is to be
displaced for immediate need and also the hard copy output. It is the most important and direct
source information to the user. Efficient and intelligent output design improves the system’s
relationship to help user decision-making.

1.Designing computer output should proceed in an organized, well thought out manner; the right
output must be developed while ensuring that each output element is designed so that people will
find the system can use easily and effectively. When analysis design computer output, they
should Identify the specific output that is needed to meet the requirements.

2.Select methods for presenting information.

3.Create document, report, or other formats that contain information produced by the system.

The output form of an information system should accomplish one or more of the following
objectives.

 Convey information about past activities, current status or projections of the

 Future.
 Signal important events, opportunities, problems, or warnings.
 Trigger an action.
 Confirm an action.

.
 11

CHAPTER 2

LITERATURE SURVEY

Literature survey is the most important step in software development process. Before developing
the tool it is necessary to determine the time factor, economy and company strength. Once these
things are satisfied, ten next steps are to determine which operating system and language can be
used for developing the tool. Once the programmers start building the tool the programmers need
lot of external support. This support can be obtained from senior programmers, from book or
from websites. Before building the system the above consideration are taken into account for
developing the proposed system.
 12

CHAPTER 3

REQUIREMENT ANALYSIS
This part depicts about the prerequisites. It determines the equipment and programming
prerequisite that are needed for software to keeping in mind the end goal, to run the application
appropriately. The Software Requirement Specification (SRS) is clarified in point of interest,
which incorporates outline of this exposition and additionally the functional and non-practical
necessity of this thesis.

3.1 General Description

The reason behind the framework prerequisites and determination record is to depict the
assets and administration of those assets utilized as a part of the configuration of the Public Key
Cryptosystem for information partaking in distributed storage. This framework necessity and
particular will likewise give insights with respect to the utilitarian and non-useful prerequisites of
the venture.

3.1.1 Users Perspective

The Characteristic of this task work is to give information adaptability security while
sharing information through cloud. It gives a proficient approach to share information through
cloud.

3.2 Non Functional Requirement

Non utilitarian necessities are the prerequisites which are not straightforwardly having a
place with the specific capacity gave by the framework. This gives the criteria that can be
utilized to finish up the operation of a framework rather than particular practices.

This can be utilized to relate the rising structure properties, for instance, immovable
quality, response time and store inhabitancies. Here again they ought to portray objectives on the
system, for instance, the capacity of the data yield devices and data representation used as a piece
of structure interfaces. In all probability all non helpful essentials can be relating to the system as
whole rather than to individual structure highlights. This suggests they are every now and again
essential appear differently in relation to the individual commonsense necessities. Non utilitarian
necessity gets through the client needs, in view of spending plan limitations, hierarchical
 13

approaches, and the requirement for interoperability with other programming and equipment
frameworks.

The going with non-valuable requirements are meriting thought.

 Security: The framework ought to permit a secured correspondence between information

proprietor and beneficiary.
 Reliability: The system should be trustworthy and ought not corrupt the execution of the
present structure and should not to provoke the hanging of the structure.

3.3 System Requirement

3.3.1 Hardware Requirement

 Processor : intel/amd
 Keyboard : 104 Keys
 Floppy Drive : 1.44 MB MHz Pentium III
 RAM : 128 MB
 Hard Disk : 10 GB
 Monitor : 14” VGA COLOR
 Mouse : Logitech Serial Mouse
 Disk Space : 1 GB

3.3.2 Software Requirements

 Operating System : Win 2000/ XP

 Server : Apache Tomcat
 Technologies used : Java, Servlets, JSP, JDBC
 JDK : Version 1.7
 Database : My SQL 5.0
 14

3.4 Feasibility Study

Believability is the determination of paying little respect to whether an undertaking justifies
action. The framework followed in building their strength is called acceptability Study, these kind of
study if a task could and ought to be taken.

Three key thoughts included in the likelihood examination are:

 Technical Feasibility

 Economic Feasibility

 Operational Feasibility

3.4.1 Technical Feasibility

Here it is considered with determining hardware and programming, this will effective
fulfill the client necessity the specialized requires of the framework should shift significantly yet
may incorporate.

 The office to create yields in a specified time.

 Reaction time under particular states.
 Capacity to deal with a particular segment of exchange at a specific pace.

3.4.2 Economic Feasibility

Budgetary examination is the often used system for assessing the feasibility of a
projected structure. This is more usually acknowledged as cost/favorable position examination.
The method is to center the focal points and trusts are typical casing a projected structure and a
difference them and charges. These points of interest surpass costs; a choice is engaged to
diagram and realize the system will must be prepared if there is to have a probability of being
embraced. There is a consistent attempt that upgrades in exactness at all time of the system life
cycle.

3.4.3 Operational Feasibility

It is for the most part identified with human association and supporting angles. The
focuses are considered:

 What alterations will be carried through the framework?

 What authoritative shapes are dispersed?
 15

 What new aptitudes will be needed?

 Do the current framework employee’s individuals have these aptitudes?
 If not, would they be able to be prepared over the span of time?

3.5 Resource Requirement

3.5.1 HTML
HTML, an initialize of Hypertext Markup Language, is the predominant markup language for
web pages. It provides a means to describe the structure of text-based information in a document
— by denoting certain text as headings, paragraphs, lists, and so on — and to supplement that
text with interactive forms, embedded images, and other objects. HTML is written in the form of
labels (known as tags), surrounded by angle brackets. HTML can also describe, to some degree,
the appearance and semantics of a document, and can include embedded scripting language code
which can affect the behavior of web browsers and other HTML processors.

HTML is also often used to refer to content of the MIME type text/html or even more broadly as
a generic term for HTML whether in its XML-descended form (such as XHTML 1.0 and later)
or its form descended directly from SGML.

Hypertext Markup Language (HTML), the languages of the World Wide Web (WWW), allows
users to produces Web pages that include text, graphics and pointer to other Web pages
(Hyperlinks).
HTML is not a programming language but it is an application of ISO Standard 8879, SGML
(Standard Generalized Markup Language), but specialized to hypertext and adapted to the Web.
The idea behind Hypertext is that instead of reading text in rigid linear structure, we can easily
jump from one point to another point. We can navigate through the information based on our
interest and preference. A markup language is simply a series of elements, each delimited with
special characters that define how text or other items enclosed within the elements should be
displayed. Hyperlinks are underlined or emphasized works that load to other documents or some
portions of the same document.
HTML can be used to display any type of document on the host computer, which can be
geographically at a different location. It is a versatile language and can be used on any platform
or desktop.
 16

HTML provides tags (special codes) to make the document look attractive. HTML tags are not
case-sensitive. Using graphics, fonts, different sizes, color, etc., can enhance the presentation of
the document. Anything that is not a tag is part of the document itself.

3.5.2 JavaScript

JavaScript is a script-based programming language that was developed by Netscape

Communication Corporation. JavaScript was originally called Live Script and renamed as
JavaScript to indicate its relationship with Java. JavaScript supports the development of both
client and server components of Web-based applications. On the client side, it can be used to
write programs that are executed by a Web browser within the context of a Web page. On the
server side, it can be used to write Web server programs that can process information submitted
by a Web browser and then update the browser’s display accordingly.

Even though JavaScript supports both client and server Web programming, we prefer JavaScript
at Client side programming since most of the browsers supports it. JavaScript is almost as easy to
learn as HTML, and JavaScript statements can be included in HTML documents by enclosing
the statements between a pair of scripting tags

<Script> ………. </Script>

<Script Language = “JavaScript”>

JavaScript statements

</Script>

Here are a few things we can do with JavaScript

 Validate the contents of a form and make calculations.

 Add scrolling or changing messages to the Browser’s status line.
 Animate images or rotate images that change when we move the mouse over them.
 Detect the browser in use and display different content for different browsers.
 Detect installed plug-ins and notify the user if a plug-in is required.
 We can do much more with JavaScript, including creating entire application.
 17

3.5.3 Java Server Pages

Java Server Pages technology lets you put snippets of servlet code directly into a text-based
document. A JSP page is a text-based document that contains two types of text: static template
data, which can be expressed in any text-based format such as HTML, WML, and XML, and JSP
elements, which determine how the page constructs dynamic content.Java Server Page™ (JSP):
An extensible Web technology that uses template data, custom elements, scripting languages,
and server-side Java objects to return dynamic content to a client. Typically the template data is
HTML or XML elements, and in many cases the client is a Web browser.

According to JSP model1 we can develop the application as,

Fig 3.1 Sevlet

According to above model the presentation logic has to be implemented in JSP page and the
business logic has to be implemented as part of Java bean This model help us in separating the
presentation and business logic. For large-scale projects instead of using model1 it is better to
use model2 (MVC). Struts framework is based on model 2.

Java Server Pages (JSP) lets you separate the dynamic part of your pages from the static
HTML. You simply write the regular HTML in the normal manner, using whatever Web-
page-building tools you normally use. You then enclose the code for the dynamic parts in
special tags, most of which start with "<%" and end with "%>". For example, here is a section
of a JSP page that results in something like "Thanks for ordering Core Web Programming

For URL of

http://host/OrderConfirmation.jsp?title=Core+Web+Programming:
 18

Thanks for ordering

<I><%= request.getParameter("title") %></I>

You normally give your file a .jsp extension, and typically install it in any place you could
place a normal Web page. Although what you write often looks more like a regular HTML
file than a servlet, behind the scenes, the JSP page just gets converted to a normal servlet,
with the static HTML simply being printed to the output stream associated with the servlet's
service method. This is normally done the first time the page is requested, and developers can
simply request the page themselves when first installing it if they want to be sure that the first
real user doesn't get a momentary delay when the JSP page is translated to a servlet and the
servlet is compiled and loaded. Note also that many Web servers let you define aliases that so
that a URL that appears to reference an HTML file really points to a servlet or JSP page.

Aside from the regular HTML, there are three main types of JSP constructs that you embed in
a page: scripting elements, directives, and actions. Scripting elements let you specify Java
code that will become part of the resultant servlet, directives let you control the overall
structure of the servlet, and actions let you specify existing components that should be used,
and otherwise control the behavior of the JSP engine. To simplify the scripting elements, you
have access to a number of predefined variables such as request in the snippet above.

3.6 MySql

3.6.1 Introduction:

MySql is a relational database management system, which organizes data in the form of tables.

MySQL is one of many databases servers based on RDBMS model, which manages a seer of

data that attends three specific things-data structures, data integrity and data manipulation. With

MySQL cooperative server technology we can realize the benefits of open, relational systems for

all the applications. MySQL makes efficient use of all systems resources, on all hardware

architecture; to deliver unmatched performance, price performance and scalability.

 19

3.6.2 Distinct Features of MySql:

MySQL adaptable multithreaded server architecture delivers scalable high performance

for very large number of users on all hardware architecture including symmetric
multiprocessors (sumps) and loosely coupled multiprocessors. Performance is achieved
by eliminating CPU, I/O, memory and operating system bottlenecks and by optimizing
the MySQL DBMS server code to eliminate all internal bottlenecks.

FEATURES OF MYSQL:

Most popular RDBMS in the market because of its ease of use

 Client/server architecture.
 Data independence.
 Ensuring data integrity and data security.
 Managing data concurrency.
 Parallel processing support for speed up data entry and online transaction processing
used for applications.
 20

CHAPTER 4

DIAGRAMS

4.1 USE CASE DIAGRAM:

4.1.1 Use case Diagram User

YES

User

Field Name City Message Image Fileupload

Fig 4.1 User Use Case Diagram

 21

4.1.2 Use case Diagram officer

YES

Officer

Query type query Suggestion Status

Fig 4.2 Officer Use Case Diagram

 22

4.1.3 Use case Diagram Admin

YES

Admin

use r deta ils officer details

Fig 4.3 Admin Use Case Diagram

 23

4.2 DATA FLOW DIAGRAM:

4.2.1 Data flow Diagram user

Start

YES NO
User Login

Field name

City

Messge

Unauthorised
User
Image
Fileuplode

End Process

Fig 4.4 User DFD

 24

4.2.2 Data flow Diagram officer

Start

YES NO
OFFICER LOGIN

Query Type

Query

Suggestion

Unauthorised
User
Status

End Process

Fig 4.5 Officer DFD

 25

4.2.3 Data flow Diagram Admin

Start

YES NO
Admin login

User detalis

officer detalis

Unauthorised
User

End Process

Fig 4.6 Admin DFD

 26

4.3 Sequence Diagram:

4.3.1 Sequence Diagram Admin

Login Office r
user de talis
de ta lis
Admin
Login

Fig 4.7 Admin Sequence Diagram

 27

4.3.2 Sequence Diagram User

Login user query query view

User
Login

Fig 4.8 User Sequence Diagram

 28

4.3.3 Sequence Diagram officer

Login user que ry

Sugge stion
view
office r
Login

Fig 4.9 Officer Sequence Diagram

 29

4.4 Action Diagram:

4.4.1 Action Diagram User

Login
User

query

query view

Logout

Fig 4.10 User Action Diagram

 30

4.4.2 Action Diagram Officer

Login
officer

query view

suggestion

Logout

Fig 4.11 Officer Action Diagram

 31

4.4.3 Action Diagram Admin

Login
Admin

user view detalis

officer view
detalis

Logout

Fig 4.12 Admin Action Diagram

 32

CHAPTER 5

TESTING
5.1 Introduction
Unit testing is an improvement system where software engineers make tests as they create
programming. The tests are basic short tests that test practically of a specific unit or module of
their code, for example, a class or capacity.

Utilizing open source libraries like cunit, oppunit and religious recluse it (for C, C++ and Java)
these tests can be consequently run and any issues discovered rapidly. As the tests are created in
parallel with the source unit test exhibits its rightness.

5.2 Validation and System Testing

Approval testing is a worry which covers with reconciliation testing. Guaranteeing that the
application satisfies its detail is a noteworthy standard for the development of a coordination test.
Approval testing additionally covers to a huge degree with System Testing, where the application
is tried concerning its normal workplace. Thusly for some procedures no reasonable division
amongst approval and framework testing can be made. Particular tests which can be performed
in either or the two phases incorporate the accompanying.

 Regression Testing: Where this version of the software is tested with the automated test
harness used with previous versions to ensure that the required features of the previous
version are skill working in the new version.
 Recovery Testing: Where the software is deliberately interrupted in a number of ways
off, to ensure that the appropriate techniques for restoring any lost data will function.
 Security Testing: Where unauthorized attempts to operate the software, or parts of it,
attempted it might also include attempts to obtain access the data, or harm the software
installation or even the system software. As with all types of security determined will be
able to obtain unauthorized access and the best that can be achieved is to make this
process as difficult as possible.
 Stress Testing: Where abnormal demands are made upon the software by increasing the
rate at which it is asked to accept, or the rate t which it is asked to produce information.
More complex tests may attempt to crate very large data sets or cause the soft wares to
make excessive demands on the operating system.
 33

 Performance testing: Where the performance requirements, if any, are checked. These
may include the size of the software when installed, type amount of main memory and/or
secondary storage it requires and the demands made of the operating when running with
normal limits or the response time.
 Usability Testing: The process of usability measurement was introduced in the previous
chapter. Even if usability prototypes have been tested whilst the application was
constructed, a validation test of the finished product will always be required.
 Alpha and beta testing: This is where the software is released to the actual end users.
An initial release, the alpha release, might be made to selected users who be expected to
report bugs and other detailed observations back to the production team. Once the
application changes necessitated by the alpha phase can be made to larger more
representative set users, before the final release is made to all users.

The final process should be a Software audit where the complete software project is
checked to ensure that it meets production management requirements. This ensures that
all required documentation has been produced, is in the correct format and is of
acceptable quality. The purpose of this review is: firstly to assure the quality of the
production process and by implication construction phase commences. A formal hand
over from the development team at the end of the audit will mark the transition between
the two phases.

5.3 Integration Testing

Integration Testing can continue in various diverse ways, which can be comprehensively
portrayed as best down or base up. In top down reconciliation testing the abnormal state control
schedules are tried to begin with, conceivably with the center level control structures exhibit just
as stubs. Subprogram stubs were introduced in section2 as fragmented subprograms which are
just present to permit the higher. Level control schedules to be tried.
 34

Top down testing can continue in a profundity first or an expansiveness first way. For profundity
first reconciliation every module is tried in expanding subtle element, supplanting an ever
increasing number of levels of detail with real code as opposed to stubs. On the other hand
expansiveness initially would handle by refining every one of the modules at a similar level of
control all through the application .by and by a blend of the two methods would be utilized. At
the underlying stages every one of the modules may be just halfway useful, potentially being
actualized just to manage non-mistaken information. These eventual tried in expansiveness first
way, yet over some stretch of time each future supplanted with progressive refinements which
were nearer to the full usefulness. This permits profundity initially testing of a module to be
performed at the same time with expansiveness initially testing of the considerable number of
modules.

The other significant classification of mix testing is Bottom Up Integration Testing where an
individual module is tried frame a test outfit. Once an arrangement of individual module have
been tried they are then consolidated into an accumulation of modules ,known as assembles,
which are then tried by a moment test saddle. This procedure can proceed until the point that the
fabricate comprises of the whole application. By and by a blend of best down and base up testing
would be utilized. In a substantial programming venture being produced by various sub-groups,
or a littler venture where diverse modules were worked by people. The sub groups or people
would lead base up testing of the modules which they were developing before discharging them
to a coordination group which would gather them together for top-down testing.

5.4 Unit Testing

Unit testing manages testing a unit overall. This would test the association of many capacities yet
bind the test to one unit. The correct extent of a unit is left to understanding. Supporting test
code, once in a while called Scaffolding, might be important to help an individual test. This sort
of testing is driven by the engineering and usage groups. This concentration is additionally called
 35

discovery testing on the grounds that exclusive the points of interest of the interface are
unmistakable to the test. Limits that are worldwide to a unit are tried here.

In the development business, platform is a transitory, simple to amass and dismantle, outline set
around a working to encourage the development of the building. The development specialists
initially construct the platform and afterward the building. Later the framework is expelled,
uncovering the finished building likewise, in programming testing, one specific test may require
some supporting programming. This product builds up can a right assessment of the test occur.
The platform programming may build up state and qualities for information structures and giving
sham outside capacities to the test. Distinctive platform programming might be required frame
one test to another test. Platform programming seldom is considered piece of the framework.

A few times the platform programming winds up noticeably bigger than the framework
programming being tried. Typically the platform programming is not of an indistinguishable
quality from the framework programming and oftentimes is very delicate. A little change in test
may prompt considerably bigger changes in the framework.

Inner and unit testing can be computerized with the assistance of scope apparatuses. Dissects the
source code and created a test that will execute each option string of execution. Regularly, the
scope device is utilized as a part of a marginally extraordinary way. To begin with the scope
instrument is utilized to enlarge the source by putting data prints after each line of code. At that
point the testing suite is executed creating a review trail. This review trail is broke down and
reports the percent of the aggregate framework code executed amid the test suite. On the off
chance that the scope is high and the untested source lines are of low effect to the framework's
general quality, at that point not any more extra tests are required.
 36

CHAPTER 6

SCREEN SHOT:

6.1 USER

Fig 6.1 User Login Screen

 37

6.2 User Query

Fig 6.2 User Query

 38

6.3 Query User View

Fig 6.3 User Query View

 39

6.4 OFFICER PAGE

Fig 6.4 Officer Login

 40

6.5 FIELD OFFICER QUERY VIEW

Fig 6.5 Officer Query View

 41

6.6 FIELD OFFICER SUGGESTION

Fig 6.6 Officer Query Suggestions

 42

6.7 ADMIN

Fig 6.7 Admin Login Page