AUTO

CONTENTS
S.NO CONTENTS PAGE
1 SYNOPSIS 1
2 SYSTEM CONFIGURATION 5
A.HARDWARE CONFIGURATION
B.SOFTWARE CONFIGURATION
3 SOFTWARE DESCRIPTION 6
4 DATAFLOW DIAGRAM 25
5 TABLE DESIGN 33
6 PROJECT DESCRIPTION 40
7 SAMPLE SOURCE CODE 42
8 SCREEN DESIGN 67
9 SYSTEM ANALYSIS 95
10 SYSTEM TESTING 98
11 CONCLUSION 106
12 BIBLIGRAPHY 108
SYNOPSIS
1
SYNOPSIS
Automated Employee Information System (AEIS) is
a scheduling program for people and tasks. It is easy to move and edit tasks right on
the screen. There are several displays that allow you to see your schedule over
different periods, such as rotation and payroll periods. You can copy or delete days
of tasks to quickly build new schedules. When a schedule has been created you can
copy them to your web site for all too easily see.
Seed dates are used as starting points. There are two seed dates that
control the weekly, rotation and payroll schedules the work date in the seed date is
used to find the day of the week the weekly schedule starts and a date that began a
rotation. The program will work forward from this date to keep track of where you
are in a rotation. The other seed date is for the payroll period .The payroll seed date
should be a date from the past on which a payroll period started .The schedule
displays show one day, a week, a rotation, or a payroll period . The rotation schedule
displays all tasks in a user defined rotation period.
The rotation periods start from a seed date. If a group has been
selected, only the individuals qualified for tasks in that group will appear. The payroll
schedule displays the tasks for a payroll period. Like the other schedules the payroll
schedule display will show the payroll period that the current date falls in .The payroll
period and the date the payroll starts is selected on the configuration screen. The
payroll period starts and ends on the dates defined on the configuration screen. The
user can select a seed date and an optional payroll period.
2
INTRODUCTION
3
INTRODUCTION
The purpose of this software specification (SS) is to
establish the major requirements & Specification necessary to develop the Software
Systems for the Developers. The overall objective of the Team Project is to establish a
web-based. The goal of this document is the same as any requirements document, to
lie out all requirements of the application in order to have both the developers and the
end users maintaining the same understanding and expectations from the application.
The project requirements will define, in general terms, the setup of the web site,
topics for available information concerning the Software Project Management.
SCOPE:
This Insurance Claims & Management System
Is a web Based application for Horizon Technologies for updating the claims of their
employees. Horizon is going to give the other processors and maintain the site.
4
SYSTEM CONFIGURATION
HARDWARE REQUIREMENTS
Processor : Pentium
Speed : 3.0 GHZ
RAM : 512 MB
Hard disk : 40 GB
Mouse : Optical scroll mouse
Keyboard : Internet keyboard, 104 keys
SOFTWARE REQUIREMENTS
Operating System : Windows XP
Front-End : ASP .NET
Back-End : SQL Server 2000
Web Server : IIS
Web Browser : Internet Explorer 6.0 Version
Documentation : MS-Word
5
SOFTWARE DESCRIPTION
6
.NET
The.NET frame work is the last platform from Microsoft and it provides a
multi language environment that enables you to develop deploy, and run web based
applications and services. It provides a new level of interoperability that enables you
to reuse components created in other language. It also provides new and advanced
features such as garbage collection and enhanced security. This chapter examines the
components of the .NET framework.
COMPONENTS OF THE .NET FRAMEWORK:
The .NET framework is composed of classes and service

That forms a layer between applications and the operating system. It consists of the
following two main components.
 Common language runtime (CLR)
 .NET framework class library
COMMON LANGUAGE RUNTIME:

The CLR is the runtime environment of the .NET framework. CLR
provides a common set of services such as exception handling, security, and
debugging to languages that are CLR compatible. All programming language in visual
studio.NET such as visual basic .NET and visual c# .NET supports the CLR
During the execution of a program, the CLR controls the
Interaction of code with the operating system .code that is executed by the CLR is
known as managed code. In contrast, code that is not executed by the CLR is known
as unmanaged code. Managed code ―cooperates ―with the CLR by providing metadata
to the CLR. The CLR, in turn .provides services, such as garbage collection,
unmanaged code can by pass the .NET framework API and make direct calls to the
operating system
7
.NET Framework Class Library:
The .NET Framework class library includes

multiple reusables, object-oriented, and extensible classes. It is integrated with the
CLR and is common to all programming language in visual studio .NET.
The .NET framework class library provides a common set of
classes across programming languages. While developing applications, you can use
the classes in the .NET framework class library to develop applications and
implements cross-language inheritance.
The classes in the .NET framework class library are organized
hierarchically. In the .NET framework library, the system namespace is at the top of
the hierarchy and contains all other classes. On a broad level, the system namespace
contains classes that enable you to perform the following tasks.
 Converting data types
 Manipulation parameters
 Invoking local and remote programs
 Managing the application
.NET is the Microsoft web services strategy to connect information

.people, systems, and devices through software .integrated across the Microsoft
platform, .NET technology provides the ability to quickly build, deploy, manage, and
use connected, security –enhanced solutions with web services. .NET-connected
solutions enable businesses to integrate their systems more rapidly and in a more agile
manner and help they realize the promise of anytime, anywhere, on any device
The Microsoft platform includes everything a business needs to

develop and deploy a web service –connected IT architecture .servers to host web
services .Development tools to create them applications to use them and a worldwide
network of more than 35000 Microsoft certified partner organizations to provide any
help you need.
8
WHAT ARE WEB SERVICES?
If you ask a developer what web services are? You‘ll hear

something like. ―Self –describing software modules, semantically encapsulating
discrete functionality, wrapped in and accessible via standard internet communication
protocols like XML and SOAP
But if you ask a businesses leader who has implemented web service
–based solutions .you‘ll get a different kind of answer .you‘ll hear that web services
are an approach that helps the business connect with its customers, partners and
employees .they enable the businesses to extend existing service to new customers
.they help the businesses work more efficiently with its partners and suppliers. They
unlock information so it can flow to every employee who needs it. They reduce
development time and expense for new projects .you‘ll hear less about what web
services are and more about what they enable the business to do.
BENEFITS OF WEB SERVICES:

By enabling applications to share data across different
hardware platforms and operating systems, web services provide many benefits,
including:
 Opening the door to new businesses opportunity by
making it easy to connect with partners.
 Delivering dramatically more personal, integrated
Experiences to users through the new breed of smart devices –including PCs
 Saving time and money by cutting development
time
 Increasing revenue streams by enabling business
To easily make their own web services available to others.
9
ASP.NET
OBJECTIVES:
 Identify the components of dynamic Web Applications

 Identify the benefits of ASP.NET as a server-side scripting language.
 Identify ASP.NET in .NET Framework.
 Identify development environment of ASP.NET applications.
 Identify the features of ASP.NET
 Identify the programming models in ASP.NE
 Identify the server controls used in ASP.NET applications.
 Identify the files used in ASP.NET web applications.
COMPONENTS OF ASP APPLICATIONS:
Web Applications have both client-side components, server-side

components and both.
 Client-Side scripting enables you to develop web pages that can

Dynamically respond to user input without having to interact with a Web
Server.
 A Client-Side script helps in reducing network traffic because it does
