DISNIC PLAN PROJECT (IRRIGATION)

A Project Submitted in partial fulfillment of the requirements for the award of the degree Of Master of Computer Application By Kunal Singh (MRT08PGMCA-010)

School of Computer Engineering & Information Technology

SHOBHIT UNIVERSITY, MEERUT June, 2011

1

GOVERNMENT OF INDIA
MINISTRY OF COMMUNICATIONS & INFORMATION TECHNOLOGY DEPARTMENT OF INFORMATION TECHNOLOGY

National Informatics Centre

This is to certify that Mr. Kunal Singh a student of Master of Computer Application from Shobhit University, Meerut has done/is doing his full-semester project training at DISNIC Programme Division, NIC, New Delhi, from 15.01.2011 to 15.06.2011. The project work entitled A Web Enabled Information System DISNIC PROJECT PLAN - Irrigation embodies the original work done by him during his above full semester project training period.

Mr. Anil Kumar Chaursiaa

Mrs. Sameena Mukhija

(Scientist C)
2

(Technical Director)

Certificate
I hereby certify that the work which is being submitted in this project entitled A Web Enabled Information System DISNIC PROJECT PLAN (IRRIGATION) in partial fulfillment of the requirements for the award of the degree of MCA and submitted in the School of Computer Engineering & Information Technology undertaken by me during the period 15/01/2011 to 15/06/2011 under the supervision of Informatics Centre, New Delhi Matter presented in this project has not been submitted by me for the award of any Degree/Diploma in any other Institute/University. Mrs. Sameena Mukhija (Technical Director NIC, New Delhi) and Mr. Anil Chaursia(Scientist-C) at National

Signature of the Student This is to certify that the above statement made by the candidate is correct to the best of my knowledge.

Signature of Guide Mentor

Declaration
I do, hereby, declare that the dissertation entitled A Web Enabled Information System DISNIC PLAN PROJECT is an authentic work developed by me at National Informatics Centre, New Delhi , under the guidance of Mrs. Sameena Mukhija (Technical Director, NIC, New Delhi) and Mr. Anil Kumar Chaursia (Scientist-C) and Mr. Yogesh Awasthi(Assistant Professor, Shobhit University,Meerut ) submitted as a partial fulfillment of the degree of Master Of Computer Application (MCA) of Shobhit University. I also declare that, any or all contents incorporated in this dissertation have not been submitted in any form for the award of any degree or diploma of any other institution or university.

Kunal Singh Vikramendra Singh 6th semester,M.C.A. Shobhit University,Meerut

Acknowledgement
I take this opportunity to express my profound sense of gratitude and respect to all those who helped me throughout the duration of this project. I acknowledge the effort of those who have contributed significantly to my project. I express my sincere gratitude and thankfulness towards Mr. Yogesh Awasthi(Department of Computer Application) of Shobhit University, Meerut, Uttar Pradesh for his valuable time and guidance throughout the MCA. I feel privileged to offer my sincere thanks and deep sense of gratitude to Training Division, NIC Headquarters, Mr. M. Moni (Deputy Director General), Mrs. Sameena Mukhija (Technical Director) and Mr. Anil Chaurasia(Scientist -C) at DISNIC Programme Division, NIC, New Delhi, for expressing their confidence in me by letting me work on a project of this magnitude and providing their support, help & encouragement in completing this project. I am grateful for the co-operation & valuable suggestions rendered by all the staff members Of the DISNIC Programme Division, National Informatics Centre, New Delhi. I am grateful to all our friends for providing critical feedback & support whenever required. I regret any inadvertent omissions.

Kunal Singh Vikramendra Singh

TABLE OF CONTENTS
CHAPTER NO. TITLE PAGE NO.

INTRODUCTION

1 - 10 1 3 3 4 5 9 11 - 18 11 15 18 18 19 - 24 3 4 23 25 - 42 25 28 33 34 36 43 - 46 43 45
6

1.1 About the NIC 1.2 About Project 1.2.1 Project Title 1.2.2 Objective of Project 1.2.3 Background Analysis 1.2.4 Application of the Project
2.

Technology Used 2.1 Front End 2.2 Back End 2..3 H/W requirement 2..4 S/W requirement 3. System Development Life Cycle 3.1 Problem Definition or Identification 3.1 System Analysis 3.1 Feasibility Study 4. System Design 4.1 Three Tier Architecture 4.2 Data Flow Diagram (D.F.D.) 4.3 E-R Diagram 4.4 Normalization 4.5 Data Dictionary 5. Testing & Implimentation 5.1 Testing 5.1.2 Level of Testing

5.2 Implementation 6. 7. Conclusion Annexure References/Bibliography

46 47 - 48 49 - 56 57

CHAPTER - 1

INTRODUCTION

1.1

About NIC (National Informatics Centre) National Informatics Centre (NIC) is a premier Science and Technology Organization

under the Department of Information Technology of the Government of India actively working for the past three decades in the area of Information and Communication Technology (ICT) Applications in the Government Sector. National Informatics Centre (NIC) of the Department of Information Technology is providing network backbone and e-Governance support to Central Government, State Governments, UT Administrations, Districts and other Government bodies. It offers a wide range of ICT services including Nationwide Communication Network for decentralized planning, improvement in Government services and wider transparency of national and local Governments. NIC assists in implementing Information Technology Projects, in close collaboration with Central and State Governments, in the areas of (a) Centrally sponsored schemes and Central sector schemes, (b) State sector and State sponsored projects, and (c) District Administration sponsored projects. NIC endeavors to ensure that the latest technology in all areas of IT is available to its users. NIC Headquarters is based in New Delhi. At NIC Headquarters, a large number of Application Divisions exist which provide total Informatics Support to the Ministries and Departments of the Central Government. NIC computer cells are located in almost all the Ministry Bhawans of the Central Government and Apex Offices including the Prime Ministers Office, the Rashtrapati Bhawan and the Parliament House. Apart from this, NIC has various Resource Divisions at the Headquarters which specialize into different areas of IT and facilitate the Application Divisions as well as other NIC Centres in providing state-of-the-art services to the Govt. At the State level, NICs State/UTs Units provide informatics support to their respective State Government and at the District level lie the NIC District Informatics Offices. NIC has conceptualized, developed and implemented a very large number of projects for various Central and State Government Ministries, Departments and Organizations. Many of these projects are continuing projects being carried out by various divisions of NIC at New Delhi Headquarters and State/District centres throughout the country. Some of the
9

