EIS

1
 EIS

1.1) Overview:-
 Our system is about “EMPLOYEE INFORMATION
SYSTEM”. In this system we prepare Login master for
admin & Employee, Employee master, for Employee
come to our website for registration. The information
about Employee is takes down.

 First in our system Employee comes to website and

takes Registration about Employee master table. Our
website has provided about Employee information for
admin and user.

 Administer give Employee all list select specific details

of Employee list and give a post details and about the
employee post and all user details about login in the
web side.

 Admin side many details show this all details when you
visit website and show all website.

 In this system you get all information about employee

take employee number salary, post, contactno, emailid,
address and all details about employee.

2
 EIS

1.2) Scope of System:-

 “Employee Information system” is design for
Registration the Employee for its data and
information about Employee Rajratan metal Pvt.
Ltd.

 First in our system Employee comes to website

and fills the registration form of employee and
show information about any employee. Our
website has provided about Employee registration
information for Employee.

 Administer Check all details of all employee and

checked all user list of website visitor.

 Administer also checked selected post employee

list and select employee all information.

 We provide their facility in our website once

employee fill registration form then after he can
also change its information from the update button
administer also provide the checking of data and
retrieve a data form specific employee.

3
 EIS

-: Problem Description:-

 In the company this is interested in developing a database

maintains information about the Employee Details.
 The database will keep information about post
information, Employee details , User details etc.

-: ASP.NET Application Development :-

Welcome To Screen

Master Page Employee List post List Feedback Form Result

Login Req.
Present Result

Exit the database

4
EIS

5
 EIS

Existing System Relates To All The System

Which The User Was Working On Previously Before
This System Was Put Into The Action Into The Market.
The Existing System Is “Rajratan Metal industry ” Was
Manual. The Organization In With All The Works Are
Done Manually The Management Approve The Needs
Of Computerization Of Work. During The Study Of
Existing System Following Points Are Observed:

 The Current System Was Totally Manual.

 Due To The Manual Process, It Requires More
Time For Completion Of Any Work.
 As The Existing System Was Manual. So It
Increases The Chance Of Errors And Also
Increases Turnaround Time.
 Lot Of Time Was Consumed For Searching
Required Student Info.
 More Manpower Is Required & Timely Updating Is
Complicated.
 Immediate Response To The Inquiries Is Difficult
And Time Consuming.

 Reports Can Not Be Generated As And What

Required On Time.

6
 EIS

Hence On Analyzing All The Points

Above It Was Felt By The Management Of The Collage
That There Was Need Of Such A Tool Which Could
Fulfill All The Needs Of Feedback.

-: Investigation techniques:-

1. Interviewing

 The information is collected from project

leader by interviewing to them and took
suggesting from end user as per their
requirement.

2. Visiting

 For clarification, visited some site like

Google.com, yahoosearch.com, 4tests.com,
codeforu.Com etc.

3. Questionnaires

 By asking possible questions to the project

leader at the time of interview by making
some questionnaires to collect the required
information

7
 EIS

-: REQUIREMENT ANALYSIS:-

Requirement analysis is a software engineering task that

bridges the gap between system engineering and software
design. It provides the software designer with a
representation of information and function that can be
translated to data.

Before developing any computerized system, it is

imperative to examine initially. The problem in the existing
system and also ascertain the basic needs that should be
fulfilled by the proposed system the primary aspect of
developing a full l fledged automated system would be to
learn the current procedure and the information flow to
locate the problem in the existing system to identify what
recourses are used to discuss with user and their authority
as to what improvement must in the existing system.

-:Definition:-

 “Analysis of system is the process of gathering facts,

solution of problem and to decide overall constitution of
the desired system. In system analysis we have to
analyze all the processes, related features, required
function, available sources and the time which should
be specified for the analysis stage.”

 The most important phase of developing any system is

system analysis. Because of the analysis phase
decides that what type of requirements, materials,
strangles and techniques, models are required.

 All these things are depend upon our system that what
type of our output of our system to function. We desire

8
 EIS

from the system is also responsible for defining the

above factors. So the overall structure of system that
we want to implement will be decided in anal sis part of
a system development by analyst.

Feasibility study is the study of the system to

check whether the system made is feasible or not. It
is very Useful to check whether the system work as
per the requirement or not. It is undertaken to
determine the possibility of the probability of
developing completely new system.

-: Need of the feasibility study :-

 Answer the question whether the new system is

to be developed or Not?

 Define the problem and objectives involved.

 Is the cost incurred in the development of the
system of the Justified?

-: Operational feasibility:-

9
 EIS

It covers mainly two aspects. It determines that

how the proposed system will fit in the current
operation and what if the job retraining and
restructuring may be needed at the end of the
implementation of the system. The operational
feasibility checks whether user who is going to use the
system as able to work with the software with which
the system is coded!