not need to interact with a Web Server to provide dynamic response to
user input.
 Client-Side scripting speeds up the response time of a web application
by ensuring that a Web Server is not overloaded with the job of processing
the client-side script for every client.
Server-Side scripting provides dynamic content to users based on the

information stored in a remote location, such as a back-end database
10
 Server-Side scripting includes code written in server-side scripting
languages, such as Active Server Pages (ASP) and Java Server Pages(JSP)
 A Server-side script is executed on a Web Server.
 ASP .NET is a standard HTML file that contains embedded server-side

scripts.
 ASP .NET is the .NET version of ASP and is built on Microsoft .NET
Framework.
 ASP.NET applications are based on Common Language Runtime
(CLR), .NET class libraries.
 You can ensure the accessibility of .NET Framework by installing either
of the following Software components.
1. .NET Framework SDK (Software Development Kit)
2. Visual Studio.NET(VS.NET)
WORKING OF AN ASP.NET APPLICATION:

You create an ASP.NET application by using the tools integrated with
the Microsoft .NET Framework. After the application is developed, the
ASP.NET files need to be stored on an IIS Server, which is the Web

Server for Windows Platform. An IIS Server processes ASP.NET files
from top to bottom and then executes the scripts. Finally the results are sent to
the Web Browser that requested the ASP.NET file.
FEATURES OF ASP.NET:
ASP .NET has the following advanced features that help develop
robust Web Applications:
 Compiled Code
 Enriched Tool Support
 Power and Flexibility
 Simplicity
 Manageability
 Scalability
 Security
11
ASP .NETCONFIGURATION:
Explains the flexible yet powerful ASP.NET text based

configuration system and its requirements.
ASP.NET configuration system features an extensible infrastructure

that enables you to define configuration settings at the time your Asp .Net
applications are first deployed so that you can add or revise configuration settings at
any time with minimal impact on operational web applications and servers.
The ASP.NET configuration system provides the following benefits:
Configuration information is stored in XML based text files. You can

use any standard text editor or XML parser to create and edit ASP.NET
configuration files.
Multiple Configuration files, all named Web.Config, can appear in
multiple directories on an ASP.NET web application server. Each Web.Config file
applies configuration settings to its own directory and all child directories below it.
Configuration files in child directory can supply configuration information in addition
to that inherited from parent directories and the child directory configuration settings
can overwrite or modify settings defined in parent directories.
At run time, ASP.NET uses the configuration information provided by
the Web.config files in a hierarchical virtual directory structure to compute a
collection of configuration settings for each unique URL resource. The resulting
configuration settings are then cached for all
Subsequent requests to a resource. Note that inheritance is defined by the incoming
request path (the URL), not the file system paths to the resources on disk. (The
physical paths).
ASP. NET detects changes to configuration files and automatically
applies new configuration settings to web resources affected by the changes. The
server does not have to be rebooted for the changes to take effect. Hierarchical
12
configuration settings are automatically recalculated and reached whenever a
configuration file in the hierarchy is changed.
The ASP.NET configuration system is extensible. You can define
new configuration parameters and write configuration section handlers to process
them.
ASP .NET protects configuration files from outside access by
configuring Internet Information Services. (IIS) to prevent direct browser access to
configuration files. HTTP access error 403 (forbidden) is returned to any browser
attempting to request a configuration file directly.
ASP.NETWEB FORMS:
Web Forms consist of a user Interface and Programming logic that is

applied to the components of User Interfaces. ASP.NET Web forms have the
following advantages over other technologies.
Web Forms can be designed and programmed using Rapid
Application Development (RAD) tools.
Web Forms support a rich set of controls, including User-defined and
third party controls that make the application more user-friendly.
Web Forms can be programmed using any of the .NET Framework
languages, such as C# or Visual Basic .NET.
SERVER CONTROLS IN ASP.NET:
ASP .NET server Controls work within the ASP.NET

Framework. As soon as the client requests a web page, ASP .NET converts these
controls into HTML elements.
Which are displayed in the browser? These controls use the

client-side script that ASP.NET automatically generates to alert the server whenever
any event occurs. The code written for these controls are executed at the server-end.
13
The base class of all server controls is the Control Class that
resides in the System Web UI namespace.
VALIDATION SERVER CONTROL:
Validation Server Controls is used to validate user-input. If the

user-input does not pass validation, it will display an error message to the user. Each
Validation control performs a specific type of validation (like validating
against a specific value or a range of values).
By default, page validation is performed when a Button, Image Button or
Link Button control is clicked. You can prevent validation when a button control is
clicked by setting the CausesValidationProperty to false.
14
ADO.NET
ADO.NET provides consistent access to data sources

such as Microsoft SQL Server, as well as data sources exposed via OLE DB and
XML. Data-sharing consumer applications can use ADO.NET to connect to

these data sources and retrieve, manipulate, and update data.
ADO.NET cleanly factors data access from data manipulation into discrete
components that can be used separately or in tandem. ADO.NET includes .NET data
providers for connecting to a database, executing commands, and retrieving results.
Those results are either processed directly, or placed in an ADO.NET Dataset object
in order to be exposed to the user in an ad-hoc manner, combined with data from
multiple sources, or remote between tiers. The ADO.NET Dataset object can also be
used independently of a .NET data provider to manage data local to the application or
sourced from XML.
The ADO.NET classes are found in System.Data.dll, and are integrated with
the XML classes found in System.Xml.dll. When compiling code that uses the
System. Data namespace, reference both System.Data.dll and System.Xml.dll. For an
example of compiling an ADO.NET application using a command line compiles.
ADO.NET provides functionality to developers writing managed code similar

to the functionality provided to native COM developers by ADO.
DESIGN GOAL FOR ADO.NET:

DATASET CLASS:
As application development has evolved, new applications

have become loosely coupled based on the Web application model. More and more of
15
today's applications use XML to encode data to be passed over network connections.
Web applications use HTTP as the fabric for communication between tiers, and
therefore must explicitly handle maintaining state between requests. This new model
is very different from the connected, tightly coupled style of programming that
characterized the client/server era, where a connection was held open for the duration
of the program's lifetime and no special handling of state was required.
In designing tools and technologies to meet the needs of today's developer,

Microsoft recognized that an entirely new programming model for data access was
needed, one that is built upon the .NET Framework. Building on the .NET Framework
ensures that the data access technology would be uniform components would share a
common type system, design patterns, and naming conventions.
ADO.NET was designed to meet the needs of this new

programming model: disconnected data architecture, tight integration with XML,
common data representation with the ability to combine data from multiple and varied
data sources, and optimized facilities for interacting with a database, all native to the
.NET Framework.
LEVERAGE CURRENT ADO KNOWLEDGE:
The design for ADO.NET addresses many of the requirements of

today's application development model. At the same time, the programming model
stays as similar as possible to ADO, so current ADO developers do not have to start
from the beginning in learning a brand new data access technology. ADO.NET is an
intrinsic part of the .NET Framework without seeming completely foreign to the ADO
programmer.
ADO.NET coexists with ADO. While most new .NET-based

applications will be written using ADO.NET, ADO remains available to the .NET
programmer through .NET COM interoperability services.
16
SUPPORT THE N-TIER PROGRAMMING MODEL:
ADO.NET provides first-class support for the disconnected, n-tier