most important note worthy projects, which offer a glimpse of the multifaceted, diverse activities of NIC, touching upon all spheres of e-governance and thereby influencing the lives of millions of citizens of India is given below:

Agrictural Marketing Information Network (AGMARKNET) Central Passport System Community Information Centres (CICs) Computerized Rural Information Systems Project (CRISP) Court Information System (COURTIS) Department of Agriculture Network (DACNET) District Information System for Planning (DISNIC-PLAN) Computerization of Agricultural Census and Input Survey. Examination Results Portal Training Spatial Data Infrastructure (SDI)

1.2

ABOUT PROJECT

1.2.1 Project Title:

A Web Enabled Information System- DISNIC PLAN PROJECT - IRRIGATION DISNIC Programme Division was formed as a Core Group at National Informatics Centre in the financial year 1987-88 and given the responsibility of design, development and implementation of the DISNIC Programme using NICNET facilities at the district level, and also to interact with NIC State Units and Regional centres for effective implementation, feedback analysis, impact analysis & strengthening of Information System development strategy and future enhancement etc. of the DISNIC Programme. DISNIC facilitated easy collection, compilation, dissemination and on-line accessibility of information on several sectors of the economy at state level with the timely availability of qualitative information at all possible levels like . . . . Nation State District Block
10

Village

DISNIC also facilitated for the building up of databases of national importance through active co-operation of the state governments. 1.2.2

OBJECTIVE OF DISNIC PLAN PROJECT SCHEMES:

The objectives of the DISNIC Programme are as follows;

Develop necessary databases in various sectors of the economy for planning and decision making at the district level. Promote informatics culture at the district level through appropriate training programmes. Improve the analysis capacity and presentation of statistics utilised for National, Regional and District Planning. Develop modelling and forecasting techniques that are required for making for socioeconomic development.
Promote Geographic Information System (GIS) techniques for planning, and also

Remote sensing data applications for Natural Resources Management at grass-root level.

All ground water schemes and surface water schemes (both flow and lift) having culturable command area up to 2000 ha. Individually are classified as Minor Irrigation Schemes. Ground water schemes comprise of dug wells, dug-cum-bore wells, borings, private shallow tube wells, filter points and deep tube wells. The command area of private ground water schemes varies from 1 to 5 hectares. The State Governments provide assistance in installation of such schemes which confines mainly to technical guidance, custom service for boring and arrangements for credit facilities at reasonable rates of interest. The subsidies are also made available for installation of these schemes to weaker sections of farmers. The construction, operation and maintenance of these schemes are done by the farmers themselves. The deep tube wells which extend up to the depth of 200 meters or more are designed to give a discharge of 100 to 200 cubic meters per hour.
11

The surface water schemes comprise of surface flow schemes and surface lift irrigation schemes. The surface flow schemes typically consist of tanks, check dams, structures and can serve as water conservation cum ground water recharge scheme. The structures are generally prevalent in hilly regions. These are known as Kuhl in Jammu & Kashmir and Himachal Pradesh, Gul in Uttar Pradesh, Ahars and Pynes inBihar and low Khones and Dongs in north-eastern region. The small storage tanks are owned by community or local bodies and generally have command areas up to 40 hectares. The large storage tanks alongwith the distribution system having command area varying from 40 to 2000 hectares are constructed by State Government Department. 1.2.3

Background Analysis:
During the process of implementation, many states have expressed their financial

constraint to undertake information collection at village level and its update periodically, to facilitate micro-level planning. It was, therefore, recommended to include the DISNIC-PLAN project under Central Sector Scheme and sufficient budget be allocated accordingly, to facilitate systematic decentralization of planning process at the grass root level. Indian planning and development process is moving ahead for a change, from the centralized to more of decentralized approach, in order to give due recognition to the microlevel needs and potentials in decision making. Micro-level Planning is progressively gaining momentum in India in view of the enactment of Panchayat Raj Institutions at grass-root level. The Planning steps, the data needs, the institutional requirements, the macro-micro linkages and the information flows are necessary to make the planning process more effective.

In this process, the National Informatics Centre, through this proposed Scheme for DISNIC-PLAN Programme, will take up creation of a distributed database on village level information for about 6 lakhs villages, in the country, at its 540 district nodes. Project activities will be taken-up to link these databases with the spatial technology in the form of maps to provide an effective framework for spatial analysis under Geographical Information System (GIS) environment. Further, development of INTRANET site over NICNET National Info-Highway, on DISNIC-PLAN Programme will also be undertaken. Thus DISNIC-PLAN

12

Programme as a Centrally Sponsored Scheme will facilitate the district authorities in their planned effort at the decentralized spatial units. In addition, it is realized that, various institutions, research organizations, NGOs involved in micro-level planning should be linked up through NICNET, for wider dissemination and utility of DISNIC-PLAN database. In close association with these organizations, NIC will build development indicators at the decentralized spatial units, using the DISNIC-PLAN database, to gauge the spatial variations in the levels of development. Certainly, these indicators will form a base to evade the subjectivity in resource allocation at district level. 1.2.3.1 DEFINITIONS A) Culturable Command Area (CCA): The area which can be irrigated from a scheme and is fit for cultivation.

B)

Gross Irrigated Area: The area irrigated under various crops during a year, counting the area irrigated under

more than one crop during the same year as many times as the number of crops grown and irrigated.

C)

Irrigation Potential Created: The total gross are purposed to be irrigated under different crops during a year by a

scheme. The area purposed to be irrigated under more than one crop during the same year is counted as many times as the number of crops grown and irrigated. D) Irrigation Potential Utillised: The gross area actually irrigated during reference year out of the gross purposed area to be irrigated by the scheme during the year.
13

E)

Minor Irrigation (M.I) Scheme: A scheme having CCA up to 2,000 hectares individually is classified as Minor

Irrigation Scheme. F) Medium Irrigation Scheme: A scheme having CCA more than 2,000 hectares and up to 10,000 hectare individually is a medium irrigation scheme. G) Major Irrigation Scheme: A scheme having CCA more than 10,000 hectare Minor Irrigation schemes Irrigation schemes using either groundwater or surface water and having a cultivable area up to 2000 hectare individually is categorized as Minor Irrigation schemes. The schemes have been categorized into five major types; (1) Dug well (2) Shallow tube well (3) Deep tube well (4) Surface flow and (5) Surface lift.

