System Requirment Specifications for Online Revenue Recovery

SYSTEM REQUIRMENT SPECIFICATIONSFOR

ONLINE REVENUE RECOVERY

INTRODUCTION TO PROJECTThe main objectives of this System is

To provide software support to the revenue recovery in Mandal and Divisional level

Maintain basic citizen details: By maintaining the ration card system maintains the basic citizen information in the centralized database.

Maintain official document transaction details: The documents which are manually moved within the office is tracked and stored in DB.

Web portal: Provide web portal for interaction between citizen and government office

Using the web portal, awareness about the government office working is made know to citizens.

Make the citizens aware of the revenue from the various heads such as Library cess, stamp duty, educational cess, etc.

Information regarding acquiring certificate or ration card is also provided. Status of the document: Citizens can view the processing status of their

application form. Maintain Certificate data: Information regarding what all certificates is

acquired and their expiry dates will be maintained. Report: Reports generated on monthly quarterly, half yearly and revenue

year (Aug-July) basis.

PURPOSE OF THE PROJECT

Citizens can request online services to pay property tax, stamp duty, Educational cess, etc. Create different system users and assign different role with related permissions. Maintaining and Keeping general information of the civilians. Working is made easy for the Mandal Revenue Office in subject to validating and maintaining received documents. Tracking of Civilian information in a state level situation is made easy. Keeping track of the documents, those are submitted by the civilians. Manage all the account details such as user name, department, phone numbers, address, websites, email ID of all the users from one central location.

PROBLEM IN EXISTING SYSTEM

The existing system is a manual system. Here the User of the system needs to save his information in the form of excels sheets or Disk Drives.

There is no sharing is possible if the data is in the form of paper or Disk drives.

The manual system gives us very less security for saving data; some data may be lost due to mismanagement.

It’s a limited system and fewer users friendly.

Searching of particular information is very critical it takes lot of time.

The users only know his information only not others.

It is very critical to share public information to all users.

SOLUTION OF THESE PROBLEMS

• Reliability: The project performs intended function with required

precision; hence this project is very reliable.

• Feasibility: The project maintenance is very easy and modifications

can be made in the existing system in future. All data will locate as

centralized.

• Online Processing: The online processing of the project is very

simple following the existing manual method without changes and

suitable validation is provided for the easy and correct access of

users.

• Security: Security measures are taken to avoid mishandling of

database. Password restrictions are provided to enter into database.

A correct password only will access to the database

PROPOSED SYSTEM

The development of this Online Revenue Recovery contains the following

activities, which try to automate the entire process keeping in the view of database

integration approach.

User Friendliness is provided in the application with various controls provided by system Rich User Interface. Online Revenue Recovery makes the overall project management much easier and flexible. It can be accessed over the Intranet.

Various classes have been used for file uploading and down loading. The user information files can be stored in centralized database which can be maintained by the system.

Online Revenue Recovery can give the good security for user information because data is not in client machine. Authentication is provided for this application only registered users can access. User can share is data to others, and also he can get data from others.

FUNCIONAL REQUIREMENTS

1. Maintaining and Keeping general information of the civilians.2. Working is made easy for the Mandal Revenue Office in subject to validating

and maintaining received documents.3. Tracking of Civilian information in a state level situation is made easy.4. Keeping track of the documents, those are submitted by the civilians.5. Citizens can request online services to pay property tax, stamp duty,

Educational cess, etc.6. Create different system users and assign different role with related

permissions.7. Manage all the account details such as user name, department, phone

numbers, address, websites, email ID of all the users from one central location.

PERFORMANCE REQUIREMENTS

Performance is measured in terms of the output provided by the application.

Requirement specification plays an important part in the analysis

of a system. Only when the requirement specifications are properly

given, it is possible to design a system, which will fit into required

environment. It rests largely in the part of the users of the existing

system to give the requirement specifications because they are the

people who finally use the system. This is because the requirements

have to be known during the initial stages so that the system can be

designed according to those requirements. It is very difficult to change

the system once it has been designed and on the other hand designing

a system, which does not cater to the requirements of the user, is of

no use.

The requirement specification for any system can be broadly stated as

given below:

The system should be able to interface with the existing system

The system should be accurate

The system should be better than the existing system

The existing system is completely dependent on the user to perform all

the duties.

NO. OF MODULES

Public User

Revenue Administrator (Officer)

Employees

Citizen (People)

Web Registration

Search

Authentication

Reports

MODULES DESCRIPTION

1. REVENUEADMINISTRATOR: Revenue Administrator is owner of this site .He/She Can view the existing Division details.Admin can add new division Details to this site. He/She can view detail of divisions at once or can see details of individual division and update those details if required.

Admin can view the existing Mandal details by selected Division wise. Admin can add new Manadal details to the site. Can view individual Mandal details and will update if it required any modifications.