programming environment for which many new applications are written. The concept
of working with a disconnected set of data has become a focal point in the
programming model. The ADO.NET solution for n-tier programming is the Dataset.
INTEGRATE XML SUPPORT:
XML and data access are intimately tied — XML is

all about encoding data, and data access is increasingly becoming all about XML. The
.NET Framework does not just support Web standards — it is built entirely on top of
them.
XML support is built into ADO.NET at a very fundamental level.

The XML classes in the .NET Framework and ADO.NET are part of the same
architecture — they integrate at many different levels. You no longer have to choose
between the data access set of services and their XML counterparts; the ability to
cross over from one to the other is inherent in the design of both.
17
VBSCRIPT
Perhaps the most important difference between these two scripting

languages is the extent to which they rely on objects. As you have seen, JavaScript is
a strongly object-based language that relies on objects and their attendant methods
and properties for a great deal of its functionality. In contrast VBScript – at least in its
current incarnation—relies much less upon objects and much more on built-in
functions. To illustrate, let‘s take a quick look at how these two languages deal with
strings.
JavaScript has the built-in string object. Whatever text data exists in a
JavaScript program -– for example, in a named variable -– a string object
automatically exists. You can then use this object‘s methods and properties to
manipulate and obtain information about the string. The following JavaScript code
creates a variable named buffer and loads it with the text "JavaScript."
Val buffer = "java script"
Now, you can use the strings object‘s length property to determine the length
of the text:
Len = buffer. Length
Similarly, you can call upon the string object‘s char at () method to extract a
single character from a specified position in the string:
Char = buffer.charAt (5)
VBScript permits the same types of string operations, but uses built-in
functions instead. Here is the VBScript code to create a variable and initialize it to
"VBScript":
Dimbuffer
Buffer = "vbscript"
To obtain the length of the string, call the Len () function:
Length = Len (buffer)
Likewise, to extract a single character from the string, we use the mid ()
function:
Char = mid (buffer, 5, 1)
18
Is one approach better than the other? You will hear a lot of programmers
preach the object-oriented gospel, claiming that any programming technique that is
object-based is automatically superior to anything else. In certain programming
situations, much can be said for this point of view. In the case of scripting languages,
however, it does not necessarily hold true.
Indeed, object-oriented programming languages are superior for large,
complex programming tasks. If I were writing a sophisticated statistical analysis
program, I would tend to choose an object-oriented language such as C++ over a non
object-oriented language, such as FORTRAN. However, for the small, relatively
simple programs JavaScript and VBScript were designed to create, the benefits of
object-orientation largely fade away. At the very least, the benefits are offset by the
greater complexity of thinking in objects. For most rapid development tasks on web
sites, JavaScript's object flavor does not convey a telling advantage.
THE STRUCTURE OF VBSCRIPT PROGRAM:
In many ways a VBScript program is like a JavaScript program, at

least in terms of how it fits in an HTML file. Procedures, defined as discreet blocks of
code that have been assigned a name, are placed in the file header, the section
between the <HEAD> and </HEAD> tags. Other non-procedure code is placed in the
file body. Also, VBScript code must be enclosed in HTML comment tags to prevent it
from being displayed in browsers that do not support VBScript.
19
FEATURES OF SQL SERVER 2000
INTERNET INTEGRATION:
The SQL Server 2000 database engine includes integrated

XML support. It also has the scalability, availability, and security features required to
operate as the data storage component of the largest Web sites. The SQL Server 2000
programming model is integrated with the Windows DNA architecture for developing
Web applications, and SQL Server 2000 supports features such as English Query and
the Microsoft Search Service to incorporate user-friendly queries and powerful search
capabilities in Web applications.
SCALABILITY AND AVAILABILITY:
The same database engine can be used across platforms ranging from
laptop computers running Microsoft Windows® 98 through large, multiprocessor
servers running Microsoft Windows 2000 Data Center Edition. SQL Server 2000
Enterprise Edition supports features such as federated servers, indexed views, and
large memory support that allow it to scale to the performance levels required by the
largest Web sites.
ENTERPRISE-LEVEL DATABASE FEATURES:
The SQL Server 2000 relational database

engine supports the features required to support demanding data processing
environments. The database engine protects data integrity while minimizing the
overhead of managing thousands of users concurrently modifying the database. SQL
Server 2000 distributed queries allow you to reference data from multiple sources as
if it were a part of a SQL Server 2000 database, while at the same time, the distributed
transaction support protects the integrity of any updates of the distributed data.
Replication allows you to also maintain multiple copies of data, while ensuring that
the separate copies remain synchronized. You can replicate a set of data to multiple,
20
mobile, disconnected users, have them work autonomously, and then merge their
modifications back to the publisher.
EASE OF INSTALLATION, DEPLOYMENT, AND USE:
SQL Server 2000 includes a set of administrative and development

tools that improve upon the process of installing, deploying, managing, and using
SQL Server across several sites. SQL Server 2000 also supports a standards-based
programming model integrated with the Windows DNA, making the use of SQL
Server databases and data warehouses a seamless part of building powerful and
scalable systems. These features allow you to rapidly deliver SQL Server applications
that customers can implement with a minimum of installation and administrative
overhead.
DATAWAREHOUSING:
SQL Server 2000 includes tools for extracting and analyzing summary data for
online analytical processing. SQL Server also includes tools for visually designing
databases and analyzing data using English-based questions.
INPUT DESIGN:
The goal of designing input data is to make data entry easy logical
and free from errors. In entering data, the user needs to know the following:
 Allocated space for each field / inputs.

 Input type, which should match that of field type.
 The format in which data is entered.
The inputs, which are given by the user, will form the core of the
processes. So the inputs have to be carefully verified and care has to be taken to avoid
incorrect end-user inputs.
21
Design has been described as a multi-step process in which
representations of data structure interface characteristics and procedural details are
synthesized from information requirements.
Design builds coherent, well planned representation of program

that concentrate on the interrelations of parts at the higher level and logical operations
involved at the lower levels.
The input design specification describes the manner in which data

enter the system from processing.
The following features have been incorporated in the input design to avoid incorrect
inputs.
 Effectiveness
 Formatted Forms
 Data Validation
 User Friendly
 Consistency
 Attractiveness
EFFECTIVENESS:
The input screens serve specific purpose. Each screen has it own server
program to back it up. The screens are developed in ASP.NET.
FORMATTED FORMS:
A formatted form is a table that requests the user to enter data in

appropriate locations. The form is showing on the screen as a unit. Spaces will be
allocated for the user to enter the needed information.
22
DATA VALIDATION:
Input data are validated to minimize error in data entry. For certain
data, validation is done which enables the operator to enter the required data or
correct the data if the entered data is incorrect. From level and field level validations
are performed. Here the input validations are done in the client side using VBScript.
USER FRIENDLY:
Appropriate messages are displayed to inform the operator of the