In the system Operation feasibility following are the

question to be asked!

 Is there sufficient support for the system?

 Is current method are acceptable to the user?
 Have the user been involved in the planning and
development of the system?
 System is very useful for online system.
 System is very user-friendly.
 Level of security and any other access control
constrains are high.

-: Technical feasibility:-

It determines that work for the system is done

with the present equipments and existing software
technology.

Necessary all things is easily feasible for the

system. Necessary technology, documents, reports

10
 EIS

are also available. Technical guarantee of accuracy,

reliability and security are also provided.

It asks following question?

 Does necessary technology exists to do what is

suggested?

 Do the Proposed equipments have the technical

capacity to hold the data required to use new
system?

 Are there technical guarantees of accuracy,

reliability ease of access and data security?

-: Economical feasibility:-
It looks the financial aspects of the system.
Economic feasibility concerns with the returns of the
investments in the system. It determines whether it is
worthwhile to invest money in the proposed system?

It asks for the following question.

 What is the cost to conduct a full system
investigation?
 What is the cost of hardware and software
required in the development of the proposed
system?
 Estimated cost is fitted in budget. (I.e. cost of
software and hardware is feasible to common
person.)s

11
 EIS

2.4.1) Time line chart:-

 When creating a software project schedule, the planner

begins with a set of tasks. If automated tools are used,
the work breakdown is input as a task network or task
outline. Effort, duration, and start date are then input
for each task. In addition, tasks may be assigned to
specific individuals.

 A timeline chart, also called a Gantt chart, is

generated. A timeline chart can be developed for the
entire project. Timeline charts can be developed for
each project function.

 All project tasks are listed in the left-hand column. The

horizontal bars indicate the duration of each task.
When multiple bars occur at the same time on the
calendar, task concurrency is implied. The diamonds
indicate milestones, which indicate the place where our
project reach.

 Once the information necessary for the generation of a

timeline chart has been input, the majority of software
project scheduling tools produce project tables listing
of all project tasks, their planned and actual start and
end table dates and variety of related information,
enable the project manager to track progress.

12
 EIS

Week 1
Work Task D1 D2 D3 D4 D5
Analysis
 Get project title
 Discuss about
project’s
functionality with
project guide.

Week 2
 Make the System
Flow Diagram.
 Make Data Flow
Diagram.
 Make
modifications in
System Flow Dia.
And DFD.

Week 3
 Make the Data
Dictionary related
to project
requirement.
 Identify features
and functionality to
be added.
 Visit related sites
and do the
compartmentalizat
ion
 Milestone
Analysis is Complete

13
 EIS

Week 4
Work Task D1 D2 D3 D4 D5
Design
 Design
home, login,
and Main
page
 Designing of
the other
pages.
.
Week 5
 Inserting
validation
for the
information
insertion
 Checking of
the
validation.

Week 6

14
 EIS

 Establishing
database
connectivity.

 Creating table.

 Testing of the
connectivity.

 Check the
complete
project for
Errors.

2.4.2 Estimation:-

 Software is the most expensive element of virtually

all computer-based systems. For complex, custom
system, a large cost estimation error can make the
difference between profits and lost. Cost overrun can
be disastrous for the developer.

 Software cost and effort estimation will never be

an exact science. Too many variables human,
technical, environment, political can affect the ultimate
cost of software and effort applied to develop it.
However, software system estimation can be
transformed from a black art to a series of systematic
steps that provide estimate with acceptable risk. To
achieve reliable cost and effort estimates, a number of
options arise:

15
 EIS

 Software Sizing:-

 Fuzzy Logic Sizing

 Function point sizing

 Standard component sizing

 Change sizing.

-: Problem-Based Estimation:-

 LOC and FP data are used in two ways

during software system Estimation:-

 As an estimation variable to size each element of

the software and

 As baselines matrices collected from past

systems and used in conjunction with estimation
variables to develop cost and effort projections.

-: Costs:-

 Cost drivers such as staff and schedule

constraints, specification volatility, and the impact of
using new versus reused software, and development
methods and standards can be taken into account
using SEER for Software (formerly SEER-SEM).

-: Schedules:-

16
 EIS

 Obtain an early view of staffing requirements and

constraints, and demonstrate the impact of changing
deadlines, understaffing, and staff loading.

-: Quality:-

 Quantify the impact on defect rates of building to

deadlines or reducing staff.

-: Risk:-

 Fine tune risk levels for all the major types of risk:
size, requirements, technology, maintenance, systems
integration, and defects.

-: Metrics:-

 Evaluate your system against the industry,

comparing your development costs, reliability,
functions, and more.

17
 EIS

