Payroll Automation Final

PAYROLL AUTOMATION SYSTEM
CHAPTER 1
INTRODUCTION
JYOTI SHUKLA Page 1

INTRODUCTION:-
Today every work is going to be computerized. Manpower is used with computer system to
increase the efficiency and reliability of the work. It also provides a lot of saving of time to
do that work with friendliness
1.1 PROBLEM DEFINITION:-

In existing system, manages data related to various entities and activities manually.
Problem in existing system:
1. Time consuming: As the system is not computerized and a lot of works are done manually
it consumes a significant amount of time. It is required to prepare the result as early as
possible ,which not possible in the existing system.
2. Accuracy: Accuracy is statistically necessarily for result preparation, which is not possible
in the existing system. There may be changes of making mistakes while considering such a
complex problem manually.
3. Detailed report: The existing system is unable to give the detailed report due to non-
availability of information in database.
4. Paper work: As the existing system is manual, lots of paper work has to be done.
5. Security: There is a lack of security and privacy checks in existing system. Anybody can
be access and modify the information in to registers.
6. Static: The existing system is not dynamic and can’t accept the changes at advanced stage.
JYOTI SHUKLA Page 2

Disadvantages of manual system:
• Slow speed of execution.

• Accuracy of work is not 100%
• Ability to remember inaccurate information.
• Slow thinking & modifying in new situations.
• Ability to learn by trial and error method.
• Work may not be very neat.
• Secrecy of work is not maintained completely.
• Paper work can be misplaced & at the time of need it’s hard to find.
Advantages of Computerization:
• Fast speed of execution.

• Accuracy of work is 100%
• Ability to remember accurate information.
• Follows the instructions perfectly.
• Continues a very good process over a long period.
• Ability to think and modify in new situations.
• Ability to learn by enables trial and error method.
JYOTI SHUKLA Page 3

1.2 PROJECT OVERVIEW:-

Today every work is going to be computerized. Manpower is used with computer system
to increase the efficiency and reliability of the work. It also provides a lot of saving of
time to do that work with friendliness.
Payroll is a windows-based application intended to provide automated solution and services

to Admin & Employee.
In our project mainly we have to provide a facility to student & collage faculty to manage
student information easily & provide security.
1.3 Need &Scope:-
Today every work is going to be computerized. Main power is used with computer system to
increase the efficiency and reliability of the work. It also provides a lot of saving of time to
do that work with friendliness.
Whenever a new project is undertaken or a new system is proposed it has always certain
objectives.
 Computerization will have a great effect on proper use of resources, thus
contributing to rise the institution standard and to solve the complications that
occur while handling through the paper work.
 This reduces the extra costs and efforts that are spend while performing all the
tasks manually.
JYOTI SHUKLA Page 4

CHAPTER 2
REQUIERMENT
ANALYSIS
JYOTI SHUKLA Page 5

2.1 Hardware Requirement:-
hardware specification of machine used:
CPU DUAL CORE
RAM 512MB
HDD 10 GB
KEYBOARD MULTIMEDIA
MOUSE OPTICAL MOUSE
MONITOR 17” (COLORS)
2.2 Software Requirement:-
Software (O.S. Language, Packages) used along version:
OPERATING SYSTEM WINDOWS-7
FRONT END VB. NET
BACK END MS WORD
PACKAGE MS-WORD
JYOTI SHUKLA Page 6

2.3 Feasibility Study:-

