SYNOPSIS Electronic Shop Management System allows to view the details of the sales and purchase details.

It contain the information of the stocks and complaints. Customer, Products, Billing Generation: Automate the current manual bill generation system and maintain the searchable customer, products database and product invoice, maintain the data security, user rights. Report Generation: A Report Generation system will be developed for the user and management of eBilling and Invoicing System. This system will have both details and summary type reports for analysis the sales volume, sales trend, and available stock. The software project is initiated by the client needs. In the beginning, these needs are in the minds of various people in the client organization. The requirement analyst has to identify the requirements by talking to these people and understanding their needs. For such systems, the requirements problem is complicated by the fact that the needs and requirements of the system many not to be known even to the user-they have to be visualized and created. Hence, identifying requirements necessarily involves specifying what some people have in their minds. When inputs from multiple people are to be gathered, as is often the case, these inputs are likely to be inconsistent as well. The main purpose for creating this application is to automate the all inventory management of the Electronic Shop. This application allows to store the details of purchasing, sales & stocks.

1.0 INTRODUCTION This project is aimed at providing an economically feasible security and communication system that will provide very good features that can fulfill the security needs of a small organization. The project will be supposed to implement the storage of products so that a large collection could be maintained with minimum storage space. This project will also be able to provide reports of products sold to the customer and brought to the store.

1.1 SYSTEM SPECIFICATION 1.1.1 Hardware Specification

HARDWARE 1 2 3 4 5 Processor Keyboard Hard Drive Network Adapter Printer

SPECIFICATION Intel Pentium4 Processor 1,600GHz Standard key board 80GB 5400RPM /8M/PATA) PCI 10/100 Ethernet Adapter Ink jet printer attached in wireless

1.1.2 Software Specification

SOFTWARE 1 Operating System

SPECIFICATION Windows 7 Professional and Windows Server 2008 R2

2 3 4 5

Spread Sheet Internet Tool Programming Tool Backup Software

Tool Microsoft Excel Microsoft Internet Explorer version 6.0 Asp.net, SQL CD-R/CD-RW Disk and Data tape/hard disk

File Utilities

Win Rar 8.1/7-zip for extracting a files

1.1.3 Software Description The system is to develop online Sale and Inventory Management system. This system should be used to store information the Store sales and price their various functions,

salesperson and their various functions, Administrator, management and their various functions. USER REQUIREMENTS The main users in this system are salespersons, sales managers, inventory managers and administrators. By using this system, users can access online Sales and Inventory Management System with some function. The system will allow them to login and key in the main requirement in the update item details and price form. Inventory managers/sales managers/administrator can check a receipt and print out the bill as reference of items purchased. Inventory managers can generate inventory reports of the items category-wise and see the reports from salespersons about items not available a d need to keep in the inventory. Administrator also can add new user for the system.

FUNCTIONAL REQUIREMENTS A requirement specifies a function that a system or component must be able to allow the user to perform some kind of function. (Thomas Andrew 2009) The main purpose of the system is to increase sales by creating the complete inventory records of stock, receipt, details of purchasers and sellers at departmental store.

NON FUNCTIONAL REQUIREMENTS The Salesperson Inventory manager Administrator must be able to access their account 24 hours a day, seven days a week. The non-functional requirements of the Sale and Inventory Management systems are as described below. 1) Security The system must have protection from unauthorized users. By using username and password. Also system show error if the username or password is not correct To use the system, every user has to login by key in their username and password.

2) Performance The time system required to process and respond when a user key in the Identification that is username and password The system is supposed to respond in less than 2 seconds.

3) Availability

Sale and Inventory Management system is a standalone system which has four to five (4 5) users and users must have to use it during operating hours. 2.0 SYSTEM STUDY The management use manually to keeping they record of the store, but the system is difficult to maintain due to the cost of material, human errors, less data integrity, difficulty in searching and retrieving product and feasible loss of records and retrieving files. 2.1 Existing System Electronic Store management system becoming an essential to efficiently manage inventories in computer age. Electronic Shop Management System is a workable application for retail store inventory and accounts management. It keeps a list STOCKS and products at a store and can do operations on them. The most important operation is a PURCHASE, all the transactions and billing details and stock purchasing details involved on it. 2.1.1 Drawbacks Why We Want to Hold Inventories

Improve customer service Reduce certain costs such as Ordering costs Stock out costs Acquisition costs Start-up quality costs Contribute to the efficient and effective operation of the production system

2.2 Proposed System The project could be implemented in an average sized organization. An average company will not be very keen on spending loads of money on ledgers. Where as our project will greatly reduce the costs which is using common and cheap office items like database and desktop application. And also there is no requirement to store books or accounts. The data is directly stored in the database in the hard disk of the PC. This system is developed in such a way that even a nave user can also operate the system easily. The calculations are made very quickly and the records are directly saved into databases and the databases can be maintained for a longer period of time. Each record can be

retrieved and can be verified for the future transactions. Also this system provides high level of security for data leaking as only admin people can access the database no changes can be made in it until it verifies the user login id and password. We also have operator login through which operator can take orders but cant make changes in the database. Limited access is available to the operator.
2.2.1 Advantages

To increase sale and production To maintain the complete inventory records of stock, receipt, details of purchasers and sellers for a departmental store. To Create an easy to use system for an illiterate workforce To prepare a secure and reliable system to protect the store data from man-made and natural disasters To spend less time in searching and retrieving of information To create a backup of files in every successful operation To increase alternatives to manual handling of data of the store inventory To produce simple not complexity system To tend to present flexibility in the ways data and information are inputted, processes, retrieved and stored