erroneous entry. In the proposed system the various required inputs are obtained from
the various available forms.
CONSISTENCY:
That is grouped data of similar nature together.
ATTRACTIVENESS:
The input screens are of attractive design that will surely please
the user. The software uses multiple screens rather than viewing all data into one
screen.
OUTPUT DESIGN
Output generally refers to the results and
information that are generated by the system. For many end users, output is the main
reason for developing the system the basis of which they will evaluate the usefulness
of the system, Most of the end users will not actually operate the information system
23
to enter data through workstations, but they will use the output from the system.
Usually outputs generated in a system are displayed in terms of reports and forms.
In this system developed all outputs are displayed in web pages, for example
the result of a search is displayed as structured contents on a web page. Requested
output is achieved by retrieving data from the respective tables.
24
DATAFLOW DIAGRAM
25
SYSTEM FLOW –ADMIN:
Login
User Login DBADMIN Site Admin Finance

Admin
Claims Status Claims View Claims Add Claims

View Acceptance
Claims Claims Claims Edit Prepare Pay

Register Process /Del slip
Claims
Send to Send to User
Enquiry
Finance
Home
26
Data Flow Diagram – Employee Registration:
DB Admin
Employee Details
Entry
Seq Id
Store into table
Emp_Id list
Emp_Profile
Home
27
Data Flow Diagram – Employee Login:
Employee
Employee ID
Entry
NO Check Emp ID
YES
Employee ID
Entry
Store into table
Emp_Login
Home
28
Data Flow Diagram – Claim Entry:
Employee
Claim View Check Claim Entry

Option
Store into table Claim Details

Entry
Store into Emp-Claim
Emp_claim
Home
29
Data Flow Diagram – Claim Process:
DB Admin
View EMP Claim
Emp_claim
Claim Verification
Claim_Type
IF Claim = No Set Flag as ―NOT

OK? OK‖
Yes
Set Flag as ―OK‖ Entry the Reason
Store into Emp Claim
Send to Finance Admin
Home
30
Data Flow Diagram – Claim Acceptance:
Finance Admin
Login
View Claim Details
View Claim Status Emp_Claim

from
DB Admin
Covert claim into pay

slip
Store into pay slip
Pay Slip
Home
31
Use Case Diagram:
Emp Claim
User View
Emp User Login
Claim
Claim
Entry
Status
Emp User
DB Emp
Admin Addition
Login
DB ADMIN
Claim
Claim
Verificati
Allotment
on
Financ Claim
e Login View
Finance ADMIN
Claim
Claim
Allot
Acceptanc
Check
e
32
TABLE
33
Database Detail:
DB Admin Login:
Column Name Data Type Length
Login Name Var char 10
Password Var char 10
Site Admin Login:
Login Name Varchar 10
Password Varchar 10
Finance Admin Login:
Password Varchar 10
Employee Login:
Password Varchar 10
34
Claim Name:
Claim ID Numeric 9
Claim Name Varchar 20
Max Amount Numeric 9
Max Grade Varchar 10
Claim Desk Varchar 200
Business Claim:
Seq ID Numeric 5
Emp ID Varchar 10
Emp Name Varchar 50
Claim Date Varchar 15
Claim Name Varchar 30
Place Varchar 50
Hotel Name Varchar 50
From Date Varchar 15
To Date Varchar 15
Claim Amount Numeric 9
Status Varchar 50
35
Health Insurance:
Seq ID Numeric 5
Emp ID Varchar 10
Emp Name Varchar 50
Claim Reason Varchar 30
Apply For Varchar 50
Doctor Name Varchar 50
Hospital Varchar 50
To Date Varchar 15
Status Varchar 50
House Loan:
Seq ID Numeric 5
Emp ID Varchar 10
Emp Name Varchar 50
36
House Status Varchar 50
Document Number Varchar 15
Status Varchar 50
Employee Medical Claim:
Seq ID Numeric 5
Emp ID Varchar 10
Emp Name Varchar 50
Claim Reason Varchar 30
Apply For Varchar 50
Doctor Name Varchar 50
Hospital Varchar 50
To Date Varchar 15
Status Varchar 50
EMPLOYEE PREOFILE
37
Emp ID Varchar 10
Emp Name Varchar 50
Address Varchar 200
DOB Varchar 15
Gender Varchar 50
Contact Number Varchar 50
Mobile Number Varchar 50
Mail ID Varchar 15
Employee Salary Claim:
Seq ID Numeric 5
Emp ID Varchar 10
Emp Name Varchar 50
Status Varchar 50
Pay Slip:
38
Emp ID Varchar 10
Emp Name Varchar 50
Claim Type Varchar 15
Date of Claim Varchar 15
Date of Pay Varchar 15
39
MODULE DESCRIPTION:
 Employee Registration Module

 Emp-User Login Module
 Claims Entry Module
 DB Admin – Claim Process Module
 Finance Admin – Claim Accept Module
 Claim Search Module code
Module Description
Employee Employees in the organization can

Registration enter their personal details like
Module name, age, mail-id, emp-id etc and
register themselves in the data
Base
Emp-User
Login The Registered employees can enter
Module the emp-id and password to login
into the system. Employee gains
access only if it is valid.
It contains the forms and procedures for

Claims various claims that can be availed.
Entry Employees / Users can query about a
particular claim including insurance
claims and also avail it.
40
MODULE DESCRIPTION:
Module Description
An employee request and on eligibility, passes

the pay bill to higher-authority for approval. If
the request is an invalid one, an error message
DB Admin-Claim is displayed and the request is rejected.
Process Module Updating is required, if there is any change in
the Employee‘s details.
After the approval of higher authority, the pay

Finance Admin – bill is converted into a pay slip with account
Claim Accept number, bill date, bill amount etc by the
Module Finance dept. printer is used to print the pay
slip.
The search module is used search the

Search Module employees details and various claims details
quickly, in a specific order or in a full list
order.
41
SAMPLE SOURCE CODE
42
HOME PAGE
<Html>
<Head>
<TITLE>Banner and Content Frameset</TITLE>
<Meta name="GENERATOR" content="Microsoft Visual Studio .NET 7.1">
<Meta content="http://schemas.microsoft.com/intellisense/ie5"
name="vs_targetSchema">
</head>
<frameset rows="109, 73 %">
<frame name="banner" src ="banner.aspx" scrolling="no" no resize>
<frameset cols="167, 79 %">
<frame name="contents" src="">
<frame name="main" src="WebForm2.aspx">
</frameset>
<No frames>
<pre id="p2">
</pre> <p id="p1">
This HTML frameset displays multiple Web pages. To view this frameset, use a
Web browser that supports HTML 4.0 and later.
</p>
</no frames>
</frameset>
</html>
43
DB ADMIN LOGIN
Imports System.Data.SqlClient
Public Class ceo_login
Inherits System.Web.UI.Page
―Web Form Designer Generated Code‖
'This call is required by the Web Form Designer.
<System.Diagnostics.DebuggerStepThrough ()> Private Sub Initialize Component

()
End Sub
Protected With Events Label1 as System.Web.UI.WebControls.Label
Protected With Events TextBox1 as System.Web.UI.WebControls.TextBox
Protected With Events TextBox2 as System.Web.UI.WebControls.TextBox
Protected With Events Button1 as System.Web.UI.WebControls.Button
Protected With Events Button2 as System.Web.UI.WebControls.Button
'NOTE: The following placeholder declaration is required by the Web Form