The feasibility study is important because it forces the ideas to put on paper and to assess
whether or not these idea are realistic. Before you begin writing your business plan you need
to identify how, where, and to whom you intend to sell a service or product. You also need
your competition and figure out how much money you need to start your business and keep it
running until it is established.
1. Technical Feasibility
It centers around the existing computer system (h/w, s/w…) and to what extent it can
support the proposed system. The necessary H/W and S/W tools available in the organization
and the software recommended support the system objects. Thus, it is technically feasible to
and develops the proposed system.
Our project is technically feasible, as we have takenVB.NEt as our front end.
Advantages of language are achieved as:-
Good interface for user.
Allow changes as when required.
It is Rapid Action development tool, which makes processing fast.
Coding make technical processing easy.
VB.NEt is event driven which means use is in control of application.
VB.NEt is infinitely extensible through the use of Active-X control, dynamically linked
libraries.
2. Economic Feasibility
Economic feasibility is the most frequently used method for evaluating the effectiveness of
the proposed system. This is an on going effort that improves in accuracy at each phase of the
system life cycle. As the necessary software and hardware is nil. The proposed system is
minimizes the time and effort of the data collection, answering queries and generate reports
which results significant saving of the operating cost. Thus, the proposed system is
economically feasible.
JYOTI SHUKLA Page 7

3. Operational Feasibility
Users are inherently resistant to change and computers have been known to facilitate change.
An estimate should be made of how strong a reaction the user is likely to words the
development of a new system. As the proposed system is user is almost negligible.
Therefore, resistance to the proposed system is nil. Based on the above analysis the
recommended system is feasible.
JYOTI SHUKLA Page 8

CHAPTER 3
SYSTEM ANALSIS
&
DESIGN
JYOTI SHUKLA Page 9

Level-0 DFD
INPUT OUTPUT
Process
Data Base
JYOTI SHUKLA Page 10

Level-1 DFD
INPUT
Add
Employee
Employee
Attendance
ADMIN
Salary
Advances
INFORMATION

CHAPTER 4
SYSTEM
DESIGN

4.1 E-R Diagram:-
An entity-relationship diagram (ERD) is a type of data modeling that shows a graphical

representation of objects or concepts within an information system or organization and their
relationship to one another. Diagram consists of the following major components:
1. Rectangles, which represent entity sets
2. Ellipses, which represent attributes
3. Diamonds, which represent relationship sets
A relationship is the association that describes the interaction between entities.

E-R DIAGRAM

Addres
DOB s
User Name
Passwor
Registration d
Email
Name
Logi
n
Employee
Name
Salary attenda Paymen

nce t
advanc
e
salary
report

CHAPTER 5
TECHNICAL
DESCRIPTION

VB.NET IN FRONT END
VB.NET, the next version of VB, is a programming framework used to create

enterprise-class window Applications
. These applications are accessible on a global basis leading to efficient information
management
. The advantage VB.NET offers is more than just the next version of VB.
Why VB.NET?
Since 1995, Microsoft has been constantly working to shift it's focus from
Windows-based platforms to the Internet. As a result, Microsoft introduced VB (Active
Server Pages) in November 1996. VB offered the efficiency of ISAPI applications along
with a new level of simplicity that made it easy to understand and use. However, VB script
was an interpreted script and consisted unstructured code and was difficult to debug and
maintain. As the web consists of many different technologies, software integration for Web
development was complicated and required to understand many different technologies.
Also, as applications grew bigger in size and became more complex, the number of lines
of source code in VB applications increased dramatically and was hard to
maintain. Therefore, an architecture was needed that would allow development of Web
applications in a structured and consistent way.
The .NET Framework was introduced with a vision to create globally distributed
software with Internet functionality and interoperability. The .NET Framework consists of
many class libraries, includes multiple language support and a common execution platform.

It's a very flexible foundation on which many different types of top class applications can
be developed that do different things. Developing Internet applications with the .NET
Framework is very easy. VB.NET is built into this framework; we can create VB.NET
applications using any of the built-in languages.
Unlike VB, VB.NET uses the Common Language Runtime (CLR) provided by
the .NET Framework. This CLR manages execution of the code we write. VB.NET code is
a compiled CLR code instead of interpreted code (VB). CLR also allows objects written in
different languages to interact with each other. The CLR makes development of Web
applications simple.
Advantages Using VB.NET