14

Dug Well: It covers ordinary open wells of varying dimensions dug or sunk from the ground surface into water bearing stratum to stratum to extract water for irrigation purposes.These are broadly masonry wells, kuchcha wells and dug-cum-bore wells.

Shallow Tube well: A shallow tube well is which consist of a borehole built into ground with the purpose of tapping ground water from previous zones. These tube wells are either cavity tube wells are either cavity tube wells or strainer tube wells usually drilled by percussion method of using hand boring sets or strainer tube wells usually drilled by percussion method of using hand boring sets and sometimes percussion rigs coir structures from by binding coir strings over and iron frame or bamboo frame are used as strainer. Bore-wells in which borehole is stable without a lining in the bottom portion and a tube is inserted only in the upper zone, are also shallow tube wells. Dug cum bore wells with pump sets are shallow tube wells.

Deep Tube well: Deep tube wells are usually designed to give a discharged of 100 to 200 cubic meters per hour and extend to the depth of 70 meters or more only. These include wells that are drilled by rotary percussion of rotary come percussion rigs. Deep tube wells are usually owned and operated by government departments are co-operative. Its annual output is approximately 15 times that of an average shallow tube well depending on power availability.

Surface Flow:

15

All surface flow in irrigation schemes, which are exclusively based on irrigation by gravity flow, are to be covered. In case, surface flow schemes having lifting device is also installed on it and the irrigation is partly done through lifting the water and partly by gravitational method turn by turn or simultaneously, the scheme has to be accounted only as one, either as surface lift scheme or surface flow depending upon the acreage irrigated during the year 2000-2001, whichever is more of the two. It covers storage scheme; diversion scheme; water conservation-cum-ground water recharging scheme. Storage schemes include tanks and reservoirs, which impound water of streams and rivers. Small storage tanks which are called ponds or bundhis are also covered. The essential features of these schemes are

A bund or a dam which is generally of earth but also sometimes partly or fully masonry. Anicuts and feeder channels to divert water from adjoining catchments. Waste weir to dispose of surplus flood water. Sluice or sluices to let out water for irrigation and Conveyance and distribution system Diversion schemes aim at providing gravity flow irrigation by more diversion of stream water supply without arranging any storage. Essentially this scheme consists of two parts: A) An obstruction (Weir) or bund constructed across the stream for raising and diverting water. B) An artificial channel, known as kuhl in the hilly areas.

Surface Lift: A scheme may be considered as surface lift scheme if the major part of irrigation is done through lifting the surface water. These schemes are similar to those of diversion schemes but in addition, pumps are installed and pump houses constructed. In regions, where the topography does not permit direct flow irrigation from rivers and streams, water has to be lifted in to the irrigation channels.

16

1.2.4 Application of the Project:

A Web Enabled Information System - DISNIC PLAN PROJECT IRRIGATION is a web enabled system which helps general public as well as policy makers to gather information about every possible objects in irrigation. This system is being developed for the ministry of Irrigation. The system provides irrigation census information under various criteria and formats at various levels of administration like village level, block level, district levels, state levels and lastly at national level. The system is also made secured as all the updation of irrigation census database can be done by the authorized person i.e. the administrator only. The vast opportunities offered by the Computer and Information Technology, in particular Database Technology and GIS & RS Technology, are to be exploited to facilitate scientific approach in plan preparation as well as plan execution and monitoring. This will certainly bring about a holistic change in both quantitative as well as qualitative, in plan making aspects. Currently the huge volume of data stored in various forms is under-utilized. This is mainly due to the lack of awareness among the district planning officers and other sectoral officers about the recent developments and potential of Information Technology

17

CHAPTER-2

TECHNOLOGY USED

18

2. Technology Used 2.1

2.1.1

Front End
ASP.NET

ASP.NET is a programming framework built on the common language runtime that can be used on a server to build powerful Web applications. ASP.NET offers several important advantages over previous Web development models: A) Enhanced Performance.

ASP.NET is compiled common language runtime code running on the server. Unlike its interpreted predecessors, ASP.NET can take advantage of early binding, just-in-time compilation, native optimization, and caching services right out of the box. This amounts to dramatically better performance before you ever write a line of code. B) World-Class Tool Support.

The ASP.NET framework is complemented by a rich toolbox and designer in the Visual Studio integrated development environment. WYSIWYG editing, drag-and-drop server controls, and automatic deployment are just a few of the features this powerful tool provides. C) Power and Flexibility. Because ASP.NET is based on the common language runtime, the power and flexibility of that entire platform is available to Web application developers. The .NET Framework class library, Messaging, and Data Access solutions are all seamlessly accessible from the Web. ASP.NET is also language-independent, so you can choose the language that best applies to your application or partition your application across many languages. Further,

19

common language runtime interoperability guarantees that your existing investment in COM-based development is preserved when migrating to ASP.NET.

D) Simplicity. ASP.NET makes it easy to perform common tasks, from simple form submission and client authentication to deployment and site configuration. For example, the ASP.NET page framework allows you to build user interfaces that cleanly separate application logic from presentation code and to handle events in a simple, Visual Basic - like forms processing model. Additionally, the common language runtime simplifies development, with managed code services such as automatic reference counting and garbage collection. E) Manageability.

ASP.NET employs a text-based, hierarchical configuration system, which simplifies applying settings to your server environment and Web applications. Because configuration information is stored as plain text, new settings may be applied without the aid of local administration tools. This "zero local administration" philosophy extends to deploying ASP.NET Framework applications as well. An ASP.NET Framework application is deployed to a server simply by copying the necessary files to the server. No server restart is required, even to deploy or replace running compiled code. F) Scalability and Availability.

ASP.NET has been designed with scalability in mind, with features specifically tailored to improve performance in clustered and multiprocessor environments. Further, processes are closely monitored and managed by the ASP.NET runtime, so that if one misbehaves (leaks, deadlocks), a new process can be created in its place, which helps keep your application constantly available to handle requests. G) Customizability and Extensibility.

20

ASP.NET delivers a well-factored architecture that allows developers to "plug-in" their code at the appropriate level. In fact, it is possible to extend or replace any subcomponent of the ASP.NET runtime with your own custom-written component. Implementing custom authentication or state services has never been easier. H) Security.

