TERM PAPER

TOPIC:- STORE KEEPING MANAGEMENT

Course Code: CAP407

Course Instructor: Mr.Pankaj Sharma

Date of Allotment: 27/03/2010

Date of submission: 11/05/2010

Student’s Roll No.: D3802B48

Section No.; D3802

Declaration:
I declare that this term paper is my individual work. I
have not copied from any other student’s work or from
any other source except where due acknowledgment is
made explicitly in the text, nor has any part been written
for me by another person.

Student’s Signature: Rajvinder Kaur

Evaluator’s comments:

Marks obtained: out of

Content

1.)Goal & Objective

2.)Introduction
3.)Requirement analysis
4.)Feasibility study:-
(i)Economic Feasibility
(ii)Technical Feasibility
(a) Software Requirement
(b) Hardware Requirement
(iii) Behavioral Feasibility
5.)Analysis
6.)Design
7.)Planning
8.)Coding
9.)Testing
10.) Types Of Testing
11.) Implementation & Maintenance
12.) Advantages
13.) Future Scope
14.) Bibliography
ACKNOWLEDGEMENT:

I would like to express my gratitude for the many helpful comment

and suggestions .I have received over the last few days regarding the
expository and critical expects of my term work and especially for
those comments which bear directly or may various argument for the
center thesis of term work. I am undebted to several people in this
regard.

Most importantly I would like to thank my teacher Mr. Pankaj

Sharma sir, for his days of supervision. His critical commentary on
my work has played a major role in both the content and presentation
of our discussion and arguments.

I have extend my appreciation to the several sources which provided

various kinds of knowledge base support for me during this period.
Goals and objectives:-
The project has been undertaken with following goal and objective:-

 To facilitate the quick, smooth, generation of the various reports.

 To minimize the problem faced during the work carried out.

 An effective use of computer is very important.

 All the information gattered & various activities are performed by using
Religious Web Site.

Introduction:-
One sees frequent waste of executive time and labor due to delays in retrieval of
stocks, deterioration of stocks, mismatches in quantities, damage during
handling or storage, poor planning of replenishment, etc. Storekeeping is a
custodian’s job, but in many organizations it lacks in efficiency because the
concerned personnel lack knowledge of the processes and their importance.

The stores executive has to be proficient and knowledgeable in materials

accounting, physical storage and handling, transport and related procedures,
relevant tax and duties, and aware of computerized working of stores. Only
sound and accurate materials account can allow reliable planning of purchase or
production. Prompt issues of required materials to production, maintenance or
projects depend on organized stowage and accurate identification of the stocks
and right type of handling equipment. Stores function would often interface
with transporters or operate transport contracts, so they should be aware of the
processes, practices and market conditions in the transport trade. In receipt and
dispatch documentation it is vital that the stores executive has fundamental
knowledge of taxation and related requirements. Lastly, in computer age
knowledge of how the computerized system works cannot miss the stores man.
The program caters to this need by covering the transaction cycle for stores with
stage by stage function of the computerized system.
According to industry, type of operation or type of stock item special situations
are faced by stores executive. The program specifically deals with them which
would widen perspective of the participants. It also has an additional input on
basic know-how of replenishment planning for regular stock items.

The Sales Department:-

Close liaison is necessary between the Sales and Stores Departments. There is
no value in the Stores holding stocks of items which the Sales Department
cannot sell, or in the Sales Department securing customers for items which
Stores does not have in stock, or will not have in stock at the times required by
customers. The Stores Department requires adequate information, based on
forecasts of future sales and trends, to assist in planning orders, setting stock
levels, allocating storage space, etc.Stores might also have to take back into
stock items sold but rejected (for one reason or another)by customers or items
supplied, for instance, to a shop but not sold. In many cases orders made by
customers will be filled direct by the Stores Department.

The Purchasing Department:-

In smaller enterprises responsibility for purchasing might rest with the Stores
Department, and in many large enterprises the Purchasing and Stores
Department might be linked in a ‘Supply Division’. Obviously in cases where
there are two separate departments, there must be a very close,co-ordinated
relationship between them. Stores must keep purchasing up to date with
information about stock levels, whilst Stores relies on Purchasing to buy all the
items and materials needed by the enterprise for its operations.