o VB.NET drastically reduces the amount of code required to build large applications
o VB.NET makes development simpler and easier to maintain with an event-driven,
server-side programming model
o VB.NET pages are easy to write and maintain .
o The source code is executed on the server. The pages have lots of power and
flexibility by this approach
o The source code is compiled the first time the page is requested. Execution is fast as
the Web Server compiles the page the first time it is requested. The server saves the
compiled version of the page for use next time the page is requested
o The HTML produced by the VB.NET page is sent back to the browser. The
application source code you write is not sent and is not easily stolen
o VB.NET makes for easy deployment. There is no need to register components
because the configuration information is built-in
o The Web server continuously monitors the pages, components and applications
running on it. If it notices memory leaks, infinite loops, other illegal software or
activities, it seamlessly kills those activities and restarts itself
o VB.NET validates information (validation controls) entered by the user without
writing a single line of code

o VB.NET easily works with ADO .NET using data-binding and page formatting
features
o VB.NET applications run fater and counters large volumes of users without
performance problems
 s
MS-ACCESS IN BACK END
Microsoft Access is a DBMS (also known as Database Management System) from Microsoft
that combines the relational Microsoft Jet Database Engine with a graphical user interface
and software-development tools. It is a member of the Microsoft Office suite of applications,
included in the Professional and higher editions or sold separately.
Microsoft Access stores data in its own format based on the Access Jet Database Engine. It
can also import or link directly to data stored in other applications and databases.
Software developers and data architects can use Microsoft Access to develop application
software, and "power users" can use it to build software applications. Like other Office
applications, Access is supported by Visual Basic for Applications (VBA), an object-based
programming language that can reference a variety of objects including DAO (Data Access
Objects), ActiveX Data Objects, and many other ActiveX components. Visual objects used in
forms and reports expose their methods and properties in the VBA programming
environment, and VBA code modules may declare and call Windows operating-system
functions.

CHAPTER 6
DATABASE
DESGINE


CHAPTER 7

SCREENSHOTS







CHAPTER 8
TESTING
TESTING STRATEGIES ADAPTED:-

White Box Testing:-
It is also called glass box testing. It is a test case design

to derive test cases. In this, all statement in the program has been executed at least once
during testing that all logical condition has been exercised. Using white box testing
methods, the software engineer can derive test cases that

Guarantee that all independent paths within a module have been exercised at least once.
Exercise all loops at their boundaries and within their operational bounds.
Exercise internal data structure to assure their validity.
Basic path testing, a white-box technique, makes use of program graphs to drive
the set of linearly independent tests that will ensure coverage. Condition and data floe
testing further exercise program logic, and loop testing complements other white-box
technique by providing a procedure for exercising loops of varying degrees of
complexity.
Black Box Testing:-
Knowing the specified function that a product has been design

to perform, tests can be conducted that demonstrate each function is fully operational
while at the same time searching for errors in each function black box testing alludes to
test that are conducted at the software interface. A black box test examines some
fundamental aspect of a system with little regard for he internal logical structure of
software.
SYSTEM TESTING
Testing Techniques:-
The time dependent, asynchronous nature of many real-time

applications adds a new and potential difficult element to the mix-time. Not only does the test
case designer have to consider white-box test cases but also event handing, the timing of the
data, and the parallelism of the tasks (Process) that handle the data.

Comprehensive test case design methods for real-time system have yet to evolve.
However an overall four-step strategy can be proposed:
 Task Testing
 Behavioral Testing
 Inter Task Testing
 System Testing
Task Testing:-
The first step in the testing of real-time software is to test each task
independently. That is, white-box and black-box tests are designed and executed for each
task. Each task is executed independently during these tests; Task testing uncovers error
in logic and function but not timing or behavior.
Behavioral Testing:-
Using system models created with CASE tools, it is possible to