With built in Windows authentication and per-application configuration, you can be assured that your applications are secure. ASP.NET is a set of web application development technologies marketed by Microsoft. Programmers can use it to build dynamic web sites, web applications and XML web services. It is part of Microsoft's .NET platform and is the successor to Microsoft's Active Server Pages (ASP) technology. 2.1.1.2 Principles of ASP.NET Even though ASP.NET takes its name from Microsoft's old web development technology, ASP, the two differ significantly. Microsoft has completely rebuilt ASP.NET, based on the Common Language Runtime (CLR) shared by all Microsoft .NET applications. Programmers can write ASP.NET code using any of the different programming languages supported by the .NET Framework, usually C#, Visual Basic.NET, or JScript .NET, but also including open-source languages such as Perl and Python. ASP.NET has performance benefits over other script-based technologies because the server-side code is compiled to one or a few DLL files on a web server. ASP.NET attempts to simplify developers' transition from Windows application development to web development by offering the ability to build pages composed of controls similar to a Windows user interface. A web control, such as a button or label, functions in very much the same way as its Windows counterpart: code can assign its properties and respond to its events. Controls know how to render themselves: whereas Windows controls draw themselves to the screen, web controls produce segments of HTML and JavaScript which form part of the resulting page sent to the end-user's browser.

21

ASP.NET encourages the programmer to develop applications using an event-driven GUI paradigm, rather than in conventional web-scripting environments like ASP and PHP. The framework attempts to combine existing technologies such as JavaScript with internal components like "Viewstate" to bring persistent (inter-request) state to the inherently stateless web environment. ASP.NET uses the .NET Framework as an infrastructure. The .NET Framework offers a managed runtime environment (like Java), providing a virtual machine with JIT and a class library. The numerous .NET controls, classes and tools can cut down on development time by providing a rich set of features for common programming tasks. Data access provides one example, and comes tightly coupled with ASP.NET. A developer can make a page to display a list of records in a database, for example, significantly more readily using ASP.NET than with traditional web technologies like ASP or PHP. 2.1.1.3 Server side Dynamic web page: With server side model, the HTML source is sent to the web server with an extra set of instructions (that can be intermingled or sent separately). This set of instructions is again used to generate HTML for the page at the time the user requests the page. The page is generated dynamically on request.

2.2

Back End:

Features of SQL Server 2005 Microsoft SQL Server 2005 features include: Internet Integration. The SQL Server 2005 database engine includes integrated XML support. It also has the scalability, availability, and security features required to operate as the data storage component of the largest Web sites. The SQL Server 2005 programming model is integrated with the Windows DNA architecture for developing Web applications, and
22

SQL Server 2005 supports features such as English Query and the Microsoft Search Service to incorporate user-friendly queries and powerful search capabilities in Web applications.

Scalability and Availability. The same database engine can be used across platforms ranging from laptop computers running Microsoft Windows 98 through large, multiprocessor servers running Microsoft Windows 2000 Data Center Edition. SQL Server 2005 Enterprise Edition supports features such as federated servers, indexed views, and large memory support that allow it to scale to the performance levels required by the largest Web sites. Enterprise-Level Database Features. The SQL Server 2000 relational database engine supports the features required to support demanding data processing environments. The database engine protects data integrity while minimizing the overhead of managing thousands of users concurrently modifying the database. SQL Server 2000 distributed queries allow you to reference data from multiple sources as if it were a part of a SQL Server 2000 database, while at the same time, the distributed transaction support protects the integrity of any updates of the distributed data. Replication allows you to also maintain multiple copies of data, while ensuring that the separate copies remain synchronized. You can replicate a set of data to multiple, mobile, disconnected users, have them work autonomously, and then merge their modifications back to the publisher. Ease of installation, deployment, and use. SQL Server 2005 includes a set of administrative and development tools that improve upon the process of installing, deploying, managing, and using SQL Server across several sites. SQL Server 2005 also supports a standards-based programming model integrated with the Windows DNA, making the use of SQL Server databases and data warehouses a seamless part of building powerful and scalable systems. These features allow you to

23

rapidly deliver SQL Server applications that customers can implement with a minimum of installation and administrative overhead. Data warehousing. SQL Server 2005 includes tools for extracting and analyzing summary data for online analytical processing. SQL Server also includes tools for visually designing databases and analyzing data using English-based questions.

SQL Server Enterprise Manager Microsoft Management Console (MMC) is a tool that presents a common interface for managing different server applications in a Microsoft Windows network. Server applications provide a component called an MMC snap-in that presents MMC users with a user interface for managing the server application. SQL Server Enterprise Manager is the Microsoft SQL Server MMC snap-in. SQL Server Enterprise Manager is the primary administrative tool for SQL Server and provides an MMC-compliant user interface that allows users to: SQL Query Analyzer. Invoke the various wizards defined for SQL Server. Define groups of SQL Server instances. Register individual servers in a group. Configure all SQL Server options for each registered server. Create and administer all SQL Server databases, objects, logins, users, and Permissions in each registered server. Define and execute all SQL Server administrative tasks on each registered server. Design and test SQL statements, batches, and scripts interactively by invoking

Overview of the SQL Server Tools Microsoft SQL Server 2005 includes many graphical and command prompt utilities that allow users, programmers, and administrators to:
24

Administer and configure SQL Server. Determine the catalog information in a copy of SQL Server. Design and test queries for retrieving data. Copy, import, export, and transform data. Provide diagnostic information. Start and stop SQL Server.

2.3 Hardware
The following hardware is used while developing this project. Processor Memory Hard Disk : Intel Pentium 4 CPU 1.60GHz : 256 MB of RAM : 40 GB

Network adapter

: Intel PRO/100 VE Network connection

Monitor Printer

: Preferably color. : LaserJet 1010 Series, DeskJet or Dot Matrix

2.4 Software
The following Software used while developing this project. Operating System: Windows XP Professional ASP.NET Web server IIS 5.1 Microsoft SQL server 2005 Visual Studio.Net 2008 (Professional Edition.)

25

CHAPTER-3

SDLC
26

3.

System Development Life Cycle 3.1 Problem Definition or Identification

DISNIC Programme Division was formed as a Core Group at National Informatics Centre in the financial year 1987-88 and given the responsibility of design, development and implementation of the DISNIC Programme using NICNET facilities at the district level, and also to interact with NIC State Units and Regional centres for effective implementation, feedback analysis, impact analysis & strengthening of Information System development strategy and future enhancement etc. of the DISNIC Programme. DISNIC facilitated easy collection, compilation, dissemination and on-line accessibility of information on several sectors of the economy at state level with the timely availability of qualitative information at all possible levels like . . . . . Nation State District Block Village