-: Hardware specification:-

1. Pentium series or above processor

2. 20GB or above Hard Disk Drive
3. 128MB RAM
4. CD ROM Drive or DVD Drive
5. Floppy Drive

-:Software specification:-

1. Platform support :

 Windows 98
 Windows 2000
 Windows NT
 Windows XP

2. Application Development tool used:

 Front End - Visual Studio 2008

 Back End – SQL Database

18
 EIS

-: Water fall Diagram for methodology:-

Requirement

Design

Implementation

Verification

Maintenance

19
 EIS

-: Waterfall Model:-

 The waterfall model derivers its name due to the

cascading effect from one phase to the other as is
illustrated in above figure. In this model each phase
well define starting and ending point, with identifiable
deliveries to the next phase. Note that this model is
sometime referred to as the linear sequential model or
the software life cycle model.

 The water fall diagram is basically divided into

following 5 models.

 Requirement
 Design
 Implementation
 Verification
 Maintenance

-:Requirement:-

 In the requirement phase the need to create the

application is specified. What is the need of the project
is defined. What information to be feeder to create the
application will come under the requirement phase?

-:Design:-

20
 EIS

 After the requirement phase the next phase is the

Design phase where the application is designed
according to the forms and other modules created. This
phase is much important phase because it will structure
the layout of your application.

-:Implementation:-

 Implementation is the process of having a system

personnel phase check out and put new equipment into
use, train users, install new application and construct
any file of data need to use it.

-:Verification:-

 After the whole application is being the developed the

main phase is the verification phase where the whole
application tested and verified to check the whole
application
-:Maintenance:-

 After the successful verification of the application the

main phase is the maintenance phase where the
application needs to be maintained for its successful
operation in future.

21
 EIS

CONTEXT LEVEL DFD

Login for 0.0

Login
ADMIN Update Employee
Employee
Information
Replay employee Info.
SYSTEM

22
 EIS

1st LEVEL DFD FOR

ADMIN

Login Login info.

1.0
Admin LOGIN Login Master
PROCES
S Login Details
Reply

Submit for Reg. Employee info.

2.0
Employee Employee Employee Master
Regi.
process Reply
Reply

Update his profile 3.0 Update information

Update
OWN
Profile

4.0
Repot
generation 23
 EIS

CommunicateDetail
s
Repot

2nd level DFD

Uid & pwd

2.1 Uid & pwd
Employee EIS Login master
For
Company
In valid

2.1
Post _ Post master
Master

24
 EIS

E-R DIAGRAM

Usernam Password
Admin
e
1

Logi
n
User Id
Post id 1

1 Chec M
Employee k data User data
Post Ins Information entry
1 - M System

ert Detail
1
Post

Registration

Employee

Empl. Id Detail

25
 EIS

Start

Username/Password

Login

No
Authentication

Yes

Admi
n

Yes

Add/Delete
Update

Resources

Logout 26

End
EIS

27
 EIS

The different modules of this site are as follows:

1. HOME MODULE

2. LOGIN PAGE MODULE

3. CONTACT AS MODULE

4. EMPLOYEE REGISTRATION MODULE

5. SELECT SPECIFIC EMPLOYEE LIST EMPLOYEE SIDE

MODULE

6. ABOUT US MODULE

7. POST MODULE

8. EMPOLOYEE MODULE

9. CHECK DATA ENTERY MODULE

10. USER MODULE

11. SELECT SPECIFIC EMPLOYEE LIST ADMINSIDE MODULE

28
 EIS

1. HOME MODULE:-

 It provides the functionality for an Authorized person.

 In this site the authorized person or the main owner

of the site can get the facility of Checking of
employee list.

2. LOGIN MODULE:-

 It gets the functionality for a new Employee entry.

 This module admin, employee and visitor use and

Login and store user information in user data master.

 In this module new Employee having login facility.

3. CONTACT MODULE:-

 In This module is use to see all contact details of

admin.
 In this module all contact details about system
developer.

4. EMPLOYEE REGISTRATION MODULE :-

29
 EIS

 In this module is used for Employee registration.

 In this module new employee adds its information

and registered employee show its inserted record
and update its inserted record using add, delete,
and update facility throw.

 Employee also deletes all its record and show all

record.

5. SELECT SPECFIC EMPOLEE LIST EMPLOYEE

SIDE MODULE:-

 In this module you can show selected employee

name post salary and net salary of selected
employee.
 This module employee side and admin side but
differs is that in this side you show only employee
name, no, post, salary and net salary.

6. ABOUT US MODULE:-

 In this module is providing all information about this

project.

7. POST MODULE:-

 This module is Admin side module. This module

only can use Admin.
 In this module all the post details are include on this
module.

30
 EIS

 In this module you add new post of company and