simulate the behavior of a real-time system and examine its behavior as a consequence of
external events. These analysis activities can serve as the basic for the design of test cases
that are conducted when the real-time software has been built. Using a technique that is
similar to equivalent partitioning, events are categorized for testing. For example, events
for the photocopier might be user interrupts mechanical interrupts, system interrupt, and
failure mode. Each of these events tested individually and the behavior of the executable
system is examined to detect errors that occur as a consequence of processing associated
with these events. The behavior of system model and the executable software can be
compared for performance.
Inter Task Testing:-
Once errors in individual tasks and in system behavior have been isolated,
testing shifts to time-related errors. Asynchronous tasks that are known to communicate
with one another are tested with different data rates and processing load to determine if
inters task synchronization errors will occur. Task that communicate via a message queue
or data store are tested to uncover errors in the sizing of these data storage areas.

System Testing:-
Software and hardware are integrated and full ranges of system test are
conducted in an attempt to uncover errors at the software/hardware interface. Most real-
time systems process interrupts. The tester develops a list of all possible interrupts and
the processing that occurs as a con sequence of the interrupts. Tests are then designed to
asses the following system characteristics.
Testing is a very important part of a SDLC, and check that all modules of project working
correct or not. Checking is based on a give all possible inputs after that if modules is work
fine then testing goes to successfully.
Objectives of Testing
Major objectives for performing Application Testing are:
1. Once the programming part is over, the software is tested. This is done to ensure that
the software works in the way that it was supposed to work. Also bugs, if any, are
removed once these are found.
2. The goal of testing is to find errors. A test, which reveals an error is more useful, then
hundreds of test that sail smoothly. Thus testing can only show the presence of an
error however it can never show the absence of an error.
3. Good testing procedures followed by well device testing strategies and testing data
can help in quality assurance and decrease the chances of system failure.
Testing Methods / Techniques used

There are many testing methods but only two testing methods used and methods are:
1. Unit testing
Each component or part of the system is tested individually. The programmer does this
testing. Valid and invalid data are used to check the program (destructive testing). This helps
to see if the program breaks under any circumstances.
2. System Testing

This is an integrated form of testing which focuses on functionality and interfaces between n
units or modules. After all the units are successfully tested and bugs are removed the whole
of the software is tested as combination of all the modules that interact with each other to
achieve a goal.
Test Case Design (Manual/ Automated)

What is test case?
A set of test inputs, execution conditions, and expected results developed for a particular
objective, such as to exercise a particular program path or to verify compliance with a
specific requirement.
Definition
“A test case has components that describe an input, action or event and an expected response,
to determine if a feature of an application is working correctly.” Definition by IEEE
Test Automated
Another important aspect of test automation is the idea of partial test automation, or
automating parts but not all of the software testing process. If, for example, a MySql cannot
reasonably be created, or if fully automated tests would be too difficult to maintain, then a
software tools engineer can instead create testing tools to help human testers perform their
jobs more efficiently. Test automation is expensive and it is an addition, not a replacement, to
manual testing.

CHAPTER 6
CODING
Public Class Form8

Inherits System.Windows.Forms.Form
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
#Region " Windows Form Designer generated code "
Public Sub New()

MyBase.New()
'This call is required by the Windows Form Designer.

InitializeComponent()
'Add any initialization after the InitializeComponent() call
End Sub
'Form overrides dispose to clean up the component list.

Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)

If disposing Then
If Not (components Is Nothing) Then
components.Dispose()
End If
End If
MyBase.Dispose(disposing)
End Sub
'Required by the Windows Form Designer

Private components As System.ComponentModel.IContainer
'NOTE: The following procedure is required by the Windows Form Designer