DISNIC also facilitated for the building up of databases of national importance through active co-operation of the state governments.

3.2

System Analysis

Assuming that a new system is to be developed, the next phase is system analysis. Analysis involved a detailed study of the current system, leading to specifications of a new system. Analysis is a detailed study of various operations performed by a system and their
27

relationships within and outside the system. During analysis, data are collected on the available files, decision points and transactions handled by the present system. Interviews, on-site observation and questionnaire are the tools used for system analysis. Using the following steps it becomes easy to draw the exact boundary of the new system under consideration:

Keeping in view the problems and new requirements Workout the pros and cons including new areas of the system

All procedures, requirements must be analyzed and documented in the form of detailed data flow diagrams (DFDs), data dictionary, logical data structures and miniature specifications. System Analysis also includes sub-dividing of complex process involving the entire system, identification of data store and manual processes. The main points to be discussed in system analysis are:

Specification of what the new system is to accomplish based on the user requirements. Functional hierarchy showing the functions to be performed by the new system and their relationship with each other. Function network which are similar to function hierarchy but they highlight the those functions which are common to more than one procedure. List of attributes of the entities - these are the data items which need to be held about each entity (record)

3.1 Existing System At present only the DISNIC database is available but no web enabled system is there to access those data and to display them in a meaningful way. So, without a proper front end or interface it is very difficult to display DISNIC information based on different criteria and to generate DISNIC reports in a proper way. Without a web enabled system it is very difficult for common people to get the DISNIC information irrespective of their location.

3.1.2

Drawbacks of the existing system

28

Without a proper user interface it is very difficult to understand the meaning of

the data stored in the database. Without proper front end it is difficult for users to get specific information based

on some specific parameters. It is not possible for people from different locations to access census

information at any time. If some modifications has to be done to the data stored in the database, those

must be done directly in the database. 3.2 Proposed System

In the proposed system concern of the user and the management have been kept in mind before proceeding towards the generation of useful and meaningful results. With the development of this system all kinds of information related to irrigation could be accessed quite easily through this system. This system generates information under various criteria and at different levels of administration like village, block, district, state as well as the nation as a whole. The proposed system will generate the following information based on Size Class/Group and Social Groups at village, block, district, state and national level.

Number and area of operational holdings. Number and area of operational holdings by tenure and tenancy status. Leased in area by terms of leasing. Area under different land use. Number and area of operational holdings by irrigation status. Number of operational holdings receiving irrigation and area irrigated by Number of dug wells, tube wells, surface flow, deep tube wells Number and area of operational holdings according to dispersal of operated

different sources. area.

29

This system also makes this information available as reports which are very useful for making policies for the farming community.

3.3

Feasibility Study

3.3.1 Economic Feasibility

The financial and economic questions raised during preliminary investigations are for the purpose of estimating

The cost to conduct full system investigation. The cost of hardware and software for class of application. The benefits in terms of reduced cost and fewer costly errors. The cost if nothing changes, i.e., if the proposed system is not developed.

The proposed system is economically feasible because The system works efficiently and gives higher performance then the existing All the hardware and software required for developing the system is already While developing this system, there is no requirement of any new hardware or Due to the above mentioned reason the proposed system is economically feasible. 3.3.2 Technical Feasibility

system. available with the organization. software.

Technical feasibility centers on the existing computer system (H/W and S/W) whether it can support the addition of proposed system, if not, to what extent it can support and the organizations capacity to acquire additional components.
30

The proposed system is technically feasible because The hardware and software required are easy to install and handle. The system supports interactivity with the user through GUI. The organization is having highly qualified staffs to understand and manage the

hardware and software.

3.3.3

Behavioral Feasibility

Behavioral feasibility determines how much effort will go into selling the proposed system, in educating and training the user staff on the new system. Behavioral study strives on ensuring that the equilibrium of the organization is not disturbed. The changes should be readily accepted by the staff and sanctioned by authority to achieve organizational objective. The proposed system is behaviorally feasible because The proposed system will be faster and higher in performance. As the system will support a simple Graphical User Interface (GUI), no expertise

is needed to run the system.

31

CHAPTER - 4

32

SYSTEM DESIGN

33

4. System Design 4.1 System Architecture 3-Tier Architecture

A special type of client/server architecture consisting of three well-defined and separate processes, each running on a different platform: The user interface, which runs on the user's computer (the client). The functional modules that actually process data. This middle tier runs on a

server and is often called the application server. A database management system (DBMS) that stores the data required by the

middle tier. This tier runs on a second server called the database server.

Fig 3.1: 3-Tier Architecture

34

Fig 3.2: Three tier architecture

Fig 3.2: Three Tier Layer

35

The three-tier design has many advantages over traditional two-tier or single-tier designs, the chief ones being: The added modularity makes it easier to modify or replace one tier

without affecting the other tiers.

Separating the application functions from the database functions makes it Adequate security policies can be enforced within the server tiers without hindering the clients.

easier to implement load balancing.

4.1.1 Data Flow Diagram (DFD)

The DFD (also known as the bubble chart) is a simple graphical formalism that can be used to represent a system in terms of input data to the system, various processing carried out on these data, and the output data generated by the system. The main reason why the DFD technique is so popular is probably because of the fact that DFD is very simple formalism-it is simple to understand and use. A DFD model uses a very limited number of primitive symbols o represent the functions performed by a system and the data flow among these functions. Starting with a set of high-level functions that a system performs, a DFD model hierarchically represents various sub functions. Primitive Symbols Used for Constructing DFDs

36

Fig 4.1: 1 Level DFD

37

Fig 4.2: Level 1 DFD

38

Fig4.3: Level 2 DFD of Select Criteria

39

Fig4.4: Level 2 DFD of Process Information

Database Design

4.2

ER-Diagram

40

Fig 4.5: E-R Diagram of Process

4.3 Normalization
Normalization is an important step in database in designing a process of breaking down A complex design into a group of simple relations. Normalization is important for adapting A real life situation, something that will fit effectively into a relational database. 4.3.1 The advantages of normalizing are

41