delete the post and update the post name using this
module.

8. EMPLOYEE MODULE:-

 This module is Admin side module. This module

only can use admin.

 In this module Admin show all registered employee

Record and also shoe all employee information
throw out employee registration table.

9. CHECK USER DATA ENTERY MODULE:-

 In this module employee site employee checked its

record inserted or not.
 In this form employee enter no and name then
another page open and show entered no and name
record.

10. USER INFORMATION MODULE:-

 This is admin site user module. In this module only

can use admin.
 In this module only show details about website
visitor and show its record.

11. SELECT SPECIFIC EMPLOYEE

INFORMATION ADMIN SIT MODULE:-

31
 EIS

 This is admin site user module. In this module only

can use admin.

 In this module first show all post name in the post

name admin selected any post then in this post
jointed employee list show and then select only one
employee name and show selected employee name
all details.

32
 EIS

 In database management systems, a file that defines

the basic organization of a database. A data
dictionary contains a list of all files in the database,
the number of records in each file, and the names
and types of each field.

 Most database management systems keep the data

dictionary hidden from users to prevent them from
accidentally destroying its contents.

 Data dictionaries do not contain any actual data from

the database, only book keeping information for
managing it

 Without a data dictionary, however, a database

management system cannot access data from the
database.

33
 EIS

Login Master For Admin

Table Name : Login Master For Admin

Table Description:- This table provides information about the

username and password.

Table Column Data size Constrain

name name type
User Varchar 50 Primary
Login name key
master Password Varchar 50 Not null
User type Varchar 50 Not Null

34
 EIS

Employee MASTER
Table Name: - Employee MASTER

Table Description:-This Table Provide Information about

Employee.

Table Column Data type size Description

name name
No Integer 50 Primary
key
Name Varchar 50 Not null
Address Varchar 100 Not null
City Varchar 50 Not null
Age Integer 50 Not null
Employee Email Varchar 50 Not null
Master Contac no Varchar 50 Not null
Post Varchar 50 Not null
Salary Integer 50 Nut null
Da Integer 50 Not null
Hra Integer 50 Not null
It Integer 50 Not null
Pf Integer 50 Not null
allowance Integer 50 Not null
Deduction Integer 50 Not null
Net salary integer 50 Not null

35
 EIS

POST_MASTER

Table Name:- POST_Master

Table Description:- This Table is store all post is available in

post_master table.

Table Column Data size Description

name name type
Post Id integer 50 Primary
Master key
post name Varchar 100 Not null

36
 EIS

LOGIN DETAILS_MASTER

Table Name:- LOGIN DETAILS Master

Table Description:- This Table is store all website user

password, usertype,username,and its id no. This all
information is store in login details master table.

Table Column Data size Description

name name type
Id integer 50 Primary
Login key
details User Varchar 100 Not null
Master name
Password Varchar 100 Not null
User Type Varchar 100 Not null

37
 EIS

LOGIN Page

Login Page Description: - This is Login page. Visiter,

admin, employee all website user login on this page.

38
 EIS

Employee registration Page

Employee registration Page Description: - This is

Employee page. In this page employee fill all information
about its.

39
 EIS

Contact Us Page

Contact us Description: - This is Contact us page. In this

page information about Admin and Website developer.

40
 EIS

About Us Page

About us Description: - This is about us page. In this page

information about this website.

41
 EIS

Check for data entry Page

Check for data entry Description: - This is Checking page.

This page Employee when using then he enter and
registered its registration form.

42
 EIS

Select Specific Employee list in employee

side Page

Select Specific Employee list in employee side

Description: - This is Employee side page. This page
Employee when using then he show specific employee
details.

43
 EIS

Admin side Login page Page

Admin side login Description: - This is Admin side login

page. In this page Admin enter user name and password
and password is true then user login otherwise he is not
login admin side.

44
 EIS

User Details Page

User Details Description: - This is Admin side User details

page. In this page Admin Show all website visitor list.

45
 EIS

Select Specific Employee list in Admin side

Page

Select Specific Employee list in Admin side Description:

- This is Admin site page. In this page Admin show selected
post in selected employee all information.

46
 EIS

Employee Details Page

User Details: - This is Admin side User details page. In this

page Admin Show all Employee list.

47
 EIS

Post Details Page

Post Details: - This is Admin side Post details page. In this

page Admin Show all Post list is available in this company
and admin can add, delete and update the post list.

48
EIS

49
 EIS

Coding for Login button

Description: - This page of coding is about login of admin

and user.