3.0 SYSTEM DESIGN AND DEVELOPMENT 3.1 INPUT DESIGN The input design is the link between the information system and the user. It comprises the developing specification and procedures for data preparation and those steps are necessary to put transaction data in to a usable form for processing can be achieved by inspecting the computer to read data from a written or printed document or it can occur by having people keying the data directly into the system. The design of input focuses on controlling the amount of input required, controlling the errors, avoiding delay, avoiding extra steps and keeping the process simple. The input is designed in such a way so that it provides security and ease of use with retaining the privacy. Input Design considered the following things: What data should be given as input? How the data should be arranged or coded? The dialog to guide the operating personnel in providing input. Methods for preparing input validations and steps to follow when error occur. 3.1.1 Objectives:1) Input Design is the process of converting a user-oriented description of the input into a computer-based system. This design is important to avoid errors in the data input process and show the correct direction to the management for getting correct information from the computerized system. 2) It is achieved by creating user-friendly screens for the data entry to handle large volume of data. The goal of designing input is to make data entry easier and to be free from errors. The data entry screen is designed in such a way that all the data manipulates can be performed. It also provides record viewing facilities. 3) When the data is entered it will check for its validity. Data can be entered with the help of screens. Appropriate messages are provided as when needed so that the user will not be in maize of instant. Thus the objective of input design is to create an input layout that is easy to follow.

This program is a menu driven program. When we click the main menu the different forms will be enabled. The program consists of the following modules:

Source listing This module is suppose to identify the products by their discription.

Add products This module is suppose to take the inputs from an input device.

Add customers This module is capable of adding customers in the specified formats.

Update and delete products This module will update and delete products.

Update and delete customers This module will be able to update and delete customers

Searching In this module the admin or emplyee can search the customer or products from the database based on criterias

Transactions This module will take up transactions like selling products, buying products from supplier updating cash and updating the bills.Appropriate actions will be taken.

Report Generation This is a client program which will request for reports.

3.2 OUTPUT DESIGN A quality output is one, which meets the requirements of the end user and presents the information clearly. In any system results of processing are communicated to the users and to other system through outputs. In output design it is determined how the information is to be displaced for immediate need and also the hard copy output. It is the most important and direct source information to the user. Efficient and intelligent output design improves the systems relationship to help user decision-making.

Electronic Shop is a process of storing the products which is capable of maintaining storage of large amount of products. The primary purpose of this application is to implement the above stated functionality. The application should be capable enough to store the products and also perform some updating on the products that is stored. It will be having user friendly GUIs that will guide the user to easily achieve the same. The application shall also have some features like reports displaying in the same window. In addition to this the application also supports feature to search products. It can also search products based on criteria so that the employees will be able to view the same. The application is to be fully developed under vb platform using Visual Basic 6.0 3.2.1 Analysis Strategies A) ANALYSIS OF AS IS SYSTEM Currently, most of the Store still using normal or manual system to manage their transaction and day to day activities, the normal system that they are using still using paper base system to enter the transaction. Which the movement of our technologies, some of the store are interested in make an evolution by changing the methods on how to managing a store. As we familiar with the current system which based on paper base always has problem in time consuming, man errors to do the entire duty. For instance, if the administrator wants to log in or change his password or the file of the salesperson can see clearly, change price. We lead to files or records that having high probability to lost either by natural disaster or human error.

b) IMPROVEMENTS The new system will have some unique functionality of add new users, View price/ update price, view record, also make log in, and change password, this will lead to the fast interaction among users and administrator. The system is powerful secured, in the sense that the performance and standard of security on the system will be so tight to keep data safe from an unauthorized access from outsiders. The system is fully computerizing system. The improvement of the new system is view calendar, view staff information, feedback, maintain database, and backup.

c) PROPOSED TO BE SYSTEM By using this system, most problems faced in the store will be eliminated. This is done by the means of the Online Sale and Inventory Management System, which allows salesperson, Inventory manager, sale manager, and administrator to use the system immediately once they

fill the record of the sale. Now, there is no need to the Salesperson and Inventory manager to make paper record Sale and Inventory system which it will give benefit of cost savings by reducing their salesperson, Inventory manager services, and communication. Almost salesperson, Inventory manager complain about the inconsistence in the manual record of transaction procedure. Sales person and Inventory manager can save their time by using the online Sales and Inventory Management system as an alternative of going to the departmental Store.

3.3 DATA FLOW DIAGRAM A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through an Information System. A data flow diagram can also be used for the visualization of Data Processing. It is common practice for a designer to draw a context-level DFD first which shows the interaction between the system and outside entities. This context-level DFD is then "exploded" to show more detail of the system being modeled. A DFD represents flow of data through a system. Data flow diagrams are commonly used during problem analysis. It views a system as a function that transforms the input into desired output. A DFD shows movement of data through the different transformations or processes in the system. Dataflow diagrams can be used to provide the end user with a physical idea of where the data they input ultimately has an effect upon the structure of the whole system from order to dispatch to restock how any system is developed can be determined through a dataflow diagram. The appropriate register saved in database and maintained by appropriate authorities.

MASTER HIERARCHY:

CUSTOMER

STORE DEPARTMENT

Place Order

0.0
Check Stock
FeedBack

Accept / Rejected
Invoice Payment

Purchase Request

Order Details Check Stock Accept / Rejected Invoice Payment