Requirement analysis:-
The first step in selection understands the user’s requirement within the
framework of the organization objectives and the environment in which the
system is being installed. Consideration is given to given to the user’s recourse
as well as the finances.

In selecting software, the user must decide whether to develop it in house, hire a
service company or a contact programmer to create it, or simple acquire it from
a software house. The choice is logically made after the user has clearly defined
the requirement expected of the software. Therefore requirement analysis sets
the tone for software selection.
Feasibility study:-
Depending on the result of the initial investigation, the survey is expanded to a
more detailed feasibility study.

Feasibility study is a test of a system proposal according to its workability,

impact on the organization, ability to meet user needs and effective use of
resources.

The objective of a feasibility study is not to a solve the problem but to acquire a
sense of its scope. During the study, the problem definition is crystallized and
aspects of the problem to be included in the system are determined. The result
of the feasibility study is a formal proposal. This is simply a report a formal
document detailing the nature and scope of the proposed solution.

Types of feasibility study:- Three key consideration are involved in

the feasibility analysis:- economic,technical,behavioral. Let briefly reviews each
consideration and how it relates to the system effort.

(i)Economic Feasibility:- Economic analysis is the most frequently

used method for evaluating the effectiveness of a candidate system. More
commonly known as cost/benefits analysis, the procedure is to be determine
the benefits and savings that are expected from a candidate system and
compare them with costs. If benefits outweigh costs, then the decision is
made to design and implement the system. Otherwise, further justification or
alterations in the proposed system will have a change of being approved.
This is an ongoing effort that improves in accuracy at each phase. .

(ii) Technical Feasibility:- technical feasibility centers around the

existing computer system(hardware, software, etc.) and to what extent it can
support the proposed addition. This involves financial consideration to
accommodate technical enhancement. If the budget is a serious constraint
then the project is judged not feasible.
 (a) Software Requirements:- After the analyst has collected all the
required information regarding the software to be developed and
regarding the software to be developed and has removed all
incompleteness, inconsistencies and anomalies from the specification,

Software Components:-
1.) Operating system
2.)MS-word
3.)VB.NET(framework)

(b) Hardware Requirement:-

1.)120 MB RAM
2.)Hard disk 40GB
3.)Processor
4.)Monitor(1024*768 higher resolution screens)
5.)Keyboard
6.)Mouse
7.)Printer
8.)Graphic card
9.)BIOS/CMOS
 (i) Behavioral Feasibility:- People are inherently resistant to
change and computers have known to facilitate change. An
estimate should be made of how strong a reaction the user staff is
likely to have towards the development of computerized system. If
is common knowledge that computer installations have something
to do with turnover, transfer, retraining and changes in employee
job status.

Analysis:-
Analysis is a detailed study of the various operation performed by a system and
their relationship with in and outside of the system. During analysis, data are
collected on the available files decision point and transaction handled by the
present system. Interview and site observation and questionnaires are example.

System Design:-
The discussion so for bring us to a pivotal point in the system development life
cycle. User requirement have been identified. Information has been gathered to
verify the problem and evaluate the existing system.

Software design is a process of problem-solving and planning for a software

solution. After the purpose and specifications of software are determined,
software developers will design or employ designers to develop a plan for a
solution. It includes low-level component and algorithm implementation issues
as well as the architectural view.

Design concepts:-
The design concepts provide the software designer with a foundation from
which more sophisticated methods can be applied. A set of fundamental design
concepts has evolved. They are:

• Abstraction :- Abstraction is the process or result of

generalization by reducing the information content of a concept or
an observable phenomenon, typically in order to retain only
information which is relevant for a particular purpose.
• Refinement:- It is the process of elaboration. A hierarchy is
developed by decomposing a macroscopic statement of function in
a stepwise fashion until programming language statements are
reached. In each step, one or several instructions of a given
program are decomposed into more detailed instructions.
Abstraction and Refinement are complementary concepts.

• Modularity :- Software architecture is divided into components

called modules.

• Software Architecture:- It refers to the overall structure of the

software and the ways in which that structure provides conceptual
integrity for a system. A software architecture is the development
work product that gives the highest return on investment with
respect to quality, schedule and cost.

• Control Hierarchy:- A program structure that represent the

organization of a program components and implies a hierarchy of
control.

• Structural Partitioning:- The program structure can be divided