Try
Dim cn As New SqlConnection("Data Source=.\
SQLEXPRESS;AttachDbFilename=|DataDirectory|\
luck.mdf;Integrated Security=True;User Instance=True")
Dim cmd As New SqlCommand
Dim cnstring As String
Dim s As String
If DropDownList1.SelectedItem.Selected = True
Then
s = DropDownList1.SelectedItem.Text
End If
cn.Open()
cnstring = "insert into Logindata values('" &
TextBox1.Text & "','" & TextBox2.Text & "','" & s & "')"
cmd = New SqlCommand(cnstring, cn)
cmd.ExecuteNonQuery()
cn.Close()
cmd = Nothing
MsgBox("record inserted")
Response.Redirect("show.aspx?")
Catch ex As Exception
MsgBox(ex.Message)

End Try

50
 EIS

Coding for Insert button

Description: - This page of coding is about insert data into

database.
Try
Dim s, ss As String
If D1.SelectedItem.Selected = True Then
s = Dl.SelectedItem.Text
End If
If Dl.SelectedItem.Selected = True Then
ss = Dl.SelectedItem.Text

End If
cn.Open()
cnstring = "Insert into employee values(" &
TextBox1.Text & ",'" & TextBox2.Text & " ','" &
TextBox3.Text & "','" & TextBox4.Text & "'," & TextBox5.Text
& ",'" & TextBox6.Text & "'," & TextBox7.Text & ",'" & s &
"','" & ss & "'," & TextBox8.Text & "," & TextBox9.Text &
"," & TextBox10.Text & "," & TextBox11.Text & "," &
TextBox15.Text & "," & TextBox12.Text & "," & TextBox13.Text
& "," & TextBox14.Text & ")"

cnd = New SqlCommand(cnstring, cn)

cnd.ExecuteNonQuery()
cn.Close()
cnd = Nothing
MsgBox("record inserted")

Catch ex As Exception
MsgBox(ex.Message)

End Try

51
 EIS

Coding for Delete button

Description: - This page of coding is about delete data into

database.

Try
cn.Open()
cnstring = "delete employee where no="
& TextBox1.Text
cnd = New SqlCommand(cnstring, cn)
' cmd.Parameters.Add("@no",
Data.SqlDbType.Int).Value.TextBox1.Text()

cnd.ExecuteNonQuery()
MsgBox("record deleted")

Catch ex As Exception
MsgBox(ex.Message)

End Try

52
 EIS

Coding for Update button

Description: - This page of coding is about update data into

database.