P u r c h a s e O r d e r

INVENTORY SYSTEM

Accept / Rejected Invoice

Payment

SALES DEPARTMENT

P l a c e O r d e r

Payment Invoice Acknowlegment Place Order

SUPPLIER

PURCHASE DEPARTMENT

FIRST LEVEL DIAGRAM:

CUSTOMER

Customer Details

Group Details

GROUP_MASTER
1.0 2.1
Customer Details
Supplier Details Product Details

Supplier Details

CUSTOMER_MASTER SUPPLIER_MASTER PRODUCT_MASTER

SUPPLIER STORE DEPARTMENT

Product Details Group Details

Master

Invoice

SUPPLIER STORE DEPARTMENT

SALES DEPARTMENT

Purchase Order

Produc Details Supplier Details

Our Requisition Order Details Sales Details

Customer Details

1.2

Purchase Order Details

Sales Details

PURCHASE INVOICE ORDER

Transaction

PURCHASE DEPARTMENT

Purchase Details

Product Order Details

Oreder Details Product Wise Report Purchase Order Report

Invoice Report Stock Report Sales Details

1.2

Purchase Order Details

Report Generation

MANEGEMENT

SECOND LEVEL DIAGRAM:

Supplier Details

SUPPLIER_MASTER

2.1
Purchase Order

SUPPLIER

Purchase Order Generation

Give Order

PURCHASE_MASTER

2.2
Give Order

CUSTOMER
Accepted / Rejected

Order Entry Process

Cuatomer Details

CUSTOMER_MASTER

2.3
SALES DEPARTMENT CUSTOMER Sales Details

Invoice

Invoice Generation

Invoice Details

SALES

2.4 PURCHASE DEPARTMENT

SALES DEPARTMENT

Purchase Details

Stock Updation

Product Inward Product Outward

STOCK

Sales Details

ER-DIAGRAM:

CUSTOMER
M

M
GIVES

ORDER

1
CONTAINS

PRODUCT
M

CONTAINS

M
CONTAINS

PURCHASE ORDER
1
CAN RECEIVE

GENERATE

M
M M
FOR

SUPPLIER
M

INVOICE

3.4 System Development

3.4.1 Description Modules The product functions will include the following areas. The application is capable enough to store different products and also perform some editng on them that is added.It will be having user friendly GUIs that will guide the user to easily achive the same. AdminForm User Form Adding users Adding products Updating users Updating products Searching users and products Report generations

The user of this product is supposed to be fairly educated about the usage of the computers. He should understand how to store products and he should have knowledge about various products so that they could be saved. A person who has no knowledge of computers will find it difficult to understand the system. But with a little knowledge it will be very easy to handle the project. This project is aimed at providing an economically feasible security and communication system that will provide very good features that can fulfill the security needs of a small organization. The project will be supposed to implement the storage of products so that a large collection could be maintained with minimum storage space. This project will also be able to provide reports of products sold to the customer and brought to the store.
All necessary hardware and software are available for implementing and use of the tool. The proposed system would be designed, developed and implemented based on the software requirements specifications document. End users should have basic knowledge of computer and we also assure that the users will be given software training documentation and reference material.

3.4.2 Code Design

Login Form
Public Shared temp As String Public Shared flag As Integer Dim hcl As Integer Private Sub Login_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load OleDbConnection1.Open() Dim objReader As OleDbDataReader = OleDbCommand1.ExecuteReader Do While objReader.Read() ComboBox1.Items.Add(objReader("USER_NAME")) Loop OleDbConnection1.Close() TextBox1.Focus() End Sub Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click Dim username, password, temp1, temp2 As String Dim Read As OleDb.OleDbDataReader If ComboBox1.Text <> "" And TextBox1.Text <> "" Then username = UCase(ComboBox1.Text) password = UCase(TextBox1.Text) temp = UCase(TextBox1.Text) OleDbCommand2.Parameters.Add("USER_NAME", Data.OleDb.OleDbType.LongVarChar) OleDbCommand2.Parameters("USER_NAME").Value = username OleDbConnection1.Open() Read = OleDbCommand2.ExecuteReader With Read While .Read temp1 = .GetValue(0) temp2 = .GetValue(1) End While End With OleDbConnection1.Close() If password.Equals(temp1) = True Then Me.Hide() curr = New Main 'curr.Show() curr.Hide() Else MessageBox.Show("Wrong Password !!!", "Login Error", MessageBoxButtons.OK, MessageBoxIcon.Exclamation) GoTo bug1 TextBox1.Focus() End If If temp.Equals("ADMIN") = True Then flag = 1 End If If temp.Equals("OP") = True Then flag = 2 End If hcl = MsgBox("Login Successful... Welcome to Sales and Inventory Management System !!!", MsgBoxStyle.OKOnly + vbInformation, "Sales And Inventory Management System") If (hcl = MsgBoxResult.OK) Then curr = New Main curr.Show() End If Else

MsgBox("All fields required not to be a null value.", vbExclamation, "Sales and Inventory Management System") bug1: ComboBox1.Focus() End If End Sub Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click End End Sub End Class

Electronic Shop Main screen