Designer.
'Do not delete or move it.
Private DesignerPlaceholderDeclaration as System. Object
Private Sub Page_Init (By Val sender As System. Object, By Val e As

System.EventArgs) Handles MyBase.Init
'CODEGEN: This method call is required by the Web Form Designer
'Do not modify it using the code editor.
Initialize Component ()
End Sub
44
Dim cn As New SqlConnection ("Integrated Security=SSPI; Persist Security
Info=False; Initial Catalog=AEIS; Data Source=.")
Dim cmd As New SqlCommand
Dim rs As SqlDataReader
Private Sub Page_Load (By Val sender As System. Object, By Val e as

System.EventArgs) Handles MyBase.Load
'Put user code to initialize the page here
Me.Label3.Visible = False
Me.TextBox1.TabIndex = 1
Me.Button1.TabIndex = 3
End Sub
Private Sub Button1_Click (By Val sender As System. Object, By Val e as

System.EventArgs) Handles Button1.Click
Response. Redirect ("ceo_form.aspx")
cn.Open ()
Cmd = New SqlCommand ("select LOGIN, PASSWORD from CEO", cn)
Rs = cmd.ExecuteReader
While rs.Read
If Me.TextBox1.Text.Equals (rs (0)) And Me.TextBox2.Text.Equals (rs (1))

Then
Response. Redirect ("ceo_form.aspx")
Else
Me.Label3.Visible = True
45
End If
End While
cn.Close ()
End Sub

Me.TextBox1.Text = ""
Me.TextBox2.Text = ""
End Sub
End Class
CEO FORM
<HTML>
<HEAD>
<Title>ceo_form</title>
<Meta name="GENERATOR" content="Microsoft Visual Studio

.NET 7.1">
<Meta name="CODE_LANGUAGE" content="Visual Basic .NET

7.1">
<Meta name="vs_defaultClientScript" content="JavaScript">
<Meta name="vs_targetSchema"
content="http://schemas.microsoft.com/intellisense/ie5">
</HEAD>
<body MS_POSITIONING="Grid Layout" bgColor="#005f00">
<form id="Form1" method="post" runat="server">
46
<asp: Hyperlink id="HyperLink4" style="Z-INDEX: 103;
LEFT: 0px; POSITION: absolute; TOP: 232px"
Runat="server" Fore Color="White"

Navigate="project_details.aspx" Target="contents" Font-Bold="True">Project
Details</asp: Hyperlink>

Runat="server" Font-Bold="True" Target="main"

Navigate="resource.aspx" Fore Color="White">Resource Details</asp: Hyperlink>


Navigate="employee_details.aspx" Target="main" Font-Bold="True">Employee
Details</asp: Hyperlink>

Navigate="pl_details.aspx" Target="main" Font-Bold="True">PL Details</asp:

Hyperlink>


Navigate="pm_details.aspx" Target="main" Font-Bold="True">PM Details</asp:
Hyperlink>
</form>
</body>
</HTML>
Completed projects
Public Class completed projects
47

()
Me.OleDbDataAdapter1 = New System.Data.OleDb.OleDbDataAdapter
Me.OleDbConnection1 = New System.Data.OleDb.OleDbConnection
Me.OleDbSelectCommand1 = New System.Data.OleDb.OleDbCommand
Me.OleDbInsertCommand1 = New System.Data.OleDb.OleDbCommand
Me.DataSet21 = New AEIS.DataSet2
Type (Me.DataSet21, System.ComponentModel.ISupportInitialize).
Begin Init ()
'OleDbDataAdapter1
Me.OleDbDataAdapter1.InsertCommand = Me.OleDbInsertCommand1
Me.OleDbDataAdapter1.SelectCommand = Me.OleDbSelectCommand1
Me.OleDbDataAdapter1.TableMappings.AddRange(New
System.Data.Common.DataTableMapping() {New
System.Data.Common.DataTableMapping("Table", "PROJECT_STATUS", New
System.Data.Common.DataColumnMapping() {New
System.Data.Common.DataColumnMapping("PROJECT_ID", "PROJECT_ID"),
New System.Data.Common.DataColumnMapping("PROJECT_TITLE",
"PROJECT_TITLE"), New
System.Data.Common.DataColumnMapping("TECHNOLOGY",
"TECHNOLOGY"), New
System.Data.Common.DataColumnMapping("PROJECT_DOMAIN",
"PROJECT_DOMAIN"), New
System.Data.Common.DataColumnMapping("PROJECT_DURATION",
"PROJECT_DURATION"), New
System.Data.Common.DataColumnMapping("STATUS", "STATUS")})})
'OleDbConnection1
48
Me.OleDbConnection1.ConnectionString = "Integrated Security=SSPI; Packet
Size=4096; Data Source="".""; Tag with column collati" & _
"on when possible=False; Initial Catalog=Aegis‘s Procedure for Prepare=1;Auto

Tra" & _
"nslate=True; Persist Security Info=False; Provider=""SQLOLEDB.1"";

Workstation ID=""HO" & _
"ME-952C3803B0""; Use Encryption for Data=False"
'OleDbSelectCommand1
Me.OleDbSelectCommand1.CommandText = "SELECT PROJECT_ID,

PROJECT_TITLE, TECHNOLOGY, PROJECT_DOMAIN,
PROJECT_DURATION, S" & _
"TATUS FROM PROJECT_STATUS WHERE (STATUS = 'COMPLETED')"
Me.OleDbSelectCommand1.Connection = Me.OleDbConnection1
'OleDbInsertCommand1
Me.OleDbInsertCommand1.CommandText = "INSERT INTO

PROJECT_STATUS (PROJECT_ID, PROJECT_TITLE, TECHNOLOGY,
PROJECT_DOMAIN," & _
―PROJECT_DURATION, STATUS) VALUES (?); SELECT PROJECT_ID,

PROJECT" & _
"_TITLE, TECHNOLOGY, PROJECT_DOMAIN, PROJECT_DURATION,

STATUS FROM PROJECT_STATUS" & _ ""
Me.OleDbInsertCommand1.Connection = Me.OleDbConnection1
Me.OleDbInsertCommand1.Parameters.Add (New
System.Data.OleDb.OleDbParameter ("PROJECT_ID",
System.Data.OleDb.OleDbType.Decimal, 9, System.Data.ParameterDirection.Input,
49
False, CType (18, Byte), CType (0, Byte), "PROJECT_ID",
System.Data.DataRowVersion.Current, Nothing))
System.Data.OleDb.OleDbParameter ("PROJECT_TITLE",
System.Data.OleDb.OleDbType.VarChar, 50, "PROJECT_TITLE"))
System.Data.OleDb.OleDbParameter ("TECHNOLOGY",
System.Data.OleDb.OleDbType.VarChar, 50, "TECHNOLOGY"))
System.Data.OleDb.OleDbParameter ("PROJECT_DOMAIN",
System.Data.OleDb.OleDbType.VarChar, 50, "PROJECT_DOMAIN"))
System.Data.OleDb.OleDbParameter ("PROJECT_DURATION",
System.Data.OleDb.OleDbType.VarChar, 50, "PROJECT_DURATION"))
System.Data.OleDb.OleDbParameter ("STATUS",
System.Data.OleDb.OleDbType.VarChar, 50, "STATUS"))
'DataSet21
Me.DataSet21.DataSetName = "DataSet2"
Me.DataSet21.Locale = New System.Globalization.CultureInfo ("en-US")
CType (Me.DataSet21, System.ComponentModel.ISupportInitialize).
EndInit ()
End Sub
Protected With Events DataGrid1 as System.Web.UI.WebControls.DataGrid
50
Protected With Events OleDbDataAdapter1 as
System.Data.OleDb.OleDbDataAdapter
Protected With Events OleDbConnection1 as