Try
cn.Open()
cnstring = ("update employee set
name=@n,address=@a,city=@c,age=@age,email=@email,Contactno=@
cno,bg=@bg,post=@post,salary=@salary,da=@da,hra=@hra,it=@it,
pf=@pf,allow=@allow,ded=@ded,net=@net where no=@noo")
cnd = New SqlCommand(cnstring, cn)
cnd.Parameters.Add("@n",
Data.SqlDbType.VarChar).Value = TextBox2.Text
cnd.Parameters.Add("@a",
Data.SqlDbType.VarChar).Value = TextBox3.Text
cnd.Parameters.Add("@c",
Data.SqlDbType.VarChar).Value = TextBox4.Text
cnd.Parameters.Add("@age",
Data.SqlDbType.Int).Value = TextBox5.Text
cnd.Parameters.Add("@email",
Data.SqlDbType.VarChar).Value = TextBox6.Text
cnd.Parameters.Add("@cno",
Data.SqlDbType.Int).Value = TextBox7.Text
cnd.Parameters.Add("@bg",
Data.SqlDbType.VarChar).Value = D1.SelectedItem.Text
cnd.Parameters.Add("@post",
Data.SqlDbType.VarChar).Value = Dl.SelectedItem.Text
cnd.Parameters.Add("@salary",
Data.SqlDbType.Int).Value = TextBox8.Text
cnd.Parameters.Add("@da",
Data.SqlDbType.Int).Value = TextBox9.Text
cnd.Parameters.Add("@hra",
Data.SqlDbType.Int).Value = TextBox10.Text
cnd.Parameters.Add("@it",
Data.SqlDbType.Int).Value = TextBox11.Text

53
 EIS
cnd.Parameters.Add("@pf",
Data.SqlDbType.Int).Value = TextBox15.Text
cnd.Parameters.Add("@allow",
Data.SqlDbType.Int).Value = TextBox12.Text
cnd.Parameters.Add("@ded",
Data.SqlDbType.Int).Value = TextBox13.Text
cnd.Parameters.Add("@net",
Data.SqlDbType.Int).Value = TextBox14.Text
cnd.Parameters.Add("@noo",
Data.SqlDbType.Int).Value = TextBox1.Text
cnd.ExecuteNonQuery()

MsgBox("Recored Updated")

Catch ex As Exception
MsgBox(ex.Message)

End Try

End Sub

54
 EIS

Coding for Select button

Description: - This page of coding is about select data into

database.
Try
cn.Open()
cnstring = "select
name,address,city,age,email,Contactno,bg,post,salary,da,hra,
it,pf,allow,ded,net from employee where no=" & TextBox1.Text

cnd = New SqlCommand(cnstring, cn)

dr = cnd.ExecuteReader
dr.Read()
If dr.HasRows Then
TextBox2.Text = dr(0)
TextBox3.Text = dr(1)
TextBox4.Text = dr(2)
TextBox5.Text = dr(3)
TextBox6.Text = dr(4)
TextBox7.Text = dr(5)

Dim i As Integer
For i = 0 To Dl.Items.Count - 1
If D1.Items.Item(i).Text = dr(6) Then

D1.Items.Item(i).Selected = True
Exit For
Else
D1.Items.Item(i).Selected = False
End If
Next
Dim n As Integer
For n = 0 To Dl.Items.Count - 1
If Dl.Items.Item(n).Text = dr(7) Then

Dl.Items.Item(n).Selected = True
Exit For
Else
Dl.Items.Item(n).Selected = False
End If

55
 EIS
Next

TextBox8.Text = dr(8)
TextBox9.Text = dr(9)
TextBox10.Text = dr(10)
TextBox11.Text = dr(11)
TextBox15.Text = dr(12)
TextBox12.Text = dr(13)
TextBox13.Text = dr(14)
TextBox14.Text = dr(15)

Else
MsgBox("Enter valid number")
End If

Catch ex As Exception
MsgBox(ex.Message)
MsgBox("Enter correct data")

End Try

Coding for Submit button

56
 EIS

Description: - This page of coding is about When user click

submit then its salary, da, hra, allow is counting and display
its solution.

Try

Dim da, hra, pf, allow, ded, net, salary, it As

Integer
salary = Dl.SelectedValue

da = salary * TextBox9.Text / 100

hra = salary * TextBox10.Text / 100
it = salary * TextBox11.Text / 100
pf = salary * TextBox15.Text / 100

ded = pf + it
allow = salary + da + hra
net = allow - ded
TextBox8.Text = salary
TextBox12.Text = allow
TextBox13.Text = ded
TextBox14.Text = net

Catch ex As Exception
MsgBox(ex.Message)
End Try

57
EIS

58
 EIS

There are mainly three types of user.

<1> Admin:-

Admin has the main Functionality. He has all Rights.

Admin can Insert, Update, or Delete a customer details. He
has the responsibility of Employee list which has less
quantity and also that material which are requested by the
user.

Admin has also responsibility of managing the

Employee list, user data list, post details order which is given
by the user.

<2> Employee:-

In Employee site Employee add its record update,

delete, insert, select its record in employee site employee
show contact module, about us module, login module and
check data eatery module.

Employ also check your data is enter or not in the

employee site specific five module authorize is selected.

<3> Visitor:-

Visitor can see the home page, contact us page ,about us

page and enter user data enter form select visitor type
selecting then it is insert data visited the “employee
information n system”.

59
EIS

60
 EIS

 Testing presents an interesting anomaly for the

software engineering activities, the engineer attempts
to build software from an abstract concept to a tangible
product. Now comes testing. The engineer creates a
series of test case that are initiated to "demolish" the
software that has been build. Infect, testing is the one
step in the software process that could be viewed
(psychologically, at least) as destructive rather than
constructive.

6.1 Testing Principle:-

 Testing is a process of executing a program with the

intent of finding an error.

 A good test case is one that has a high probability of

finding an as yet undiscovered error.

 A successful test is one that uncovers a yet

undiscovered error.

 Principle #1:- All tests should be traceable to

EMPLOYEE requirements.

 Principle #2:- Tests should be planned long before

testing begins.

61
 EIS

 Principle #3:- The pare to principle applied to

software testing.

 Principle #4:- Testing should begin in the small and

progress toward testing in large.

 Principle #5:- Exhaustive testing is not possible.

6.2 Testability:-
Software Testability is simple how easily can be tested.
The following characteristics lead to software.

 Operability.
 Observables.
 Controllability.
 Decomposability.
 Simplitycity.
 Stability.
 Understandability.

62
 EIS

6.3 Model Of Testing:-

 There are different Models of testing. On the basis of

testing methods there are two types of testing:-

1. White-box testing.

2. Black-box testing.

 White-box tests are used to examine the procedural

details. It checks the logical paths by test case. It can
also checks the conditions, loops used in the software
coding. It checks that loops are working correctly on
defined boundary value.

 Black-box tests are used to demonstrate that software

functions are operational, that input is properly
accepted and output is correctly produced, and that
integrity of external information is maintained.

1. WHITE-BOX TESTING:-

 White-box testing some times called glass-box testing,

is a test case design method that users the control
structure of the procedural design to drive the test case.

 Always we are thinking that there is no necessary to

execute or checks the loops and conditions.

63
 EIS

 And so large number of errors is uncovered.

 With using white-box testing methods, we have

checked that,
 All independent paths within a function have been
executed at least once.
 All logical decisions on their true and false side.
 A11 loops working correctly at their boundary
values and within their specified conditions.

 In our coding we test that all the loops works truly in

each module. The one technique of white-box testing is
basis path testing. It contains two parts, one is flow
graph notation and the second is cyclometer
complexity. In flow graph notation we are checking
logical control of flow. By using cyclometer complexity
we find complexity of our project structure.

2. BLACK-BOX TESTING:

 Black-box testing focuses on the functional

requirements of the software. That is black-box testing
enables the software engineer to drive sets of input
conditions that will fully exercise all functional
requirements for the program.

64
 EIS

 Black-box testing is not an alternative to white-box

testing techniques. Rather, it is a complementary
approach that is likely to uncover a different class of
errors than white-box methods.

 We use in our coding to find errors in the following

categories:
 Incorrect or missing functions
 Interface errors
 Errors in database
 Performance errors
 Initialization and termination errors.

 Unlike white-box testing, which is performed earlier in

the testing process, black-box testing tends to be
applied during later stages of testing. Because black-
box testing purposely disregards control structure,
attention is focused on the information domain.

 By applying black-box techniques, we derive a set of

test cases that satisfy following criteria.

 Test cases that reduce, by a count that is greater then

one, the number of additional test cases must be
designed to achieve reasonable testing.

65
 EIS

 Test cases that tell us something about the present or

absence of classes of errors, rather then an error
associated only with the specific test at hand.

6.4 Testing Strategy:-

Content Testing:-

 Errors in Web Application content can be as trivial as

minor typographical error as incorrect information,
improper organization or validation of intellectual
property laws. Content Testing attempt to uncover this
and many other problems before the user encounter
them.

Content Testing Objectives:-

 There are three types of objectives.

 To uncover syntactic errors in text-based

documents, graphical representation and other
media.
 To uncover semantic errors in any content object
represented as navigation occurs, and
 To find errors in organization or structure of
content that is presented to the end-user

Database Testing:-

 Modern Web Application does much more than present

static content objects. In many application domains,

66
 EIS

WebApps interface with sophisticated database

management system and build dynamic content object
that are created in real time using the data acquired
from a database.

 Database Testing for WebApps is complicated by a

variety of factor.

1) The original client side request for information is