Imports System.Data Public Class transaction Inherits System.Windows.Forms.Form Public Shared temporder_no As Integer Public Shared temporder_value As Integer Public Shared tempplant_code As String Dim random As New random Dim num As Integer = random.Next(99999) Dim challan_no As Integer = random.Next(999) Dim order_no As Integer Dim order_creation_date As Date Dim order_status As String Dim customer_ref_no As String Dim customer_slno As String Dim customer_ref_date As Date Dim order_value As Integer Dim plant_code As String Dim material_required_date As Date Dim customer_initial As String Dim delivery_challan_no As Integer Dim shipment_date As Date Dim invoice_number As Integer Dim invoice_date As Date Dim transporter_name As String Dim machine_installed_by As String Dim cheque_no As String Dim bank_name As String Private Sub Button101_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button101.Click Me.Close() End Sub Private Sub Button100_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button100.Click Me.TabPage1.Enabled = True Me.TabControl1.SelectedIndex = 0 End Sub Private Sub transaction_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load Me.TabPage1.Enabled = False Me.TabPage2.Enabled = False Me.TabPage3.Enabled = False Me.TabPage4.Enabled = False Me.TabPage5.Enabled = False Me.TabPage6.Enabled = True Me.TabControl1.SelectedIndex = 5

TextBox1.Text = Str(num) temporder_no = num Button11.Visible = False End Sub Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button3.Click If TextBox1.Text <> "" And TextBox4.Text <> "" And TextBox5.Text <> "" And TextBox3.Text <> "" And TextBox21.Text <> "" And DateTimePicker1.Text <> "" And DateTimePicker5.Text <> "" Then Me.TabPage2.Enabled = True Me.TabControl1.SelectedIndex = 1 Me.TabPage1.Enabled = False order_no = TextBox1.Text order_creation_date = DateTimePicker1.Text order_status = "SCHD" customer_ref_no = TextBox4.Text customer_ref_date = DateTimePicker2.Text material_required_date = DateTimePicker5.Text order_value = TextBox21.Text plant_code = TextBox5.Text customer_slno = TextBox3.Text TextBox12.Text = Str(order_no) TextBox22.Text = order_status customer_initial = Mid(customer_slno, 1, 1) TextBox46.Text = customer_initial TextBox13.Text = Str(challan_no) Else MsgBox("All fields required not to be a null value.", vbExclamation, "Sales Management System") TextBox3.Focus() End If End Sub Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button4.Click If TextBox13.Text <> "" And TextBox14.Text <> "" Then Dim invoice_int As Integer Dim random As New Random Dim num As Integer = random.Next(99999) Me.TabPage3.Enabled = True Me.TabControl1.SelectedIndex = 2 order_status = "SHIP" delivery_challan_no = TextBox13.Text shipment_date = DateTimePicker3.Text transporter_name = TextBox14.Text invoice_int = Val(TextBox23.Text) + Val(num) TextBox23.Text = Str(delivery_challan_no) TextBox28.Text = Str(invoice_int) TextBox29.Text = Str(order_value) Dim Read As OleDb.OleDbDataReader If customer_slno <> "" Then accountCommand1.Parameters.Add("cust_slno", Data.OleDb.OleDbType.Integer) accountCommand1.Parameters("cust_slno").Value = customer_slno accountConnection1.Open() Read = accountCommand1.ExecuteReader() With Read While .Read TextBox24.Text = .GetValue(0) TextBox25.Text = .GetValue(1) TextBox26.Text = .GetValue(2)

TextBox27.Text = .GetValue(3) End While End With accountConnection1.Close() End If Else MsgBox("All fields required not to be a null value.", vbExclamation, "Sales Management System") TextBox14.Focus() End If End Sub Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button5.Click Me.TabPage4.Enabled = True Me.TabControl1.SelectedIndex = 3 order_status = "INVG" invoice_number = Val(TextBox28.Text) invoice_date = DateTimePicker4.Text TextBox36.Text = Str(delivery_challan_no) Dim Read As OleDb.OleDbDataReader If customer_slno <> "" Then machCommand1.Parameters.Add("cust_slno", Data.OleDb.OleDbType.Integer) machCommand1.Parameters("cust_slno").Value = customer_slno machConnection1.Open() Read = machCommand1.ExecuteReader() With Read While .Read TextBox35.Text = .GetValue(0) TextBox33.Text = .GetValue(1) TextBox34.Text = .GetValue(2) TextBox31.Text = .GetValue(3) End While End With machConnection1.Close() End If End Sub Private Sub Button6_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button6.Click If TextBox30.Text <> "" Then Me.TabPage5.Enabled = True Me.TabControl1.SelectedIndex = 4 order_status = "MACI" TextBox41.Text = Str(order_no) TextBox32.Text = order_status machine_installed_by = TextBox30.Text Dim Read As OleDb.OleDbDataReader If customer_slno <> "" Then comCommand1.Parameters.Add("cust_slno", Data.OleDb.OleDbType.Integer) comCommand1.Parameters("cust_slno").Value = customer_slno comConnection1.Open() Read = comCommand1.ExecuteReader() With Read While .Read TextBox40.Text = .GetValue(0) TextBox38.Text = .GetValue(1) TextBox39.Text = .GetValue(2) TextBox37.Text = .GetValue(3) End While