Citizen’s applications first come to Mandal Level Manager. If Mandal Manager approve that application then it will come to Revenue Administrator. At the same time Revenue admin will get the ration card details of that Applicant, then he will approve/reject the application. Once application is rejected that applicant can’t login into this site.

Revenue administrator has rights to register new employees into this site. He will take all the details like name, last-named, phone no, address of new Employee and register them into the site. The Employees who got registration they can only login into the site.

Revenue administrator can see the Revenue Report of different Mandals between selected dates. She/he can see the Revenue report of Mandals of different Tax type like Education, Professional, Entertainment, Income, Property Taxes.

Revenue administrator can send or receive messages from Employee, Citizens who registered in the site.

2. Employees:

Employees are Mandal level Managers. They will get the ration card details of citizens in his Mandal enter those card details to the site. Manager and admin get those ration card details depends upon those card Numbers

Citizens applications first come to Mandal level manager if she/he verify those then they will send to Revenue administrator ,After Revenue Administrator approve those then again those applications come back to Mandal Manger finally She/he will approve or reject those applications.

Employees can view their profiles. If required they will update details like phone no, address, Age, Emailed etc.

Mandal Mangers can see the Revenue Report of their Mandal between selected dates. She/he can see the Revenue report of different Tax type like Education, Professional, Entertainment, Income, Property Taxes.

Mandal Manager can send or receive messages from Employee, Citizens who registered in the site.

3. Citizens:

Citizens who visit the site can know about this site. If they want they will get registration by giving the details like name, address, phone no, mandal, division, income, ratincard no etc.But this applications must approve by Revenue Administrator and Mandal manager then only citizens will login.

The citizens who have sent registration applications they can check their application status by using application No, Which generates when enter the registration details.

The citizens whose application is approved by both Revenue Administrator and Mandal level manger those can login into the site with their username and password.

Once Citizen Login she/he can pay different type of taxes like property tax, education tax, Professional tax, Entertainment tax directly in online.

4. Web Registration:

Both citizens and Employee must got registration with their details like name, last name, phone, address etc.

5. Search:

In these search module citizens who have sent registration application check their application status .once the application is approved then only they can login.

6. Reports:

In this module both admin and Mandal Mangers get the Revenue report between selected dates of different tax types like education, entertainment, income tax etc.

7. Authentication:

Authentications process of granting or denying access to a Web based Application. It is the process of determining whether someone or something is, in fact, who or what it is declared to be. Authentication is commonly done through the use of credentials i.e. user name and passwords

NO. OF USERS

1. Revenue Administrator2. Employee3. Citizen4. Visitor

INPUT & OUTPUT

The following some are the projects inputs and outputs.

Inputs:

Admin enters credentials.

Admin enters Employee information like name, last name, and generates User ID, Password to the

Employee.

Admin sends a Mail of Employee credentials.

Admin fills Division details

Admin fills Mandal details

Admin registers Employee details.

Admin approve/reject the citizen applications.

Mandal Manager enters credentials.

Mandal Manger adds Ration Card details

Mandal Manager approve the applications form citizens.

Mandal Manager can send or receive mails from those who registered in the site.

Citizens enter credentials.

Citizens will enter their detail while registration.

Citizens Login to the system.

Citizens enter tax details while paying tax.

Outputs:

Admin will get his home page.

Registration details will be stored in centralized database.

Admin can add Employee, Division, Mondal details

Admin can generate Reports.

Mandal Manager can add Field Officer details.

Citizen can see the Status of the Verification.

Citizens can send mail to admin and Revenue Manager.

Employee, citizen details will be stored in centralized database.

SDLC METHDOLOGIES

This document play a vital role in the development of life cycle (SDLC) as it describes the complete requirement of the system. It means for use by developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.

SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.

As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.

The steps for Spiral Model can be generalized as follows:

The new system requirements are defined in as much details as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.

A preliminary design is created for the new system.

A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.

A second prototype is evolved by a fourfold procedure:

1. Evaluating the first prototype in terms of its strengths, weakness, and risks.

2. Defining the requirements of the second prototype.

3. Planning an designing the second prototype.

4. Constructing and testing the second prototype.

At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involve development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer’s judgment, result in a less-than-satisfactory final product.

The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above.

The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.

The final system is constructed, based on the refined prototype.

The final system is thoroughly evaluated and tested. Routine maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time.

The following diagram shows how a spiral model acts like:

Fig 1.0-Spiral Model

ADVANTAGES:

Estimates(i.e. budget, schedule etc .) become more relistic as work progresses, because important issues discoved earlier.

It is more able to cope with the changes that are software development generally entails.

Software engineers can get their hands in and start woring on the core of a project earlier.

INPUT DESIGN

Input design is a part of overall system design. The main objective during the input design as given below:

To produce cost-effective method of input

To achieve the highest possible level of accuracy.

To ensure that the input is acceptable and understood by the user.

Input States:

The main input stages can be listed as below:

Data recording

Data transcription

Data conversion

Data verification

Data control

Data transmission

Data validation

Data correction

Input Types:

It is necessary to determine the various types of input. Inputs can be categorized as follows:

External Inputs which are prime inputs for the system.

Internal Inputs, which are user communications with the systems.

Operational, which are computer department’s communications to the system?

Interactive, which are inputs entered during a dialogue.

Input Media:

At this stage choice has to be made about the input media. To conclude about the input media consideration has to be given to:

Type of Input

Flexibility of Format

Speed

Accuracy

Verification methods

Rejection rates

Ease of correction

Storage and handling requirements

Security

Easy to use

Portability

Keeping in view the above description of the input types and input media, it can be said that most of the inputs are of the form of internal and interactive. As input data is to be directly keyed in by the user, the keyboard can be considered to be the most suitable input device.

OUTPUT DESIGN:

Outputs from computer systems are required primarily to communicate the results of

processing to users. They are also used to provide a permanent copy of the results for later

consultation. The various types of outputs in general are:

External Outputs, whose destination is outside the organization,.

Internal Outputs whose destination is within organization and they are the

User’s main interface with the computer.

Operational outputs whose use is purely within the computer department.

Interface outputs, which involve the user in communicating directly with User

Interface.

Output Definition:

The outputs should be defined in terms of the following points:

Type of the output

Content of the output

Format of the output

Location of the output

Frequency of the output

Volume of the output

Sequence of the output

It is not always desirable to print or display data as it is held on a computer. It should be

decided as which form of the output is the most suitable.

For Example

Will decimal points need to be inserted

Should leading zeros be suppressed.

Output Media:

In the next stage it is to be decided that which medium is the most appropriate for the

output. The main considerations when deciding about the output media are:

The suitability for the device to the particular application.

The need for a hard copy.

The response time required.

The location of the users

The software and hardware available.

Keeping in view the above description the project is to have outputs mainly coming

under the category of internal outputs. The main outputs desired according to the

requirement specification are: The outputs were needed to be generated as a hot copy

and as well as queries to be viewed on the screen. Keeping in view these outputs, the

format for the output is taken from the outputs, which are currently being obtained after

manual processing. The standard printer is to be used as output media for hard copies.

SYSTEM ARCHITECTURE

N-Tier Applications:

N-Tier Applications can easily implement the concepts of Distributed Application Design and Architecture. The N-Tier Applications provide strategic benefits to Enterprise Solutions. While 2-tier, client-server can help us create quick and easy solutions and may be used for Rapid Prototyping, they can easily become a maintenance and security night mare

The N-tier Applications provide specific advantages that are vital to the business continuity of the enterprise. Typical features of a real life n-tier may include the following:

Security

Availability and Scalability

Manageability

Easy Maintenance

Data Abstraction

The above mentioned points are some of the key design goals of a successful n-tier application that intends to provide a good Business Solution.

Definition:

Simply stated, an n-tier application helps us distribute the overall functionality into various tiers or layers:

Presentation Layer

Business Rules Layer

Data Access Layer

Database/Data Store

Each layer can be developed independently of the other provided that it adheres to the standards and communicates with the other layers as per the specifications.

This is the one of the biggest advantages of the n-tier application. Each layer can potentially treat the other layer as a ‘Block-Box’.

In other words, each layer does not care how other layer processes the data as long as it sends the right data in a correct format.

Fig 1.1-N-Tier Architecture

1. The Presentation Layer:

Also called as the client layer comprises of components that are dedicated to presenting the data to the user. For example: Windows/Web Forms and buttons, edit boxes, Text boxes, labels, grids, etc.

2. The Business Rules Layer:

This layer encapsulates the Business rules or the business logic of the encapsulations. To have a separate layer for business logic is of a great advantage. This is because any changes in Business Rules can be easily handled in this layer. As long as the interface between the layers remains the same, any changes to the functionality/processing logic in this layer can be made without impacting the others. A lot of client-server apps failed to implement successfully as changing the business logic was a painful process.

3. The Data Access Layer:

This layer comprises of components that help in accessing the Database. If used in the right way, this layer provides a level of abstraction for the database structures. Simply put changes made to the database, tables, etc do not affect the rest of the application because of the Data Access layer. The different application layers send the data requests to this layer and receive the response from this layer.

4. The Database Layer:

This layer comprises of the Database Components such as DB Files, Tables, Views, etc. The Actual database could be created using SQL Server, Oracle, Flat files, etc. In an n-tier application, the entire application can be implemented in such a way that it is independent of the actual Database. For instance, you could change the Database Location

with minimal changes to Data Access Layer. The rest of the Application should remain unaffected

CONTEXT LEVEL DFD

FEASIBILITY STUDYPreliminary investigation examine project feasibility, the

likelihood the system will be useful to the organization. The main

objective of the feasibility study is to test the Technical, Operational

and Economical feasibility for adding new modules and debugging old

running system. All system is feasible if they are unlimited resources

and infinite time. There are aspects in the feasibility study portion of

the preliminary investigation:

TECHNICAL FEASIBILITY