database is easier to maintain database can be expanded with minimum effort does not include more duplicated data than necessary minimizes inconsistency in the database Minimizes the effect of update and delete anomalies. The various normal forms are as follows:

4.3.2

1NF: A relation R is in 1NF if and only if it contains atomic values. 2NF: A relation R is in 2NF if and only if it is in 1NF and every non-key attribute is fully Dependent on the primary key. 3NF: A relation R is in 3NF if and only if it is in 2NF and every non-key attribute is non transitively dependent on the primary key. BCNF: A relation R is in BCNF if and only if every determinant is a candidate key. 4NF: A relation R is in 4NF if and only if, whenever there exists multivalued dependencies (MVD) in the R, say A B, then all other attributes of R are also functionally dependent on A 5NF: A relation R is in 5NF if and only if every join dependency in R is implied by the Candidate keys of R. In the proposed system the databases are normalized up to 3rd Normal Form.

4.4
State

Table Design

This table structure is used to store the description of the States and Union Territories. Fields Type Remarks

42

STATECODE STATENAME

Tinyint VARCHAR(30)

PRIMARY KEY NOT NULL

Dist This table contains district names and corresponding district codes and state code of the state in which it belongs. Fields STATECODE DISTCODE DISTNAME Block This table structure is to store the description of all Blocks existing in the districts of State or Union Territories. Fields STATECODE DISTCODE BLOCKCODE BLOCKNAME Type TINYINT TINYINT TINYINT VARCHAR(30) Remarks PRIMARY KEY PRIMARY KEY PRIMARY KEY NOT NULL Type TINYINT VARCHAR(30) TINYINT(1) Remarks PRIMARY KEY PRIMARY KEY NOT NULL

Village This table structure is to store the description of all Villages in the various blocks of a particular District in a given State or Union Territories. Fields STATECODE DISTCODE BLOCKCODE VILLCODE VILLNAME Type TINYINT TINYINT TINYINT TINYINT VARCHAR(30) Remarks PRIMARY KEY PRIMARY KEY PRIMARY KEY PRIMARY KEY NOT NULL

4.5

Data Dictionary

43

A data dictionary plays a very important role in any software development process because of The following reasons: A data dictionary provides a standard terminology for all relevant data for Use by all engineers working in the same project. A consistent vocabulary for data items is very Important, since in large projects different engineers have a tendency to use different terms to Refer to the same data, which unnecessarily causes confusion. The data dictionary provides the analyst with a means to determine the definition of different Data structures in terms of their component elements. A data dictionary lists the purpose of all Data items and the definition of all composite data items in terms of their component data items.

1) DUGWELL
This table structure is used to store data of Dug well Scheme. Data entry is done through the Data Entry Module. Element Name STATECODE DISTCODE BLOCKCODE VILLCODE DT_ENUM SNO NAMECODE NAME KHAS_NO Hold_SIZE CAST COM_YEAR WELL_TYPE WELL_STAT FIN_SOURCE DIST_DEVI LIFT_DEVI DEVI_HP AVG_PUMP CCA MAJ_MED Element Type tinyint tinyint tinyint tinyint int int tinyint text text tinyint tinyint tinyint tinyint tinyint tinyint tinyint tinyint double tinyint double tinyint Element Description State Code District Code Block Code Village Code Date of Enumeration Serial Number of the Record Owners Code of the Scheme Name of the Owner Khasra Number of Scheme Code for Different Holding Size Social Status Code Of Owner Commissioning Year of the Scheme Code for Different Type of Well Code for the Status of Well Source of Finance Major distribution Device Lifting Device for the Scheme Horse Power of Lifting Device Average Pumping Hours of the Device Total Cultivable Command Area Whether the Scheme is in maj/med area
44

KHARIF_A RABI_A PERENIAL_A OTHER_A KHARIF_B RABI_B PERENIAL_B OTHER_B KHARIF_C RABI_C PERENIAL_C OTHER_C CONSTRAINT

double double double double double double double double double double double double tinyint

Gross Potential created for Kharif Season Gross Potential created for Rabi Season Gross Potential created for Perrnnial Season Gross Potential created for Other Season Area Irrigated in Kharif Season Area Irrigated in Rabi Season Area Irrigated in Perenial Season Area Irrigated in Other Season Area Irrigated in Kharif Season by major/medium scheme Area Irrigated in RabiSeason by major/medium scheme Area Irrigated in Perenial Season by major/medium scheme Area Irrigated in Other Season by major/medium scheme Code for Constraints in utilization of the Irrigation Potential created

Primary Key (STATECODE, DISTCODE, BLOCKCODE, VILLCODE, SNO)

2) SHALLOW TUBEWELL This table structure is used to store data of Shallow tube well Scheme. Data entry is done through the Data Entry Module. Element Name STATECODE DISTCODE BLOCKCODE VILLCODE DT_ENUM SNO NAMECODE NAME Element Type tinyint tinyint tinyint tinyint int int tinyint text
45

Element Description State Code District Code Block Code Village Code Date of Enumeration Serial Number of the Record Owners Code of the Scheme Name of the Owner

KHAS_NO Hold_SIZE CAST COM_YEAR WELL_TYPE WELL_STAT FIN_SOURCE DIST_DEVI LIFT_DEVI DEVI_HP AVG_PUMP CCA MAJ_MED KHARIF_A RABI_A PERENIAL_A OTHER_A KHARIF_B RABI_B PERENIAL_B OTHER_B KHARIF_C RABI_C PERENIAL_C OTHER_C CONSTRAINT

text tinyint tinyint tinyint tinyint tinyint tinyint tinyint tinyint double tinyint double tinyint double double double double double double double double double double double double tinyint

Khasra Number of Scheme Code for Different Holding Size Social Status Code Of Owner Commissioning Year of the Scheme Code for Different Type of Well Code for the Status of Well Source of Finance Major distribution Device Lifting Device for the Scheme Horse Power of Lifting Device Average Pumping Hours of the Device Total Cultivable Command Area Whether the Scheme is in maj/med area Gross Potential created for Kharif Season Gross Potential created for Rabi Season Gross Potential created for Perrnnial Season Gross Potential created for Other Season Area Irrigated in Kharif Season Area Irrigated in Rabi Season Area Irrigated in Perenial Season Area Irrigated in Other Season Area Irrigated in Kharif Season by major/medium scheme Area Irrigated in RabiSeason by major/medium scheme Area Irrigated in Perenial Season by major/medium scheme Area Irrigated in Other Season by major/medium scheme Code for Constraints in utilization of the Irrigation Potential created