End With comConnection1.Close() End If Else MsgBox("All fields required not to be a null value.", vbExclamation, "Sales Management System") TextBox30.Focus() End If End Sub Private Sub Button7_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button7.Click If TextBox42.Text <> "" And TextBox1.Text <> "" Then order_status = "PYMR" cheque_no = TextBox42.Text bank_name = TextBox43.Text On Error GoTo fix If TextBox32.Text = "" Or TextBox37.Text = "" Or TextBox38.Text = "" Or TextBox39.Text = "" Or TextBox40.Text = "" Or TextBox41.Text = "" Or TextBox42.Text = "" Or TextBox43.Text = "" Then MsgBox("All fields required not to be a null value.", vbExclamation, "Library System") Exit Sub End If paymentConnection1.Open() paymentCommand1.CommandText = _ "INSERT INTO ORDER_HEADER(bank_name, cheque_no, customer_initial, customer_ref_date, customer_ref_no, customer_slno, delivery_challan_no, invoice_date, invoice_number,machine_installed_by, material_required_date, order_creation_date, order_no, order_status, order_value, plant_code, shipment_date,transporter_name)VALUES('" & bank_name & "','" & cheque_no & "','" & customer_initial & "','" & customer_ref_date & "','" & customer_ref_no & "','" & customer_slno & "' ,'" & delivery_challan_no & "','" & invoice_date & "','" & invoice_number & "','" & machine_installed_by & "', '" & material_required_date & "' , '" & order_creation_date & "', '" & order_no & "', '" & order_status & "', '" & order_value & "', '" & plant_code & "', '" & shipment_date & "' ,'" & transporter_name & "')" MsgBox("New Record has been added.", vbInformation, "Sales Management System") paymentCommand1.ExecuteNonQuery() paymentConnection1.Close() Me.Close() fix: Exit Sub Else MsgBox("All fields required not to be a null value.", vbExclamation, "Sales Management System") TextBox42.Focus() End If End Sub Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click Dim str1 As String Dim Read As OleDb.OleDbDataReader If TextBox3.Text <> "" Then str1 = TextBox3.Text If str1 <> "" Then orderCommand1.Parameters.Add("cust_slno", Data.OleDb.OleDbType.Integer) orderCommand1.Parameters("cust_slno").Value = str1 orderConnection1.Open()

Read = orderCommand1.ExecuteReader() With Read While .Read TextBox6.Text = .GetValue(0) TextBox7.Text = .GetValue(1) TextBox8.Text = .GetValue(2) TextBox9.Text = .GetValue(3) TextBox10.Text = .GetValue(4) TextBox11.Text = .GetValue(5) End While End With orderConnection1.Close() End If Else MsgBox("Please provide an Customer Code to search", MsgBoxStyle.Exclamation, "Sales Management System") TextBox3.Focus() End If End Sub Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click curr = New Orderdetail curr.Show() Button1.Visible = False Button11.Visible = True order_status = "REVD" End Sub Private Sub Button11_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button11.Click TextBox21.Text = temporder_value TextBox5.Text = tempplant_code order_status = "CLRD" End Sub Private Sub Button10_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) TextBox22.Text = order_status End Sub Private Sub Button8_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button8.Click Dim enq As String Dim Read As OleDb.OleDbDataReader If TextBox15.Text <> "" Then enq = TextBox15.Text enquiryCommand.Parameters.Add("order_no", Data.OleDb.OleDbType.Integer) enquiryCommand.Parameters("order_no").Value = enq enquiryConnection.Open() Read = enquiryCommand.ExecuteReader() With Read While .Read TextBox20.Text = .GetValue(1) TextBox16.Text = .GetValue(2) TextBox17.Text = .GetValue(3) TextBox18.Text = .GetValue(4) TextBox19.Text = .GetValue(5) TextBox44.Text = .GetValue(7) TextBox45.Text = .GetValue(6) End While End With enquiryConnection.Close()