both horizontally and vertically. Horizontal partitions define
separate branches of modular hierarchy for each major program
function. Vertical partitioning suggests that control and work
should be distributed top down in the program structure.
• Data Structure: - It is a representation of the logical relationship
among individual elements of data.
 • Software Procedure - It focuses on the processing of each
modules individually

• Information Hiding:- Modules should be specified and designed

so that information contained within a module is inaccessible to
other modules that have no need for such information.

Design considerations:-
There are many aspects to consider in the design of a piece of software. The
importance of each should reflect the goals the software is trying to achieve.
Some of these aspects are:

• Compatibility:- The software is able to operate with other products

that are designed for interoperability with another product. For
example, a piece of software may be backward-compatible with an
older version of itself.

• Extensibility:- New capabilities can be added to the software without

major changes to the underlying architecture.

• Fault-tolerance :- The software is resistant to and able to recover

from component failure.

• Maintainability - The software can be restored to a specified

condition within a specified period of time. For example, antivirus
 software may include the ability to periodically receive virus
definition updates in order to maintain the software's effectiveness.

• Modularity :- the resulting software comprises well defined,

independent components. That leads to better maintainability. The
components could be then implemented and tested in isolation before
being integrated to form a desired software system. This allows
division of work in a software development project.

• Packaging - Printed material such as the box and manuals should

match the style designated for the target market and should enhance
usability. All compatibility information should be visible on the
outside of the package. All components required for use should be
included in the package or specified as a requirement on the outside of
the package.

• Reliability - The software is able to perform a required function

under stated conditions for a specified period of time.
• Reusability - the modular components designed should capture the
essence of the functionality expected out of them and no more or less.
This single-minded purpose renders the components reusable
wherever there are similar needs in other designs.

• Robustness:- The software is able to operate under stress or tolerate

unpredictable or invalid input. For example, it can be designed with
resilience to low memory conditions.

• Security:- The software is able to withstand hostile acts and

influences.
 • Usability:- The software user interface must be usable for its target
user/audience. Default values for the parameters must be chosen so
that they are a good choice for the majority of the users.

What is Test Planning:-

 Define the functions, roles and methods for all test phases.

 Test planning usually start during the requirements phase.

 Major test plan elements are:-

 Clarify Objectives for each test phase

 Schedules and responsibilities for each test activity

 Availability of tools, facilities.

Coding:-

Login Form:-
Main Form:-
Insert:-
Public Class insert

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

System.EventArgs) Handles Button1.Click
Dim con As New OdbcConnection("dsn=new")
con.Open()
Dim qry As String
qry = " insert into
items(product_id,product_name,product_type,product_size) values (' " +
TextBox1.Text + " ',' " + TextBox2.Text + " ',' " + TextBox3.Text + " ',' " +
TextBox4.Text + " ')"
Dim com As New OdbcCommand(qry, con)
com.ExecuteNonQuery()
MessageBox.Show("inserted")
con.Close()

End Sub

Delete:-
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Dim con As New OdbcConnection("dsn=new")
con.Open()
Dim qry As String
Dim a As String
a = TextBox1.Text
qry = " delete from items where product_id=' " & a & " ' "
Dim com As New OdbcCommand(qry, con)
com.ExecuteNonQuery()
MessageBox.Show("deleted")
con.Close()

End Sub

Search:-
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Dim con As New OdbcConnection("dsn=new")
Dim dr As OdbcDataReader
con.Open()
Dim qry As String
Dim a As String
a = TextBox1.Text
qry = " select *from items where pid=' " & a & " ' "
Dim com As New OdbcCommand(qry, con)
dr = com.ExecuteReader
If dr.HasRows Then
While dr.Read
TextBox2.Text = dr.Item("product_name")
TextBox3.Text = dr.Item("product_size")

End While
End If

MessageBox.Show("searched")
con.Close()
End Sub

Update:-
Dim con As New OdbcConnection("dsn=new")
'Dim dr As OdbcDataReader
con.Open()
Dim qry As String
Dim a, b As String
a = TextBox1.Text
b = TextBox2.Text

qry = " update items set product_name=' " + b + " ' where product_id=' " &
a&"'"
Dim com As New OdbcCommand(qry, con)
com.ExecuteNonQuery()
MessageBox.Show("updated")
Me.ItemsTableAdapter.Fill(Me.AmanDataSet4.items)
con.Close()
End Sub