rarely presented in form that can be input to a database
management system.

2) The database may be remote to the server that

houses the Web Applications.

Web Application Server and properly formatted for

subsequent transmittal to the client.

3) RAW data acquired from the database must be

transmitted to the client.

4) The dynamic content objects must be transmitted to

the client in a form that can be displayed to the end
user.

 In figure testing should be ensure that :-

1. Valid information is passed between the client

and server from the interface layer.

2. The WebApps process script correctly and

properly extract or formats user data.

67
 EIS

3. Queries are passed to a data management

layer that communicates with
database access routines.

4. User data are passed correctly to a server side

data transformation function that format
appropriate queries.

Client layer-user interface

Server layer- WebApp

Server layer-
Data transformation

Server layer - data

Management

Database layer – data access

68
 EIS

4.3[Layers of interaction]

Interface Testing:-

 Interface design model is reviewed to ensure that

generic quality criteria established for all user interfaces
have been achieved and that application specific
interface design issue has been properly addressed.

Interface Testing Strategy:-

 The overall strategy for interface testing is to (1)

Uncover error related to specific Interface mechanisms
(2) uncover errors in the way the interface implements
the semantics of navigation, WebApp functionality, or
content display .to accomplish this strategy, a number
of objectives must be achieved:

 Interface futures are tested to ensure that design

rules, aesthetics, and related visual content are
available for the user without error.

 Individual interface mechanisms are tested in a

manner that is alogous to unit testing For example,
tests are designed to exercise all forms, client-side
scripting, dynamic HTML.

69
 EIS

Testing Interface Mechanisms:-

 When a user interacts with a WebApp, the interaction

occurs through one or more interface mechanisms.

Links: -

 Each link is tested to ensure that the proper content

object or function is reached. The Web engineer
builds a list of all links associated with interface
layout. And then executes each individually.

Forms: - At a microscopic level, tests are performed to

ensure that

(1) Labels correctly identified fields within the form

and that mandatory fields are identified visually for
the user.

(2) The server receives all information content

within the form and their no data are lost in the
transmission between client and server.

(3) Appropriate defaults are used when the user

does not select from a pull down menu or set of
buttons.

(4) Browser function don’t corrupt data enter in a