In the feasibility study first step is that the organization or company

has to decide that what technologies are suitable to develop by

considering existing system.

Here in this application used the technologies like Visual Studio 2008

and SQL Server 2005. These are free software that would be

downloaded from web.

Visual Studio 2008 –it is tool or technology.

OPERATIONAL FEASIBILITY

Not only must an application make economic and technical sense, it

must also make operational sense.

Issues to consider when determining the operational feasibility of a project.

Operations Issues

Support Issues

What tools are needed to support operations?

What skills will operators need to be trained in?

What processes need to be created and/or updated?

What documentation do operations

What documentation will users be given?

What training will users be given?

How will change requests be managed?

need?

Very often you will need to improve the existing operations,

maintenance, and support infrastructure to support the operation of

the new application that you intend to develop. To determine what the

impact will be you will need to understand both the current operations

and support infrastructure of your organization and the operations and

support characteristics of your new application.

To operate this application BG Verification system that the user

no needs to require any technical knowledge that we are used to

develop this project is. Asp.net, C#.net. that the application providing

rich user interface by user can do the operation in flexible manner.

ECONOMIC FEASIBILITYIt refers to the benefits or Outcomes we are deriving from the product

as compared to the total cost we are spending for developing the

product. If the benefits are more or less the same as the older system,

then it is not feasible to develop the product.

In the present system, the development of new product

greatly enhances the accuracy

of the system and cuts short the delay in the processing BG

Verification application. The errors can be greatly reduced and at

the same time providing a great level of security. Here we don’t

need any additional equipment except memory of required capacity.

No need for spending money on client for maintenance

because the database used is web enabled database.

Class Diagram for Online Revenue Recovery:

Context Level Diagram:

Login DFD:

Admin Activities DFDs:

1st Level

Admin Activity DFD:

2nd level:

Employee (Mandal Manger) activities DFD:

Level1:

Employee DFD

2nd Level:

Citizen Activity DFD:

1st level:

Citizen Activity DFD:

2nd Level:

s

tbl_CitizenDetailsUserId

UserName

PassWord

Name

LastName

CitizenTypeId

PhoneNo

Address

profession

Photo

CardNo

MondalId

DivisionId

EmailId

HintQuestion

Answer

MondalStatus

DivisionStatustbl_CitizenType

CitizenId

CitizenType

tbl_DivisionDetailsDivisionId

DivisionName

tbl_EmpDetailsEmpId

UserName

password

Name

LastName

age

PhoneNo

EmailId

Address

MondalId

DivisionId

Role

Salary

JoinDate

HintQuestion

Answer

tbl_IncomeDetailsReciptId

UserId

TotalAmount

Category

PayDate

CheckNo

CardNo

MondalId

DivisionId

tbl_IncomeTaxDetailsTaxId

IncomeRange

TaxAmount

CitizenId

tbl_MondalMondalId

MondalName

DivisionId

tbl_OrganizationsOrganizationId

OrganizationName

RegistrationNo

AnnulaIncome

PhoneNo

EmailId

Website

MondalId

DivisionId

tbl_RationCardDetailsCardNo

CardholderName

NoOfPersons

AnnualIncome

Address

MondalId

DivisionId

ABSTRACT

Project Title: Online Revenue Recovery

Domain: Finance

Category: Application Development, Enterprise

Objective:

The main objectives of this System is

To provide software support to the revenue recovery in Mandal and Divisional level

Maintain basic citizen details: By maintaining the ration card system maintains the basic citizen information in the centralized database.

Maintain official document transaction details: The documents which are manually moved within the office is tracked and stored in DB.

Web portal: Provide web portal for interaction between citizen and government office

Using the web portal, awareness about the government office working is made know to citizens.

Make the citizens aware of the revenue from the various heads such as Library cess, stamp duty, educational cess, etc.

Information regarding acquiring certificate or ration card is also provided. Status of the document: Citizens can view the processing status of their

application form. Maintain Certificate data: Information regarding what all certificates is

acquired and their expiry dates will be maintained. Report: Reports generated on monthly quarterly, half yearly and revenue

year (Aug-Jly) basis.

Functional requirements

1. Maintaining and Keeping general information of the civilians.2. Working is made easy for the Mandal Revenue Office in subject to validating

and maintaining received documents.3. Tracking of Civilian information in a state level situation is made easy.4. Keeping track of the documents, those are submitted by the civilians.5. Citizens can request online services to pay property tax, stamp duty,

Educational cess, etc.

6. Create different system users and assign different role with related permissions.

7. Manage all the account details such as user name, department, phone numbers, address, websites, email ID of all the users from one central location.

Non-functional requirements

i. Secure access of confidential data (user’s details) should be provided.ii. 24 X 7 availability of the applicationiii. Application should be accessible over Internet.iv. Better component design to get better performance at peak timev. Flexible service based architecture will be highly desirable for future

extension.Out of scope

1. Providing Communication between Citizen’s and Employees through Email and chat.