Primary Key(STATECODE, DISTCODE, BLOCKCODE,VILLCODE, SNO)

3) DEEP TUBEWELL This table structure is used to store data of Deep tube well Scheme. Data entry is done through the Data Entry Module.

46

Element Name

Element Type

Element Description

47

STATECODE DISTCODE BLOCKCODE VILLCODE DT_ENUM SNO NAMECODE NAME KHAS_NO Hold_SIZE CAST COM_YEAR WELL_TYPE WELL_STAT FIN_SOURCE DIST_DEVI LIFT_DEVI DEVI_HP AVG_PUMP CCA MAJ_MED KHARIF_A RABI_A PERENIAL_A OTHER_A KHARIF_B RABI_B PERENIAL_B OTHER_B KHARIF_C RABI_C PERENIAL_C OTHER_C CONSTRAINT

tinyint tinyint tinyint tinyint int int tinyint text text tinyint tinyint tinyint tinyint tinyint tinyint tinyint tinyint double tinyint double tinyint double double double double double double double double double double double double tinyint

State Code District Code Block Code Village Code Date of Enumeration Serial Number of the Record Owners Code of the Scheme Name of the Owner Khasra Number of Scheme Code for Different Holding Size Social Status Code Of Owner Commissioning Year of the Scheme Code for Different Type of Well Code for the Status of Well Source of Finance Major distribution Device Lifting Device for the Scheme Horse Power of Lifting Device Average Pumping Hours of the Device Total Cultivable Command Area Whether the Scheme is in maj/med area Gross Potential created for Kharif Season Gross Potential created for Rabi Season Gross Potential created for Perrnnial Season Gross Potential created for Other Season Area Irrigated in Kharif Season Area Irrigated in Rabi Season Area Irrigated in Perenial Season Area Irrigated in Other Season Area Irrigated in Kharif Season by major/medium scheme Area Irrigated in RabiSeason by major/medium scheme Area Irrigated in Perenial Season by major/medium scheme Area Irrigated in Other Season by major/medium scheme Code for Constraints in utilization of the Irrigation Potential created

Primary Key (STATECODE, DISTCODE, BLOCKCODE,VILLCODE, SNO)

48

4) SURFACE FLOW This table structure is used to store data of Surface Flow tube well Scheme. Data entry is done through the Data Entry Module. Element Name STATECODE DISTCODE BLOCKCODE VILLCODE DT_ENUM SNO NAMECODE NAME KHAS_NO Hold_SIZE CAST COM_YEAR WELL_TYPE WELL_STAT FIN_SOURCE DIST_DEVI LIFT_DEVI DEVI_HP AVG_PUMP CCA MAJ_MED KHARIF_A RABI_A PERENIAL_A OTHER_A KHARIF_B RABI_B PERENIAL_B OTHER_B KHARIF_C Element Type tinyint tinyint tinyint tinyint int int tinyint text text tinyint tinyint tinyint tinyint tinyint tinyint tinyint tinyint double tinyint double tinyint double double double double double double double double double Element Description State Code District Code Block Code Village Code Date of Enumeration Serial Number of the Record Owners Code of the Scheme Name of the Owner Khasra Number of Scheme Code for Different Holding Size Social Status Code Of Owner Commissioning Year of the Scheme Code for Different Type of Well Code for the Status of Well Source of Finance Major distribution Device Lifting Device for the Scheme Horse Power of Lifting Device Average Pumping Hours of the Device Total Cultivable Command Area Whether the Scheme is in maj/med area Gross Potential created for Kharif Season Gross Potential created for Rabi Season Gross Potential created for Perrnnial Season Gross Potential created for Other Season Area Irrigated in Kharif Season Area Irrigated in Rabi Season Area Irrigated in Perenial Season Area Irrigated in Other Season Area Irrigated in Kharif Season by major/medium scheme
49

RABI_C PERENIAL_C OTHER_C CONSTRAINT

double double double tinyint

Area Irrigated in RabiSeason by major/medium scheme Area Irrigated in Perenial Season by major/medium scheme Area Irrigated in Other Season by major/medium scheme Code for Constraints in utilization of the Irrigation Potential created

Primary Key (STATECODE, DISTCODE, BLOCKCODE, VILLCODE, SNO)

5) SURFACE LIFT FLOW This table structure is used to store data of Surface Flow tube well Scheme. Data entry is done through the Data Entry Module. Element Name STATECODE DISTCODE BLOCKCODE VILLCODE DT_ENUM SNO NAMECODE NAME KHAS_NO Hold_SIZE CAST COM_YEAR WELL_TYPE WELL_STAT FIN_SOURCE DIST_DEVI LIFT_DEVI DEVI_HP AVG_PUMP CCA MAJ_MED KHARIF_A RABI_A Element Type tinyint tinyint tinyint tinyint int int tinyint text text tinyint tinyint tinyint tinyint tinyint tinyint tinyint tinyint double tinyint double tinyint double double
50

Element Description State Code District Code Block Code Village Code Date of Enumeration Serial Number of the Record Owners Code of the Scheme Name of the Owner Khasra Number of Scheme Code for Different Holding Size Social Status Code Of Owner Commissioning Year of the Scheme Code for Different Type of Well Code for the Status of Well Source of Finance Major distribution Device Lifting Device for the Scheme Horse Power of Lifting Device Average Pumping Hours of the Device Total Cultivable Command Area Whether the Scheme is in maj/med area Gross Potential created for Kharif Season Gross Potential created for Rabi

PERENIAL_A OTHER_A KHARIF_B RABI_B PERENIAL_B OTHER_B KHARIF_C RABI_C PERENIAL_C OTHER_C CONSTRAINT

double double double double double double double double double double tinyint

Season Gross Potential created for Perrnnial Season Gross Potential created for Other Season Area Irrigated in Kharif Season Area Irrigated in Rabi Season Area Irrigated in Perenial Season Area Irrigated in Other Season Area Irrigated in Kharif Season by major/medium scheme Area Irrigated in RabiSeason by major/medium scheme Area Irrigated in Perenial Season by major/medium scheme Area Irrigated in Other Season by major/medium scheme Code for Constraints in utilization of the Irrigation Potential created

Primary Key (STATECODE, DISTCODE, BLOCKCODE, VILLCODE, SNO)

