1
ABOUT THE ORGANIZATION
1
NATIONAL INFORMATICS CENTER
The organizational set up of NIC encompasses its Headquarters at New
Delhi, State Units in all the 25 state capitals and 7 Union Territory Headquarters and
District centers in more than 540 districts of India. NIC computer cells are located in
almost all the Ministry Bhawans of the Central Government and Apex Offices
including the Prime Minister’s Office, the Rashtrapati Bhawan and the Parliament
House.
NETWORKING:
NIC provides effective networking solutions networks such as video-
conferencing, electronic data interchange, etc.. Having a strong backbone support of
NICNET, NIC provides all kinds of VSAT based services such as CDMA, SCPC,
FTDMA, DirecPC, IP Advantage and also the RF (wireless) technology to its user
organizations.
VAST services
LAN Technologies
E-Mail Services
INTERNET SERVICES:
Internet was evolved into one of technology’s greatest democracies,
permitting the passage of all kinds of information carries crossing with full freedom.
the ‘Global Villages’ created by the Internet. The Internet services of NIC are
provided through NICNET, NIC’s satellite based computer communication network,
which is a prominent gateway of Internet in India.The range of Internet services being
provided by the NIC includes:
Electronic mail
WWW Browsing
File Transfer Facility
Remote Login
Gateway to SMTP/UUCP Video Conferencing
2
NIC has been providing video-conferencing services in the country since April 1995
and has set up video-conferencing services in 26 cities all over India including all the
northeastern state capitals. The VC network runs over NIC’s high-speed satellite
based network called “NICNET”.
NORTH: New Delhi, Chandigarh, Jaipur, Jammu, and Lucknow.
WEST: Navi Mumbai, Pune, Ahmedabad, and Bhopal.
SOUTH:Chennai,Banglore,Hyderabad,Thiruvananthapuram,Tripurand
Visakhapatnam.
EAST: Calcutta, Patna, and Bhubaneshwar.
NORTH-EAST:Guwahati, Shillong, Gangtok, Agartala, Itanagar, Kohima, Imphal
and Aizwal, For more information about NIC's VC services, visit
http://www.nic.in/vidcon or mailto:[email protected]
WEBSITE DEVELOPMENT & HOSTING:After the commercialization of
Internet, World Wide Web is experiencing a revolution of unmatched magnitude.
Web site design and development
Web page hosting and maintenance
Enhancement of existing web sites http://www.webservices.nic.in/
NIC – YANAM:The NIC-Yanam was started in November, 1996 with one Micro
Earth Station, one computer and three terminals. Later it has been updated and started
full pledged functioning from July, 1998. In 1999, it has got the Internet connectivity
through DirecPC technology. NIC has started new project called "TOTAL
COMPUTERIZATION".The following projects are the highlights of NIC-Yanam:
1. Old age pensioner's schemes (Social Welfare Dept)
2. Online issue of caste/income certificates/pattas (Revenue Dept)
3. Guidelines register for land values (Revenue Dept)
4. MIS for service profile/ GPF loan (Many Depts.)
3
ORGANIZATION PROFILE
GFGF
4
Government Of India
Ministry Of Information Technology
National Informatics Center
Northern Region(New Delhi)
Southern Region(Hyderabad)
Eastern Region(Bhubaneshwar)
Western Region(Pune)
Andhra Pradesh
Tamil Nadu Pondicherry Karnataka Kerala
Yanam Karkal Mahe
NICProjects
Dept #1
Dept #2Dept #3
R.E.O
Dept #5
Dept #4
AROGYA SRI
(Health Insurance Card Monitoring System)
ABSTRACT
The project titled “AROGYASRI – Health Card Monitoring System” is to
reduce the burden of rural people by managing the costs obtained for treatment,
involved in Chronic diseases. The basic goal of Arogyasri is to provide high quality
health care for the people those who belongs to below poverty line (BPL).
Arogyasri is one of the Health Insurance Scheme which monitors the cases
by using Health Cards. Health Cards are issued to each citizen in particular area on
the basis of Ration Cards. There are two types of Ration Cards namely Red card and
Yellow card; the Red card holders belongs to below poverty line, whereas the health
insurance card is issued for both type of card holders but there is a slight difference
between the benefits of each card holder.
Every year, the Government is paying the insurance money to the Insurance
Company on each citizen for the claim of around Rs.2Lakhs for each individual. The
Insurance Company will pay the amount to the hospitals recognized by the Govt. for
the treatment given to these Health Insurance Card Holders. In Yanam, there are
around 40,000 people who are expected to get benefit out of this scheme.
This software project is aimed at automation of all the details related to the
Health Insurance Card like Card Preparation, Issue, Insurance Company Dealings,
Issue of Non-Objection Certificate etc.
The system also provides a comprehensive mechanism for maintaining the
Health Dept Activities in any area. It also helps the administrator for managing the
tasks related to health dept. like Details Collection, Insurance Money Management,
NOC Issue, Verification of survey data etc. The timely production of cards, bills etc
will help the management to achieve their goals/activities. The administrator can
reach through his needs at the close of a mouse.
5
Modules
The project “Health Card Monitoring System” is mainly divided into
following modules.
Survey Details
Health Department Details
Insurance Details
Corporate Hospital Details
Users Details
Survey Details:
The Survey details maintains the personal and as well as official details of
all the families currently staying in a particular region. The administrator can access
these details only. This module provides the details like
Collection of individual details in each family
Capturing the door to door survey details along with their photos
Digital photo capturing and linking with Database
Verification / Scrutiny of the survey data
Authorization of survey data
Health Department Details:
This module maintains the details about Health Dept activities. The
Administrator can access these details. The activities provided by this module are
Match the data with Ration card details to assess their socio-economical
status
Monitors the Non-Objection Certificate issued to the patients by Govt.
hospitals to get the treatment in corporate hospitals.
Issues Health Insurance Card for each and very citizen iff the survey
details are matched with the data in the Database.
Maintains the information of Health Insurance Hospitals.
Manages the new entries and renewals
Insurance Company Details:
6
This module maintains the information regarding all Insurance companies.
Administrator has rights to access these details. Govt. will select the Insurance
companies on the basis of their credit worthiness and quotations placed at the time of
Tender notices. This module provides details like
Sum assured
This feature is the coverage on a policy which depends on the
functions sum assured every year and minimum sum assured for a policy.
Policy Term
This feature provides the duration of time on particular Health policy.
Insurance Amount
This feature manages the total amount sanctioned by the
Insurance Company on a policy holder.
Corporate Hospital Details:
This module maintains the details of hospitals (CH, SSH) which are
recognized by the Govt. i.e the private hospitals which also provides treatment for
Health card holders. Administrator can access these details. Users can view the
information but not having any rights to modify the details. Some of the details this
module presents
Patient care administration
Manages the logistical and record-keeping aspects of patient care.
Clinical services
Provide laboratory testing and procedures, facilities (radiology,
electrodiagnosis, hermatology, and so on) and patient monitoring and screening.
Patient care services
Provide patients with medical care and support services.
Financial management
Manage the financial resources and operations of the hospital.
Users Details:
7
This module maintains the details about the users, involves
queries. The users retrieve information from these queries. A Query on different
modules provides up to date information regarding Health Dept. activities.
Objectives of this project:
To issue Health Insurance Card for each and every citizen.
To incorporate the door to door survey details from the individuals with
photos.
To capture the digital photos of the citizens and incorporate into the
Database.
To match the data with ration card details to assess their socio-economical
status.
To monitor the scrutiny, verification of the Application for the Insurance.
To monitor the cases which are benefited under this scheme.
To monitor the Non-Objection certificate issued to the patients by Govt.
Hospitals.
To monitor the renewals and new entries of the insurance amount given to
the Insurance companies by the Govt.
Client:
The client is Government General Hospital, Yanam. It is being developed
at National Informatics Centre, Government of India, Ministry of Communications &
IT, Yanam.
Tools:
.NET Framework 2.0
C#
UML
JAVA SCRIPT
VISUAL STUDIO 2005
Active Server Pages .NET
SQL Server 2000
ERWIN Model
IIS Internet Information Server
8
9
FEASIBILITY ANALYSIS
Feasibility analysis proposes one or more conceptual solutions to the
problem set of the PROJECT WORK. Conceptual solution gives an idea of how the
new system should be. It is not possible to collect all the information that is required
for the PROJECT WORK within the security restriction. So these solutions must
provide feasible and perform the action accordingly that is acceptable. Three things
must be done to establish feasibility.
TECHNICAL FEASIBLITY:
Technical feasibility centers on the existing computer system and to what
extent it can support the proposed addition. For example if the current computer is
operating at 80% capacity then running another application could overload the system
or require additional hardware. This involves financial considerations to
accommodate technical enhancements. If the budget is a serious constraint, then the
project is judged not feasible.
Microsoft Visual Inter Development Studio and its supporting hardware are already
under use in the organization. This package does not require any additions of purchase
of new software. Therefore this package is technically feasible.
ECONOMIC FEASIBLITY:
Economic feasibility is the most frequently used method for evaluating the
effectiveness of a candidate system. More commonly known as cost/benefit analysis,
the procedure is to determine the benefits and savings that are expected from a
candidate system and compare them with the costs. If benefits outweigh costs, the
decision is made to design and implement the system. Otherwise, further justification
or alterations in the proposed system will have to be made if it is to have a chance of
being approved.
10
This package reduces the operating costs in terms of time by automating the process
of report generation. The chance of errors is minimized and the benefit to the
organization is more. Hence this package is economically feasible.
DEVELOPMENT RISK:
Determine whether the system can be designed so that necessary function and
performance are achieved within the constraints uncovered during the analysis. In this
PROJECT the development risk is considered to be low, since the requirements of the
system are well defined.
RESOURCE AVAILIBILITY:
The hardware and software resources necessary to develop the system are
available. As for the availability of the resources they are already available in the
Pentium-3 processor and supporting ASP and SQL SERVER.
OPERATIONAL FEASABILITY:
People are inherently resistant to change and computers have been known to
facilitate change. An estimate should be made of how strong reaction the user-staff is
likely to have towards the development of a computerized system. It is common
knowledge that computer installations have something to do with turnover, transfer,
retraining and changes in employee job status.
11
PROPOSED SYSTEM
Proposed System:
The proposed system can overcome the drawbacks of the existing
system. The proposed system HEALTH CARD MONITORING SYSTEM tries to
provide a user friendly, GUI based client/server application that will automate the
different activities involved in day-to-day planning of Health Dept. Programs.
Goals of proposed system:
To reduce the time,
effort and errors at the time of details gathering, renewals, card issue
and so on.
To monitor the
cases, new entries and verification, authorization of data in a planned
and efficient manner.
Capturing of data
into the Database and insurance money management in a secure
manner.
Provide security
from different users of the system.
To reduce paper
work.
To improve
management of updated information i.e databases by providing
facilities to edit this information, manipulate it and finally retrieve this
information as efficiently possible.
Advantages:
12
Rural area people can be benefited from this system. Poor people are able to get
the latest treatment from the Corporate Hospitals with the support by the
Government.
The Government could monitor the diseases occurring in each village and their
causes which will be helpful to take prevention of the diseases by the effective
maintenance of Database.
Card is issued only after scrutinizing the details two to three times so there is no
question of any mal-practices.
13
OPERATING ENVIRONMENT
Microsoft.NET Framework
The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet. The .NET
Framework is designed to fulfill the following objectives:
To provide a consistent object-oriented programming environment
whether object code is stored and executed locally, executed locally but
Internet-distributed, or execute remotely.
To provide a code-execution environment that minimizes software
deployment and versioning conflicts.
To provide a code-execution environment that guarantees safe execution
of code, including code created by an unknown or semi-trusted third
party.
To provide a code-execution environment that eliminates the
performance problems of scripted or interpreted environments.
To make the developer experience consistent across widely varying
types of applications, such as Windows-based applications and Web-
based applications.
To build all communication on industry standards to ensure that code
based on the .NET Framework can integrate with any other code.
14
The .NET Framework has two main components: the common language runtime
and the .NET Framework class library. The common language runtime is the
foundation of .NET Framework. You can think of the runtime as an agent that
manages code at execution time, providing core services such as memory
management ,thread management, and remoting, while also enforcing strict type
safety and other forms of code accuracy that ensure security and robustness. In fact,
the concept of code management is a fundamental principle of the runtime. Code that
targets the runtime is known as managed code, while code that does not target the
runtime is known as unmanaged code. The class library, the other main component of
the .NET Framework, is a comprehensive, object-oriented collection of reusable types
that you can use to develop applications ranging from traditional command-line or
graphical user interface (GUI) applications to applications based on the latest
innovations provided by ASP.NET, such as Web Forms and XML Web services.
For example, ASP.NET hosts the runtime to provide a scalable, server-side
environment for managed code. ASP.NET works directly with the runtime to enable
Web Forms applications and XML Web services, both of which are discussed later in
this topic.
Internet Explorer is an example of an unmanaged application that hosts the
runtime (in the form of a MIME type extension). Using Internet Explorer to host the
runtime enables you to embed managed components or Windows Forms controls in
HTML documents. Hosting the runtime in this way makes managed mobile code
possible, but with significant improvements that only managed code can offer, such as
semi-trusted execution and secure isolated file storage.
The following illustration shows the relationship of the common language runtime
and the class library to your applications and to the overall system. The illustration
also shows how managed code operates within a larger architecture.
Features of the Common Language Runtime
The common language runtime manages memory, thread execution, code
execution, code safety verification, compilation, and other system services. These
features are intrinsic to the managed code that runs on the common language runtime.
15
With regards to security, managed components are awarded varying degrees of
trust, depending on a number of factors that include their origin (such as the Internet,
enterprise network, or local computer). This means that a managed component might
or might not be able to perform file-access operations, registry-access operations, or
other sensitive functions, even if it is being used in the same active application.
The runtime enforces code access security. The runtime also enforces code
robustness by implementing a strict type- and code- verification infrastructure called
the common type system (CTS). The CTS ensures that all managed code is self-
describing. The various Microsoft and third-party language compilers generate
managed code that conforms to the CTS. This means that managed code can consume
other managed types and instances, while strictly enforcing type fidelity and type
safety.
Interoperability between managed and unmanaged code enables developers to
continue to use necessary COM components and DLLs.
The runtime is designed to enhance performance. Although the common language
runtime provides many standard runtime services, managed code is never interpreted.
A feature called just-in-time (JIT) compiling enables all managed code to run in the
native machine language of the system on which it is executing. Meanwhile, the
memory manager removes the possibilities of fragmented memory and increases
memory locality-of–reference to further increase performance.
.NET Framework Class Library
The .NET Framework class library is a collection of reusable types that tightly
integrate with the common language runtime. The class library is object oriented,
providing types from which your managed code can derive functionality. This not
only makes the .NET Framework types easy to use, but also reduces the time
associated with learning new features of the .NET Framework. In addition, third-party
components can integrate seamlessly with classes in the .NET Framework.
As you would expect from an object-oriented class library, the .NET
Framework types enable you to accomplish a range of common programming tasks,
including tasks such as string management, data collection, database connectivity, and
16
file access. For example, you can use the .NET Framework to develop the following
types of applications and services:
Console applications.
Scripted or hosted applications.
Windows GUI applications (Windows Forms).
ASP.NET applications.
XML Web services.
Windows services.
Client Application Development
Client applications are the closest to a traditional style of application in
Windows-based programming. These are the types of applications that display
windows or forms on the desktop, enabling a user to perform a task. Client
applications include applications such as word processors and spreadsheets, as well as
custom business applications such as data-entry tools, reporting tools, and so on.
Client applications usually employ windows, menus, buttons, and other GUI
elements, and they likely access local resources such as the file system and
peripherals such as printers.
The Windows Forms classes contained in the .NET Framework are designed
to be used for GUI development.
Introduction
Windows Forms is the new platform for Microsoft Windows application
development, based on the .NET Framework. Additionally, Windows Forms can act
as the local user interface in a multi-tier distributed solution. Windows Forms is a
framework for building Windows client applications that utilize the common language
runtime. Windows Forms applications can be written in any language that the
common language runtime supports.
What Is a Form?
A form is a bit of screen real estate, usually rectangular, that you can use to
present information to the user and to accept input from the user. Forms can be
17
standard windows, multiple document interface (MDI) windows, dialog boxes, or
display surfaces for graphical routines. Forms are objects that expose properties which
define their appearance, methods which define their behavior, and events which
define their interaction with the user. By setting the properties of the form and writing
code to respond to its events, you customize the object to meet the requirements of
your application.
When you add a form to your project, you can choose whether it inherits from
the Form class provided by the framework, or from a form you have previously
created.
Some of the advantages of using Windows Forms include the following:
Simplicity and power: Windows Forms is a programming model for developing
Windows applications that combines the simplicity of the Visual Basic 6.0
programming model with the power and flexibility of the common language
runtime.
Lower total cost of ownership: Windows Forms takes advantage of the
versioning and deployment features of the common language runtime to offer
reduced deployment costs and higher application robustness over time. This
significantly lowers the maintenance costs (TCO) for applications written in
Windows Forms.
Architecture for controls: Windows Forms offers an architecture for controls
and control containers that is based on concrete implementation of the control
and container classes. This significantly reduces control-container interoperability
issues.
Security: Windows Forms takes full advantage of the security features of the
common language runtime. This means that Windows Forms can be used
implement everything from an untrusted control running in the browser to a fully
trusted application installed on a user’s hard disk.
XML Web services support: Windows Forms offers full support for quickly and
easily connecting to XML Web services.
Rich graphics: Windows Forms is one of the first ship vehicles for GDI+, a new
version of the Windows Graphical Device Interface (GDI) that supports alpha
blending, texture brushes, advanced transforms, rich text support, and more.
18
Flexible controls: Windows Forms offers a rich set of controls that encompass all
of the controls offered by Windows. These controls also offer new features, such
as “flat look” styles for buttons, radio buttons, and check boxes.
Data awareness: Windows Forms offers full support for the ADO data model.
ActiveX control support: Windows Forms offers full support for ActiveX
controls. You can easily host ActiveX controls in a Windows Forms application.
You can also host a Windows Forms control as an ActiveX control.
Licensing: Windows Forms takes advantage of the common language runtime
enhanced licensing model.
Printing: Windows Forms offers a printing framework that enables applications
to provide comprehensive reports.
Accessibility: Windows Forms controls implement the interfaces defined by
Microsoft Active Accessibility (MSAA), which make it simple to build
applications that support accessibility aids, such as screen readers.
Design-time support: Windows Forms takes full advantage of the meta-data and
component model features offered by the common language runtime to provide
thorough design-time support for both control users and control implementers.
ACTIVE X DATA OBJECTS.NET
ADO.NET Overview
ADO.NET is an evolution of the ADO data access model that directly addresses
user requirements for developing scalable applications. It was designed specifically
for the web with scalability, statelessness, and XML in mind.
ADO.NET uses some ADO objects, such as the Connection and Command
objects, and also introduces new objects. Key new ADO.NET objects include the
DataSet, DataReader, and DataAdapter.
19
The important distinction between this evolved stage of ADO.NET and
previous data architectures is that there exists an object – the DataSet – that is
separate and distinct from any data stores. Because of that, the DataSet functions as a
standalone entity. You can think of the DataSet as an always disconnected recordset
that knows nothing about the source or destination of the data it contains. Inside a
DataSet, much like in a database, there are tables, columns, relationships, constraints,
views, and so forth.
A DataAdapter is the object that connects to the database to fill the DataSet.
Then, it connects back to the database to update the data there, based on operations
performed while the DataSet held the data. In the past, data processing has been
primarily connection-based. At the center of this approach is the DataAdapter, which
provides a bridge to retrieve and save data between a DataSet and its source data
store. It accomplishes this by means of requests to the appropriate SQL commands
made against the data store.
The XML-based DataSet object provides a consistent programming model that
works with all models of data storage: flat, relational, and hierarchical.
While the DataSet has no knowledge of the source of its data, the managed
provider has detailed and specific information. The role of the managed provider is to
connect, fill, and persist the DataSet to and from data stores. The OLE DB and SQL
Server .NET Data Providers (System.Data.OleDb and System.Data.SqlClient) that are
part of the .Net Framework provide four basic objects: the Command, Connection,
DataReader and DataAdapter. In the remaining sections of this document, we’ll
walk through each part of the DataSet and the OLE DB/SQL Server.NET Data
Providers explaining what they are, and how to program against them.
The following sections will introduce you to some objects that have evolved,
and some that are new. These objects are:
Connections. For connection to and managing transactions against a database.
Commands. For issuing SQL commands against a database.
DataReaders. For reading a forward-only stream of data records from a SQL
Server data source.
20
DataSets. For storing, remoting and programming against flat data, XML data
and Relational Data.
DataAdapters. For pushing data into a DataSet, and reconciling data against a
Database.
When dealing with connections to a database,there are two different options: SQL
Server .NET Data Provider (System.Data.SqlClient) and OLE DB .NET Data
Provider (System.Data.OleDb). In these samples we will use the SQL Server .NET
Data Provider. These are written to talk directly to Microsoft SQL Server. The OLE
DB .NET Data Provider is used to talk to any OLE DB Provider (as it uses OLE DB
underneath).
Connections
Connections are used to ‘talk to’ databases, and are represented by provider-
specific classes such as SQLConnection. Commands travel over connections and
resultsets are returned in the form of streams which can be read by a DataReader
object, or pushed into a DataSet object.
Commands
Commands contain the information that is submitted to a database, and are
represented by provider-specific classes such as SQLCommand. A command can be
a stored procedure call, an UPDATE statement, or a statement that returns results.
DataReaders
The DataReader object is somewhat synonymous with a readonly/forward-only
cursor over data. The DataReader API supports flat as well as hierarchical data. A
DataReader object is returned after executing a command against a database. The
format of the returned DataReader object is different from a recordset. For example,
you might use the DataReader to show the results of a search list in a web page.
DataSets and DataAdapters
DataSets
21
The DataSet object is similar to the ADO Recordset object, but more
powerful, and with one other important distinction: the DataSet is always
disconnected. The DataSet object represents a cache of data, with database like
structures such as tables, columns, relationships, and constraints. However, though a
DataSet can and does behave much like a database, but DataSet objects do not
interact directly with databases, or other source date. This allows the developer to
work with a programming model that is always consistent, regardless of where the
source data resides. Data coming from a database, an XML file, from code, or user
input can all be placed into DataSet objects. Then, as changes are made to the
DataSet they can be tracked and verified before updating the source data. The
GetChanges method of the DataSet object actually creates a second DataSet that
contains only the changes to the data. This DataSet is then used by a DataAdapter
(or other objects) to update the original data source.
The DataSet has many XML characteristics, including the ability to produce
and consume XML data and XML schemas. XML schemas can be used to describe
schemas interchanged via WebServices. In fact, a DataSet with a schema can actually
be compiled for type safety and statement completion.
DataAdapters (OLEDB/SQL)
The DataAdapter object works as a bridge between the DataSet and the
source data. Using the provider-specific SqlDataAdapter (along with its associated
SqlCommand and SqlConnection) can increase overall performance when working
with a Microsoft SQL Server databases. For other OLE DB-supported databases, you
would use the OleDbDataAdapter object and its associated OleDbCommand and
OleDbConnection objects.
The DataAdapter object uses commands to update the data source after
changes have been made to the DataSet. Using the Fill method of the DataAdapter
calls the SELECT command; using the Update method calls the INSERT, UPDATE,
or DELETE command for each changed row. You can explicitly set these commands
in order to control the statements used at runtime to resolve changes, including the use
of stored procedures. For ad-hoc scenarios, a CommandBuilder object can generate
22
these at run-time based upon a select statement. However, this run-time generation
requires an extra round-trip to the server in order to gather required metadata, so
Server-side managed code
ASP.NET is the hosting environment that enables developers to use
the .NET Framework to target Web-based applications. However, ASP.NET is more
than just a runtime host; it is a complete architecture for developing Web sites and
Internet-distributed objects using managed code. Both Web Forms and XML Web
services use IIS and ASP.NET as the publishing mechanism for applications, and both
have a collection of supporting classes in the .NET Framework.
XML Web services, an important evolution in Web-based technology, are
distributed, server-side application components similar to common Web sites.
However, unlike Web-based applications, XML Web services components have no UI
and are not targeted for browsers such as Internet Explorer and Netscape Navigator.
Instead, XML Web services consist of reusable software components designed to be
consumed by other applications, such as traditional client applications, Web-based
applications, or even other XML Web services. As a result, XML Web services
technology is rapidly moving application development and deployment into the highly
distributed environment of the Internet.
If you have used earlier versions of ASP technology, you will immediately
notice the improvements that ASP.NET and Web Forms offers. For example, you can
develop Web Forms pages in any language that supports the .NET Framework. In
addition, your code no longer needs to share the same file with your HTTP text
(although it can continue to do so if you prefer). Web Forms pages execute in native
machine language because, like any other managed application, they take full
advantage of the runtime. In contrast, unmanaged ASP pages are always scripted and
interpreted. ASP.NET pages are faster, more functional, and easier to develop than
unmanaged ASP pages because they interact with the runtime like any managed
application.
The .NET Framework also provides a collection of classes and tools to aid in
development and consumption of XML Web services applications. XML Web
23
services are built on standards such as SOAP (a remote procedure-call protocol),
XML (an extensible data format), and WSDL (the Web Services Description
Language). The .NET Framework is built on these standards to promote
interoperability with non-Microsoft solutions.
For example, the Web Services Description Language tool included with
the .NET Framework SDK can query an XML Web service published on the Web,
parse its WSDL description, and produce C# or Visual Basic source code that your
application can use to become a client of the XML Web service. The source code can
create classes derived from classes in the class library that handle all the underlying
communication using SOAP and XML parsing. Although you can use the class
library to consume XML Web services directly, the Web Services Description
Language tool and the other tools contained in the SDK facilitate your development
efforts with the .NET Framework.
If you develop and publish your own XML Web service, the .NET Framework
provides a set of classes that conform to all the underlying communication standards,
such as SOAP, WSDL, and XML. Using those classes enables you to focus on the
logic of your service, without concerning yourself with the communications
infrastructure required by distributed software development.
Finally, like Web Forms pages in the managed environment, your XML Web
service will run with the speed of native machine language using the scalable
communication of IIS.
ASP.NET
ASP.NET is a programming framework built on the common language
runtime that can be used on a server to build powerful Web applications. ASP.NET
offers several important advantages over previous Web development models:
Enhanced Performance. ASP.NET is compiled common language
runtime code running on the server. Unlike its interpreted predecessors, ASP.NET
can take advantage of early binding, just-in-time compilation, native optimization,
and caching services right out of the box. This amounts to dramatically better
performance before you ever write a line of code.
24
World-Class Tool Support. The ASP.NET framework is complemented by a
rich toolbox and designer in the Visual Studio integrated development
environment. WYSIWYG editing, drag-and-drop server controls, and automatic
deployment are just a few of the features this powerful tool provides.
Power and Flexibility. Because ASP.NET is based on the common language
runtime, the power and flexibility of that entire platform is available to Web
application developers. The .NET Framework class library, Messaging, and Data
Access solutions are all seamlessly accessible from the Web. ASP.NET is also
language-independent, so you can choose the language that best applies to your
application or partition your application across many languages. Further, common
language runtime interoperability guarantees that your existing investment in
COM-based development is preserved when migrating to ASP.NET.
Simplicity. ASP.NET makes it easy to perform common tasks, from simple
form submission and client authentication to deployment and site configuration.
For example, the ASP.NET page framework allows you to build user interfaces
that cleanly separate application logic from presentation code and to handle events
in a simple, Visual Basic – like forms processing model. Additionally, the
common language runtime simplifies development, with managed code services
such as automatic reference counting and garbage collection.
Manageability. ASP.NET employs a text-based, hierarchical configuration
system, which simplifies applying settings to your server environment and Web
applications. Because configuration information is stored as plain text, new
settings may be applied without the aid of local administration tools. This “Zero
local administration” philosophy extends to deploying ASP.NET Framework
applications as well. An ASP.NET Framework application is deployed to a server
simply by copying the necessary files to the server. No server restart is required,
even to deploy or replace running compiled code.
25
Scalability and Availability. ASP.NET has been designed with scalability in
mind, with features specifically tailored to improve performance in clustered and
multiprocessor environments. Further, processes are closely monitored and
managed by the ASP.NET runtime, so that if one misbehaves (leaks, deadlocks), a
new process can be created in its place, which helps keep your application
constantly available to handle requests.
Customizability and Extensibility. ASP.NET delivers a well-factored
architecture that allows developers to “plug-in” their code at the appropriate level.
In fact, it is possible to extend or replace any subcomponent of the ASP.NET
runtime with your own custom-written component. Implementing custom
authentication or state services has never been easier.
Security. With built in Windows authentication and per-application
configuration, you can be assured that your applications are secure.
Language Support
The Microsoft.NET Platform currently offers built-in support for three
languages: C#, Visual Basic, and JScript. What is ASP.NET Web Forms?
The ASP.NET Web Forms page framework is a scalable common language
runtime programming model that can be used on the server to dynamically generate
Web pages.
Intended as a logical evolution of ASP (ASP.NET provides syntax
compatibility with existing pages), the ASP.NET Web Forms framework has been
specifically designed to address a number of key deficiencies in the previous model.
In particular, it provides:
The ability to create and use reusable UI controls that can encapsulate
common functionality and thus reduce the amount of code that a page
developer has to write.
The ability for developers to cleanly structure their page logic in an orderly
fashion (not “spaghetti code”).
26
The ability for development tools to provide strong WYSIWYG design
support for pages (existing ASP code is opaque to tools).
ASP.NET Web Forms pages are text files with an .aspx file name extension.
They can be deployed throughout an IIS virtual root directory tree. When a browser
client requests .aspx resources, the ASP.NET runtime parses and compiles the target
file into a .NET Framework class. This class can then be used to dynamically process
incoming requests. (Note that the .aspx file is compiled only the first time it is
accessed; the compiled type instance is then reused across multiple requests).
An ASP.NET page can be created simply by taking an existing HTML file and
changing its file name extension to .aspx (no modification of code is required). For
example, the following sample demonstrates a simple HTML page that collects a
user’s name and category preference and then performs a form postback to the
originating page when a button is clicked:
ASP.NET provides syntax compatibility with existing ASP pages. This
includes support for <%> code render blocks that can be intermixed with HTML
content within an .aspx file. These code blocks execute in a top-down manner at page
render time.
Code-Behind Web Forms
ASP.NET supports two methods of authoring dynamic pages. The first is the
method shown in the preceding samples, where the page code is physically declared
within the originating .aspx file. An alternative approach-known as the code-behind
method - enables the page code to be more cleanly separated from the HTML content
into an entirely separate file.
Introduction to ASP.NET Server Controls
In addition to (or instead of) using <% %> code blocks to program
dynamic content, ASP.NET page developers can use ASP.NET server controls to
program Web pages. Server controls are declared within an .aspx file using custom
tags or intrinsic HTML tags that contain a runat=”server” attribute value. Intrinsic
27
HTML tags are handled by one of the controls in the System.Web.UI.HtmlControls
namespace. Any tag that doesn’t explicitly map to one of the controls is assigned the
type of System.Web.UI.HtmlControls.HtmlGenericControl. Server controls
automatically maintain any client-entered values between round trips to the server.
This control state is not stored on the server (it is instead stored within an <input
type=”hidden”> form field that is round-tripped between requests). Note also that no
client-side script is required.
In addition to supporting standard HTML input controls, ASP.NET enables
developers to utilize richer custom controls on their pages. For example, the following
sample demonstrates how the <asp:adrotator> control can be used to dynamically
display rotating ads on a page.
1. ASP.NET Web Forms provide an easy and powerful way to build
dynamic Web UI.
2. ASP.NET Web Forms pages can target any browser client (there are
no script library or cookie requirements).
3. ASP.NET Web Forms pages provide syntax compatibility with
existing ASP pages.
4. ASP.NET server controls provide an easy way to encapsulate
common functionality.
5. ASP.NET ships with 45 built-in server controls. Developers can
also use controls built by third parties.
6. ASP.NET server controls can automatically project both uplevel
and downlevel HTML.
7. ASP.NET templates provide an easy way to customize the look
and feel of list server controls.
28
8. ASP.NET validation controls provide an easy way to do
declarative client or server data validation.
SQL SERVER
DATABASE
A database management, or DBMS, gives the user access to their data and
helps them transform the data into information. Such database management systems
include dBase, paradox, IMS, Sql Server and SQL Server. These systems allow users
to create, update and extract information from their database.
A database is a structured collection of data. Data refers to the characteristics
of people, things and events. SQL Server stores each data item in its own fields. In
SQL Server, the fields relating to a particular person, thing or event are bundled
together to form a single complete unit of data, called a record. Each record is made
up of a number of fields. No two fields in a record can have the same field name.
SQL Server Tables
SQL Server stores records relating to each other in a table. Different tables
are created for the various groups of information. Related tables are grouped together
to form a database.
Primary Key
Every table in SQL Server has a field or a combination of fields that uniquely
identifies each record in the table. The Unique identifier is called the Primary Key, or
simply the Key. The primary key provides the means to distinguish one record from
all other in a table. It allows the user and the database system to identify, locate and
refer to one particular record in the database.
Relational Database
Sometimes all the information of interest to a business operation can be
stored in one table. SQL Server makes it very easy to link the data in multiple tables.
Matching an employee to the department in which they work is one example. This is
29
what makes SQL Server a relational database management system, or RDBMS. It
stores data in two or more tables and enables you to define relationships between the
tables.
Foreign Key
When a field in one table matches the primary key of another field is referred to
as a foreign key. A foreign key is a field or a group of fields in one table whose values
match those of the primary key of another table.
Referential Integrity
Not only does SQL Server allow you to link multiple tables, it also maintains
consistency between them. Ensuring that the data among related tables is correctly
matched is referred to as maintaining referential integrity.
Data Abstraction
A major purpose of a database system is to provide users with an abstract view
of the data. This system hides certain details of how the data is stored and maintained.
Data abstraction is divided into three levels.
Physical level
This is the lowest level of abstraction describes the data storage and access
methods.
Conceptual Level
The conceptual level describes what data are stored in the database, and what
relationships exist among those data.
View Level
This is the highest level of abstraction at which one describes only part of the
database. This level simplifies the end user’s interaction with the system.
Advantages of RDBMS
Redundancy can be avoided
Inconsistency can be eliminated
Data can be Shared
Standards can be enforced
Security restrictions can be applied
30
Integrity can be maintained
Conflicting requirements can be balanced
Data independence can be achieved.
Disadvantages of DBMS
A significant disadvantage of the DBMS system is cost. In addition to the
cost of purchasing of developing the software, the hardware has to be upgraded to
allow for the extensive programs and the workspace required for their execution and
storage. While centralization reduces duplication, the lack of duplication requires that
the database be adequately backed up so that in case of failure the data can be
recovered.
FEATURES OF SQL SERVER (RDBMS)
SQL SERVER is one of the leading database management systems (DBMS)
because it is the only Database that meets the uncompromising requirements of
today’s most demanding information systems. From complex decision support
systems (DSS) to the most rigorous online transaction processing (OLTP) application,
even application that require simultaneous DSS and OLTP access to the same critical
data, SQL Server leads the industry in both performance and capability
SQL SERVER is a truly portable, distributed, and open DBMS that delivers
unmatched performance, continuous operation and support for every database.
SQL SERVER RDBMS is high performance fault tolerant DBMS which is
specially designed for online transactions processing and for handling large database
application.
SQL SERVER with transactions processing option offers two features which
contribute to very high level of transaction processing throughput, which are
The row level lock manager
Enterprise wide Data Sharing
31
The unrivaled portability and connectivity of the SQL SERVER DBMS
enables all the systems in the organization to be linked into a singular, integrated
computing resource.
Portability
SQL SERVER is fully portable to more than 80 distinct hardware and operating
systems platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of
proprietary platforms. This portability gives complete freedom to choose the database
server platform that meets the system requirements.
Open Systems
SQL SERVER offers a leading implementation of industry -standard SQL.
SQL Server’s open architecture integrates SQL SERVER and non -SQL SERVER
DBMS with industries most comprehensive collection of tools, application, and third
party software products SQL Server’s Open architecture provides transparent access
to data from other relational database and even non-relational database.
Distributed Data Sharing
SQL Server’s networking and distributed database capabilities to access data
stored on remote server with the same ease as if the information was stored on a
single local computer. A single SQL statement can access data at multiple sites. You
can store data where system requirements such as performance, security or
availability dictate.
Unmatched Performance
The most advanced architecture in the industry allows the SQL SERVER
DBMS to deliver unmatched performance.
Sophisticated Concurrency Control
Real World applications demand access to critical data. With most database
Systems application becomes “contention bound” – which performance is limited not
by the CPU power or by disk I/O, but user waiting on one another for data access.
SQL Server employs full, unrestricted row-level locking and contention free queries
to minimize and in many cases entirely eliminates contention wait times.
32
SOFTWARE REQUIREMENTS
Operating Systems : Windows NT / server 2000
Database : MS SQL Server 2000 for database on
Server.ADO.NET
GUI Tools : ASP.NET for Code, components and forms.
33
HARDWARE REQUIREMENTS
Processor : Intel Pentium or more
Ram : 256 or more
Cache : 512 KB
Hard Disk : 16 GB hard disk recommended
34
35
DATA DICTIONARY
Data dictionary consists of descriptions of all the data used in the system.
Data dictionary is a catalog, a repository of the elements in the system. The Data
dictionary is used to manage the data in large systems and to communicate a common
meaning for all system elements. The Data dictionary is used to document the features
of the system elements, system, and also to locate errors and omissions in the system.
Data dictionary contains two types of description for the data flowing
through the system: Data element and Data structure. Data Elements are used to
group together to make up the Data Structure. Data Structure is a set of data items; the
data related to one another and collectively describe a component in the system. The
description of the data elements consists of data names, data description, aliases, and
length and data values. The description of data structure consists of sequence
relationship, selection, Iteration relationship and option relationship.
Data Design for Health card Monitoring System:
TABLE NAME: RATION
Field Name Data Type Length Remarks
Ration code char 3 Primary Key
Ration name Varchar 30 Allow Null
TABLE NAME: STREET
Field Name Data Type Length Remarks
Area code char 3 Primary key, Foreign key to Area table
36
Street code char 3 Primary key
Street name varchar 30 Allow Null
TABLE NAME: FAMILY RATIONCARD HEAD DETAILS
Field Name Data Type Length Remarks
Ration card no char 10 Primary Key
Area code char 3 Foreign key to Area table
Street code char 3 Foreign key to Street table
Door no char 3 Allow Null
Owner name varchar 30 Allow Null
Family members char 2 Allow Null
Age numeric 9 Allow Null
Sex char 1 Allow Null
Relation code Char 3 Foreign key to Relation table
Relation name varchar 30 Allow Null
Profession code char 3 Foreign key to Profession table
Caste code char 3 Foreign key to Caste table
Religion code char 3 Foreign key to Religion table
Ration code char 3 Foreign key to Ration table
TABLE NAME: HEALTH CARD ISSUE
Field Name Data Type Length Remarks
Hcard no char 10 Primary Key
Rtcard no char 10 Foreign key to RCFH table
Family members char 2 Foreign key to RCFH table
Issue date Date time 8 Allow Null
Issued by Date time 8 Allow Null
Remarks varchar 30 Allow Null
TABLE NAME: HEALTH INSURANCE COVERAGE
Field Name Data
Type
Lengt
h
Remarks
Hcard no char 10 Primary Key
Rtcard no char 10 Foreign key to RCFH table
Family members char 2 Foreign key to RCFH table
Financial Year Char 4 Primary Key
Insurance amount money 8 Allow Null
37
Start Date Date time 8 Allow Null
End Date Date time 8 Allow Null
Annual Premium money 8 Allow Null
Coverage numeric 2 Allow Null
TABLE NAME: HEALTH INSURANCE HOSPITALS
FIELD NAME DATA TYPE LENGTH REMARKS
Hcode char 3 Primary key
Name Varchar 50 Null
Address Varchar 50 Null
Phone char 10 Null
E-mail varchar 30 Null
Contact Person varchar 50 Null
TABLE NAME: HEALTH INSURANCE HOSPITAL DISEASE
Field Name Data Type Length Remarks
Hospital code char 3 Primary Key & Foreign key to Hinshos table
Disease code char 3 Primary Key & Foreign key to Disease table
TABLE NAME: NON-OBJECTION CERTIFICATE
FIELD NAME DATA TYPE LENGTH REMARKS
Appno varchar 30 Primary key
Date Date time 8 Null
Rtcardno Char 10 Foreign key to Ration table
Patient name Varchar 50 Null
Address Varchar 50 Null
Sex char 1 Null
Marital status char 1 Null
Age char 2 Null
Discode Char 3 Foreign key to Disease table
Hcode Char 3 Foreign key to Hinshos table
TABLE NAME: USERMAIN
Field Name Description Data Type Constraint
USID
PASSWORD
LC CODE
User name
Password
Code
VARCHAR2 (20)
VARCHAR2 (20)
VARCHAR2 (20)
PRIMARY KEY
NOT NULL
NOT NULL
38
TABLE NAME: FINAL PAYMENT BILL
FIELD NAME DATA TYPE LENGTH REMARKS
Hcno Char 10 Primary key
Appno Char 10 Primary key
Tamt Money 8 Null
Samt Money 8 Null
Medamt Money 8 Null
Misamt Money 8 Null
Room amt Money 8 Null
Jdate Date time 8 Null
DisDate Date time 8 Null
Totalamt Money 8 Null
TABLE NAME: HEALTHINSURANCE HOSPITAL STATUS
Field Name Data Type Length Constraint
Hospital Code
Financial Year
Start Date
End Date
char
int
datetime
datetime
3
4
8
8
PRIMARY KEY, Foreign Key to HInsHosp
NOT NULL
NOT NULL
NOT NULL
TABLE NAME: CORPORATE HOSPITAL PAYMENT BILL
Column Name Data Type Length Constraints
HcardNo char 3Primary Key,
Foreign Key, References(hcard)
NocNo char 3 Foreign Key, References(noc)
TAmt money 8 Not null
SgAmt money 8 Not null
MedAmt money 8 Not null
MisAmt money 8 Not null
RoomAmt money 8 Not null
JDate datetime 8 Not null
DisDate datetime 8 Not null
TotalAmt money 8 Not null
39
MODULE DESCRIPTION
USER VIEW FOR MODULE – 1
ADMINISTROR
Collection of Details
Verification
Authorization
Updates Database
40
USER VIEW FOR MODULE – 2
Verifies Rtcard Details
Photo Capturing
HCard Issue
Manages Insurance Money
41
Manages Renewals & New Entries
Updates Database
Administrator
Citizen
USER VIEW FOR MODULE – 3
Selects Insurance Company
Gives details of HCard holders
Coverage
Administrator
42
Insurance Amount
Updates Database
USER VIEW FOR MODULE – 4
USER VIEW FOR MODULE – 5
Selects CH/ SSH
PatientCareAdministrationnn
Clinical Services
PatientCare Services
ADMINSTRATOR
43
Financial Mgmt
Updates Database
Queries
Users Users
DATABASE DESIGN
UML
UML stands for Unified Modeling Language developed by Grady Booch,
James Rumbaugh, and Ivar Jacobson of Rational Corporation in 1996. It is a standard,
modeling language used for modeling software systems of varying complexities. It is
used to understand design, configure, maintain and control information about systems.
UML is a notation that resulted from the unification of OMT and OOSE.
Diagrams are used to represent multiple views of a system. The multiple views of the
system together represent the model of the system.
The five fundamental notations of UML are:
1. Use case Diagrams
2. Class Diagrams
3. Sequence Diagrams
4. State chart Diagrams
5. Activity Diagram
Use case diagrams: Use case diagrams are used during requirements elicitation and
analysis to represent the functionality of the system. Use cases focus on the behavior
of the system from an external point of view.
Class diagrams: Class diagrams are used to describe the structure of system. Classes
are abstractions that specify the common structure and behavior of a set of objects.
Objects are the instances of classes.
Sequence diagrams: Sequence diagrams are used to formalize the behavior of the
system and to visualize the communication among objects. They are useful for
identifying additional objects that participate in the use cases.
State chart diagrams: State chart diagrams describe the behavior of an individual
objects as a number of states and transitions between these states. A state represents a
particular set of values for an object.
Activity diagrams: An activity diagram describes a system in terms of activities.
Activities are states that represent the execution of a set of operations. The completion
of these operations triggers a transition to another activity.
44
USECASE DIAGRAMS:
45
USE CASE DIAGRAM FOR CITIZEN:
46
USE CASE DIAGRAM FOR GOVERNMENT OF PONDICHERRY:
47
SEQUENCE DIAGRAM
48
State Diagram
49
Citizen enters Govt.With rtcard
Govt. verifies rtcard
Rt details correct
Issues health card
Y N
Activity Diagram for Health Card Issue
Chronic disease
Issues NOC
Y N
Activity Diagram for Issue of NOC
Citizen enters GGH with Health card
GGH tests the severityOf disease
DATA NORMALIZATION
50
Normalization of data can be defined as a process of analyzing the given relational
schemas based on functional dependencies (FD) and primary keys
The most popular and most widely used are:
First normal form
Second normal form
Third normal form
Boyce codd normal form
Fourth normal form
Fifth normal form
First Normal Form:
A relation R is said to be in first normal form (1 NF) if and only if all
underlying domain contain atomic values only.
Second Normal Form:
A relation R is said to be in second normal form if and only if it is in
1NF and every non-key attribute is fully dependent on the primary key.
Third Normal Form:
A relation is in third normal form (3NF) if and only if it is in second normal
form and e very non-key attribute is non-transitively dependent on the primary key.
Boyce-codd Normal Form:
A relation is in Boyce-codd normal form (BCNF) if and if every
determinant is a candidate key.
Fourth Normal Form:
A relation R is in fourth normal form if and only if wherever there
exists a multi-valued dependency in R, say A -> B, then attributes of R also
functionally dependent on A.
Fifth Normal Form:
A relation R is in fifth Normal form if and only if the candidate keys
of R imply every join dependency in R.
51
In my module I have normalized the tables up to 3rd normal form. In
the first normal form I have identified all the non-atomic or divisible fields and
decomposed them into atomic and indivisible fields. In the second normal form I have
identified all the composite primary keys and checked whether every non-key
attribute is fully functionally dependant on the composite primary key but not
dependant on any individual field. In the third normal form I have checked whether
every non key attribute is non transitively dependant on the primary key.
ENTITY- RELATION DIAGRAMS:
RATION
CASTE
has
RELIGION
has
has
PROFESSION
rationrtcode area
Owner name
Family members
street
religioncaste
sex
age
profession
pfcode pfname
ctcode ctname relicode reliname
52
HEALTH INSURANCE
has
HCARD
Issued by remarks
hcnoIssue date
hcard
End date
Annual premium
hcardnoFinancial year
Insurance amount
Start date
NOC
has
HINS DISEASE
has
HINS HOSP
Application no
date
Hins hospitals
rtno
Hins disease
address
Patient name
hcode
name
address phoneE-mail
contact
hcode dscode
53
TESTING
54
Introduction:
Testing is one of the most important phases in the software
development activity. In software development life cycle (SDLC), the main aim of
testing process is the quality; the developed software is tested against attaining the
required functionality and performance.
The success of the testing process in determining the errors is mostly
depends upon the test case criteria, for testing any software we need to have a
description of the expected behavior of the system and method of determining
whether the observed behavior confirmed to the expected behavior.
Levels of Testing:
Since the errors in the software can be injured at any stage. So, we
have to carry out the testing process at different levels during the development.
The basic levels of testing are Unit, Integration, System and Acceptance Testing.
The Unit Testing is carried out on coding. Here different modules are
tested against the specifications produced during design for the modules. In case
of Integration Testing, different tested modules are combined into sub systems and
tested; In case of the System Testing, the full software is tested and in the next
level of testing (Acceptance Testing) the system is tested with user requirement
document prepared during SRS.
There are two basic approaches for testing. They are
1) Functional Testing
2) Structural Testing
Functional Testing:
In Functional Testing test cases are decided solely on the basis of
requirements of the program or module and the internals of the program or modules
are not considered for selection of test cases. This is also called Black Box Testing.
Structural Testing:
In Structural Testing test cases are generated on actual code of the program or
module to be tested. This is called White Box Testing.
TESTCASE SPECIFICATION
55
Sno Test cases Condition checked Output
1
Invalid login or password Check for the logins or
passwords.
Print different an appropriate
error message for login error and
password each.
2
Invalid RTCARDNO with
less than or greater than
10 digits.
Check the length of the
entered RTCARD.
Give error message and ask for
reentry
3
Verify RTCARDNO to issue
HCARD
Check the format of the
entered RTCARDNO
HCARDNO.
Give error message and ask for
reentry
4.
Verify RTCARDNO and
HCARDNO to issue NOC
Check the length of the
entered RTCARD and HCARD
no’s.
Give error message and ask for
reentry
5
Verify HCARDNO and NOC
for final billing
1) Check for validity of dates.
They should not be greater
than system date.
2) From date should not be
greater than to date.
Give error message and ask for
reentry.
ERROR REPORT
The error report gives the summary of all errors found. Some sample errors:
Sno Error Action taken
1Date entered is greater than
system date. Fixed.
2From date is greater that to
date.Fixed
3
Family number contains
some characters not totally
digits
Fixed.
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
86
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
public partial class hcard : System.Web.UI.Page
{
SqlCommand sqlcom;
SqlConnection sqlcon;
Int32 i;
String comstr,rno, arcode, fam;
SqlDataReader sqlrdr;
SqlDataAdapter sqlada;
DataSet ds;
protected void Page_Load(object sender, EventArgs e)
{
// Response.Write("hai ");
Connect();
if (Page.IsPostBack == false)
{
getAllAreaDetails();
showGrid1();
}
}
private void clearall()
{
TextBox1.Text = "";
TextBox2.Text = "";
TextBox3.Text = "";
TextBox4.Text = "";
}
protected void getAllAreaDetails()
{
comstr = "select * from area";
sqlcom = new SqlCommand(comstr, sqlcon);
sqlrdr = sqlcom.ExecuteReader();
DropDownList1.Items.Clear();
DropDownList1.Items.Add("Select Area");
if (sqlrdr.HasRows)
87
{
Response.Write("Data available");
while (sqlrdr.Read())
{
DropDownList1.Items.Add(sqlrdr.GetString(0) + "-" +
sqlrdr.GetString(1));
}
}
else
{
Response.Write("no data available");
}
sqlrdr.Close();
sqlcom.Dispose();
}
protected void getAllRcfhDetails()
{
arcode = DropDownList1.SelectedItem.ToString().Substring(0,
3);
comstr = "select * from rcfh1 where arcode='" + arcode + "'";
sqlcom = new SqlCommand(comstr, sqlcon);
sqlrdr = sqlcom.ExecuteReader();
DropDownList2.Items.Clear();
DropDownList2.Items.Add("Select CARD");
if (sqlrdr.HasRows)
{
while (sqlrdr.Read())
{
DropDownList2.Items.Add(sqlrdr.GetString(0) );
}
}
else
{
Response.Write("no data available");
}
sqlrdr.Close();
sqlcom.Dispose();
}
88
protected void getAllRcMemDetails()
{
rno = DropDownList2.SelectedItem.ToString();
arcode = DropDownList1.SelectedItem.ToString().Substring(0,
3);
comstr = "select * from rcfh1 where arcode='" + arcode + "'
and rtcardno='"+rno+"'";
// Response.Write(comstr);
sqlcom = new SqlCommand(comstr, sqlcon);
sqlrdr = sqlcom.ExecuteReader();
DropDownList3.Items.Clear();
DropDownList3.Items.Add("Select Member");
if (sqlrdr.HasRows)
{
while (sqlrdr.Read())
{
DropDownList3.Items.Add(sqlrdr.GetString(5)+"-"+sqlrdr.GetString(4));
}
}
else
{
//Response.Write("no data available");
}
sqlrdr.Close();
sqlcom.Dispose();
}
private void Connect()
{
comstr = "data source='madhu';uid=sa;pwd=madhu;initial
catalog='shalini';";
sqlcon = new SqlConnection(comstr);
sqlcon.Open();
// Response.Write("Connected");
}
protected void showGrid()
{
arcode = DropDownList1.SelectedItem.ToString().Substring(0,
3);
rno = DropDownList2.SelectedItem.ToString();
fam = DropDownList3.SelectedItem.ToString().Substring(0, 2);
89
comstr = "select * from rcfh1 where arcode='" + arcode + "'
and rtcardno='" + rno + "' and familymem='" + fam + "'";
// Response.Write(comstr);
sqlada = new SqlDataAdapter(comstr, sqlcon);
ds = new DataSet();
sqlada.Fill(ds, "rcfh1");
GridView1.DataSource = ds;
GridView1.DataMember = "rcfh1";
GridView1.DataBind();
sqlada.Dispose();
}
protected void showGrid1()
{
comstr = "select * from hcard";
// Response.Write(comstr);
sqlada = new SqlDataAdapter(comstr, sqlcon);
ds = new DataSet();
sqlada.Fill(ds, "hcard");
GridView2.DataSource = ds;
GridView2.DataMember = "hcard";
GridView2.DataBind();
}
protected void Button2_Click(object sender, EventArgs e)
{
rno = DropDownList2.SelectedItem.ToString();
arcode = DropDownList1.SelectedItem.ToString().Substring(0,
3);
fam = DropDownList3.SelectedItem.ToString().Substring(0, 2);
comstr = "insert into hcard values('" +TextBox1.Text + "','"
+rno+"','"+fam+"','"+ TextBox2.Text + "','" + TextBox3.Text +
"','"+TextBox4.Text+"')";
// Response.Write(comstr);
sqlcom = new SqlCommand(comstr, sqlcon);
i = sqlcom.ExecuteNonQuery();
if (i > 0)
Response.Write("successfully inserted");
else
Response.Write("failed to insert");
sqlcom.Dispose();
showGrid1();
// getAllAreaDetails();
90
// getAllRcfhDetails();
}
protected void Button4_Click(object sender, EventArgs e)
{
rno = DropDownList2.SelectedItem.ToString();
arcode = DropDownList1.SelectedItem.ToString().Substring(0,
3);
fam = DropDownList3.SelectedItem.ToString().Substring(0, 2);
comstr = "delete from hcard where hcno='"+TextBox1.Text+"'";
sqlcom = new SqlCommand(comstr, sqlcon);
i = sqlcom.ExecuteNonQuery();
if (i > 0)
Response.Write("successfully deleted");
else
Response.Write("failed to delete");
sqlcom.Dispose();
clearall();
showGrid1();
// getAllAreaDetails();
// getAllRcfhDetails();
}
protected void Button5_Click(object sender, EventArgs e)
{
comstr = "select * from hcard where hcno='" + TextBox1.Text +
"'";
sqlcom = new SqlCommand(comstr, sqlcon);
sqlrdr = sqlcom.ExecuteReader();
if (sqlrdr.HasRows)
{
sqlrdr.Read();
TextBox2.Text = sqlrdr.GetSqlDateTime(3).ToString();
TextBox3.Text = sqlrdr.GetString(4);
TextBox4.Text = sqlrdr.GetString(5);
}
else
{
Response.Write("no data is vailable");
}
sqlrdr.Close();
sqlcom.Dispose();
91
}
protected void Button6_Click(object sender, EventArgs e)
{
clearall();
}
protected void Button1_Click(object sender, EventArgs e)
{
showGrid();
}
protected void DropDownList1_SelectedIndexChanged(object sender,
EventArgs e)
{
arcode = DropDownList1.SelectedItem.ToString().Substring(0,
3);
getAllRcfhDetails();
}
protected void DropDownList2_SelectedIndexChanged(object sender,
EventArgs e)
{
rno = DropDownList2.SelectedItem.ToString();
getAllRcMemDetails();
}
protected void GridView1_SelectedIndexChanged(object sender,
EventArgs e)
{
showGrid();
}
protected void GridView2_SelectedIndexChanged(object sender,
EventArgs e)
{
showGrid1();
}
protected void DropDownList3_SelectedIndexChanged(object sender,
EventArgs e)
{
fam = DropDownList3.SelectedItem.ToString().Substring(0, 2);
}
protected void Button3_Click1(object sender, EventArgs e)
{
rno = DropDownList2.SelectedItem.ToString();
92
arcode = DropDownList1.SelectedItem.ToString().Substring(0,
3);
fam = DropDownList3.SelectedItem.ToString().Substring(0, 2);
comstr = "update hcard set rtcardno='" + rno +
"',familymem='" + fam + "',isdt='" + TextBox2.Text + "',isby='" +
TextBox3.Text + "',remarks='" + TextBox4.Text + "' where hcno='" +
TextBox1.Text + "'";
sqlcom = new SqlCommand(comstr, sqlcon);
i = sqlcom.ExecuteNonQuery();
if (i > 0)
Response.Write("successfully updated");
else
Response.Write("failed to update");
sqlcom.Dispose();
clearall();
showGrid1();
}
}
93
CONCLUSION
94
This Health Insurance Card Monitoring System serves as the basement
for good treatment to the people under Below Poverty Line (BPL). This package with
its amicable Graphical User Interface (GUI) is bound to add governments proper
functioning and its Health Insurance activities. With the use of advanced tools like
ADO.NET, it is compatible with any backend. Also, ADO.NET provides greater
XML support, easier disconnected data access, more control over updates, and greater
update flexibility as compared to other data access technologies.
Since this project is first of its kind, it needs to be updated frequently
and constant monitoring should be there for the successful implementation. The
government should take measures for the implementations of the project. The
government should take steps to make public aware and familiar with the
AROGYASRI (Health Insurance Card).The government should act very strictly in
scrutinizing the Ration Card Details before issuing the Health Card to the citizens.
The government should use the data stored in the Internet Information Server (IIS) to
carry out any development programs. This should be developed as a Web application
project.
I hope this will become successful and will become a model to all
regions in Pondicherry.
95
BIBLIOGRAPHY
Books:
1. ASP.NET
by Evangeleous
96
2. Microsoft Developer Network
MSDN library
3. SQL Server Help
4. Object Oriented Software Engineering
Bernd Bruegge and Allen H.Dutoit
5. Software Engineering
Roger S. Pressman
6. Database Concepts
Henry.F.Korth
7. System Analysis and Design
I.T.Hawryszkiewycz
WEBLIOGRAPHY
Websites
http://www.msdn.microsoft.com
http://www.google.com
97
http://www.kyapoocha.com
E-books
Material present in CD provided by Microsoft Training Program.
98