2. Not to implement the complete functionalities for a revenue department because it’s a tedious job.

No. of Modules

1. Public User

Revenue Administrator(Officer)

2. Employees

3. Citizen (People)

4. Web Registration

5. Search

6. Authentication

7. Reports

No. of Users

5. Revenue Administrator6. Employee7. Citizen8. Visitor

KEYWORDS:

Generic Technology Keywords: Database, User Interface, Programming

Specific Technology Keywords: Asp.Net 3.5, C#.Net, MS SqlServer-05

Project Keywords: Presentation, Business Object, Data Access Layer

SDLC Keywords: Analysis, Design, Implementation, Testing

ENVIRONMENT:

Servers:

Operating System Server: Windows XP

Database Server: Microsoft SQL Server-2005

Client: Microsoft Internet Explorer

Tools: Microsoft Visual Studio .Net-2008 (Framework 3.5)

User Interface: Asp.Net with Ajax

Code Behind: VC#.Net

Hardware Specification:

Processor: Intel Pentium or More

RAM: 512 MB Ram

Hard Disk: PC with 20GB

Collaboration Diagram for Login:

Collaboration Diagram For Registration:

Collaboration Diagram for Admin adding Division:

User

Login.aspx

BAL(ClsRegistrationDetails)

DAL(SqlHelper.cs)

Database

Home

1 : Enter login details()

2 : Invalid Input()

3 : Check Login()

4 : ExecuteNonQuery()

5 : ExecuteProcedure()

6 : GetResponseFormDB()

7 : GetResponseFromBAL()

8 : Display Message()

9 : IfValidGetHomePage()

Admin

FormRegistration.aspx

BAL(ClsRegistration)

DAL(SqlHelper.cs)

DataBase

1 : OpenRegistrationPage()

2 : Invalid Input()

3 : CitixenRegister()

4 : ExecuteScalar()


6 : GetResponseFormDB()

7 : GetResponseFromBAL()

8 : DisplayMessage()

Admin

FormDivisionDetails.aspx

BAL(ClsRegistration)

DAL(SqlHelper.cs)

DataBase

1 : FormDivisionDetails.aspx()

2 : Invalid Input()

3 : InsertUpdateDivision()

4 : ExecuteNonQuery()


6 : GetResponseFormDB()7 : GetResponseFromBAL()

8 : DisplayMessage()

Collaboration Diagram for Revenue Report:

Activity Diagram For Login:

Admin

FormRevenueReport.aspx

BAL(ClsTaxDetails)

DAL(SqlHelper.cs)

Database1 : enter the details of tax type()

2 : Invalid Input()

3: GetTaxDetailByAdmin () 4 : Execute Dataset()


6: GetResponseFormDB ()7 : GetResponseFromBAL()

8 : Display Data()

Activity diagram for Registration:

Get LoginDetails

enter Login Details

Submit details

AcceptReject

submit data

validate data

yes

No

wrong username and passwrod

Show Home Page

Get Details

Validate Details

Valid DataReject

Validate Details

Enter Required Details

yes

No

Enter Details are Wrong

Successfully Registered

ActivityDiagram For Admin:

Get LoginDetails

enter Login Details

Submit details

Reject

submit data

validate data

No


Division Details Mondal Details Register Employees Revenue Report Mails Citizen Request

Successfully Signout

Activity Diagram For MondalManager:

Get LoginDetails

enter Login Details

Submit details

Reject

submit data

validate data

No


Change Password Ration Details Update Profile Revenue Report Mails Citizen Request


Activity Diagram For Citizen:

Get LoginDetails

enter Login Details

Submit details

Reject

submit data

validate data

No


Change Password Profession Tax Education Tax Income Tax Property Tax Entertinement Tax


Mails

Screen shot

HOME

<%@ Page Language="C#" MasterPageFile="~/MainMasterPage.master" AutoEventWireup="true" CodeFile="FormHome.aspx.cs" Inherits="FormHome" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server"> <style type="text/css"> .style20 { width: 100%; } .style21 { width: 258px; } .style22 { width: 447px; }</style></asp:Content><asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">

 <table class="style20"> <tr> <td class="style21"> <asp:Image ID="Image2" runat="server" ImageUrl="~/Images/renue build.jpg" Width="275px" /> </td> <td class="style22"> During the British times the Revenue Department was the pivot of Administration. The Board of Revenue that wielded extraordinary powers administered it. The Collector was the virtual monarch at the District. </td> <td> </td> </tr> <tr> <td class="style21"> </td> <td class="style22"> </td> <td> </td> </tr></table></asp:Content>

Contact Us:

<%@ Page Language="C#" MasterPageFile="~/MainMasterPage.master" AutoEventWireup="true" CodeFile="FormContactUs.aspx.cs" Inherits="FormContactUs" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server"> <style type="text/css"> .style20 { width: 100%; } .style21 { width: 304px; }