CHAPTER - 5

51

TESTING & IMPLIMENTATION

52

5. Testing and Implementation 5.1 Testing.

Testing is the process of exercising the software with the intent of finding errors. The search for errors represents a significant challenge as web based applications reside on a network and interoperate with many different operating systems, browsers, hardware platforms and communication protocols. 5.1.1 Strategies of testing:

One of the most important level of quality assurance is system testing. Testing is the process of executing a program with the explicit intention of finding errors that are making the program to fail. A successful test is then finding errors. There are two strategies for testing software. These are code testing and Specification testing Code Testing: The code testing strategy examines the logic of the program. To follow this testing method, the analyst develops the test cases resulting in execution of every instruction in the program or modules. i.e. every path through the program is tested. Specification Testing To perform specification testing, the analyst examines the specification stating what the program is going to do and how it should perform under various conditions. Then test cases are developed for each condition or combination of conditions and submitted for processing.

53

5.1.2

Level of Testing

Regardless of which strategy the analyst follows, there are preferred practices to ensure that the testing is useful. The analyst must perform the following tests.

5.1.2.1 Unit Testing In the unit testing the analyst tests the programs making up a system. The software units in a system are the modules and routines that are assembled and integrated to perform a specific function. Unit testing first focuses on the modules, independently of one another, to locate errors. This enables the tester to detect errors in coding and logic that are contained within that module alone. 5.1.2.2 System Testing System testing does not test software but rather the integration of the modules in the system. It also tests the discrepancies between the system and its original objectives, current specifications and system documentation. 5.1.2.3 Program Testing A program testing represents the logical elements of a system. For a program to run satisfactorily, it must compile and test data correctly and lie in properly with other programs. Program testing checks for two types of errors namely: Syntax Error. Logical Errors 5.1.2.4 String Testing Programs are invariably related to one another and interact in a total system. Each program is testing to see wheather it confirms to related programs in the system. Each portion of the program is tested against the entire modules with both test and line data before the entire system is ready to be tested.
54

5.1.2.5 User Acceptance Testing An acceptance test has the objective of selling the user on the validity and reliability of the system. Performance of the acceptance test is actually the users show. Users motivation and knowledge are critical for the successful performance of the system. The authorized person of the organization, who is responsible for data entry, is familiarized with the various operation of the system Conclusion As the inputs provided by the users is a source of major errors in any system. So while developing the proposed system this point has been taken care of. In the proposed system user can give inputs by selecting values from a list of existing values, so users are not allowed to provide any unusual or unexpected values. It helps in reducing the amount of errors caused due to erroneous inputs by the user and reduces the amount of time taken for testing.

5.2 Implementation Implementation includes all those activities that take place to convert from the old system to new system. The new system may be totally new; replacing an existing manual or automated system, or it may be a major modification to an existing system. In either case proper modification is essential to provide a reliable system to meet the organization requirements. Implementing a system consists of the three primary activities of training personnel, conversion and post implementation review. Training Personnel The quality of training received by the personnel involved with the system in various capacities helps or hinders, and may even prevent the successful implementation of an information system. Those who will be associated with or affected by the system must know in detail what their rolls will be, how they can use the system and what the system will or will not do. Both system operators and users need training.

55

Conversion Conversion is a process of changing from old system to the new one. There are four methods of handling a system conversion, viz. parallel, direct cutover, pilot approach and phase-in method.

Post implementation and review After the system is implemented and the system conversion is complete, a review of the system is usually conducted by the users and analysts alike. It should be a formal process to determine how well the system is working and how it has been accepted and whether adjustments are needed.

56

CHAPTER - 6
Conclusion

57

6. Conclusion
The web Enabled Information System can improve the performance of various schemes by better monitoring of related achievements and identification of appropriate actions to account for discrepancies by providing timely, accurate, consistent and up to date information necessary for agricultural purposes. 6.1 The immediate direct benefits that can be expected are: Improved documentation of records. Better availability of complete and relevant data to the users in desired formats. Redundancy of data can be reduced. Inconsistency of data can be avoided. Integrity can be maintained. Faster and accurate traditional data processing activities such as updates and production of predefined reports. Quick response to ad-hoc queries. Improved data analysis. Reduction in administrative paper work of professionals. Reduction in tedium for repetitive manual jobs. 6.2 Limitation of the project

Since every system has some limitations so this proposed system is also not untouchable in this regard. Although it includes many kind of features but still it would require more technical manpower and more tools e.g. analytical tools could be used for further analysis of the system and GIS software could be used for the visual representation of the reports and queries in the form of maps.

58

CHAPTER 7

Annexure

59

7. 7.1

Annexure Screen Shots

1. Page for selecting various parameters for displaying State Level Irrigation Scheme Information.

Fig 7.1 State Name

60

2. Page for selecting various parameters for displaying District Level Irrigation Scheme Information.

Fig 7.2 District Name 3. Page for selecting various parameters for displaying Block Level Irrigation Scheme Information.

61

4. Page for selecting various parameters for displaying Village Level Irrigation Scheme Information.

Fig 7.4: Village Name 5. Page for selecting various parameters for displaying Dug Well Information.

Fig 7.5: Dug Well Information

62

6. Page for selecting various parameters for displaying Deep Tube Well Information.

Fig 7.6: Deep Tube Well Information

63

7. Page for selecting various parameters for displaying Shallow Tube Well Information.

Fig 7.7: Shallow Tube Well Information

64

8. Page for selecting various parameters for displaying Surface Flow Information.

Fig 7.8: Surface Flow Information 9. Page for selecting various parameters for displaying Surface Lift Information.

Fig 7.9: Surface Lift Information

65

66

References/Bibliography

67

Bibliography
Beginning ASP.NET 3.5 with C# 2005 , Wrox Publication By Chris Ullman, John Kauffman, Chris Hart, David Sussman Professional ASP.NET 3.5 By Alex Home, Dave Sussman, Rob Howard, Brian Francis, Karli Watson, Richard Anderson Mastering SQL SQRVER 2005 By Mike Gunderloy, Joseph L. Jorden Software Engineering By Pressman System Design and Analysis By E.Awad

Database System Concepts, 3rd Edition, Mc Graw-Hill, Inc. By Abraham Silberschatz, Henry F. Korth, S. Sudershan

Websites: www.godotnet.com www.4guysfromroll.com www.wikipedia.com

68

69

70