'It can be modified using the Windows Form Designer.
'Do not modify it using the code editor.
Friend WithEvents TextBox1 As System.Windows.Forms.TextBox
Friend WithEvents Button1 As System.Windows.Forms.Button
Friend WithEvents Label1 As System.Windows.Forms.Label
Friend WithEvents PictureBox1 As System.Windows.Forms.PictureBox
<System.Diagnostics.DebuggerStepThrough()> Private Sub
Dim resources As System.Resources.ResourceManager = New
System.Resources.ResourceManager(GetType(Form8))
Me.TextBox1 = New System.Windows.Forms.TextBox
Me.Button1 = New System.Windows.Forms.Button
Me.Label1 = New System.Windows.Forms.Label
Me.PictureBox1 = New System.Windows.Forms.PictureBox
Me.SuspendLayout()
'
'TextBox1
'
Me.TextBox1.Location = New System.Drawing.Point(208, 72)
Me.TextBox1.Name = "TextBox1"
Me.TextBox1.TabIndex = 0
Me.TextBox1.Text = ""
'
'TextBox2
'
Me.TextBox2.PasswordChar = Microsoft.VisualBasic.ChrW(42)
Me.TextBox2.Text = ""
'
'Button1
'
Me.Button1.BackColor = System.Drawing.Color.Red
Me.Button1.ForeColor = System.Drawing.SystemColors.HighlightText
Me.Button1.Location = New System.Drawing.Point(184, 160)
Me.Button1.Name = "Button1"
Me.Button1.TabIndex = 2

Me.Button1.Text = "LOGIN"
'
'Label1
'
Me.Label1.ForeColor = System.Drawing.SystemColors.Highlight
Me.Label1.Location = New System.Drawing.Point(136, 112)
Me.Label1.Name = "Label1"
Me.Label1.Size = New System.Drawing.Size(64, 16)
Me.Label1.TabIndex = 3
Me.Label1.Text = "Password"
'
'Label2
'
Me.Label2.ForeColor = System.Drawing.SystemColors.Highlight
Me.Label2.Text = "User Name"
'
'Label8
'
Me.Label8.BackColor = System.Drawing.Color.Red
Me.Label8.BorderStyle = System.Windows.Forms.BorderStyle.FixedSingle
Me.Label8.Font = New System.Drawing.Font("Arial Narrow", 16.0!,
System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0,
Byte))
Me.Label8.ForeColor = System.Drawing.SystemColors.ControlLight
Me.Label8.Text = "LOGIN FORM"
'
'PictureBox1
'
Me.PictureBox1.BackgroundImage =
CType(resources.GetObject("PictureBox1.BackgroundImage"),
System.Drawing.Image)
Me.PictureBox1.BorderStyle = System.Windows.Forms.BorderStyle.Fixed3D
Me.PictureBox1.Location = New System.Drawing.Point(16, 56)
Me.PictureBox1.Name = "PictureBox1"
Me.PictureBox1.Size = New System.Drawing.Size(96, 128)
Me.PictureBox1.TabIndex = 21
Me.PictureBox1.TabStop = False
'
'Form8
'
Me.AutoScaleBaseSize = New System.Drawing.Size(5, 13)
Me.BackColor = System.Drawing.Color.FromArgb(CType(255, Byte),
CType(255, Byte), CType(192, Byte))
Me.ClientSize = New System.Drawing.Size(376, 214)
Me.Controls.Add(Me.PictureBox1)
Me.Controls.Add(Me.Label8)
Me.Controls.Add(Me.Button1)

Me.Controls.Add(Me.TextBox2)
Me.Controls.Add(Me.TextBox1)
Me.Name = "Form8"
Me.Text = "Login Form"
Me.ResumeLayout(False)
End Sub
#End Region
Private Sub Form8_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load
' Try
cn.Open("Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=hospital_management.mdb")
rs.Open("login", cn, ADODB.CursorTypeEnum.adOpenDynamic,
ADODB.LockTypeEnum.adLockOptimistic)
'Catch ex As Exception
' MsgBox(Err.Description)
' End Try
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button1.Click
' On Error Resume Next
rs.MoveFirst()
'MsgBox(rs(0).Value)
rs.Find("userid='" & Trim(TextBox1.Text) & "'")

'MsgBox(rs(0).Value)
If rs.EOF Or rs.BOF Then
MsgBox(" wrong username or password ")
Exit Sub
End If
If (rs(0).Value = Trim(TextBox1.Text)) And (rs(1).Value =

Trim(TextBox2.Text)) Then
'MsgBox(" password is correct")
Me.Hide()
Dim F9 As New Form9

F9.Show()
Else
MsgBox(" wrong username or password ")
End If
End Sub
Private Sub Label2_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Label2.Click
End Sub
Private Sub Label1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Label1.Click

Public Class Form2

Inherits System.Windows.Forms.Form
#Region " Windows Form Designer generated code "
Public Sub New()

MyBase.New()
'This call is required by the Windows Form Designer.

'Add any initialization after the InitializeComponent() call
End Sub
'Form overrides dispose to clean up the component list.

Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)
If disposing Then
If Not (components Is Nothing) Then
components.Dispose()
End If
End If
MyBase.Dispose(disposing)
End Sub
'Required by the Windows Form Designer

Private components As System.ComponentModel.IContainer
'NOTE: The following procedure is required by the Windows Form Designer

'It can be modified using the Windows Form Designer.
'Do not modify it using the code editor.
Friend WithEvents GroupBox2 As System.Windows.Forms.GroupBox
Friend WithEvents BTNCLOSE As System.Windows.Forms.Button
Friend WithEvents BTNFIND As System.Windows.Forms.Button
Friend WithEvents BTNCNC As System.Windows.Forms.Button
Friend WithEvents BTNSAVE As System.Windows.Forms.Button
Friend WithEvents BTNADD As System.Windows.Forms.Button
Friend WithEvents GroupBox1 As System.Windows.Forms.GroupBox
Friend WithEvents DateTimePicker1 As System.Windows.Forms.DateTimePicker
<System.Diagnostics.DebuggerStepThrough()> Private Sub
Me.GroupBox2 = New System.Windows.Forms.GroupBox

Me.BTNCLOSE = New System.Windows.Forms.Button

Me.BTNFIND = New System.Windows.Forms.Button
Me.BTNCNC = New System.Windows.Forms.Button
Me.BTNSAVE = New System.Windows.Forms.Button
Me.BTNADD = New System.Windows.Forms.Button
Me.GroupBox1 = New System.Windows.Forms.GroupBox
Me.DateTimePicker1 = New System.Windows.Forms.DateTimePicker
Me.GroupBox2.SuspendLayout()
Me.GroupBox1.SuspendLayout()
Me.SuspendLayout()
'
'Label1
'
Me.Label1.BackColor = System.Drawing.Color.FromArgb(CType(255, Byte),
CType(192, Byte), CType(192, Byte))
Me.Label1.Font = New System.Drawing.Font("Monotype Corsiva", 24.0!,
CType((System.Drawing.FontStyle.Bold Or System.Drawing.FontStyle.Italic),
System.Drawing.FontStyle), System.Drawing.GraphicsUnit.Point, CType(0, Byte))
Me.Label1.ForeColor = System.Drawing.Color.Red
Me.Label1.Text = "SALES ENTRY"
'
'GroupBox2
'
Me.GroupBox2.BackColor = System.Drawing.Color.FromArgb(CType(192,
Byte), CType(192, Byte), CType(255, Byte))
Me.GroupBox2.Controls.Add(Me.BTNCLOSE)
Me.GroupBox2.Controls.Add(Me.BTNFIND)
Me.GroupBox2.Controls.Add(Me.BTNCNC)
Me.GroupBox2.Controls.Add(Me.BTNSAVE)
Me.GroupBox2.Controls.Add(Me.BTNADD)
Me.GroupBox2.Location = New System.Drawing.Point(64, 454)
Me.GroupBox2.Name = "GroupBox2"
Me.GroupBox2.Size = New System.Drawing.Size(616, 88)
Me.GroupBox2.TabIndex = 8
Me.GroupBox2.TabStop = False
Me.GroupBox2.Text = "OPERATION"
'
'BTNCLOSE
'
Me.BTNCLOSE.Location = New System.Drawing.Point(440, 40)
Me.BTNCLOSE.Name = "BTNCLOSE"
Me.BTNCLOSE.Size = New System.Drawing.Size(80, 24)

Me.BTNCLOSE.TabIndex = 4
Me.BTNCLOSE.Text = "CLOSE"
'
'BTNFIND
'
Me.BTNFIND.Location = New System.Drawing.Point(344, 40)
Me.BTNFIND.Name = "BTNFIND"
Me.BTNFIND.Size = New System.Drawing.Size(80, 24)
Me.BTNFIND.TabIndex = 3
Me.BTNFIND.Text = "FIND"
'
'BTNCNC
'
Me.BTNCNC.Location = New System.Drawing.Point(248, 40)
Me.BTNCNC.Name = "BTNCNC"
Me.BTNCNC.Size = New System.Drawing.Size(80, 24)
Me.BTNCNC.TabIndex = 2
Me.BTNCNC.Text = "CANCLE"
'
'BTNSAVE
'
Me.BTNSAVE.Location = New System.Drawing.Point(152, 40)
Me.BTNSAVE.Name = "BTNSAVE"
Me.BTNSAVE.Size = New System.Drawing.Size(80, 24)
Me.BTNSAVE.TabIndex = 1
Me.BTNSAVE.Text = "SAVE"
'
'BTNADD
'
Me.BTNADD.Location = New System.Drawing.Point(32, 40)
Me.BTNADD.Name = "BTNADD"
Me.BTNADD.Size = New System.Drawing.Size(80, 24)
Me.BTNADD.TabIndex = 0
Me.BTNADD.Text = "ADD"
'
'GroupBox1
'
Me.GroupBox1.BackColor = System.Drawing.Color.FromArgb(CType(255,
Byte), CType(224, Byte), CType(192, Byte))
Me.GroupBox1.Controls.Add(Me.DateTimePicker1)
Me.GroupBox1.Controls.Add(Me.TextBox5)
Me.GroupBox1.Controls.Add(Me.Label3)
Me.GroupBox1.Font = New System.Drawing.Font("Microsoft Sans Serif",
9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point,
CType(0, Byte))
Me.GroupBox1.Location = New System.Drawing.Point(32, 102)
Me.GroupBox1.Name = "GroupBox1"
Me.GroupBox1.Size = New System.Drawing.Size(688, 328)

Me.GroupBox1.TabIndex = 7
Me.GroupBox1.TabStop = False
Me.GroupBox1.Text = "SALES ENTRY"
'
'DateTimePicker1
'
Me.DateTimePicker1.Format =
System.Windows.Forms.DateTimePickerFormat.Short
Me.DateTimePicker1.Location = New System.Drawing.Point(184, 136)
Me.DateTimePicker1.Name = "DateTimePicker1"
Me.DateTimePicker1.Size = New System.Drawing.Size(104, 22)
Me.DateTimePicker1.TabIndex = 17
'
'TextBox5
'
Me.TextBox5.Multiline = True
Me.TextBox5.Size = New System.Drawing.Size(184, 88)
Me.TextBox5.Text = "SALES"
'
'TextBox4
'
Me.TextBox4.Font = New System.Drawing.Font("Microsoft Sans Serif",
CType(0, Byte))
Me.TextBox4.Text = "TextBox4"
'
'TextBox3
'
Me.TextBox3.Multiline = True
'
'Label3
'
Me.Label3.Font = New System.Drawing.Font("Microsoft Sans Serif", 9.0!,
Byte))
Me.Label3.Text = "REMARK"
'
'TextBox2
'


CType(0, Byte))
'
'TextBox1
'
CType(0, Byte))
'
'Label9
'
Byte))
Me.Label9.Text = "ORDER DATE"
'
'Label8
'
Byte))
Me.Label8.Text = "SALES TO"
'
'Label7

CHAPTER 9
CONCLUSION
CONCLUSION:-

Conclusion is the summarized evaluation of overall project objectives attainment. It shows

the limitation of project as well as highlights difficulties while carrying the development and
enhancement possible afterwards.
Conclusion and Discussion

After a completed a project we are come on a conclusion. And conclusion have some points,
points are:
1. With the help of this project any store works the accurate billing of the purchase and
sale and closing balance of the item .
2. This project mainly based on stock maintenance Purchase and sales report of the cash
memo
Difficulties encountered during project
Many Difficulties are encountered during project but some main difficulties are:
1. Difficulties in information gathering.
2. Difficulties in managing the table records.
3. Difficulties in making constraints.

CHAPTER 10
LIMITATION
&
FUTURE
ENHANCEMENT

Limitations:-
 We have tried to develop our system as best as possible, but it is developed on
automation of knowledge based collected from the responsible authorities of the
finance, any missing of information may lead to the limitation of our project.
 We can’t provide any help facility in this project due to time limitation.
 We can use this project on stand alone system
Future Enhancements
There are some limitations of current project and these limitations remove we will remove in
future. Add online features for this project.

CHAPTER 11
REFERENCES
Reference Books
1. Complete Reference
2. VB.net beginner to intermediate .nets

Websites
1. www.WordPress.ORG
2. www.W3School.com
3. www.google.co.in.

Payroll Automation Final

Uploaded by

Copyright:

Available Formats

Payroll Automation Final

Uploaded by

Document Information

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

Payroll Automation Final

Uploaded by

Copyright:

Available Formats

PAYROLL AUTOMATION SYSTEM

JYOTI SHUKLA Page 1

1.1 PROBLEM DEFINITION:-

Problem in existing system:

JYOTI SHUKLA Page 2

Disadvantages of manual system:

• Slow speed of execution.

• Fast speed of execution.

JYOTI SHUKLA Page 3

1.2 PROJECT OVERVIEW:-

Payroll is a windows-based application intended to provide automated solution and services

1.3 Need &Scope:-

JYOTI SHUKLA Page 4

JYOTI SHUKLA Page 5

2.1 Hardware Requirement:-

hardware specification of machine used:

CPU DUAL CORE

MOUSE OPTICAL MOUSE

MONITOR 17” (COLORS)

2.2 Software Requirement:-

Software (O.S. Language, Packages) used along version:

OPERATING SYSTEM WINDOWS-7

FRONT END VB. NET

BACK END MS WORD

JYOTI SHUKLA Page 6

2.3 Feasibility Study:-

JYOTI SHUKLA Page 7

JYOTI SHUKLA Page 8

JYOTI SHUKLA Page 9

JYOTI SHUKLA Page 10

JYOTI SHUKLA Page 11

JYOTI SHUKLA Page 12

4.1 E-R Diagram:-

An entity-relationship diagram (ERD) is a type of data modeling that shows a graphical

JYOTI SHUKLA Page 13

JYOTI SHUKLA Page 14

Salary attenda Paymen

JYOTI SHUKLA Page 15

JYOTI SHUKLA Page 16

VB.NET IN FRONT END

VB.NET, the next version of VB, is a programming framework used to create

JYOTI SHUKLA Page 17

Advantages Using VB.NET

JYOTI SHUKLA Page 18

MS-ACCESS IN BACK END

JYOTI SHUKLA Page 19

JYOTI SHUKLA Page 21

JYOTI SHUKLA Page 22

JYOTI SHUKLA Page 23

JYOTI SHUKLA Page 24

JYOTI SHUKLA Page 25

JYOTI SHUKLA Page 26

JYOTI SHUKLA Page 27

JYOTI SHUKLA Page 28

JYOTI SHUKLA Page 29

JYOTI SHUKLA Page 30

TESTING STRATEGIES ADAPTED:-

It is also called glass box testing. It is a test case design

JYOTI SHUKLA Page 31

Black Box Testing:-