System.Data.OleDb.OleDbConnection
Protected With Events OleDbSelectCommand1 as

System.Data.OleDb.OleDbCommand
Protected With Events OleDbInsertCommand1 as

Protected With Events DataSet21 as AEIS.DataSet2

Designer.
Private Sub Page_Init (By Val sender As System. Object, By Val e as

End Sub
Private Sub Page_Load (By Val sender As System. Object, By Val e As

Me.OleDbDataAdapter1.Fill (Me.DataSet21)
51
Me.DataGrid1.DataSource = Me.DataSet21
Me.DataGrid1.DataBind ()
End Sub
End Class
Public Class completed projects

()
CType (Me.DataSet21, System.ComponentModel.ISupportInitialize).BeginInit ()
'
'OleDbDataAdapter1
'Me.OleDbDataAdapter1.InsertCommand = Me.OleDbInsertCommand1
System.Data.Common.DataTableMapping("Table", "PROJECT_STATUS", New
52
System.Data.Common.DataColumnMapping("PROJECT_ID", "PROJECT_ID"),
New System.Data.Common.DataColumnMapping("PROJECT_TITLE",
"PROJECT_TITLE"), New
"TECHNOLOGY"), New
System.Data.Common.DataColumnMapping("PROJECT_DOMAIN",
"PROJECT_DOMAIN"), New
System.Data.Common.DataColumnMapping("PROJECT_DURATION",
"PROJECT_DURATION"), New
System.Data.Common.DataColumnMapping("STATUS", "STATUS")})})
'OleDbConnection1

"On when possible=False; Initial Catalog=Aegis‘s Procedure for Prepare=1;

Auto Tra" & _

Me.OleDbSelectCommand1.CommandText = "SELECT PROJECT_ID,

PROJECT_TITLE, TECHNOLOGY, PROJECT_DOMAIN,
PROJECT_DURATION, S" & _
"TATUS FROM PROJECT_STATUS WHERE (STATUS = 'COMPLETED')"
53
PROJECT_STATUS (PROJECT_ID, PROJECT_TITLE, TECHNOLOGY,
PROJECT_DOMAIN," & _
―PROJECT_DURATION, STATUS) VALUES (?); SELECT PROJECT_ID,

PROJECT" & _
"_TITLE, TECHNOLOGY, PROJECT_DOMAIN, PROJECT_DURATION,

STATUS FROM PROJECT_STATUS" & _
""
System.Data.OleDb.OleDbParameter ("PROJECT_ID",
False, CType(18, Byte), CType(0, Byte), "PROJECT_ID",
System.Data.OleDb.OleDbParameter ("PROJECT_TITLE",
System.Data.OleDb.OleDbType.VarChar, 50, "PROJECT_TITLE"))
System.Data.OleDb.OleDbParameter ("PROJECT_DOMAIN",
System.Data.OleDb.OleDbType.VarChar, 50, "PROJECT_DOMAIN"))
System.Data.OleDb.OleDbParameter ("PROJECT_DURATION",
System.Data.OleDb.OleDbType.VarChar, 50, "PROJECT_DURATION"))
54
System.Data.OleDb.OleDbParameter ("STATUS",
System.Data.OleDb.OleDbType.VarChar, 50, "STATUS"))
'DataSet21
EndInit ()
End Sub





Designer.
55

End Sub

End Sub
End Class
EMPLOYEE DETAILS
Public Class employee details

56
()
CType(Me.DataSet41, System.ComponentModel.ISupportInitialize).BeginInit()
'
'OleDbDataAdapter1
'
Me.OleDbDataAdapter1.InsertCommand = Me.OleDbInsertCommand1
System.Data.Common.DataTableMapping("Table", "EMPLOYEE_DETAILS", New
System.Data.Common.DataColumnMapping("EMP_ID_NO", "EMP_ID_NO"), New
System.Data.Common.DataColumnMapping("EMPLOYEE_NAME",
"EMPLOYEE_NAME"), New
System.Data.Common.DataColumnMapping("DESIGNATION",
"DESIGNATION"), New
System.Data.Common.DataColumnMapping("DATE_OF_BIRTH",
"DATE_OF_BIRTH"), New
System.Data.Common.DataColumnMapping("GENDER", "GENDER"), New
System.Data.Common.DataColumnMapping("UNDER_GRADUATE",
"UNDER_GRADUATE"), New
System.Data.Common.DataColumnMapping("POST_GRADUATION",
"POST_GRADUATION"), New
System.Data.Common.DataColumnMapping("EXPERIENCE", "EXPERIENCE"),
New System.Data.Common.DataColumnMapping("COMPANY_NAME",
"COMPANY_NAME"), New
"TECHNOLOGY"), New
57
System.Data.Common.DataColumnMapping("LANGUAGE_PROFICIENCY",
"LANGUAGE_PROFICIENCY")})})
'
'OleDbConnection1
'
"On when possible=False; Initial Catalog=AEIS; Use Procedure for Prepare=1;
Auto Tra" & _
'
'
Me.OleDbSelectCommand1.CommandText = "SELECT EMP_ID_NO,
EMPLOYEE_NAME, DESIGNATION, DATE_OF_BIRTH, GENDER,
UNDER_GRADUA" & _
"TE, POST_GRADUATION, EXPERIENCE, COMPANY_NAME,
TECHNOLOGY, LANGUAGE_PROFICIENCY‖ & _
"FROM EMPLOYEE_DETAILS"
'
'
EMPLOYEE_DETAILS (EMP_ID_NO, EMPLOYEE_NAME, DESIGNATION,
DATE_OF_BIRTH" & _
", GENDER, UNDER_GRADUATE, POST_GRADUATION, EXPERIENCE,
COMPANY_NAME, TECHNOLOGY," & _
" LANGUAGE_PROFICIENCY) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?);
SELECT EMP_ID_N" & _
"O, EMPLOYEE_NAME, DESIGNATION, DATE_OF_BIRTH, GENDER,
UNDER_GRADUATE, POST_GRADU" & _
58
"ATION, EXPERIENCE, COMPANY_NAME, TECHNOLOGY,
LANGUAGE_PROFICIENCY FROM EMPLOYEE_" & _
"DETAILS"
System.Data.OleDb.OleDbParameter ("EMP_ID_NO",
False, CType (18, Byte), CType (0, Byte), "EMP_ID_NO",
System.Data.OleDb.OleDbParameter ("EMPLOYEE_NAME",
System.Data.OleDb.OleDbType.VarChar, 50, "EMPLOYEE_NAME"))
System.Data.OleDb.OleDbParameter ("DESIGNATION",
System.Data.OleDb.OleDbType.VarChar, 50, "DESIGNATION"))
System.Data.OleDb.OleDbParameter ("DATE_OF_BIRTH",
System.Data.OleDb.OleDbType.VarChar, 50, "DATE_OF_BIRTH"))
System.Data.OleDb.OleDbParameter ("GENDER",
System.Data.OleDb.OleDbType.VarChar, 50, "GENDER"))
System.Data.OleDb.OleDbParameter ("UNDER_GRADUATE",
System.Data.OleDb.OleDbType.VarChar, 50, "UNDER_GRADUATE"))
System.Data.OleDb.OleDbParameter ("POST_GRADUATION",
System.Data.OleDb.OleDbType.VarChar, 50, "POST_GRADUATION"))
System.Data.OleDb.OleDbParameter ("EXPERIENCE",
False, CType (18, Byte), CType (0, Byte), "EXPERIENCE",
59
System.Data.OleDb.OleDbParameter ("COMPANY_NAME",
System.Data.OleDb.OleDbType.VarChar, 50, "COMPANY_NAME"))
System.Data.OleDb.OleDbParameter ("LANGUAGE_PROFICIENCY",
System.Data.OleDb.OleDbType.VarChar, 50, "LANGUAGE_PROFICIENCY"))
'
'DataSet41
'
EndInit ()
End Sub