form.

70
 EIS

(5) Scripts that perform error checking on data

entered work properly and provide meaningful error
message.

Client Side Scripting:-

 Black box tests are conducted to uncover any error in

processing as the script is executed. These tests are
coupled with forms testing because script input is often
derived from data provided as part of forms processing.

Dynamic HTML:-

 Each Web page that contains dynamic HTML is

executed to ensure that the dynamic display is correct.
In addition a compatibility test should be conducted to
ensure that the dynamic HTML is work properly in the
environmental configuration that support the WebApps.

 Application specific interface mechanisms:-Test

conforms to a checklist of functionality and features that
are defined by the interface mechanism.

 Boundary test minimum and maximum number of item

that can be placed in to shopping chart.

 Test to determine persistence of shopping chart

contents.

 Test to determine whether the WebApp can be record

shopping chart content at some future date.

71
 EIS

Usability Testing:-

 Usability test may be designed by Web engineering

team.

1. Define a set of usability testing categories and identify

goal for each.
2. Design test that will enable each goal to be evaluated.

3. Select participants who will conduct test.

4. Instrument participant’s interaction with WebApp while

testing is conducted.

5. Develop a mechanism for assessing the usability of the

WebApp.

 The following test categories and objective illustrate

establish testing:

 Interactivity: - Are interaction mechanism easy to

understand and use?

 Layout: - Are navigation mechanism, content and

function place in a manner that allows the user to
find them quickly?

 Readability: - Is text well written and under

stable?

 Aesthetics:-Do layout color, typeface, and related

characteristics lead to ease of use?

72
 EIS

 Display Characteristics: - Does the WebApp

make optimal use of screen size and resolution?

 Time Sensitivity: - Can important features,

functions and content be used in a timely manner?

 Accessibility:- Is the WebApp accessible to

people who have disabilities?

Compatibility Testing:-

 WebApps must operate within environment that differs

from one another. Different computer, display device,
OS, browser and network connection speed can have
significant on WebApp operation. Different browser
some time produced slightly different results, regardless
of the degree of HTML standardization within the
WebApps.

 The Web Engineering team derives a series of

compatibility, validation tests, derived from existing
interface tests, navigation tests, performance tests and
security tests.

Test Cases:-

(1) Invalid User:-

Test Case:-

73
 EIS

 If the username and password is not valid, means that

the person who is trying to access the website is not
authenticated so system will give the message that
unauthicated user.

Solution:-

 Solution of this case is that user is not aware about the

login criteria so the person needs to create its account
to the website and it may be there mistake in the typing
so it needs to retype the username and password.

(2) Invalid Information entered on search page:-

Test Case:-

 If the any user enters invalid information on the search

page a message is generated or on asking user to
enter the correct type.

Solution:-

 Solution of this case is that user is not aware about the

Type of data to be search or it may be person’s mistake
in the searching so it needs to research the information.

(3) Invalid Information entered on seller page:-

Test Case:-

 If the name enters invalid information an error message

is generated on asking user to enter the correct type.

74
 EIS

Solution

 Solution of this case is that user is not aware about the

Type of data to be entered or it may be person’s
mistake in the typing so it needs to retype the
information.

(4) Invalid Information entered on buyer page:-

Test Case:-

 If the name enters invalid information an error message

is generated on asking user to enter the correct type.

Solution:-

 Solution of this case is that user is not aware about the

Type of data to be entered or it may be person’s
mistake in the typing so it needs to retype the
information.

(5) Error in data base connectivity

Test Case:-

 If there is any problem connecting to the database user

will be asked to browse and search for the data base
and establish the bridge.

Solution:-

75
 EIS

 Solution of this case is that user has to first establish

the connectivity with the database and then run the
project.

(6) Error loading the module

Test Case:-

 This problem may arise if the browser does not have

the write support.

Solution:-

 Solution is to first check the browser supports for

module.

76
EIS

77
 EIS

Future Enhancement
 We think that not a single project is ever
considered as complete forever because our mind
is always thinking something new and our
necessities also are growing day by day. We
always want something more than what we have.
Our application also, if you see at the first glance
than you find it to be complete but we want to
make it still mature and fully automatic. Some of
the expansions which we have thought of are:

 We want to improve this system to the day by day

generate repot.

 We want printing facility to the employee

information.

 We want to improve feedback facility Company

related questions.

 We are planning to place this software on internet.

78
EIS

79
 EIS

Bibliography
 During the Development of our system, we have taken the
References Books which I would like to mention in this
Section.

-: Books:

 The Complete Reference vb Programming

 Asp.net 3.5

Links:

 www.code4u.com
 www.codeproject.com
 www.yahoosearch.com
 www.wikipedia.com

80
EIS

81