.style22 { width: 164px; text-align: right; } .style23 { width: 164px; text-align: right; font-weight: normal; }</style></asp:Content><asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <table class="style20"> <tr> <td class="style21"> <asp:Image ID="Image2" runat="server" Height="214px" ImageUrl="~/Images/images[5].jpg" Width="309px" /> </td> <td> <asp:Panel ID="Panel1" runat="server" Font-Bold="True" GroupingText="Contact Us" Height="195px" style="color: #003366"> <table class="style20"> <tr> <td class="style23"> Email Id:</td> <td> [email protected]</td> </tr> <tr> <td class="style23"> Phone No:</td> <td> 9999999999</td> </tr> <tr> <td class="style23"> Fax:</td> <td> 2357989</td> </tr> <tr> <td class="style22"> </td> <td> </td> </tr> </table> </asp:Panel> </td> </tr> <tr> <td class="style21"> </td>

<td> </td> </tr></table></asp:Content>

About Us:

<%@ Page Language="C#" MasterPageFile="~/MainMasterPage.master" AutoEventWireup="true" CodeFile="FormAboutUs.aspx.cs" Inherits="FormAboutUs" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server"> <style type="text/css"> .MsoBodyTextIndent { width: 739px; } </style></asp:Content><asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <a name="2"></a> ANDHRA BOARD OF REVENUE: With the formation of separate Andhra State the Andhra Board of Revenue was formed in 1953. It was a replica of Madras board. But it has only 2 members where as Madras Board has 5 members drawn from ICS. It was the link between the Government and the Districts. The first member was senior even to the then Chief Secretary to Government. <a name="3"></a> TELANGANA BOARD OF REVENUE:nbsp; The Prime Minister of Hyderabad, Sir Salar Jung, constituted a board of revenue for the first time in 1864.In 1885 it was abolished and Inspector General at State Level was appointed. In 1893, the assistant Minister of revenue, Vkar-ul-Umra, was appointed as the Prime Minister and to fill this gap a Revenue Board was created for the third time. It was abolished in 1901 and the post of Revenue Secretary was revived. He was also designated as Director General of Revenue in 1928. Thus the Secretariat and executive functions were combined. This arrangement continued till 1945 when the Board of Revenue was created for the fourth time purely as an appellate body. Its life ended by 1949.Meanwhile Hyderabad merged with the Union of India.<o:p></o:p> Then for the fifth time the board of Revenue in erstwhile State of Hyderabad was established under a Regulation issued in 1949. (Regulation LX of

1358 Fasli). The Hyderabad board as it existed in 1956 was by and large modeled on Madras pattern. However it had four members who were Secretaries to Government whereas in Madras they were seniors to Secretaries though next to Chief Secretary. The Senior Member of the Telangana Board functioned also as the Development Commissioner and was designated as ex officio Secretary to Government.<o:p></o:p> <a name="4"></a> THE BOARD OF REVENUE IN ANDHRA PRADESH: The integrated Board of Andhra Pradesh, constituted on Madras pattern enjoyed some of the powers of Hyderabad Board also. It administered through the Board Standing Orders that form the basis of administration even till today. It consisted of five members. In 1957 National savings Scheme was put under its charge. It lost its control over minor irrigation in 1962 and Endowments in 1964.The Panchayat Raj was withdrawn in 1970. But Tribal Welfare and PWD were added under its control as a coordinating agency.<o:p></o:p> Gradually the Board lost its position as the highest Revenue Court. In some matters Board Standing orders were altered by statutory amendments. Again Special Secretaries to Government were created in1961 and Board lost its distinction as the only administrative body with senior most officers though Chief Secretaries were drawn from the Board Members.<o:p></o:p> In the Revenue Department, Commissioner of Revenue assisted the Board of Revenue in its functioning. Secretary, Board’s Land revenue and irrigation Branch, in turn assisted the Commissioner. At the District Level District Collectors, District Revenue Officers performed the revenue and administrative functions. Revenue Divisional Officers and Sub Collectors at the Sub-Divisional Level, Tahsildars and Deputy Tahsildars at the Tahsil Level, Revenue Inspectors and Girdwars at the Firka/ Circle Level, and Village Officers and Village Servants at the Village Level assisted the Collector.<o:p></o:p> <a name="5"></a>COMMISSIONERS ACT 1977: The Board of Revenue was abolished by the <a href="http://apland.ap.nic.in/cclaweb/scan%20acts/1977commissioner.htm" target="_blank">A .P. Board of Revenue Replacement by Commissioners Act, 1977</a>.As per this new Act Commissioners were appointed in place of Members. The Commissioner of Land Revenue, Commissioner of Survey and Settlement, commissioner of Excise, Commissioner of Commercial Taxes and Commissioner Land Reforms and Urban Land Ceiling exercised the powers of Members. <a name="6"></a>THE PRESENT SET UP: In 1999 the posts of Commissioners, Survey Settlement & Land Records and Land reforms & Urban land Ceiling were abolished. The post of Commissioner of Land Revenue was re designated as Chief