Designer.
60
End Sub

End Sub
End Class
EMPLOYEE LOGIN
Public Class employee login

<System.Diagnostics.DebuggerStepThrough ()> Private Sub
End Sub

61
End Sub

Me.Label3.Visible = False
End Sub
cn.Open ()
Cmd = New SqlCommand ("select LOGIN_NAME, PASSWORD from
EMPLOYEE_DETAILS", cn)
Rs = cmd.ExecuteReader
While rs.Read
If Me.TextBox1.Text.Equals (rs (0)) And Me.TextBox2.Text.Equals (rs (1))
Then
Response. Redirect ("employee.aspx")
Else
Me.Label3.Visible = True
End If
End While
cn.Close ()
End Sub
End Class
62
NEW CLAIMS
Public Class new claims
Designer.

End Sub

Me.DropDownList1.Items.Add ("Male")
Me.DropDownList1.Items.Add ("Female")
cn.Open ()
Cmd = New SqlCommand ("select max (EMP_ID_NO) from
EMPLOYEE_DETAILS ", cn)
rs = cmd.ExecuteReader
If rs.Read Then
Me.TextBox2.Text = rs (0) + 1
63
Else
Me.TextBox2.Text = 1001
End If
cn.Close ()
End Sub

End Sub
‗cn.Open ()
'cmd = New SqlCommand("insert into EMPLOYEE_DETAILS values('" &
Me.TextBox1.Text & " ','" & Me.TextBox2.Text & "','" & Me.TextBox26.Text & "','"
& Me.TextBox3.Text & "','" & Me.DropDownList1.SelectedItem.Value & "','" &
Me.DropDownList2.SelectedItem.Value & "','" & Me.TextBox9.Text & "','" &
Me.TextBox8.Text & "')", cn)
‗cmd.ExecuteNonQuery ()
‗cn.Close ()
Response. Redirect ("info_save.aspx")
End Sub
End Class
ALLOT CLAIMS
Public Class new_allot_claims

64
()
End Sub

End Sub


Me.TextBox1.Enabled = False
cn.Open ()
Cmd = New SqlCommand ("select max (PROJECT_ID) from
PROJECT_DETAILS ", cn)
rs = cmd.ExecuteReader
If rs.Read Then
Me.TextBox1.Text = rs (0) + 1
Else
Me.TextBox1.Text = 101
End If
cn.Close ()
End Sub
65
‗cn.Open ()
'cmd = New SqlCommand("insert into PROJECT_DETAILS values('" &
Me.TextBox1.Text & " ','" & Me.TextBox2.Text & "','" & Me.TextBox26.Text & "','"
& Me.TextBox3.Text & "','" & Me.DropDownList1.SelectedItem.Value & "','" &
Me.DropDownList2.SelectedItem.Value & "','" & Me.TextBox9.Text & "','" &
Me.TextBox8.Text & "')", cn)
‗cmd.ExecuteNonQuery ()
‗cn.Close ()
End Sub

Response. Redirect ("info_save.aspx")
End Sub
End Class
66
SCREEN DESIGN & REPORTS
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
3
86
87
88
89
90
91
92
93
94
SYSTEM ANALYSIS
95
SYSTEM ANALYSIS
The overall requirement of the product is stated as follows;
 Information and Control Needs

 Product Function and Behavior
 Overall Product Performance
 Design and Interfacing Constraints
 Client Friendly Usage
 Online updating
OBJECTIVE:
To develop a Claims Reimbursement System, that converts the
pre-specified set of requirements as elicited by the customer into a
Integrated High-quality Application Software. The product will be
getting more concentration on Insurance Claims.
EXISTING SYSTEM:
The problems, which are perceived by the customers / users
in existing systems, are;
o Less Efficiency and accuracy due to lot of manual entries

o More Time Delay for payments.
o Increased expenditure for storage
o Increase in labor
LIMITATION OF THE EXISTING SYSTEM:
o The limitations of the existing system are,

o Date retrieval is very difficult and changes of the cannot be
able to update quickly
o Time consumption process
96
o Marketing area in small place
o Financial transactions take more time
o Less operational speed
o Cannot view all the price list
PROPOSED SYSTEM:
The proposed system is designed to provide a solution for the
drawbacks of present system. It aims to:
o Replace Manual Processing system with an automated one.

o Speedup Transactions
o Reduce the chances of malpractices associated in a manual
system.
o Reduce the workload involved in processing
o Update information system and provide easy access to
corresponding information.
GOALS OF PROPOSED SYSTEM:
 Faster information retrieval
 System should be user friendly
 Facilities all types of services
 Highly reliable
 Having high operational speed
97
SYSTEM TESTING
98
TESTING STRATEGY
Software testing is a critical element of a software quality

assurance and represents the ultimate reviews of specification, design and coding.
Testing presents an interesting anomaly for the software. During earlier definition and
development phases, it was attempted to build software from an abstract concept to a
tangible implementation.
The testing phase involves the testing of the developed system using various
test data. Preparation of test data plays a vital roll in the system testing. After the
preparing the test data system under study was tested using those test data. While
testing the system by using test data, errors were found and corrected by using
following testing steps and corrections are also noted for future use.
Thus, a series of testing was performed for the proposed system before the
system was ready for the implementation.
Testing Objectives :
There are several rules that can server as testing objectives. They are
 Testing is a process of executing a program with the intent of

finding an error.
 A good case is one that has a high probability of finding an
undiscovered error.
 A successful test is one that uncovers an undiscovered error.
 If testing is conducted successfully according to the objectives
stated above, it will uncover errors in the software. Also testing
demonstrates that software functions appear to the working
according to specifications that performance requirements appear
to have been set.
99
Types of Testing:
The various types of testing done on the system are:
 Unit Testing
 Integration Testing
 Validation Testing
 Output Testing
 System Testing
 Performance Testing
 User Acceptance Testing
Unit Testing:
Unit testing focuses verification effort on the smallest unit of software design
the module. This is also known as module testing. The unit testing is always white
box oriented and the step can be contacted in parallel for modules. In this testing each
module is found to be working satisfactory as regards to the expected output from the
module.
Integration Testing:
Integration testing is a symmetric technique for constructing the program

structure while at the same time conducting tests to uncover errors associated with
interfacing. The objectives are to take unit tested modules and build a program
structure that has been dictated by design.
A set of errors encountered. Correction is difficult because the isolation of

causes is complicated by the vast expense of the entire program. Using integrated test
plans prepare in the design phase of the system development as guide, the integration
testing was carried out. All the errors found in the system were corrected of the next
testing steps.
100
Validation Testing:
All the culmination of integration testing, software is completely assembled as

package, interfacing error have been uncovered and corrected and a final series of
software tests – the validation testing begins. Validation testing can be defined in
many ways, but a simple definition is that validation succeeds when the software
functions in a manner that can be reasonably expected by the user/customer. Software
validation conformity is followed with the following requirements
 The function or performance characteristics conform to specification

and are accepted.
 A deviation from specification uncovered and a deficiency list is
created.
Output Testing:
The output generate or displayed by the system under consideration are tested
by asking the users about the format required by them. Here, the format is considered
into two ways. One is on the screen and the other is printed format.
The output format on the screen is found to be correct as the format was
designed in the system design phase according to the user needs. The output testing
does not result any correction in the system.
System Testing:
System testing is series of different tests whose primary purpose is to fully

exercise the computer based system. Although each test has a different purpose, all
the work should verify that all system elements have been properly integrated and
perform allocated functions.
101
Performance Testing:
This testing is designed to test the runtime performance of software within the
context of an integrated system. This testing occurs throughout all steps in the testing
process.
User Acceptance Testing:
User acceptance of the system is the key factor for the success of any system.
The system under consideration was tested for the user acceptance by constantly
keeping in touch with the prospective system users at the time of developing and
making change were ever required. This is done in regard to the following points:
 Input screen design

 Output screen design
 On-line message to guide the user
 Menu-driven system
 Format of ad-hoc report and other output
102
IMPLEMENTATION
103
IMPLEMENTATION
After proper testing and validation, the questing arises whether the
system can be implemented or not. Implementation includes all those activities that
take place to convert from the old system to the new .the new system may be totally
new, replacing an existing module or automated system. Or it may be major
modification to an existing system. In either case proper implementation is essential
to provide a reliable system to meet organization requirements.
All planning has now is completed and the transformation to
a fully operational system can commerce .the first job will be writing debugging
documenting of all computer programs and their integration into a total system .the
master and transaction files are decided, and this general processing of the system is
established .programming is complete when the programs confirmed to the detailed
specification
When the system is ready for implementation, emphasis switches to
communicate with the finance and department staff .open discussion with the staff is
impartment from the beginning of the project. Staff can be expected to the concerned
about the effect of the automation on their Jobs and the fear of redundancy of loss of
status must be allayed immediately .during the implementation phase it is important
that all staff concerned be apprised of the objectives of overall operation of the system
.they will need to understand hoe their role relates to the system as a whole. An
organization-training program is advisable .this can include demonstrations,
newsletters, seminars
The department should allocate a member of staff, who understands
The system and the equipment, and should be made responsible for the smooth
operation of the system. An administrator should coordinate the users to the system.
Users should be informed about new aspects of system that will affect them.
The features of the system explained with the adequate documentation. New services
such as security and back ups must advertised on the staff when the time ripe.
The system may be come into full operation via number of possible routes.
Complete change over at point time is conceptually the most tidy. But this approach
required careful planning and coordination, particularly during the change over.
A phased approach, possible implementing the system of the section
relation to the operation or procedure first and progressing to more novel or complex
104
subsystems in fullness of time. These are like to be less traumatic. A phased approach
gives the staff time to adjust to the new system. But depends on begin able to split the
system, without reliance on it. Thus approach is sensible when the consequences of
failure are disastrous, but will tackle on a smaller scale operation generally means the
implementation of the complete system, but at one location or branch only.
105
CONCLUSION
106
CONCLUSION
The main objective of the project is to bring a fully
fledged computerized organization and to help in managing the function of logistics
carried by the Company.
Thus the proposed system has been developed with the good amount of Flexibility
without compromising on the response time.
Computerized of the entire system will enhance more accuracy and reduce
major part of the manual work fast clear and legible reports without any
ambuiguity.integrated database design and ease of each of feature of the system.
Hence by developing a system that is user friendly in nature many user are
able to work on the system with little of computer knowledge and training.
107
BIBLIOGRAPHY
108
BIBLIOGRAPHY
ASP.Net Bible E. Stephen Mack, Jenna Platt
HTML 4.0 E. Stephen Mack, Janna Platt
VBScript Tec media
Web Publishing with HTML Laura Len may
MS SQL Server Bjeletich, Mabel

7.0 Unleashed
Teach Yourself MS. Richard Way mire, Rick

SQL Server 7.0 in 21 Saw tell
Days
109

AUTO

Uploaded by

Copyright:

Available Formats

AUTO

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AUTO

Uploaded by

Copyright:

Available Formats

CONTENTS

S.NO CONTENTS PAGE

7 SAMPLE SOURCE CODE 42

The purpose of this software specification (SS) is to

topics for available information concerning the Software Project Management.

This Insurance Claims & Management System

Speed : 3.0 GHZ

Mouse : Optical scroll mouse

Keyboard : Internet keyboard, 104 keys

Operating System : Windows XP

Front-End : ASP .NET

Back-End : SQL Server 2000

Web Server : IIS

Web Browser : Internet Explorer 6.0 Version

COMPONENTS OF THE .NET FRAMEWORK:

The .NET framework is composed of classes and service

COMMON LANGUAGE RUNTIME:

The .NET Framework class library includes

.NET is the Microsoft web services strategy to connect information

The Microsoft platform includes everything a business needs to

If you ask a developer what web services are? You‘ll hear

BENEFITS OF WEB SERVICES:

 Identify the components of dynamic Web Applications

COMPONENTS OF ASP APPLICATIONS:

Web Applications have both client-side components, server-side

 Client-Side scripting enables you to develop web pages that can

Server-Side scripting provides dynamic content to users based on the

 ASP .NET is a standard HTML file that contains embedded server-side

WORKING OF AN ASP.NET APPLICATION:

ASP.NET files need to be stored on an IIS Server, which is the Web

Explains the flexible yet powerful ASP.NET text based

ASP.NET configuration system features an extensible infrastructure

The ASP.NET configuration system provides the following benefits:

Configuration information is stored in XML based text files. You can

Web Forms consist of a user Interface and Programming logic that is

SERVER CONTROLS IN ASP.NET:

ASP .NET server Controls work within the ASP.NET

Which are displayed in the browser? These controls use the

VALIDATION SERVER CONTROL:

Validation Server Controls is used to validate user-input. If the

ADO.NET provides consistent access to data sources

XML. Data-sharing consumer applications can use ADO.NET to connect to

ADO.NET provides functionality to developers writing managed code similar

DESIGN GOAL FOR ADO.NET:

As application development has evolved, new applications

In designing tools and technologies to meet the needs of today's developer,

ADO.NET was designed to meet the needs of this new

LEVERAGE CURRENT ADO KNOWLEDGE:

The design for ADO.NET addresses many of the requirements of

ADO.NET coexists with ADO. While most new .NET-based

ADO.NET provides first-class support for the disconnected, n-tier

INTEGRATE XML SUPPORT:

XML and data access are intimately tied — XML is

XML support is built into ADO.NET at a very fundamental level.

Perhaps the most important difference between these two scripting

THE STRUCTURE OF VBSCRIPT PROGRAM:

In many ways a VBScript program is like a JavaScript program, at

The SQL Server 2000 database engine includes integrated

SCALABILITY AND AVAILABILITY: