You are on page 1of 39

SYNOPSIS

The project entitled “ Work Process Management System”has been developed using
VB.Net as Front End and Sql Server as Back End

The project handles the details about customers who can purchase the product, payment
details and the available product details.This project also maintains the mode of payment and
stock details.

This project provides complete details about all the process which are carried out in the
company and to ensure users satisfaction by providing all the process details in an economic

and efficient manner, so that it reduces time delay for accessing details in the company.

The new system will allow for the automation of company details and processing of users
requests. This system mainly includes all the process of a company details and maintaining the
data update.

1
INTRODUCTION
1.1 OVERVIEW OF THE PROJECT

This project handles the details about customers, who can purchase the product, payment
details and the available product details. This project also maintains the mode of payment and
stock details.

This project provides complete details about all the process which are carried in the
company and to ensure users satisfaction by providing all the process details in an economic and
efficient manner, so that it reduces time delay for accessing details in the company.

The new system will allow for the automation of company details and processing of users
requests. This system mainly includes all the process of a company details and maintaining the
data update.

MODULES:

• Customer Details

• Employee Details

• Product and Production Details

• Purchase, order and Delivery Details

• Transport Details

2
MODULES DESCRIPTION:

EMPLOYEE DETAILS :
This module allows an employee to register himself into the scheduler who is new
for organisation,it also enables the employee to view schedule work assigned to him

CUSTOMER DETAILS
Customer module maintenance the customer name and Address amount payable, contact
number, this helps to keep the record of customer details.
This module describes the customer service based on regular they can get service
discounts, product discounts.

PRODUCT AND PRODUCTION DETAILS:


This module describes about all the product name, and its specifications, duration of the
production, stock maintenance details.

PURCHASE ,ORDER AND DELIVERY DETAILS:


This module describes the customer order details based on the quotation. If the products
are confirmed then the production process will start within few days the order will deliver to the
customer.

TRANSPORT DETAILS:
It is a subset of supply chain Management concerning transportation
operation ,it planned,worked between the oranganisation

3
2. SYSTEM STUDY
2.1 EXISTING SYSTEM

The system aims in providing quick reference and clearance about the Subjects. In this
phase the existing system has been studied, the problem is identified and alternative solutions are
analyzed and the best solution has been selected after analysis. In this all the informations are
provided manually. The details about goods inlets and outlets are held manually. It is difficult to
have all the informations together and provide manually.

DRAWBACKS OF EXISTING SYSTEM

• The process takes lot of time.


• Providing all information is not possible.
• Higher cost

The exact nature of the problem has been identified by studying the existing manual
system. Also it has been decided that the problem in existing system is solvable only by
computerization. The existing system has been studied by initial investigation through
observation and interviewing.

2.2 PROPOSED SYSTEM

The proposed system is a computerized offline system. The system aims to design and
develop the application software to computerize all the process by using VB.NET with SQL
Server.
As the work is done manually before, so it has been time consuming and require large
efforts to maintain the files. By computerizing the system these files can be handled with a small
effort and in less time.

4
The Production details can be generated easily by getting the information without any

problem from all the related files. The project is designed by using GUI concept there for it is

very user friendly & easy to use.

ADVANTAGES OF PROPOSED SYSTEM

• Quality and efficiency

• Decrease in overall costs

• Decision support

• Enterprise agility

• Increase profitability

2.3 SYSTEM SPECIFICATION

2.3.1 HARDWARE SPECIFICATION

Processor : Intel Pentium Dual core

RAM capacity : 1GB

Hard disk capacity : 160 GB

Monitor : 15.6” color monitor

Keyboard : Standard Keyboard

Mouse : Optical Mouse

2.3.2 SOFTWARE SPECIFICATION


Front End : VB. NET 2010

Back End : MS - SQL Server

Operating System : Windows

5
2.4 ABOUT THE SOFTWARE

VISUAL BASIC.NET 2010


Visual Basic .NET, the next generation of Visual Basic, is designed to be the easiest and
most productive tool for creating .NET applications, including Windows applications, Web
Services, and web applications. While providing the traditional ease-of-use of Visual Basic
development, Visual Basic .NET also allows optional use of new language features. Inheritance,
method overloading, structured exception handling, and free threading all make Visual Basic a
powerful object-oriented programming language. Visual Basic .NET fully integrates with the
.NET Framework and the CLR, which together provide language interoperability, simplified
deployment, enhanced security and improved versioning support.

EVENTS
An event is something that happens, usually but not always due to the user at the
keyboard during a program’s operation. When virtually anything happens in windows
environment, windows generate an event.

PROPERTY
A property is a named attribute of a programming object. Property defines the
characteristic of an object such as size, color etc.

METHODS
A method is an action that can be performed on objects.

STEPS TO DESIGN A VISUAL BASIC.NET APPLICATION


• Customize the window that the user sees.

• Decide what events the control on the window should recognize.

• Write the event procedure for those events and the subsidiary that make that
event procedure work.

6
OPERATION EXECUTED WHEN AN APPLICATION IS RUNNING
• Visual Basic.Net monitors the windows and the control in each window for the
entire event that each control can recognize.

• When Visual Basic.Net detects an event, if there is not a built-in response to the
event, Visual Basic.Net examines the application to see if you’ve written an event
procedure for that event.
SQL SERVER 2005
The OLAP Services feature available in SQL Server version 7.0 is now called SQL
Server 2005 Analysis Services. The term OLAP Services has been replaced with the term
Analysis Services. Analysis Services also includes a new data mining component. The
Repository component available in SQL Server version 7.0 is now called Microsoft SQL Server
2005 Meta Data Services. References to the component now use the term Meta Data Services.

SQL Server 2005 distributed queries allow you to reference data from multiple sources as
if it were a part of a SQL Server 2005 database, while at the same time, the distributed
transaction support protects the integrity of any updates of the distributed data. We can replicate
a set of data to multiple, mobile, disconnected users, have them work autonomously and then
merge their modifications back to the publisher.

EASE OF INSTALLATION, DEPLOYMENT AND USE


SQL Server 2005 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 2005 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 users can implement with a minimum of installation and administrative
overhead

DATA WAREHOUSING
SQL Server 2005 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.

7
3. SYSTEM DESIGN

Data flow diagrams are the central tool and the basis from which other components are
developed. The transformation of data from input to output through process may be described
logically and independently of the physical components associated with the system. They are
termed logical data flow diagrams, showing the actual implementation and the movement of data
between people, departments and workstations.

DFD is one of the most important modeling tools used in system design. DFD shows the
flow of adapt through different process in the system. Data flow diagram is a quite effective,
especially when the required design is unclear and the user and analyst need a notational
language for communication.

Data flow diagrams are made up of a number of symbols which represents system
components. Data flow modeling method uses four kinds of symbols, which are used to represent
four kinds of system components.

• Process
• Data stores
• Data flows
• External entities
PROCESS

Process shows the work of the system. Each process has one or more data inputs and
produce one or more data outputs. Processes are represented by rounded rectangles in Data flow
diagram. Each process has a unique name and number. This name and number appears inside the
rectangle that represents the process in a Data flow diagram.

DATA STORES

A data store is a repository of data. Processes can enter data into a store or retrieve data
from the data store. Each data has a unique name.

8
DATA FLOW

Data flows show the passage of data in the system and are represented by lines joining
system components. An arrow indicates the direction of flow and the line is labeled by name of
the data flow.

EXTERNAL ENTITIES

External entities are outside the system but they either supply input data into the system
or use other systems output.

The data flow diagram (DFD) is one of the most important tools used by system analysts.
DFD are made up of a number symbols, which represent system components. Most data flow
modeling methods use four kinds of symbols. These symbols are used to represent four kinds of
system components. Processes, data stores, data flows and external entities. To construct a Data
Flow Diagram, we use

• Arrow
• Circles
• Open End Box
• Squares

9
3.1. DESIGN NOTATION

3.1.1. DATA FLOW DIAGRAM

LEVEL 0:

ADMIN WORK MANAGEMENT


PROCESS

10
LEVEL-1

Login
Admin

Employee Employee
EmployeeTb
Details

Customer Customer
Details CustomerTb

Product Product
Details ProductTb

Order Order
details OrderTb

Production
Production
details ProductionTb

Purchase PurchaseTb
Purchase
details

TransportTb
Transport Transport
details

Delivery DeliveryTb
Delivery
details

11 Reports
Generat
e result
3.1.2.ENTITY-RELATIONSHIP DIAGRAM

Uname Pwd

CustNa DelDate Orderyr


Admin
me ProdId
CustId Address Orderno
1
Qty
M
M
Order
Customer Verifies
Date
1 Qty Supid
EmpNa Transna
MobNo TinNo me
me Purid
EmpId Remark Price

EmailId o
1
Employee Checks Purchase
Prodna
Specify Age
ProdId me
Desc
Model Addr Prodid
MobNo M

Product Verifi Production Total


1 es M

1 Price Matcon
s
Day Night
SOH

Date
PName
Gives

Remark

BalAmt
1

PaidAmt
Goes Delivery
Transport
1 M

DDate
Remark

12
Destina Prodid NetAmt
Source
t
VehNo Transno Qty
3.2 DESIGN PROCESS

3.2.1 INPUT DESIGN


Input design is part of overall system design that requires special attention designing
input data is to make the data entry easy and free from errors. The input forms are designed using
the controls available in .NET framework. Validations are made for each and every data that is
entered. Help information is provided for the users during when the company feels difficult.

Input design is the process of converting the user originated inputs to a computer based
format. A system user interacting through a workstation must be able to tell the system whether
to accept the input to produce reports. The collection of input data is considered to be most
expensive part of the system design. Since the input has to be planned in such a manner so as to
get relevant information, extreme care is taken to obtain pertinent information.

An improper design that leaves the display screen blank will confuse a user about which
action to take next. Offline system includes a dialogue or conversation between the user and the
system. Input designs are aimed at reducing the chance of mistakes or errors during data entry.
The general term given to methods aimed at detecting input is input validation. An analyst must
always assume that errors will occur. They must be found during input and corrected prior to
storing or processing data.

The main objective of input design is to produce output in neat format and get high level
accuracy. A source document has been prepared for the input of data to make data entry fast. The
major activities carried out are,

• Collection of needed data from source

• Conversion of data into computer acceptable form.

• Verification of converted data.

• Checking data for its accuracy.

The field type of input data is checked. The validation of data is done to check each
record, data items or field against certain criteria. Error information is displayed in the case of
mismatch data type or during null values.

13
The forms involved are,

• User Login
• Product information
• Purchase information
• Order information
• Production information
• Stock information
• Delivery information.
• Transport information

3.2.2 OUTPUT DESIGN

Designing computer should proceed in well thought out manner. The term output means
any information produced by the information system whether printed or displayed. When analyst
design computer output they identified the specific output that is needed to meet the requirement.
Computer is the most important source of information to the users. Output design is a process
that involves designing necessary outputs that have to be used by various users according to
requirements. Efficient intelligent output design should improve the system relationship with the
user and help in decision making.

Since the management for taking decision and to draw the conclusion directly requires
the reports must be simple, descriptive and clear to the user. Options for outputs and forms are
given in the system menus.

When designing the output, system analyst must accomplish the following:

• Determine the information to present.


• Decide whether to display, print, speak the information and select the output
medium
• Arrange the information in acceptable format.

14
3.2.3 TABLE DESIGN

Table Name: Login

Primary Key: user id

FIELD NAME DATA TYPE SIZE DESCRIPTION


User id integer 10 User Identity number
Pwd varchar 16 Password

Table Name: Employee

Primary Key: Idno

Table description: Employee Registration Details

FIELD NAME DATA TYPE SIZE DESCRIPTION


Idno varchar 10 Identification number
Name varchar 25 Name of the Employee
Pwd varchar 16 Password
Rpwd varchar 16 Retype Password
F_name varchar 20 First Name
L_name varchar 20 Last Name
Age integer 2 Age
Department_Name varchar 25 Name of the
Department
Department_no varchar 8 Department Number
Gender varchar 11 Gender of the
employee
Date of joined datetime - Joining date of
employee
Address long 70 Address of the
Employee

15
Table Name: Customer

PrimaryKey : CustId

Table Description: It is used to store the customer details.

FIELD NAME DATA TYPE SIZE DESCRIPTION


CustId varchar 10 Identification of the
customer
CustName varchar 20 Name of the customer
Address varchar 70 Address of the
customer
Cont_No integer 13 Contact number of the
customer
City varchar 15 Name of the city
State varchar 15 Name of the state
MobNo integer 13 Mobile Number
Email Id varchar 30 Email id of customer
Transport name varchar 8 Name of the transport
CSTNo varchar 11 CST Number
TINNO varchar 11 TIN Number

Table Name: Product

PrimaryKey : ProdId

Table Description: It gives the product details.

Field name Data Type Size Description


ProdId varchar 10 Product Id
ProdName varchar 20 Product Name
Model varchar 35 Model of the product
Specify varchar 50 Specification
SOH Numeric 10 Stock on Hand
Price Numeric 8 Price of the product

16
Table Name: Order

Primary Key : OrderYr,OrderNo

ForeignKey : CustId,ProdId

Table description: It gives the order details.

FIELD NAME DATA TYPE SIZE DESCRIPTION


OrderYr integer 4 Year of Order
OrderNo char 10 Number of Order
OrderDate datetime - date of order
CustId varchar 10 Customer
Identification
ProdId varchar 10 Product
Identification
Qty integer 8 Quantity
TransportName varchar 50 Name of the
transport
DeliveryDate datetime - Date of Delivery
Remrk varchar 50 Remarks of the
order

Table Name : Production

Foreign Key : ProdId

Table description: It gives the production details.


FIELD NAME DATA TYPE SIZE DESCRIPTION
ProdId Varchar 10 Product Id
Date datetime - Production Date
Day Integer 15 Day production
Night Integer 15 Night production
Total Integer 5 Total production

17
Table Name : Purchase

Primary Key : PurchaseId

Table description: It gives the production details.

FIELD NAME DATA TYPE SIZE DESCRIPTION


PurchaseId Varchar 10 Purchase Identification
SupplierId numeric 10 Supplier Identification
Date datetime - Date of Purchase
Quantity integer 5 Quantity of the
product
NetQuantity numeric 50 Net Quantity of the
product
Price numeric 8 ,2 Price of the product
NetPrice numeric 8 ,2 Net Price of the
product
Description varchar 50 Purchase description

Table Name : Transport

Primery Key:TransName

Foreign Key : CustId

FIELD NAME DATA TYPE SIZE DESCRIPTION


CustId Varchar 10 Customer ID
Source varchar 20 Source of the place
Destination varchar 20 Destination place
TransName varchar 15 Transport Name
TransNo varchar 10 Transport Number
Remrk varchar 50 Remarks

18
Table Name : Delivery

Foreign Key : CustId, ProdId

FIELD NAME DATA TYPE SIZE DESCRIPTION


CustId varchar 10 Customer ID
ProdId varchar 10 Product ID
Qty integer 5 Quantity
NetAmt numeric 8 ,2 Net amount
PaidAmt numeric 8 ,2 Paid amount
BalAmt numeric 8,2 Balance amount
Remrk varchar 50 Remarks

3.2.4 CODE DESIGN


EMPLOYEE
idno
xxx9999

string indicates number


text indicates user
Example idno
Emp0001

employee number
employee id

CUSTOMER
cusid
xxx999

string indicates number


text indicates cusid
Example cusid
cst0001
customer number
customer id

19
3.2.5.SAMPLE CODING:

EMPLOYEE FORM

Imports System.Data.SqlClient
Public Class Employee
Dim Conn As New SqlConnection("Data Source=ADMIN-PC;Initial Catalog=WPMS;User
ID=sa;Password=abc123")
Dim Cmd As New SqlCommand
Dim Da As SqlDataAdapter
Dim Ds As New DataSet
Dim Dt As DataTable
Dim Dr As SqlDataReader
Dim Sqlstr As String
Public Sub Connection()
If Conn.State = ConnectionState.Closed Then Conn.Open()
End Sub
Public Sub clear()

txtCustID.Text = ""
txtCustName.Text = ""
txtAddr.Text = ""
txtCity.Text = ""
txtState.Text = ""
TxtTransName.Text = ""
txtContNo.Text = ""
txtMobNo.Text = ""
txtEmail.Text = ""
txtTinNo.Text = ""

End Sub
Public Sub GenerateId()
Dim i As Integer
Dim Dr As SqlDataReader
Conn.Open()
Sqlstr = "SELECT IsNUll(MAX(SUBSTRING(Idno,6,4)),000) + 1 AS mEntryNo From
TbEmployee"
Cmd = New SqlCommand(Sqlstr, Conn)

Dr = Cmd.ExecuteReader(CommandBehavior.SingleRow)

While (Dr.Read())
Int(i = 0)

20
txtCustID.Text = "EMP" + Dr.GetInt32(0).ToString("0000")
i += 1
End While
Dr.Close()
End Sub
Private Sub btnSave_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles btnSave.Click
Try
Connection()
Sqlstr = " INSERT INTO TbEmployee (Idno,Name,Addr,Fname,Lname,Age,DName,DNo,
Sex,Date)" _
& " VALUES ( " _& "'" & txtCustID.Text & " ','" & txtCustName.Text & "','" &
txtAddr.Text & "','" & txtCity.Text & "','" & txtState.Text _
& "','" & TxtTransName.Text & "','" & txtContNo.Text & "','" & txtMobNo.Text & "','"
& txtEmail.Text & "','" & txtTinNo.Text _
& "')"
Cmd = New SqlCommand(Sqlstr, Conn)
Cmd.ExecuteNonQuery()
MsgBox("Customer Record Added Successfully", MsgBoxStyle.Information)
clear()
Catch ex As Exception
MsgBox("Already Inserted", MsgBoxStyle.Information)
clear()
End Try

Conn.Close()
End Sub

Private Sub btnDelete_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)


Handles btnDelete.Click
Dim Query As String = ""
Try
Connection()
Cmd.Connection = Conn
Cmd.CommandText = "Delete FROM TbEmployee WHERE Idno = @Idno"
Cmd.Parameters.AddWithValue("@Idno", txtCustID.Text)
Cmd.ExecuteNonQuery()
If MessageBox.Show("Do you really want to Delete this Record?", "Delete",
MessageBoxButtons.YesNo, MessageBoxIcon.Warning) = DialogResult.No Then

MsgBox("Operation Cancelled")

Exit Sub

End If
clear()

21
Catch ex As Exception
MessageBox.Show("Error while deleting record on table..." & ex.Message, "Delete
Records")

Finally
Conn.Close()
End Try
End Sub

Private Sub BtnSearch_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles BtnSearch.Click
Connection()
Cmd.CommandText = "Select Idno,Name,Addr,Fname,Lname,Age,DName,DNo, Sex,Date
From TbEmployee Where Idno='" & Trim(txtCustID.Text) & "'"
Cmd.Connection = Conn
Dim dr As SqlDataReader
dr = Cmd.ExecuteReader

If dr.HasRows Then

dr.Read()
txtCustID.Text = dr.Item("Idno")
txtCustName.Text = dr.Item("Name")
txtAddr.Text = dr.Item("Addr")
txtCity.Text = dr.Item("Fname")
txtState.Text = dr.Item("Lname")
TxtTransName.Text = dr.Item("Age")
txtContNo.Text = dr.Item("DName")
txtMobNo.Text = dr.Item("DNo")
txtEmail.Text = dr.Item("Sex")
txtTinNo.Text = dr.Item("Date")

Else
MsgBox("Record Not Found")
End If
Conn.Close()
End Sub

Private Sub btnUpdate_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles btnUpdate.Click
Dim Query As String = ""
Try
Connection()
Cmd.Connection = Conn
Query = "update TbEmployee set Name = @Name,"
Query = Query + "Addr =@Addr, "

22
Query = Query + "Fname = @Fname,"
Query = Query + "Lname = @Lname,"
Query = Query + "Age = @Age,"
Query = Query + "DName = @DName,"
Query = Query + "DNo =@DNo ,"
Query = Query + "Sex = @Sex,"
Query = Query + "Date =@Date"
Query = Query + " WHERE Idno = @Idno"
Cmd.Parameters.AddWithValue("@Idno", txtCustID.Text)
Cmd.Parameters.AddWithValue("@Name", txtCustName.Text)
Cmd.Parameters.AddWithValue("@Addr", txtAddr.Text)
Cmd.Parameters.AddWithValue("@Fname", txtCity.Text)
Cmd.Parameters.AddWithValue("@Lname", txtState.Text)
Cmd.Parameters.AddWithValue("@Age", TxtTransName.Text)
Cmd.Parameters.AddWithValue("@DName", txtContNo.Text)
Cmd.Parameters.AddWithValue("@DNo", txtMobNo.Text)
Cmd.Parameters.AddWithValue("@Sex", txtEmail.Text)
Cmd.Parameters.AddWithValue("@Date", txtTinNo.Text)
Cmd.CommandText = (Query)

MsgBox(Query)
Dim i As Integer = Cmd.ExecuteNonQuery()
If (i > 0) Then
MsgBox("Record is Successfully Updated")
clear()
Else
MsgBox("Record is not Updated")
End If
Catch ex As SqlException
MsgBox("Error", MsgBoxStyle.Information)
End Try
End Sub
Private Sub btnClear_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles btnClear.Click
clear()
GenerateId()
End Sub
Private Sub Employee_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
GenerateId()
End Sub
Private Sub btnExit_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles btnExit.Click
Me.Close()
End Sub
End Class

23
REPORT CODE
Imports System.Data.SqlClient
Public Class ProductReport
Dim Conn As New SqlConnection("Data Source=Admin-pc;Initial Catalog=Radiation;User
ID=sa;Password=abc123")
Dim Cmd As New SqlCommand
Dim Da As New SqlDataAdapter
Dim Ds As New DataSet
Dim Dt As DataTable
Dim Sqlstr As String
Public Sub Connection()
If Conn.State = ConnectionState.Closed Then Conn.Open()
End Sub
Private Sub ProductReport_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
Connection()
Dim sql As String = "SELECT * FROM TbProduct"
Dim Da As New SqlDataAdapter(sql, Conn)
Da.Fill(Ds, "Product_table")
Conn.Close()
GVProduct.DataSource = Ds
GVProduct.DataMember = "Product_table"
End Sub
End Class

LOGIN CODE
Imports System.Data.SqlClient
Public Class Login
Dim Conn As New SqlConnection("Data Source=ADMIN-PC;Initial Catalog=WPMS;User
ID=sa;Password=abc123")
Dim Cmd As SqlCommand
Dim Da As SqlDataAdapter
Dim Ds As New DataSet
Dim Dt As DataTable
Dim Dr As SqlDataReader
Dim Sqlstr As String
Public Sub Connection()
If Conn.State = ConnectionState.Closed Then Conn.Open()
End Sub
Public Sub Clear()
txtUserName.Text = ""
txtPassword.Text = ""
End Sub

24
Private Sub btnSignIn_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles btnSignIn.Click
Connection()
Sqlstr = "SELECT UserName,Password FROM TbLogin WHERE username = '" &
txtUserName.Text & "' AND PassWord = '" & txtPassword.Text & "'"

Da = New SqlDataAdapter(Sqlstr, Conn)


Ds = New DataSet()
Da.Fill(Ds, "UserInfo")

If (Ds.Tables("UserInfo").Rows.Count > 0) Then


MsgBox("Authenticated successfully", MsgBoxStyle.Information)
Main.Show()
Clear()
Else
MsgBox("Incorrect Username or Password", MsgBoxStyle.Critical)
Clear()
txtUserName.Focus()
End If
End Sub
End Class

25
4.SYSTEM TESTING AND IMPLEMENTATION

4.1INTRODUCTION

The method of designing the system to produce desired result accomplished in the system
development .All the facilities required for the developing the new system is acquired and
computer program preparation is started

4.2 SYSTEM TESTING

Testing is done throughout the system development at various stages. It is always a good
practice to test the system at any different levels at various intervals that is a sub-system,
program modules as work progress and finally the system as a whole.

No program or system design is perfect, communication between the user and the
designer is not always complete or clear, and time is usually short. The result is errors and more
errors. Theoretically, a new designe should have all the pieces in working order, but in reality,
each piece works independently.

Now is the time to put all the pieces into one system and test it to determine whether it
meets the users’s requirements. This is last chance to detect and correct errors before the system
is installed for user acceptance testing. The purpose of system testing is to consider all the likely
variations to which it will be subjected and then push the system to its limits.

During testing we tried to make sure that the product does exactly what is supposed to do.
Testing is the final verification and validation activity within the organization itself. In the
testing stage we try to achieve the following goals: to affirm the quality of the product, to find
and eliminate residual errors from previous stages, to validate the software as a solution to the
original problem, to demonstrate the presence of all specified functionality in the product, to
estimate the operational reliability of the system. During testing the major activities are
concentrated on the examination and modification of the source code.

26
TYPES OF TESTING

The following are the Testing Methodologies:


• Unit Testing.
• Integration Testing.
• Validation Testing
• Acceptance Testing

UNIT TESTING

Unit testing involves the design of test cases that validate that the internal program logic
is functioning properly, and that program inputs produce valid outputs. All decision branches and
internal code flow should be validated. It is the testing of individual software units of the
application .it is done after the completion of an individual unit before integration. This is a
structural testing, that relies on knowledge of its construction and is invasive.

Unit tests perform basic tests at component level and test a specific business process,
application, and/or system configuration. Unit tests ensure that each unique path of a business
process performs accurately to the documented specifications and contains clearly defined inputs
and expected results.

INTEGRATION TESTING

Integration testing addresses the issues associated with the dual problems of verification
and program construction. After the software has been integrated a set of high order tests are
conducted. The main objective in this testing process is to take unit tested modules and builds a
program structure that has been dictated by design.

27
VALIDATION TESTING

Validation checks are performed on the following fields.

TEXT FIELD

The text field can contain only the number of characters lesser than or equal to its size.
The text fields are alphanumeric in some tables and alphabetic in other tables. Incorrect entry
always flashes and error message.

NUMERIC FIELD

The numeric field can contain only numbers from 0 to 9. An entry of any character
flashes an error messages. The individual modules are checked for accuracy and what it has to
perform. Each module is subjected to test run along with sample data. The individually tested
modules are integrated into a single system. Testing involves executing the real data
information is used in the program the existence of any program defect is inferred from the
output. The testing should be planned so that all the requirements are individually tested.

ACCEPTANCE TESTING

User acceptance of a system is the key factor for the success of any system. The system
under consideration is tested for user acceptance by constantly in touch with the prospective
system users at time of developing and making changes wherever required is done in regard to
the following point:
• Input screen design.
• Output screen design.
• Menu driven system.

28
4.2 SYSTEM IMPLEMENTATION

Implementation is the stage of the project where the theoretical design is turned into a
working system. At this stage the main work load, the greatest upheaval and the major impact
on the existing system shifts to the user department. If the implementation is not carefully
planned a controlled it can cause chaos and confusion.
Implementation includes all those activities that take place to convert from the old system
to the new one. The new system may be totally new, replacing an existing manual or automated
system or it may be a major modification to an existing system. Proper implementation is
essential to provide a reliable system to meet the organization requirements. Successful
implementation may not guarantee improvement in the organization using the new system, but
improper installation will prevent it.
The process of putting the developed system in actual use is called system
implementation. This includes all those activities that take place to convert from the old system
to the new system. The system can be implemented only after thorough testing is done and if it
is found to be working according to the specifications. The system personnel check the
feasibility of the system.

29
5. CONCLUSION

This project is useful for the proper management of the company.

Identification of the drawbacks of the existing system leads to the designing of


computerized system that will be compatible to the existing system with the system which is
more users friendly.

This project helps to manage the work both in small and huge companies.

Cost efficiency. .It reduces man power.

Time can be reduce while using systematic way.

30
6. FUTURE ENHANCEMENT

The system is an integrated one, covering all aspects, which are required by the user.
Updating of information becomes more effective and quicker. Any further modification can be
made easily to extend the system to meet the entire future enhancement in the concern. This
system is found tested and examined for its successful processing. Future change in the
environment or processing can be easily adopted by having simple change in coding. It is very
user friendly, cost effective, feature rich and it provides very high level of security. Moreover,
the system coding is so well designed that new operations can be easily incorporated without
much modification.

31
7. BIBLIOGRAPHY

BOOK REFERENCE
• Sharon dooley, “ SQL Server Essential Reference” , Tata McGrawHill,Fifth Edition –
2008.
• Elias M.Award , “System Analysis and Design “, Galgotia publicationsPrivate limited,
Third Edition – 2006
• Steven Holzner “Visual Basic .Net Programming”, Paraglyph Press, 2005 Edition.
• Roger S. Pressman “Software Engineering “, A practitioners Approach, sixth edition.
• Fred Barwell, Richard Blair, Bill Forgey, Bill Sheldon, “Professional
• VB.Net” Wrox Press Ltd., Shroff Publishers & Distributors Pvt.,Ltd.,2nd Edition
• Richard Fairly “Software Engineering Concepts” Tata McGrawHill, Fift Reprint:1999.
• Steven Roman, “Visual Basic.NET Language in a Nutshell”, O’Reilly Publications, First
Edition – August 2001.

ONLINE REFERENCE

• www.w3schools.com

• www.msdn.microsoft.com

• www.codeguru.com

• www.dotnetspider.com

32
8. APPENDIX
Sample Screen Shots

33
34
35
36
37
SAMPLE SCREENSHOT:

38
39