Commissioner of Land Administration. Commissioner Appeals in a Cadre post of I.A.S and Commissioner Legal affairs in the cadre of District and Sessions judge were also created to assist the Chief Commissioner of </asp:Content>

Admin Login:

<%@ Page Language="C#" MasterPageFile="~/MainMasterPage.master" AutoEventWireup="true" CodeFile="Login.aspx.cs" Inherits="Login" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server"> <style type="text/css"> .style32 { width: 100%; color: #CCFFCC; height: 225px; } .style35 { height: 21px; font-size: x-large; } .style41 {

text-align: left; height: 27px; } .style42 { width: 235px; height: 28px; } .style43 { text-align: left; height: 28px; } .style47 { height: 289px; } .style49 { width: 235px; height: 27px; color: #000066; font-weight: bold; font-size: medium; text-align: right; } </style></asp:Content><asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"> <table align="center" class="style32"> <tr> <td align="center" class="style47"> <asp:Panel ID="Panel1" runat="server" GroupingText="Login" Width="501px" ForeColor="#CC0000" Height="250px" BackColor="#CCCCFF" style="font-size: large; color: #000066; background-color: #DAC57A"> <table class="style32" bgcolor="#CCCCFF" style="background-color: #DAC57A"> <tr> <td class="style35" colspan="2"> <asp:Label ID="Lbllogin" runat="server" style="color: #003366; font-size: x-large; " Text="Label"></asp:Label> </td> </tr> <tr> <td class="style35" colspan="2"> </td> </tr> <tr> <td class="style49">

<asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server" ControlToValidate="Txt_UName" ErrorMessage="*"></asp:RequiredFieldValidator> UserName:</td> <td class="style41"> <asp:TextBox ID="Txt_UName" runat="server"></asp:TextBox> </td> </tr> <tr> <td class="style49"> <asp:RequiredFieldValidator ID="RequiredFieldValidator2" runat="server" ControlToValidate="Txt_PassWord" ErrorMessage="*"></asp:RequiredFieldValidator> Pass Word:</td> <td class="style41"> <asp:TextBox ID="Txt_PassWord" runat="server" TextMode="Password"></asp:TextBox> </td> </tr> <tr> <td class="style42"> </td> <td class="style43"> <asp:CheckBox ID="CheckBox1" runat="server" Text="Remember Me" style="color: #003366; font-size: medium;" /> </td> </tr> <tr> <td class="style42"> </td> <td class="style43"> <asp:Button ID="But_Login" runat="server" Height="29px" Text="Login" Width="77px" onclick="But_Login_Click" style="font-weight: 700" /> <asp:LinkButton ID="LinkButton1" runat="server" ValidationGroup="forget" onclick="LinkButton1_Click" Visible="False" style="font-size: medium">Forget PassWord</asp:LinkButton> </td> </tr> <tr> <td class="style42"> </td> <td class="style43"> <asp:HyperLink ID="HyperLink2" runat="server" Font-Underline="True" style="color: #CC0000; font-size: medium;" Visible="False" NavigateUrl="~/FormRegister.aspx">New User Register Here</asp:HyperLink> </td>

</tr> <tr> <td colspan="2"> <asp:Label ID="Label1" runat="server" Text="Label" Visible="False" ForeColor="#CC0000" style="font-size: medium"></asp:Label> </td> </tr> </table> </asp:Panel> </td> </tr> <tr> <td> </td> </tr> </table> </asp:Content>

Employee Login:

Citizen Login Page:

System

Admin

Citizen

MondalManager

Register

MondalDetails

Login

DistrictDetails

Reports

RationCardDetails

Taxt Payment

SignOut

Communication

System

Admin

Register

MondalDetails

Login

DistrictDetails

Reports

RationCardDetails

SignOut

Communication

Register Employees

9.1. INTRODUCTION

The protection of computer based resources that includes hardware, software, data,

procedures and people against unauthorized use or natural

Disaster is known as System Security.

System Security can be divided into four related issues:

Security

Integrity

Privacy

Confidentiality

SYSTEM SECURITY refers to the technical innovations and procedures applied to the

hardware and operation systems to protect against deliberate or accidental damage from a

defined threat.

DATA SECURITY is the protection of data from loss, disclosure, modification and

destruction.

SYSTEM INTEGRITY refers to the power functioning of hardware and programs,

appropriate physical security and safety against external threats such as eavesdropping and

wiretapping.

PRIVACY defines the rights of the user or organizations to determine what information they

are willing to share with or accept from others and how the organization can be protected

against unwelcome, unfair or excessive dissemination of information about it.

CONFIDENTIALITY is a special status given to sensitive information in a database to

minimize the possible invasion of privacy. It is an attribute of information that characterizes

its need for protection.

9.2. SECURITY IN SOFTWARE

System security refers to various validations on data in form of checks and controls

to avoid the system from failing. It is always important to ensure that only valid data is

entered and only valid operations are performed on the system. The system employees two

types of checks and controls:

CLIENT SIDE VALIDATION

Various client side validations are used to ensure on the client side that only valid

data is entered. Client side validation saves server time and load to handle invalid data.

Some checks imposed are:

JavaScript in used to ensure those required fields are filled with suitable data only.

Maximum lengths of the fields of the forms are appropriately defined.

Forms cannot be submitted without filling up the mandatory data so that manual

mistakes of submitting empty fields that are mandatory can be sorted out at the client

side to save the server time and load.

Tab-indexes are set according to the need and taking into account the ease of user while

working with the system.

SERVER SIDE VALIDATION

Some checks cannot be applied at client side. Server side checks are necessary to save the

system from failing and intimating the user that some invalid operation has been performed

or the performed operation is restricted. Some of the server side checks imposed is:

Server side constraint has been imposed to check for the validity of primary key and

foreign key. A primary key value cannot be duplicated. Any attempt to duplicate the

primary value results into a message intimating the user about those values through the

forms using foreign key can be updated only of the existing foreign key values.

User is intimating through appropriate messages about the successful operations or

exceptions occurring at server side.

Various Access Control Mechanisms have been built so that one user may not agitate

upon another. Access permissions to various types of users are controlled according to

the organizational structure. Only permitted users can log on to the system and can have

access according to their category. User- name, passwords and permissions are

controlled o the server side.

Using server side validation, constraints on several restricted operations are imposed.

Conclusion

It has been a great pleasure for me to work on this exciting and challenging project.

This project proved good for me as it provided practical knowledge of not only programming

in ASP.NET and C#.NET web based application and no some extent Windows Application and

SQL Server, but also about all handling procedure related with “Online Revenue

Recovery”. It also provides knowledge about the latest technology used in developing web

enabled application and client server technology that will be great demand in future. This

will provide better opportunities and guidance in future in developing projects

independently.

BENEFITS:

The project is identified by the merits of the system offered to the user. The merits of this

project are as follows: -

It’s a web-enabled project.

This project offers user to enter the data through simple and interactive forms. This is

very helpful for the client to enter the desired information through so much simplicity.

The user is mainly more concerned about the validity of the data, whatever he is

entering. There are checks on every stages of any new creation, data entry or updation

so that the user cannot enter the invalid data, which can create problems at later date.

Sometimes the user finds in the later stages of using project that he needs to update

some of the information that he entered earlier. There are options for him by which he

can update the records. Moreover there is restriction for his that he cannot change the

primary data field. This keeps the validity of the data to longer extent.

User is provided the option of monitoring the records he entered earlier. He can see the

desired records with the variety of options provided by him.

From every part of the project the user is provided with the links through framing so that

he can go from one option of the project to other as per the requirement. This is bound

to be simple and very friendly as per the user is concerned. That is, we can sat that the

project is user friendly which is one of the primary concerns of any good project.

Data storage and retrieval will become faster and easier to maintain because data is

stored in a systematic manner and in a single database.

Decision making process would be greatly enhanced because of faster processing of

information since data collection from information available on computer takes much

less time then manual system.

Allocating of sample results becomes much faster because at a time the user can see the

records of last years.

Easier and faster data transfer through latest technology associated with the computer

and communication.

Through these features it will increase the efficiency, accuracy and transparency,

LIMITATIONS:

The size of the database increases day-by-day, increasing the load on the database back

up and data maintenance activity.

Training for simple computer operations is necessary for the users working on the

system.

This System being web-based and an undertaking of Cyber Security Division, needs to be

thoroughly tested to find out any security gaps.

A console for the data centre may be made available to allow the personnel to

monitor on the sites which were cleared for hosting during a particular period.

Moreover, it is just a beginning; further the system may be utilized in various

othertypes of auditing operation viz. Network auditing or similar process/workflow

based applications...

Bibliography

FOR .NET INSTALLATION

www.support.mircosoft.com

FOR DEPLOYMENT AND PACKING ON SERVER

http://www.support.mircosoft.com/

www.developer.com

www.15seconds.com

FOR SQL

www.msdn.microsoft.com

FOR ASP.NET

www.msdn.microsoft.com/net/quickstart/aspplus/default.com

www.asp.net

www.fmexpense.com/quickstart/aspplus/default.com

www.asptoday.com

www.aspfree.com

www.4guysfromrolla.com/index.aspx

System Analysis and Design

Senn

Database System Design

Elmasree

Korth

Software Engineering Concepts

Robert Pressman

http://www.4guysfromrolla.com/index.aspx

http://www.aspfree.com/

http://www.asptoday.com/

http://www.fmexpense.com/quickstart/aspplus/default.com

http://www.asp.net/

http://www.msdn.microsoft.com/net/quickstart/aspplus/default.com

http://www.msdn.microsoft.com/

http://www.15seconds.com/

http://www.developer.com/

Documents

System Requirment Specifications for Online Revenue Recovery