1
CHAPTER-1: INTRODUCTION
1.1 Introduction to Inventory Management System
The project Inventory Management System is a complete desktop based application
designed on .Net technology using Visual Studio Software. The main aim of the
project is to develop Inventory Management System Model software in which all the
information regarding the stock of the organization will be presented. It is an
intranet
based desktop application which has admin component to manage the inventory and
maintenance of the inventory system.
This desktop application is based on the management of stock of an organization.
The
application contains general organization profile, sales details, Purchase details
and
the remaining stock that are presented in the organization. There is a provision of
updating the inventory also. This application also provides the remaining balance
of
the stock as well as the details of the balance of transaction.
Each new stock is created and entitled with the named and the entry date of that
stock
and it can also be update any time when required as per the transaction or the
sales is
returned in case. Here the login page is created in order to protect the management
of
the stock of organization in order to prevent it from the threads and misuse of the
inventory.
1.2 Literature Review
Products are considered as the business resources for the organization. This
includes
managing the product with appropriate way to review any time as per the
requirement.
Therefore it is important to have a computer based IMS which has the ability to
generate reports, maintain the balance of the stock, details about the purchase and
sales in the organization. Before developing this application we came up with 2
Inventory Management System existing in the market, which helps to give the
knowledge for the development of our project. These application software are only
used by the large organization but so we came up with the application which can be
used by the small company for the management of their stock in the production
houses.
After analyzing the other inventory management system we decided to include some
of common and key features that should be included in every inventory management
system. So we decided to include those things that help the small organization in a
way or other.
2
1.3 Problem Statement
After analyzing many existing IMS we have now the obvious vision of the project to
be developed. Before we started to build the application team had many challenges.
We defined our problem statement as:
? To make desktop based application of IMS for small organization.
? To make the system easily managed and can be secured.
? To cover all the areas of IMS like purchase details, sales details and stock
management.
1.4 Objective of the Project
1.4.1 Primary objective
The primary objectives of the project are mentioned below:
? To fulfill the requirement for achieving the Bachelor�s degree of Computer
Information System.
? To know the fundamentals of the .Net Technology and Visual Studio with the
.Net Framework
1.4.2 Secondary objective
The secondary objectives of this project are mentioned below:
? To develop an application that deals with the day to day requirement of any
production organization
? To develop the easy management of the inventory
? To handle the inventory details like sales details, purchase details and balance
stock details.
? To provide competitive advantage to the organization.
? To provide details information about the stock balance.
? To make the stock manageable and simplify the use of inventory in the
organization.
1.6 Features of Project
This application is used to show the stock remaining and details about the sales
and
purchase. It gives the details about the stock on daily based and weekly based. The
details components are described below:
Login page: As application starts the login page appears. Admin login is determined
by the username and password that has all the authority to add, update and delete
the
stock of the organization as per the requirement.
3
Create Godwom: We can create godwom if we need to extend or we have more than
one godwom. We can create the godwom along with the date.
Sales details: It show the details about the sales and the remaining stock of
sales. It
also show the details about the sales in return.
Purchase details: It shows the details about the purchase made by the organization
along with the price and dates.
1.7 Scope of the Application
Inventory Management System (IMS) is targeted to the small or medium organization
which doesn�t have many godwom or warehouses i.e. only to those organization that
has single power of authority. Some of the scope are:
? Only one person is responsible in assigning the details or records
? It is security driven.
? Godown can be added as per the requirement.
#####################################
CHAPTER- 6: CODING IMPLEMENTATION
6.1 Application Code Structure
Inventory Management System was designed using Visual Studio as mentioned
earlier following the three tier application architecture. It provided us with the
code
editor as a white blank space and the solution explorer where every code files were
kept. Code Editor is where the logical were developed into code and kept safe in
the
solution explorer. In solution explorer we kept every code file by creating the
folder
and adding those files in a folder that are similar in nature. The main folder was
the
Inventory Management System. Following are the list of the folders, sub-folders and
their corresponding files:
6.2 Logic
Logic is the main component of any application portrayed through the code. Every
modules in the application includes logic. Most of the logic are common and
understandable as we call 3-tier architecture based system.
6.3 Code for Login page and validation
frmLogin.cs
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;
using System.Data.SqlClient;
namespace InventoryManagementSystem
{
public partial class frmLogin : Form
{
public frmLogin()
{
InitializeComponent();
}
private void txtUserName_KeyDown(object sender, KeyEventArgs e)
{
clsGlobalFunction.Tab_Function(e);
clsGlobalFunction.Escape_Function(e, btnCancel);
}
private void txtPassword_KeyDown(object sender, KeyEventArgs e)
{
22
clsGlobalFunction.Tab_Function(e);
clsGlobalFunction.Escape_Function(e, btnCancel);
}
private void txtFiscalYear_KeyDown(object sender, KeyEventArgs e)
{
clsGlobalFunction.Tab_Function(e);
clsGlobalFunction.Escape_Function(e, btnCancel);
}
private void btnCancel_Click(object sender, EventArgs e)
{
Application.Exit();
}
private void btnCancel_KeyDown(object sender, KeyEventArgs e)
{
if (e.KeyCode == Keys.Escape) { Application.Exit(); }
}
private void btnOK_Click(object sender, EventArgs e)
{
clsGlobalFunction.temp_text = "Select * from user_login where
user_name='" + txtUserName.Text + "' and password='" +
clsGlobalFunction.Encrypt(txtPassword.Text) + "'";
SqlDataAdapter da = new SqlDataAdapter(clsGlobalFunction.temp_text,
clsGlobalFunction.cn);
DataSet ds = new DataSet();
da.Fill(ds, "table0");
if (ds.Tables[0].Rows.Count > 0)
{
this.Hide();
}
else
{
MessageBox.Show("User Name or Password is not Correct");
txtUserName.Focus();
}
}
private void txtUserName_Validated(object sender, EventArgs e)
{
}
private void txtPassword_Validated(object sender, EventArgs e)
{
}
private void txtFiscalYear_Validated(object sender, EventArgs e)
{
}
private void frmLogin_Load(object sender, EventArgs e)
{
try
{
clsGlobalFunction.temp_text = "select * from fiscal_year";
23
SqlDataAdapter da = new
SqlDataAdapter(clsGlobalFunction.temp_text, clsGlobalFunction.cn);
DataSet ds = new DataSet();
da.Fill(ds, "table0");
txtFiscalYear.Items.Clear();
for (int i = 0; i < ds.Tables[0].Rows.Count; i++)
{
txtFiscalYear.Items.Add(ds.Tables[0].Rows[i]["fyear"].ToString());
txtFiscalYear.Text =
ds.Tables[0].Rows[i]["fyear"].ToString();
}
}
catch { }
}
private void txtUserName_Validating(object sender, CancelEventArgs e)
{
if (txtUserName.Text == "") { MessageBox.Show("Please Enter User
Name", "Inventory Management System", MessageBoxButtons.OK,
MessageBoxIcon.Information); txtUserName.Focus(); return; }
}
private void txtFiscalYear_SelectedIndexChanged(object sender,
EventArgs e)
{
}
private void label3_Click(object sender, EventArgs e)
{
}
}
}
6.4 Backup Data code
SaveFileDialog saveBACKUP = new SaveFileDialog();
try
{
DialogResult Dr;
saveBACKUP.Filter = "File format (*.bak)|*.bak";
saveBACKUP.FileName = "INVENTORY ( BACKUP ) " +
DateTime.Now.Year.ToString() + "-" + DateTime.Now.Month.ToString() + "-" +
DateTime.Now.Day.ToString();
Dr = saveBACKUP.ShowDialog();
if (Dr == DialogResult.OK)
{
string s = null;
s = saveBACKUP.FileName;
SqlCommand cmd = new SqlCommand("Backup database " +
clsGlobalFunction.DatabaseName + " to disk='" + s + "' WITH STATS",
clsGlobalFunction.cnMaster);
cmd.ExecuteNonQuery();
clsGlobalFunction.MessageBoxDisplay("Sucussfully Created
Backup !!!");
}
}
catch (Exception ex)
##################################
CHAPTER � 7: DEBUGGING AND TESTING
7.1 Purpose of Testing
The purpose of software testing is to access or evaluate the capabilities or
attributes of
a software program�s ability to adequately meet the applicable standards and
application need. Testing does not ensure quality and the purpose of testing is not
to
find bugs. Testing can be verification and validation or reliability estimation.
The
primary objective if testing includes:
? To identifying defects in the application.
? The most important role of testing is simply to provide information.
? to check the proper working of the application while inserting updating and
deleting the entry of the products.
7.2 Type of Testing
We have used one type of testing to ensure the error free features of our software
application:
7.2.1 Units Test
This type of testing is the testing of individual software components. It is
typically
done by the programmer and not by the testers. It requires details information and
knowledge about the internal program design and code to perform this.
During unit testing, we carried out various testing task such as the reflection of
the
unit data on database and its interface. Various types of bugs associated with the
component were identified and fixed. We use various functional keys to test our
software.
In our software unit testing is concerned with the stock units, opening stock units
and
product units validation as well as the validation of product units.
########################################
CHAPTER � 8: CONCLUSION AND LESSON LEARNT
8.1 Project Limitation
Since this is our first project it has some limitation. Due to less knowledge in
particular fields and limited time we were not able to fulfill all our expectations
that
we expected we could do while the project got started. We hope this limitations are
considerable. Some of the project limitations are:
? This application is not suitable for those organization where there is large
quantity
of product and different level of warehouses
? This software application is able to generate only simple reports.
? Single admin panel is only made.
? It is not suitable for large organization.
8.2 Conclusion
To conclude, Inventory Management System is a simple desktop based application
basically suitable for small organization. It has every basic items which are used
for
the small organization. Our team is successful in making the application where we
can
update, insert and delete the item as per the requirement. This application also
provides a simple report on daily basis to know the daily sales and purchase
details.
This application matches for small organization where there small limited if
godwoms.
Through it has some limitations, our team strongly believes that the implementation
of this system will surely benefit the organization.
8.3 Lesson Learnt
Doing something for long time periods always gives good lesson. Some of the things
that our team learnt are listed as below:
? Basically we learnt to work in team.
? Learnt about the IMS process.
? Learnt about .NET technology, its components and ways to implement them
? Learnt to work in pressure and to be patient.
? Learnt to manage the database under Microsoft SQL server 2008.
8.4 Future Enhancements
Since this project was started with very little knowledge about the Inventory
Management System, we came to know about the enhancement capability during the
37
process of building it. Some of the scope we can increase for the betterment and
effectiveness oar listed below:
? Interactive user interface design.
? Manage Stock Godown wise.
? Use of Oracle as its database.
? Online payment system can be added.
? Making the system flexible in any type.
? Sales and purchase return system will be added in order to make return of
products.
? Lost and breakage
38
REFERENCES
Software Reference
? Swatik Accounting And Inventory Software
High-tech Software, Kalimati
? Inventory Management Software
Sagar International, Balkhu
Website
Visual Studio Official Site: https://msdn.microsoft.com/en-us/library/dd492171.aspx
