System Requirment Specifications For Online Revenue Recovery
Content
SYSTEM REQUIRMENT SPECIFICATIONS FOR ONLINE REVENUE RECOVERY
INTRODUCTION TO PROJECT The main objectives of this System is •
•
•
•
•
•
• •
•
•
To provide software support to the revenue recovery in Mandal and Divisional level Maintain basic citizen details: 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 vali va lida dati ting ng and and main mainta tain inin ing g rece receiv ived ed docu docume ment nts. s. Trac Tracki king ng of Ci Civi vili lian an 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 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 •
Reliab Rel iabili ility: ty: The pro projec jectt per perfor forms ms int intend ended ed fun functi ction on wi with th requ require ired d precision; hence this project is very reliable. r eliable.
•
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.
•
Secu Se curi rity ty:: Se Secu curi rity ty me meas asur ures es are take taken n to avo avoid id mi mish shan andl dlin ing g 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 Maintaining and and Keeping Keeping general general informati information on of the civilian civilians. s. 2. Working Working is made easy for for the Mand Mandal al Revenue Office Office in subject subject to validatin validating g and maintaining received documents. 3. Tracking Tracking of Civilian Civilian information information in a state state level situation situation is made easy. easy. 4. Keeping Keeping track of the the documents, documents, those are are submitted submitted by the civilians. civilians. 5. Ci Citi tize zens ns ca can n requ reques estt onli online ne se serv rvic ices es to pay pay pr prop oper erty ty tax, tax, st stam amp p duty duty,, Educational cess, etc. 6. Cre reat ate e diff differ eren entt sy syst stem em user users s and assi assign gn diff differ eren entt role ole with relat elated ed permissions. 7. Mana Manage ge al alll th the e ac acco count unt detail details s such such as user user name name,, depa depart rtmen ment, t, phon phone e number num bers, s, addr address ess,, webs websit ites, es, emai emaill ID of all th the e users users fr from om one centr central al 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 sys system tem.. Onl Only y whe when n the req requir uirem ement ent spe specif cifica icatio tions ns are pro proper perly ly given, it is possible to design a system, which will fit into required environm envi ronment. ent. It rests lar largely gely iin n the part of the users o off the exist existing ing system to give the requirement specifications because they are the people peop le who fina finally lly use the syste system. m. This is becaus because e the requi requireme rements nts have to be known during the initial stages so that the system can be designed according according to those require requirements. ments. 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 Th e sys syste tem m sh shou ould ld be abl able e to in inte terf rfac ace e wi with th th the e ex exis isti ting ng
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 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 like education, entertainment, income tax etc. 7. Authentication: 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, or what it is user declared toand be. passwords Authentication is commonly done through the use ofwho credentials i.e. name
NO. OF USERS 1. 2. 3. 4.
Revenu Revenue e Admi Admini nist stra rato torr Emp Employee Citiz tizen Visitor
INPUT & OUTPUT The following some are the projects inputs and outputs. Inputs: •
Admin enters credentials.
•
Admin Adm in enter enters s Emp Employe loyee e informa informatio tion n like name name,, las lastt nam name, e,
and generat generates es User ID, Pas Passwo sword rd 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 requirement of the system. It means for use by developers developers and will be the basic during testing phase. Any changes made made to the requirements in the futur future e 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 Development and Enhancement. This model was not the first first model to discuss iterative development, but it was the first model to explain why the iteration models. As originally envisioned, envisioned, the iterations were typically 6 months to 2 years 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 system requirements are defined in as much 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. Evalu Evaluating ating the ffirst irst prototype prototype in terms terms of its stren strengths, gths, weaknes weakness, s, and risks. 2. Defin Defining ing the requi requireme rements nts of the the second second prototyp prototype. e. 3. Plann Planning ing an designing designing the secon second d prototyp prototype. e. 4. Cons Construc tructing ting and and testing testing the the second second proto prototype. type.
•
At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might might involve development development cost overruns, 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 final sys system tem is thoroughly evaluated and and tested. Routine maintenance 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 overall system design. The main objective during 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 determine the various types of input. Inputs can be categorized 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 choice has to be made about the input media. To conclude about 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 the form of internal and interactive. interactive. As input d data ata is to be directly keyed in by the user, the keyboard can be considered to be the most suitable input device. OUTPUT DESIGN: Outpu Ou tputs ts from from compu computer ter syste systems ms are requir required ed pri prima marily rily to comm communi unicat cate e the result results s 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.
•
Interf Int erface ace outputs, outputs, whic which h involv involve e the the user user in communi communicati cating ng dir direct ectly ly wi with th Interface.
Use Userr
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 un unde derr th the e ca cate tego gory ry of in inte tern rnal al outp output uts. s. The The main main ou outp tput uts s desi desire red d ac acco cord rdin ing g to th the e requirem requ irement ent sp specific ecification ation a are: re:
The outpu outputs ts we were re needed needed tto o be g gener enerated ated as a hot cop copy y
and as well as queries queries to be viewed on the scre screen. en.
Keeping Keeping in view these out outputs, puts, the
format for the output is taken from the outputs, which are currently being obtained after manual processing. processing. The standard printer is to be used used as output media for hard co copies pies.
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 o one ne of the biggest biggest advantages of the n-tier 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 Busine Business ss Rules Rules Layer: 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 functionality/proces sing 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. Th The e Dat Datab abas ase e Laye Layer: r: This layer comprises of Components asvDB Actual tual datab at abas ase e co coul uld dthebDatabase e crea eate ted d using ing SQsuch L Ser erv er er,, Files, Ora rac cTables, le, le, Flat latViews, file files, s,etc. etc. etThe c. 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 with minim minimal al chang changes es to Dat Data a Ac Acces cess s Layer. Layer. The The res restt of the the Ap Appli plicat cation ion shou should ld rem remain ain unaffected
CONTEXT LEVEL DFD
Administrator Registration
Authentication
Onl Online Revenue Recovery
Citizens
Reports
Search Employees
FEASIBILITY STUDY
Preliminary 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 The re are asp aspect ects s in the fea feasib sibili ility ty stu study dy por portio tion n of the pre prelim limina inary ry investigation:
TECHNICAL FEASIBILITY
In the feasibility study first step is that tthe he 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 an d SQ SQL L Se Serv rver er 20 2005 05.. The hese se ar are e fr fre ee so sofftw twar are e th that at wou oulld 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 •
•
•
•
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 documentati on do operations need?
Support Issues
•
•
•
What documentati on will users be given? What training will users be given? How will change requests be managed?
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 FEASIBILITY
It refers to the benefits or Outcomes we are deriving from the product as co comp mpar ared ed to th the e to tota tall co cost st we are sp spen endi ding ng fo forr de deve velo lopi ping ng the product. If the benefi benefits ts are mor more e or less the same as the olde olderr 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. application. The errors can be greatly redu reduced ced 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:
Data Input Stage
Data Out Put Stage
Data Storage
AD MIN AD MIN
EMPLOYEE
Employee
UI Screens
Citizen Managerial
CITIZEN
User Level
Reports Online Revenue Recovery
Login DFD: tblRegistration
Open Login form
Enter User Name and Password
Y es
Check User
No
Verify Data
Admin Activities DFDs:
Yes
User Home Page
1st Level
tblLoginDetails
tbl_EmpRegis tration
tbl_DivisionDetails
Ope n Fo rm() 1.0.0
Manage Employees Manage Divisions 1.0.2 Enter Login Details 1.0.1
1.0.4 Manage Mondals
Mails 1.0.5
1.0.3
Validates Data
tbl_Mondal tblMails Generate Reports
Log out
1.0.6
Data Storage
Admin Activity DFD: 2nd level:
t b _D l iv i s i o n D e ta ils
Manage D i v is io n 1.2.0
D iv is io n N a m e 1.2.2
D iv is io n Id 1.2.1
V a li d a t e s
Employee (Mandal Manger) activities DFD: Level1:
D iv is io n D e s c 1.2.3
L og o u t
tbl_CitizenDetails
tblRegistration
tbl_CardDetails
tblMails
Ope n Fo rm() 1.0.0
Manage Ration cards
Manage Citizens 1.0.2
1.0.4
Mails
1.0.5
Enter Login Details 1.0.1
tbl_EmpDetails View Report
Edit Profile
1.0.3 1.0.6
Validates Data tbl_IncomeDetails
Log out
Employee DFD nd
2
Level:
V a li d a t e s
A d d C a r d s 1.4.0
C a rd N a m e A n n u a l I n c o m e
1.4.2
1.4.4
t b lR a t io n a C a rd D e ta ils A d d r e s s
N o o fP e r s o n s
1.4.5
1.4.3
S u b m it V a li d a t e s
Citizen Activity DFD: 1st level:
tbl_PropertyTax
tblLoginDetails
tblMails
tbl_IncomeTax details
Ope n Fo rm() 1.0.0
Manage Property Tax
Manage ImcomeTax
Mails
1.0.2
1.0.4
1.0.6
Enter Login Details 1.0.1
tblRegistration Manage education tax
Manage Professional tax
Edit Profile
1.0.3 1.0.7 1.0.5
Validates Data tbl_EducationTax
tbl_ProfessionalT ax
Entertine ment Tax
1.0.7
Log out
Citizen Activity DFD: nd
2 s
Level:
MondalId MondalName DivisionId
OrganizationId OrganizationName ReciptId
RegistrationNo CardNo
UserId
PhoneNo
CardholderName
TotalAmount
EmailId
NoOfPersons
Category
Website
AnnualIncome AnnualI ncome
PayDate
MondalId
Address
CheckNo
AnnulaIncome Annu laIncome
DivisionId
MondalId
CardNo
DivisionId
MondalId DivisionId
EmpId UserName password Name
DivisionId DivisionName
LastName
UserId
age
UserName
PhoneNo
PassWord
EmailId
Name
Address
LastName
MondalId
TaxId
CitizenTypeId
DivisionId
IncomeRange
PhoneNo
Role
TaxAmount
Salary
CitizenId
Address profession
JoinDate
Photo
HintQuestion
CardNo
Answer
MondalId DivisionId EmailId HintQuestion Answer MondalStatus DivisionStatus CitizenId CitizenType
ABSTRACT
Project Title: Online 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: 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 acquiring or ration card isstatus also provided. Status of theregarding document: Citizenscertificate can view the processing 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 Maintaining and and Keeping Keeping general general informati information on of the civilian civilians. s. 2. Working Working is made easy for for the Mand Mandal al Revenue Office Office in subject subject to validatin validating g and maintaining received documents. 3. Tracking Tracking of Civilian Civilian information information in a state state level situation situation is made easy. easy. 4. Keeping Keeping track of the the documents, documents, those are are submitted submitted by the civilians. civilians.
5. Ci Citi tize zens ns ca can n requ reques estt onli online ne se serv rvic ices es to pay pay pr prop oper erty ty tax, tax, st stam amp p duty duty,, Educational cess, etc. 6. Cre reat ate e diff differ eren entt sy syst stem em user users s and assi assign gn diff differ eren entt role ole with relat elated ed permissions. 7. Mana Manage ge al alll th the e ac acco count unt detail details s such such as user user name name,, depa depart rtmen ment, t, phon phone e number num bers, s, addr address ess,, webs websit ites, es, emai emaill ID of all th the e users users fr from om one centr central al location.
Non-functional requirements
i. ii.
Secu Secure re ac acce cess ss of co conf nfid iden enti tial al data data (u (use ser’ r’s s det detai ails ls)) sho shoul uld d be be pro provi vide ded. d. 24 X 7 availability of of the ap application
iii.
Applicat atiion sho shou uld be be ac access essible ov over Intern ernet. et.
iv. iv.
Bet ettter co comp mpon onen entt des desiign to get bett better er perf perfor orma manc nce e at at pea peak k ti time
v. Flex Flexib ible le se serv rvic ice e bas based ed ar arch chit itec ectu ture re will will be high highly ly de desi sira rabl ble e ffor or futu future re extension. Out of scope 1. Pro Provid viding ing Communica Communicatio tion n between between Citizen’s Citizen’s and Employ Employees ees throug through h Email Email and chat. 2. Not to impl implem ement ent th the e comp complet lete e fu funct nctio ional nalit ities ies fo forr a re reven venue ue depa depart rtmen mentt because it’s a tedious job.
No. of Modules
1. Pu Pub blic lic Use Userr Revenue Administrator(Officer) 2. Em Empl ploy oyee ees s 3. Citi Citize zen n (P (Peop eople) le)
4. Web Regis Registr trat atio ion n 5. Search 6. Auth Authent entic icati ation on
7. Reports
No. of Users
5. Revenu Revenue e Admi Admini nist stra rato torr 6. Emp Employee 7. Citiz tizen 8. 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 (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:
BAL(ClsRegistrationDetails)
User
6 : GetResponseFormDB() 1 : Enter login details() 7 : GetResponseFromBAL() 4 : ExecuteNonQuery() Database 3 : Check Login()
5 : ExecuteProcedure() 2 : Invalid Input() Login.aspx
9 : IfValidGetHomePage() Home
8 : Display Message()
DAL(SqlHelper.cs)
Collaboration Diagram For Registration:
6 : GetResponseFormDB()
Admin Adm in
DataBase
BAL(ClsRegistration)
4 : ExecuteScalar()
1 : OpenRegistrationPage()
5 : ExecuteProcedure()
3 : CitixenRegister() 7 : GetResponseFromBAL()
DAL(SqlHelper.cs) 2 : Invalid Input() FormRegistration.aspx 8 : Di DisplayMessage() splayMessage()
Collaboration Diagram for Admin adding Division:
Admin Adm in BAL(ClsRegistration)
6 : GetResponseFormDB()
7 : Get ResponseFromBAL() ResponseFromBAL() 1 : FormDivisionDetails.aspx()
4 : ExecuteNonQuery() DataBase
3 : InsertUpdateDivision() InsertUpdateDivision() 5 : ExecuteProcedure()
2 : Inv alid Input()
DAL(SqlHelper.cs)
FormDivisionDetails.aspx 8 : DisplayMessage()
Collaboration Diagram for Revenue Report:
BAL(ClsTaxDetails) Admin
7 : GetResponseFromBAL()
3: GetTaxDetailByAdmin ()
6: GetResponseFormDB () 4 : Execute Dataset() Database
1 : enter the details of tax type() 5 : ExecuteProcedure()
2 : Invalid Input() FormRevenueReport.aspx 8 : Display Data()
Activity Diagram For Login:
DAL(SqlHelper.cs)
enter Login Login Details Get LoginDetails
wrong username username a and nd passwrod
submit data Submit Subm it det ails
validate data yes
Reject
Accept
No Show Home Home Page Pa ge
Activity diagram for Registration:
Enter Required Details Get Detail Deta ilss
Validate Vali date Details Enter Details are Wrong
Validate Vali date Details
yes
Reject
Valid Vali d Data Data
No Successfully Registered
ActivityDiagram For Admin:
enter Login Details wrong username and passwrod
Get LoginDetails
submit data
Submit Subm it det ails
validate data Reject No
Division Details
Mond ondal Det etai aills
Re Reg gister ster Employee oyeess
Rev enue Report
Successfully Signout
Activity Diagram For MondalManager:
Mails
Citizen Request
enter Login Details wrong username and passwrod
Get LoginDetails
submit data
Submit Subm it det ails
validate data Reject No
Change Password
Rat ion Det ails
Updat e Prof ile
Rev enue Report
Successfully Signout
Activity Diagram For Citizen:
Mails
Citizen Request
enter Login Details wrong username and passwrod
Get LoginDetails
submit data
Submit details
validate data Reject No
Change Password
Prof es ession T Ta ax
Education T Ta ax
Income Tax
Successfully Signout
Screen shot
HOME
Propert y Tax
Entertinement Tax
Mails
<%@ <%@ Page Page Language Language="C#" ="C#" MasterPageFile MasterPageFile="~/MainMasterPage.master" ="~/MainMasterPage.master" AutoEventWireup="true" AutoEventWireup ="true" CodeFile CodeFile="FormHome.aspx.cs" ="FormHome.aspx.cs" Inherits="FormHome" Inherits="FormHome" Title="Untitled Title ="Untitled Page" %> <asp asp: :Content Content ID ID="Content1" ="Content1" ContentPlaceHolderID ContentPlaceHolderID="head" ="head" Runat="Server"> Runat="Server"> <style style type="text/css"> type="text/css"> .style20 { width width: : 100% 100%; ; } .style21 { width: : 258px 258px; ; width } .style22 { width: 447px; width: 447px; } </ </style style> > </asp </ asp: :Content Content> > <asp asp: :Content Content ID ID="Content2" ="Content2" ContentPlaceHolderID ContentPlaceHolderID="ContentPlaceHolder1" ="ContentPlaceHolder1" Runat="Server"> Runat ="Server">
<p> <br br /> </p </ p> <table table class="style20"> class="style20"> <tr tr> > <td td class="style21"> class="style21"> <asp asp: :Image Image ID ID="Image2" ="Image2" runat runat="server" ="server" ImageUrl ImageUrl="~/Images/renue ="~/Images/renue build.jpg" build.jpg" Width="275px" ="275px" /> Width </td </td> > <td td class="style22"> class="style22"> <p align align="justify"> ="justify"> <font font color color="#333366" ="#333366" face face="Georgia, ="Georgia, Times New Roman, Times, serif" serif" size="2"> size="2"> 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. </ </font font> > </p </p> </td </td> > <td td> > </ </td td> > </tr </tr> > <tr tr> > <td td class="style21"> class="style21"> </ </td td> > <td td class="style22"> class="style22"> </ </td td> > <td td> > </ </td td> > </tr </tr> > </table </ table> > </asp </ asp: :Content Content> >
Contact Us:
Page Language Language="C#" ="C#" MasterPageFile MasterPageFile="~/MainMasterPage.master" ="~/MainMasterPage.master" <%@ <%@ Page AutoEventWireup="true" AutoEventWireup ="true" CodeFile CodeFile="FormContactUs.aspx.cs" ="FormContactUs.aspx.cs" Inherits="FormContactUs" Inherits ="FormContactUs" Title="Untitled Title="Untitled Page" %> <asp asp: :Content Content ID ID="Content1" ="Content1" ContentPlaceHolderID ContentPlaceHolderID="head" ="head" Runat="Server"> Runat="Server"> <style style type="text/css"> type="text/css"> .style20 { width: : 100% 100%; ; width } .style21 { width width: : 304px 304px; ; }
.style22 { width: : 164px 164px; ; width text-align: right text-align: right; ; } .style23 { width width: : 164px 164px; ; text-align: right; ; text-align: right font-weight: normal; ; font-weight: normal } </style> </style > </asp </ asp: :Content Content> > <asp asp: :Content Content ID ID="Content2" ="Content2" ContentPlaceHolderID ContentPlaceHolderID="ContentPlaceHolder1" ="ContentPlaceHolder1" Runat="Server"> Runat ="Server"> <table table class="style20"> class="style20"> <tr tr> > <td td class="style21"> class="style21"> <asp asp: :Image Image ID ID="Image2" ="Image2" runat runat="server" ="server" Height Height="214px" ="214px" ImageUrl="~/Images/images[5].jpg" Width Width="309px" ="309px" /> ImageUrl="~/Images/images[5].jpg" </td </td> > <td td> > <asp asp: :Panel Panel ID ID="Panel1" ="Panel1" runat runat="server" ="server" Font-Bold Font-Bold="True" ="True" #003366">
GroupingText="Contact ="Contact Us" Us" Height Height="195px" ="195px" style style=" ="color color: : GroupingText <table table class class="style20"> ="style20"> <tr tr> > <td td class="style23"> class="style23"> Email Id:</ Id:</td td> > <td td> > [email protected]</ [email protected] </td td> > </ </tr tr> > <tr tr> > <td td class="style23"> class="style23"> Phone No:</ No:</td td> > <td td> > 9999999999</ 9999999999 </td td> > </ </tr tr> >
<tr tr> ><td td class="style23"> class="style23"> Fax:</ Fax: </td td> > <td td> > 2357989</ 2357989 </td td> > </ </tr tr> > <tr tr> > <td td class="style22"> class="style22"> </ </td td> > <td td> > </ </td td> > </ </tr tr> > </ </table table> > </asp </asp: :Panel Panel> > </td </td> > </tr </tr> > <tr tr> > <td td class="style21"> class="style21"> </ </td td> >
<td td> > </ </td td> > </tr </tr> > </table </ table> > </asp </ asp: :Content Content> >
About Us:
<%@ <%@ Page Page Language Language="C#" ="C#" MasterPageFile MasterPageFile="~/MainMasterPage.master" ="~/MainMasterPage.master" AutoEventWireup="true" AutoEventWireup ="true" CodeFile CodeFile="FormAboutUs.aspx.cs" ="FormAboutUs.aspx.cs" Inherits="FormAboutUs" Inherits="FormAboutUs" Title="Untitled Title ="Untitled Page" %> <asp asp: :Content Content ID ID="Content1" ="Content1" ContentPlaceHolderID ContentPlaceHolderID="head" ="head" Runat="Server"> Runat="Server"> <style style type="text/css"> type="text/css"> .MsoBodyTextIndent { width: 739px; width: 739px; } </style> </style > </asp </ asp: :Content Content> > <asp asp: :Content Content ID ID="Content2" ="Content2" ContentPlaceHolderID ContentPlaceHolderID="ContentPlaceHolder1" ="ContentPlaceHolder1" Runat="Server"> Runat ="Server"> <p> <br br /> </p </p> <p class="MsoNormal" class ="MsoNormal" style=" style LINE-HEIGHT: : 150% 150%; ; TEXT-ALIGN TEXT-ALIGN: : justify"> <b>< ><span span style=" style="COLOR COLOR: :="LINE-HEIGHT green green; ; mso-bidi-font-size mso-bidi-font-size: : 12.0pt">< 12.0pt"><font font color="#660066" color ="#660066"
BOARD OF
face="Lucida Sans Unicode" face="Lucida Unicode" size="2">< size="2"><a a name="2"></ name="2"></a a> ANDHRA
REVENUE:</ REVENUE: </font font></ ></span span></ ></b b></ ></p p> <p align align="justify" ="justify" class="MsoBodyTextIndent"> class="MsoBodyTextIndent"> <font font face="Lucida face="Lucida Sans Unicode" Unicode" size="2"> size="2">With 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. </font </font> </ </p p> <p class class="MsoNormal" ="MsoNormal" style=" style="LINE-HEIGHT LINE-HEIGHT: : 150% 150%; ; TEXTALIGN: ALIGN : justify"> <b>< ><font font color="#660066" color="#660066" face="Lucida face="Lucida Sans Unicode" Unicode" size size="2"> ="2"> <span span style=" style="COLOR COLOR: : green; green; mso-bidi-font-size: mso-bidi-font-size : 12.0pt"> <span span style=" style="COLOR COLOR: : #660066; #660066; mso-bidi-font-size mso-bidi-font-size: : 12.0pt"><a name="3"></ 12.0pt"><a name="3"></a a> TELANGANA BOARD OF REVENUE:nbsp; REVENUE:nbsp; </span </span></ ></b b></ ></font font>< ><span span style style=" ="mso-bidi-font-size mso-bidi-font-size: : 12.0pt"> <font font face="Lucida face="Lucida Sans Unicode" Unicode" size="2"> size="2">The 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.</ India. </font font></ ></span span>< ><o o:p></ ></o o:p></ ></p p> <p class="MsoNormal" class="MsoNormal" style style=" ="LINE-HEIGHT LINE-HEIGHT: : 150% 150%; ; TEXT-ALIGN: TEXT-ALIGN: justify; justify; width: width: 729px; 729px;"> <span span style=" style="mso-bidi-font-size mso-bidi-font-size: : 12.0pt"><font 12.0pt"><font face="Lucida face="Lucida Sans Unicode" Unicode" size="2">< span style style=" ="mso-tab-count mso-tab-count: : size="2"><span 1"> 1"> </span </span> >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 Development the Commissioner and was designated as ex officio Secretary to Government.</ Government. </font font></ ></span span>< ><o o:p></ ></o o:p></ ></p p> <p class="MsoNormal" class="MsoNormal" style=" style="LINE-HEIGHT LINE-HEIGHT: : 150% 150%; ; TEXT-ALIGN TEXT-ALIGN: : justify"> <span span style=" style="mso-bidi-font-size mso-bidi-font-size: : 12.0pt"><font 12.0pt"><font face="Lucida face="Lucida Sans Unicode" Unicode" size="2"><a size="2">< a name="4"></ name="4"></a a> </ </font font></ ></span span>< ><b b>< ><span span style=" style ="COLOR COLOR: : green">< green"><span span style=" COLOR: : green; green; mso-bidi-font-size mso-bidi-font-size: : 12.0pt">< 12.0pt"><font font style="COLOR color="#660066" color ="#660066" face="Lucida Unicode" size="2"> size="2">THE THE BOARD OF REVENUE IN face="Lucida Sans Unicode" font></ ></span span></ ></span span></ ></b b></ ></p p> ANDHRA PRADESH:</ PRADESH:</font <p class="MsoNormal" class="MsoNormal" style style=" ="TEXT-INDENT TEXT-INDENT: : 0.5in 0.5in; ; LINE-HEIGHT LINE-HEIGHT: : 150%; 150%; TEXT-ALIGN: TEXT-ALIGN : justify justify; ; width: 731px width: 731px; ;"> <span span style=" style="mso-bidi-font-size mso-bidi-font-size: : 12.0pt"><font 12.0pt"><font face="Lucida face="Lucida Sans Unicode" Unicode" size="2"> The integrated Board of Andhra Pradesh, constituted on size="2">The 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.</ agency. font></ ></span span>< ><o o:p ></o o:p></ ></p p> <p </font class="MsoNormal" class ="MsoNormal" ></ style=" ="TEXT-INDENT TEXT-INDENT: : 0.5in 0.5in; ; LINE-HEIGHT LINE-HEIGHT: : 150%; 150%; TEXT-ALIGN: TEXT-ALIGN : justify justify; ; style width: 726px width: 726px; ;"> <span span style=" style="mso-bidi-font-size mso-bidi-font-size: : 12.0pt"><font 12.0pt"><font face="Lucida face="Lucida Sans Unicode" Unicode" size="2"> Gradually the Board lost its position as the highest size="2">Gradually 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.</ Members. </font font></ ></span span>< ><o o:p></ ></o o:p></ ></p p> <p class="MsoNormal" class="MsoNormal" style style=" ="TEXT-INDENT TEXT-INDENT: : 0.5in 0.5in; ; LINE-HEIGHT LINE-HEIGHT: : 150%; 150%; TEXT-ALIGN: TEXT-ALIGN : justify justify; ; width: width: 728px 728px; ;">
<span span style=" style="mso-bidi-font-size mso-bidi-font-size: : 12.0pt"><font 12.0pt"><font face="Lucida face="Lucida Sans Unicode" Unicode" size="2"> In the Revenue Department, Commissioner of Revenue size="2">In 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 and
District Collectors, District Revenue Officers performed the revenue
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.</ Collector. </font font></ ></span span>< ><o o:p></ ></o o:p></ ></p p> <p class="MsoNormal" class="MsoNormal" style=" style="LINE-HEIGHT LINE-HEIGHT: : 150% 150%; ; TEXT-ALIGN TEXT-ALIGN: : justify"> <b>< ><span span style=" style="COLOR COLOR: : green green; ; mso-bidi-font-size mso-bidi-font-size: : 12.0pt">< 12.0pt"><font font color="#660066" color ="#660066" face="Lucida Sans Unicode" face="Lucida Unicode" size="2">< size="2"><a a name="5"></ name="5"></a a>COMMISSIONERS ACT 1977: </font></ </font ></span span></ ></b b> </p </p> <p align="justify" align="justify" class class="MsoBodyTextIndent"> ="MsoBodyTextIndent"> <font font face="Lucida face="Lucida Sans Unicode" Unicode" size="2"> size="2">The The Board of Revenue was abolished by the <span span style=" style="COLOR COLOR: : blue"> <a href="http://apland.ap.nic.in/cclaweb/scan href="http://apland.ap.nic.in/cclaweb/scan %20acts/1977commissioner.htm" %20acts/1977commissioner.htm" target target="_blank"> ="_blank">A A .P. Board of Revenue Replacement by Commissioners Act, 1977</ 1977 </a a></ ></span span> >.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 of
Commissioner Land Reforms and Urban Land Ceiling exercised the powers
</font font></ ></p p> Members.</ Members. <p class="MsoNormal" class="MsoNormal" style=" style="LINE-HEIGHT LINE-HEIGHT: : 150% 150%; ; TEXT-ALIGN TEXT-ALIGN: : justify"> <b>< ><span span style=" style="COLOR COLOR: : green green; ; mso-bidi-font-size mso-bidi-font-size: : 12.0pt">< 12.0pt"><font font color="#660066" color ="#660066" face="Lucida Unicode" size="2">< size="2"><a a name="6"></ name="6"></a a>THE PRESENT face="Lucida Sans Unicode" SET UP:</ UP:</font font></ ></span span></ ></b b></ ></p p> <p class="MsoNormal" class="MsoNormal" style style=" ="LINE-HEIGHT LINE-HEIGHT: : 150% 150%; ; TEXT-ALIGN: TEXT-ALIGN: justify; justify; width: width: 741px; 741px;"> <font font face="Lucida face="Lucida Sans Unicode" Unicode" size="2">< size="2"><b b> <span span style=" style="mso-bidi-font-size mso-bidi-font-size: : 12.0pt; 12.0pt; mso-tab-count mso-tab-count: : 1"> 1"> </span </span></ ></b b></ ></font font>< ><span span style style=" ="mso-bidi-font-size mso-bidi-font-size: : 12.0pt"> <font font face="Lucida face="Lucida Sans Unicode" Unicode" size="2"> size="2">In 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 ></span span> > were also created to assist the Chief Commissioner of </font </font></ </p </ < pp >> </p </p> <p> </p </p> </asp </ asp: :Content Content> >
Admin Login:
<%@ <%@ Page Page Language Language="C#" ="C#" MasterPageFile MasterPageFile="~/MainMasterPage.master" ="~/MainMasterPage.master" AutoEventWireup="true" AutoEventWireup ="true" CodeFile CodeFile="Login.aspx.cs" ="Login.aspx.cs" Inherits="Login" Inherits="Login" Title="Untitled Title ="Untitled Page" %> <asp asp: :Content Content ID ID="Content1" ="Content1" ContentPlaceHolderID ContentPlaceHolderID="head" ="head" Runat="Server"> Runat="Server"> <style style type="text/css"> type="text/css"> .style32 { width: 100%; width: 100%; color: #CCFFCC; color: #CCFFCC; height: 225px; ; height: 225px } .style35 { height: height: 21px 21px; ; font-size: font-size: x-large x-large; ;
} .style41 {
text-align : left text-align: left; ; height: 27px height: 27px; ; } .style42 { width: 235px; width: 235px; height: 28px height: 28px; ;
} .style43 { text-align : left text-align: left; ; height: 28px; ; height: 28px } .style47 { height: 289px height: 289px; ; } .style49 { width: 235px; width: 235px; height: 27px; ; height: 27px color: #000066; color: #000066; font-weight : bold; font-weight: bold; font-size: : medium medium; ; font-size text-align text-align: : right right; ; } </style > </style> </asp </ asp: :Content Content> > <asp asp: :Content Content ID ID="Content2" ="Content2" ContentPlaceHolderID ContentPlaceHolderID="ContentPlaceHolder1" ="ContentPlaceHolder1" Runat="Server"> Runat ="Server">
<table table align="center" align="center" class="style32"> class="style32"> <tr tr> > <td td align="center" align="center" class="style47"> class="style47"> <asp asp: :Panel Panel ID ID="Panel1" ="Panel1" runat="server" runat="server" GroupingText="Login" GroupingText ="Login" Width="501px" Width ="501px" ForeColor ForeColor="#CC0000" ="#CC0000" Height="250px" Height ="250px" BackColor="#CCCCFF" BackColor ="#CCCCFF" style=" font-size: : large large; ; color color: : #000066 #000066; ; backgroundstyle="font-size color: #DAC57A"> color: <table table class class="style32" ="style32" bgcolor="#CCCCFF" bgcolor="#CCCCFF" style=" style ="background-color background-color: : #DAC57A"> <tr tr> > <td td class class="style35" ="style35" colspan="2"> colspan="2"> <asp asp: :Label Label ID="Lbllogin" ID="Lbllogin" runat runat="server" ="server" style=" ="color color: : #003366 #003366; ; font-size: font-size: xstyle large; large ; " Text Text="Label"></ ="Label"></asp asp: :Label Label> > </ </td td> > </ </tr tr> > <tr tr> > <td td class class="style35" ="style35" colspan="2"> colspan="2"> </ </td td> > </ </tr tr> > <tr tr> > <td td class class="style49"> ="style49">
<asp asp: :RequiredFieldValidator ID="RequiredFieldValidator1" ID ="RequiredFieldValidator1" runat="server" runat="server" ControlToValidate="Txt_UName" ="Txt_UName" ControlToValidate ErrorMessage="*"></ ErrorMessage ="*"></asp asp: :RequiredFieldValidator RequiredFieldValidator> > <span span> >UserName: UserName:</ </span span></ ></td td> > <td td class class="style41"> ="style41"> <asp asp: :TextBox TextBox ID="Txt_UName" ID="Txt_UName" runat="server"></ runat ="server"></asp asp: :TextBox TextBox> > td> </ </td > </ </tr tr> > <tr tr> > <td td class class="style49"> ="style49"> <asp asp: :RequiredFieldValidator ID="RequiredFieldValidator2" ID ="RequiredFieldValidator2" runat="server" runat="server" ControlToValidate ControlToValidate="Txt_PassWord" ="Txt_PassWord" ErrorMessage="*"></ ErrorMessage ="*"></asp asp: :RequiredFieldValidator RequiredFieldValidator> > <span span> >Pass Word:</ Word:</span span></ ></td td> > <td td class class="style41"> ="style41"> <asp asp: :TextBox TextBox ID="Txt_PassWord" ID="Txt_PassWord" runat="server" runat="server" TextMode="Password"></ TextMode ="Password"></asp asp: :TextBox TextBox> > </ </td td> > </ </tr tr> > <tr tr> > <td td class class="style42"> ="style42"> </ </td td> > <td td class class="style43"> ="style43"> <asp asp: :CheckBox CheckBox ID ID="CheckBox1" ="CheckBox1" runat="server" runat="server" Text="Remember Text ="Remember Me" Me" style style=" ="color color: : #003366 #003366; ; font-size: font-size: medium; medium;" /> </ </td td> > </ </tr tr> > <tr tr> > <td td class class="style42"> ="style42"> </ </td td> > <td td class class="style43"> ="style43"> <asp asp: :Button Button ID ID="But_Login" ="But_Login" runat runat="server" ="server" Height="29px" Height ="29px" Text="Login" Text="Login" Width Width="77px" ="77px" onclick onclick="But_Login_Click" ="But_Login_Click" style="font-weight style=" font-weight: : 700" 700" /> <asp asp: :LinkButton LinkButton ID="LinkButton1" ID="LinkButton1" runat="server" runat ="server" ValidationGroup ValidationGroup="forget" ="forget" onclick="LinkButton1_Click" ="LinkButton1_Click" onclick Visible="False" Visible ="False" style=" style="font-size font-size: : medium">Forget medium">Forget PassWord</ PassWord</asp asp: :LinkButton LinkButton> > </ </td td> > </ </tr tr> > <tr tr> > <td td class class="style42"> ="style42"> </ </td td> > <td td class class="style43"> ="style43"> <asp asp: :HyperLink HyperLink ID="HyperLink2" ID="HyperLink2" runat="server" runat="server" Font-Underline="True" Font-Underline ="True" style style=" ="color color: : #CC0000 #CC0000; ; font-size: font-size: medium; medium;" Visible="False" Visible ="False" NavigateUrl="~/FormRegister.aspx"> NavigateUrl ="~/FormRegister.aspx">New New User Register Here</ Here</asp asp: :HyperLink HyperLink> >
</ </td td> > </ </tr tr> > <tr tr> > <td td colspan colspan="2"> ="2"> <asp asp: :Label Label ID="Label1" ID="Label1" runat="server" runat="server" Text="Label" Text ="Label" Visible Visible="False" ="False" ForeColor="#CC0000" ForeColor="#CC0000" style=" style="font-size font-size: : medium"></asp: medium"></asp :Label Label> > </ </td td> > </ </tr tr> > </ </table table> > </ </asp asp: :Panel Panel> > </td </td> > </tr </tr> > <tr tr> > <td td> > </ </td td> > </tr </tr> > </table </table> >
</ </asp asp: :Content Content> >
Employee Login:
Citizen Login Page:
System
System
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 SYSTE M SECURITY SECURITY ref refers ers to the techn technica icall innova innovatio tions ns and proc procedu edures res app applied lied to the hardware and operation systems to protect against deliberate or accidental damage from a defined threat.
DATA DAT A SECURI SECURITY TY is th the e prot protec ectio tion n of data data fr from om loss loss,, disc disclo losu sure re,, modi modifi fica catio tion n an and d destruction.
SYSTEM SYSTE M INTEGRITY INTEGRITY re refe fers rs to th the e powe powerr fu func ncti tion onin ing g of ha hard rdwa ware re an and d prog progra rams ms,, 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 speci special al status status gi given ven to sens sensitiv itive e inform informatio ation n in a dat databa abase se 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 JavaS cript in use used d to ensure those required required fields fields are filled with sui suitable table data only only.. Maximum lengths of the fields of the forms are appropriately defined.
•
Forms For ms canno cannott be subm submitte itted d witho without ut fil fillin ling g up the manda mandator tory y dat data a so that that man manual ual 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 intimating through through appropriate appropriate message messages s about about the suc success cessful ful oper operation ations s 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 organizationa organizationall structur structure. e. Only permitted permitted users can log on to the system 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 SQ L Ser erve ver, r, but but al also so ab abou outt al alll ha hand ndlin ling g pr proc oced edur ure e rela relate ted d with with “Onlin “Online e Reven Revenue ue 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 wi will ll
pr prov ovid ide e
be bett tter er
opp ppor ortu tuni niti ties es
an and d
gu guid idan ance ce
in
futu future re
in
deve develo lopi ping ng
pr proj ojec ects ts
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 project offers offers user user to ente enterr the data through through simple and interacti interactive ve form forms. s. This This is very helpful for the client to enter the desired information tthrough hrough so much simplicity.
•
The The user user is mainly mainly more more conc concern erned ed about about the validity validity of the data, wh whate atever ver 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 thatt the project tha project is user fr frien iendly dly which which is one of the the pri prima mary ry conce concerns rns of any any goo good d 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 Decis ion maki making ng process process would be greatly greatly enhanced enhanced because of faste fasterr proc processin essing g of informatio info rmation n since since data collectio collection n from inform information ation available available on computer computer takes muc much h 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 Trai ning for for simple simple computer computer operatio operations ns is necessar necessary y for th the e
user users s working working on the the
system. This System being web-based web-based and an undertak undertaking ing of Cyber Securit Security y Divi Division sion,, need needs s to be thoroughly tested to find out any security gaps.
•
A cons console ole fo forr the data centre centre may may be made availab available le to allow the per perso sonne nnell to monitor on the sites which were cleared for hosting during a particular period.
•
Moreov Mor eover, er, it is just just a begin beginnin ning; g; furthe furtherr the syste system m may may be utiliz utilized ed in var variou ious s othertype othe rtypes s of auditing auditing operation operation viz. Network Network auditing auditing or similar similar proc process/ ess/work workflow flow based applications...
Bibliography •
FOR .NET INSTALLATION www.support.mircosoft.com
•
FOR DEPLOYMENT AND PACKING ON SERVER www.developer.com www.15seconds.com
•
FOR SQL www.msdn.microsoft.com
•
FOR ASP.NET www.msdn.microsoft.com/n et/quickstart/aspplus/default.com 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