Else MessageBox.Show("Please Enter the Order No. !!!", "Sales Management System", MessageBoxButtons.OK, MessageBoxIcon.Exclamation) End If End Sub Private Sub Button9_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button9.Click TextBox15.Text = "" TextBox16.Text = "" TextBox17.Text = "" TextBox18.Text = "" TextBox19.Text = "" TextBox20.Text = "" TextBox44.Text = "" TextBox45.Text = "" TextBox15.Focus() End Sub Private Sub GroupBox1_Enter(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles GroupBox1.Enter End Sub Private Sub TabPage1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TabPage1.Click End Sub End Class

Add customer
Imports System.Data.OleDb Public Class Addcust Inherits System.Windows.Forms.Form Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button3.Click Me.Close() End Sub Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click TextBox1.Text = "" TextBox2.Text = "" TextBox3.Text = "" TextBox4.Text = "" TextBox5.Text = "" TextBox6.Text = "" TextBox7.Text = "" TextBox8.Text = "" TextBox9.Text = "" TextBox10.Text = "" ComboBox1.Text = "" End Sub Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click On Error GoTo fix If TextBox1.Text = "" Or TextBox2.Text = "" Or TextBox3.Text = "" Or TextBox4.Text = "" Or TextBox5.Text = "" Or TextBox6.Text = "" Or TextBox7.Text = "" Or TextBox8.Text = "" Or TextBox9.Text = "" Or TextBox10.Text = "" Or ComboBox1.Text = "" Then MsgBox("All fields required not to be a null value.", vbExclamation, "Sales Management System") Exit Sub End If OleDbConnection1.Open()

OleDbCommand1.CommandText = _ "INSERT INTO customer_master(cust_slno, cust_name, cust_initial, cust_add1, cust_add2, cust_add3, contact_person_name, contact_person_number, cust_pincode, cust_city,state_code)VALUES('" & TextBox1.Text & "', '" & TextBox2.Text & "','" & TextBox3.Text & "', '" & TextBox4.Text & "','" & TextBox5.Text & "', '" & TextBox6.Text & "','" & TextBox7.Text & "', '" & TextBox8.Text & "','" & TextBox9.Text & "', '" & TextBox10.Text & "','" & ComboBox1.Text & "')" MsgBox("New Customer has been added.", vbInformation, "Sales Management System") OleDbCommand1.ExecuteNonQuery() OleDbConnection1.Close() Me.Close() fix: Exit Sub End Sub Private Sub Addcust_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load TextBox1.Focus() OleDbConnection2.Open() Dim objReader As OleDbDataReader = OleDbCommand2.ExecuteReader Do While objReader.Read() ComboBox1.Items.Add(objReader("state_code")) Loop OleDbConnection2.Close() End Sub Private Sub GroupBox1_Enter(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles GroupBox1.Enter End Sub End Class

Edit Product
Public Class Editmaterial Inherits System.Windows.Forms.Form Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click Me.Close() End Sub Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click OleDbConnection1.Open() Try Dim intRow As Integer = Me.BindingContext(DataSetSMS, "material_master").Position - 1 Me.BindingContext(DataSetSMS, "material_master").Position += intRow OleDbDataAdapter1.Update(DataSetSMS) MsgBox("Changes has been successfully save.", vbInformation, "Sales Management System") Catch End Try OleDbConnection1.Close() Me.Close() End Sub Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button3.Click On Error GoTo fix Me.BindingContext(DataSetSMS, "material_master").Position = 0 Count()

fix: Exit Sub End Sub Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button4.Click On Error GoTo fix Me.BindingContext(DataSetSMS, "material_master").Position -= 1 Count() fix: Exit Sub End Sub Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button5.Click On Error GoTo fix Me.BindingContext(DataSetSMS, "material_master").Position += 1 Count() fix: Exit Sub End Sub Private Sub Button6_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button6.Click On Error GoTo fix Me.BindingContext(DataSetSMS, "material_master").Position = Me.BindingContext(DataSetSMS, "material_master").Count - 1 Count() fix: Exit Sub End Sub Private Sub Count() Dim Records, Current As Integer Dim enableBack As Boolean = False Dim enableForward As Boolean = False Records = Me.BindingContext(DataSetSMS, "material_master").Count Current = Me.BindingContext(DataSetSMS, "material_master").Position + 1 If Me.BindingContext(DataSetSMS, "material_master").Position > 0 Then enableBack = True End If If BindingContext(DataSetSMS, "material_master").Position < DataSetSMS.material_master.Count - 1 Then enableForward = True End If Button3.Enabled = enableBack Button4.Enabled = enableBack Button5.Enabled = enableForward Button6.Enabled = enableForward End Sub Private Sub Editcust_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load TextBox1.Focus() DataSetSMS.Clear() OleDbDataAdapter1.Fill(DataSetSMS) Count() End Sub Private Sub Button7_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button7.Click Dim str1 As String Dim Read As OleDb.OleDbDataReader str1 = InputBox("Enter Material Code :", "Search by Material Code") If str1 <> "" Then

OleDbCommand1.Parameters.Add("material_code", Data.OleDb.OleDbType.Integer) OleDbCommand1.Parameters("material_code").Value = str1 OleDbConnection1.Open() Read = OleDbCommand1.ExecuteReader() With Read While .Read TextBox1.Text = .GetValue(0) TextBox2.Text = .GetValue(1) TextBox3.Text = .GetValue(2) TextBox4.Text = .GetValue(3) End While End With OleDbConnection1.Close() End If End Sub End Class

Order Detail
Imports System.Data.OleDb Public Class Orderdetail Inherits System.Windows.Forms.Form Public Shared temp1 As String Public Shared temp2 As String Dim qty As Integer Dim item_value As Integer Private Sub Orderdetail_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load TextBox1.Enabled = False Button4.Enabled = False TextBox3.Enabled = False TextBox4.Enabled = False TextBox5.Enabled = False TextBox1.Text = Str(transaction.temporder_no) materialConnection.Open() Dim objReader As OleDbDataReader = materialCommand.ExecuteReader Do While objReader.Read() ComboBox1.Items.Add(objReader("material_code")) Loop materialConnection.Close() End Sub Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button3.Click TextBox1.Text = "" ComboBox1.Text = "" TextBox2.Text = "" TextBox3.Text = "" TextBox4.Text = "" TextBox5.Text = "" Button4.Enabled = False TextBox3.Enabled = False TextBox4.Enabled = False TextBox5.Enabled = False End Sub Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click Me.Close() End Sub Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button1.Click Dim str1 As String Dim Read As OleDb.OleDbDataReader TextBox3.Enabled = True TextBox4.Enabled = True TextBox5.Enabled = True Button4.Enabled = True matorderdetailCommand1.Parameters.Add("material_code", Data.OleDb.OleDbType.Integer) matorderdetailCommand1.Parameters("material_code").Value = str1 matorderdetailConnection1.Open() Read = matorderdetailCommand1.ExecuteReader With Read While .Read TextBox4.Text = .GetValue(3) TextBox5.Text = .GetValue(2) End While End With matorderdetailConnection1.Close() qty = Val(TextBox5.Text) item_value = qty * Val(TextBox2.Text) TextBox3.Text = Str(item_value) End Sub Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button4.Click Dim flag As Integer On Error GoTo fix If TextBox1.Text = "" Or TextBox2.Text = "" Or TextBox3.Text = "" Or TextBox4.Text = "" Or TextBox5.Text = "" Or ComboBox1.Text = "" Then MsgBox("All fields required not to be a null value.", vbExclamation, "Library System") Exit Sub End If orderdetailinsertConnection1.Open() orderdetailinsertCommand1.CommandText = _ "INSERT INTO order_detail(order_no,material_code,item_qty,item_value)VALUES('" & TextBox1.Text & "', '" & ComboBox1.Text & "','" & TextBox2.Text & "', '" & TextBox3.Text & "')" flag = MsgBox("Order Placed!!!", MsgBoxStyle.OKOnly + vbInformation, "Sales Management System") If (flag = MsgBoxResult.OK) Then transaction.temporder_value = item_value transaction.tempplant_code = TextBox4.Text End If orderdetailinsertCommand1.ExecuteNonQuery() orderdetailinsertConnection1.Close() Me.Close() fix: Exit Sub Me.Close() End Sub Private Sub GroupBox1_Enter(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles GroupBox1.Enter End Sub End Class

Purchase Status
Public Class Orderstatus

Inherits System.Windows.Forms.Form Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click Me.Close() End Sub Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click On Error GoTo fix If TextBox1.Text = "" And TextBox2.Text = "" Then MsgBox("State Code and State Description cannot be a null value.", vbExclamation, "Sales Management System") Exit Sub End If OleDbConnection1.Open() OleDbCommand1.CommandText = _ "INSERT INTO status_master(order_status, description)" & _ "VALUES('" & TextBox1.Text & "','" & TextBox2.Text & "')" MsgBox("New State has been successfully added.", vbInformation, "Sales Management System") OleDbCommand1.ExecuteNonQuery() OleDbConnection1.Close() Me.Close() fix: Exit Sub End Sub

4.0 TESTING AND IMPLEMENTATION

Testing is the process of detecting errors. Testing performs a very critical role for quality assurance and for ensuring the reliability of software. The results of testing are used later on during maintenance also Psychology of Testing. The aim of testing is often to demonstrate that a program works by showing that it has no errors. The basic purpose of testing phase is to detect the errors that may be present in the program. Hence one should not start testing with the intent of showing that a program works, but the intent should be to show that a program doesnt work. Testing is the process of executing a program with the intent of finding errors. Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and coding. In fact, testing is the one step in the software engineering process that could be viewed as destructive rather than constructive. 4.1.2 Testing Objectives The main objective of testing is to uncover a host of errors, systematically and with minimum effort and time. Stating formally, we can say, Testing is a process of executing a program with the intent of finding an error. A successful test is one that uncovers an as yet undiscovered error. A good test case is one that has a high probability of finding error, if it exists. The tests are inadequate to detect possibly present errors. The software more or less confirms to the quality and reliable standards. Qualifying a software programs quality by measuring its attributes and capabilities against expectations and applicable standards. And (probably the most important role of testing is to) provide information.

4.1.3 Levels of Testing

In order to uncover the errors present in different phases we have the concept of levels of testing. The basic levels of testing are

Client Needs Requirements

Acceptance Testing System Testing

Design

Integration Testing

Code

Unit Testing

A series of testing is done for the proposed system before the system is ready for the user acceptance testing. The steps involved in Testing are: 4.1.4 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. Unit testing focuses verification effort on the smallest unit of software design, the module. The unit testing we have is white box oriented and some modules the steps are conducted in parallel. 4.1.4.1 White Box Testing This type of testing ensures that

All independent paths have been exercised at least once All logical decisions have been exercised on their true and false sides All loops are executed at their boundaries and within their operational bounds All internal data structures have been exercised to assure their validity.

To follow the concept of white box testing we have tested each form .we have created independently to verify that Data flow is correct, All conditions are exercised to check their validity, All loops are executed on their boundaries. 4.1.4.2 Basic Path Testing Established technique of flow graph with Cyclomatic complexity was used to derive test cases for all the functions. The main steps in deriving test cases were: Use the design of the code and draw correspondent flow graph. Determine the Cyclomatic complexity of resultant flow graph, using formula: V (G) =E-N+2 (or) V (G) =P+1 (or) V (G) =Number of Regions Where V (G) is Cyclomatic complexity, E is the number of edges, N is the number of flow graph nodes, P is the number of predicate nodes. Determine the basis of set of linearly independent paths. 4.1.4.3 Conditional Testing In this part of the testing each of the conditions were tested to both true and false aspects. And all the resulting paths were tested. So that each path that may be generate on particular condition is traced to uncover any possible errors. 4.1.4.4 Data Flow Testing This type of testing selects the path of the program according to the location of definition and use of variables. This kind of testing was used only when some local variable were declared. The definition-use chain method was used in this type of testing. These were particularly useful in nested statements.

4.1.4.5 Loop Testing In this type of testing all the loops are tested to all the limits possible. The following exercise was adopted for all loops: All the loops were tested at their limits, just above them and just below them. All the loops were skipped at least once. For nested loops test the inner most loop first and then work outwards. For concatenated loops the values of dependent loops were set with the help of connected loop. Unstructured loops were resolved into nested loops or concatenated loops and tested as above. Each unit has been separately tested by the development team itself and all the input have been validated. Test Results: All the test cases mentioned above passed successfully. No defects encountered. 4.1.5 INTEGRATION TESTING Integration tests are designed to test integrated software components to determine if they actually run as one program. Testing is event driven and is more concerned with the basic outcome of screens or fields. Integration tests demonstrate that although the components were individually satisfaction, as shown by successfully unit testing, the combination of components is correct and consistent. Integration testing is specifically aimed at exposing the problems that arise from the combination of components. 4.1.5.1 Functional test Functional tests provide systematic demonstrations that functions tested are available as specified by the business and technical requirements, system documentation, and user manuals. Functional testing is centered on the following items: Valid Input Invalid Input : identified classes of valid input must be accepted. : identified classes of invalid input must be rejected.

Functions Output

: identified functions must be exercised. : identified classes of application outputs must be exercised.

Systems/Procedures : interfacing systems or procedures must be invoked. Organization and preparation of functional tests is focused on requirements, key functions, or special test cases. In addition, systematic coverage pertaining to identify Business process flows; data fields, predefined processes, and successive processes must be considered for testing. Before functional testing is complete, additional tests are identified and the effective value of current tests is determined. Test Results: All the test cases mentioned above passed successfully. No defects encountered. 4.1.6 System testing System testing is the stage of implementation that is aimed at ensuring that the system works accurately and efficiently for live operation commences. The code for the new system has been written completely using JSP as the coding language, HTML as the interface for frontend designing and Java Script for validating the client-side applications. The new system has been tested well with the help of the users and all the applications have been verified from every nook and corner of the user. Testing is vital to the success of the system. System testing makes a logical assumption that if all the parts of the system are correct, then goal will be successfully achieved. 4.1.7 Validation Testing: At the conclusion of integration testing software is completely assembled as a package, interfacing errors have been uncovered and corrected and a final series of software tests begins, validation test begins. Validation test can be defined in many ways. But the simple definition is that validation succeeds when the software function in a manner that can reasonably expected by the customer. After validation test has been conducted one of two possible conditions exists. One is the function or performance characteristics confirm to specifications and are accepted and the other is deviation from specification is uncovered and a deficiency list is

created. Proposed system under consideration has been tested by using validation testing and found to be working satisfactorily.

4.1.8 Verification Testing Verification is a fundamental concept in software design. This is the bridge between customer requirements and an implementation that satisfies those requirements. This is verifiable if it can be demonstrated that the testing will result in an implementation that satisfies the customer requirements. Inadequate testing or non-testing leads to errors that may appear few months later. This will create two problems: Time delay between the cause and appearance of the problem. The effect of the system errors on files and records within the system

4.1.9 User Acceptance Testing After performing verification and validation testing, the next step is output testing of the proposed system since no system could be useful if it does not produce the required output in the specified format. Asking the users about the format required by them tests the outputs generated by the system under consideration. Here the output format is considered in two ways, one is on the screen and other is the printed format. The output format on the screen is found to be correct as the format was designed in the system designed phase according to the user needs. For the hard copy also the output comes as the specified requirements by the users. Hence output testing does not result any corrections in the system. User acceptance of a system is the key factor of the success of any system. The system under study is tested for the user acceptance by constantly keeping in touch with the prospective system users at the time of developing and making changes wherever required. 4.1.9.1 Test Data: Taking various kinds of test data does the above testing. Preparation of test data plays a vital role in the system testing after preparing the test data the system under study is tested

using the test data. While testing the system by using the test data errors are again uncovered and corrected by using above testing steps and corrections are also noted from the future use.

4.2 IMPLEMENTATION Implementation includes all those activities that take place to connect from the new one. A crucial phase in the system life cycle is the successful implementation of the new system design. Implementation includes all these activities that take place to convert from the old system to the new one. The new system may be completely new, replacing an existing system. In either case, proper implementation becomes necessary so that a reliable system based on the requirements of organization can be provided. Successful implementation may not guarantee improvements in the organization using the new system, but improper installation will prevent it. It has been observed that even the nest system cannot show good result if the analysis managing the implementation do not attend to every important detail. This is an area where the system analyst needs to work with utmost care. Three aspects of implementation are: 4.2.1 Training the Personnel Wherever software is installed, the users should be trained well to use it efficiently. Thus training of the personnel is considered as one of the major issues in system implementation. The end user who would be using the system had been trained to handle the system. Explicit instructions user given about the process that can be performed with the help of the system. The system is well validated against the chances of wrong entries. 4.2.2 Conversion Procedure Conversion is the procedure of changing from old system to the new one. It must be properly planned and executed. Four methods are common in use. They are parallel system, direct conversion pilot systems and system phase - in each method should be considered in the light of the opportunities that it offers and problems that it may create. However it may be possible that sometimes, we may be forced to apply one method over others, even other methods that may be beneficial. In general systems conversion should be accomplished in

shortest possible time; long conversion periods create problems for all persons involved both analysis and users. 4.2.3 Post Implementation Review After the system is implemented and conversion is complete a review should be conducted to determine whether the system is meeting expectation and where improvements are needed. A post implementation review measures the system's performance against predefined requirements. It determines how well the system continues to meet performance specifications. It also provides information whether major re-design or modification is required. A post implementation review is an evaluation of a system in terms of the extent to which the system accomplishes stated objectives and actual project costs exceed initial estimates. It is usually a review of major problems that need one. Here all the three aspects of implementations are discussed. While converting an old system to new one it should give all the facilities provided in old system to new one in a better way.

5.0 CONCLUSION While developing the system a conscious effort has been made to create and develop a software package, making use of available tools, techniques and resources that would generate a proper System While making the system, an eye has been kept on making it as userfriendly, as cost-effective and as flexible as possible. As such one may hope that the system will be acceptable to any user and will adequately meet his/her needs. As in case of any system development processes where there are a number of Shortcomings, there have been some shortcomings in the development of this system also. The project is still under modification.