Inventory Management

The Complete Record

A complete solution to manage a large stock of inventory in

offline mode using java technology
 List of Content

S.No Subject
Acknowledgement
Certificates
List of Contents
1. Introduction about the Project
2. System development life cycle
3. ANALYSIS
4. IMPLEMENATAION
5. DESIGN
6. DATABASE DESIGN & TABLES STRUCTURE
7. Software Environments
8 Testing
9. SreenShot
10. Conclusion
11. Bibliography

1
1. Introduction about the project

The project titled as “INVENTORY MANAGEMENT “is a GUI based application. A company has a large
stock of different types of goods in its warehouse and it is very difficult to manage it manually ,and
to do this manually we need human resources .how much is supplied ,how much is raw material
purchased , how much to return and how much we have purchase return. The software provide
facility to manage the details about purchase ,sales, sales return , purchase return and customer
entry related to the goods. The software allows us to search the old records, modifying entry ,
creating new entries delete entries from the data base.

Modules

 Main menu

 Purchase Menu

 Sales menu

 Purchase return

 sales return

 customer entry

Functional Requirements:

 Create update and delete the records

 Can search records according to the purchase

 Can search all record of a particular day

 Can update the information

 Can save new information

2
1.2. Introduction
System analysis is a process of gathering and interpreting facts, diagnosing
problems and the information to recommend improvements on the system. It
is a problem solving activity that requires intensive communication between
the system users and system developers. System analysis or study is an
important phase of any system development process. The system is studied to
the minutest detail and analyzed. The system analyst plays the role of the
interrogator and dwells deep into the working of the present system. The
system is viewed as a whole and the input to the system are identified. The
outputs from the organizations are traced to the various processes. System
analysis is concerned with becoming aware of the problem, identifying the
relevant and decisional variables, analyzing and synthesizing the various
factors and determining an optimal or at least a satisfactory solution or
program of action.

A detailed study of the process must be made by various techniques like

interviews, questionnaires etc. The data collected by these sources must be
scrutinized to arrive to a conclusion. The conclusion is an understanding of
how the system functions. This system is called the existing system. Now the
existing system is subjected to close study and problem areas are identified.
The designer now functions as a problem solver and tries to sort out the
difficulties that the enterprise faces. The solutions are given as proposals. The
proposal is then weighed with the existing system analytically and the best one
is selected. The proposal is presented to the user for an endorsement by the
user. The proposal is reviewed on user request and suitable changes are made.
This is loop that ends as soon as the user is satisfied with proposal.

3
Preliminary study is the process of gathering and interpreting facts, using the
information for further studies on the system. Preliminary study is problem
solving activity that requires intensive communication between the system
users and system developers. It does various feasibility studies. In these
studies a rough figure of the system activities can be obtained, from which the
decision about the strategies to be followed for effective system study and
analysis can be taken.

4
SYSTEM DEVELOPMENT LIFE CYCLE

2.1 SYSTEM DEVELOPMENT LIFE CYCLE

The structured sequence of operation required imaging developing and making

operational a new information system it’s a cycle because the System will need
replacement and Development, cycle will begin.

2.1.1 Phases of SDLC

 System Analysis
 System Design
 Coding
 System Testing
 System Implementation
 System Maintenance.

5
2.1.2 System Development Life Cycle

System development life cycle is a process of developing software on the basis

of the requirement of the end user to develop efficient and good quality
software. It is necessary to follow a particular procedure. The sequence of
phases that must be followed to develop good quality software is known as
SDLC

The software is said to have a life cycle composed of several phases. Each of
these phases results in the development of either a part of the system or
something associated with the system, such as a test plan or a user manual. In
the life cycle model, called the “spiral model,” each phase has well-defined
starting and ending points, with clearly identifiable deliverables to the next
phase. In practice, it is rarely so simple.

As with most undertakings, planning is an important factor in determining the

success or failure of any software project. Essentially, good project planning
will eliminate many of the mistakes that would otherwise be made, and reduce
the overall time required to complete the project. As a rule of thumb, the more
complex the problem is, and the more thorough the planning process must be.
Most professional software developers plan a software project using a series of
steps generally referred to as the software development life cycle. A number of
models exist that differ in the number of stages defined, and in the specific
activities that take place within each stage.

6
 A GENERIC SYSTEM DEVELOPMENT LIFE CYCLE

2.1.2.1 Analysis of user requirements

During this stage, the problem is defined so that a clear understanding can be
gained of what the system should do, i.e. what the inputs to the system are,
what the output should be, and the operational parameters within which the
system is expected to work. If the new system is to replace an existing system,
the problem may be defined in terms of the additional or enhanced
functionality that is required.

7
2.1.2.2 Program design

In this stage, a solution to the problem is designed by defining a logical

sequence of steps that will achieve each of the stated system objectives. Such
a sequence of steps is often referred to as an algorithm.. Some of the methods
used to define program algorithms are described later in this section, and
include flowcharts and pseudo code. These tools allow the program designer
to break a given problem down into a series of small tasks which the computer
can perform to solve the problem. The user interface will also be designed
during this stage, and will determine how input is obtained, how output is
displayed, and what controls are available to the user.

2.1.2.3 Program coding

This stage, sometimes known as the implementation stage, is where the

algorithms are translated into a programming language, and tends to be the
longest phase of the development life-cycle. In this case, we are using JSP to
write the program.

2.1.2.4 Documentation and testing

The documentation of the program fulfils two main objectives. The first is to
provide a technical reference to facilitate ongoing maintenance and
development of the software itself. The second is to provide user
documentation, i.e. a set of instructions that inform the user about the
features of the software and how to use them. The aim of software testing is to
find any errors (“bugs”) in the program, to eliminate those errors (a process
known as “debugging”), and as far as is reasonably practicable should be

8
sufficiently rigorous to ensure that the software will function as expected
under all foreseeable circumstances.

2.1.2.5 Operating and maintaining the system

Once the software has been “rolled out” and any necessary user training has
been completed, it will be necessary to monitor the performance of the system
over time to ensure that it is behaving as expected. The system will need to be
maintained, and parts of it will need to be upgraded from time to time to
handle evolving user needs or to cope with new problems. Eventually, as the
system ages, it may no longer be able to adequately cope with the demands of
a growing number of users, take advantage of advances in hardware
technology, or adapt to a constantly changing environment. When this time
comes, the system will need to be decommissioned and replaced by a new
system. Hence, the software development life cycle will begin again.

9
ANALYSIS
3.1 REQUIREMENT ANALYSIS

Requirements are a feature of a system or description of something that is

capable of doing in order to fulfil the system’s purpose. It provides the
appropriate mechanism for understanding what the customer wants, analyzing
the needs, assessing feasibility, negotiating a solution, specifying the solution
unambiguously, validating the specification and managing the requirements as
they are translated into an operational system. Requirement Analysis is a task
done under software engineering that bridges the gap between system level
requirements engineering and software design. While requirements
engineering specifies software’s operational characteristics i.e. function, data
and behaviour, indicates software’s interface constraints, requirements
analysis let the software engineer (called analyst) to refine the software
allocation and construct models of data, functional and behavioural domains.
Moreover, requirements analysis provides software developer with a
representation of data, function and behaviour that can be converted to data,
architectural, interface and component-level designs. At last, we can say that
the requirement specification makes available, the developer and the
customer, a means to assess quality, once the software has been built.

10
3.2 REQUIREMENT SPECIFICATION

A Software Requirements Specification (SRS) is a complete description of the

behaviour of the system to be developed. It includes a set of use cases that
describe all the interactions that the users will have with the software. Use
cases are also known as Functional Requirements. In addition to use cases, the
SRS also contains Non-Functional (or supplementary) Requirements. Non-
Functional Requirements are requirements which impose constraints on the
design or implementation (such as performance requirements, quality
standards, or design constraints).

11
IMPLEMENATAION
4.1 IMPLEMENTATION

A crucial phase in the system life cycle is the successful implementation of

the new system design. Implementation simply means converting a new
system design into operation. This involves creating computer compatible
files, training the operating staff and installing hardware terminals, and
telecommunication network before the system is up and running.

In system implementation, user training is crucial for minimizing resistance to

change and giving the new system a chance to prove its worth. Training aids
such as user-friendly manuals, a data dictionary and job performance aids
that communicate information about the new system and help screens.
Provide the user with a good start on the new system.

12
Hardware Requirements:-

Processor : Pentium 4 or any other higher versions

Hard Disk : Minimum 2 GB Required

Ram : Minimum 256 MB Required

Monitor : Any

Software Requirements:-

Operating System : Windows 10.

Language : JAVA

PLATFORM : JGRASP

Front End : JAVA

Data Base : MS Acess

Server Side:

Hardware Requirements:-

Processor : Dual core or any other higher versions

Hard Disk : Minimum 40 GB or higher

RAM : Minimum 256 MB Required

Monitor : Any

13
 DESIGN:
Design is the first step into the development phase for any engineered product
or system. Design is a creative process. A good design is the key to effective
system. The term “design” is defined as “the process of applying various
techniques and principles for the purpose of defining a process or a system in
sufficient detail to permit its physical realization”.

5.1 LOGICAL DESIGN:

The logical flow of a system and define the boundaries of a system. It includes
the following steps:

 Prepares input specifications – format, content and most of the input

functions.

 Prepares edit, security and control specifications.

 Specifies the implementation plan.

 Reviews benefits, costs, target dates and system constraints.

14
5.2 PHYSICAL DESIGN:

Physical system produces the working systems by define the design

specifications that tell the programmers exactly what the candidate system
must do. It includes the following steps.

 Design the physical system.

 Specify input and output media.

 Design the database and specify backup procedures.

 Design physical information flow through the system and a physical

design

Design/Specification activities:

 Concept formulation.

 Problem understanding.

 High level requirements proposals.

 Feasibility study.

 Requirements engineering.

 Architectural design.

15
5.3 MODULE DESIGN

 Main menu

 Purchase Menu

 Sales menu

 Purchase return

 sales return

 customer entry

Accountant details:

 Create update and delete the records

 Can search records according to the purchase

 Can search all record of a particular day

 Can update the information

 Can save new information

16
5.4 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.

17
OBJECTIVES:

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.

 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.

 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

5.5 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
system’s relationship to help user decision-making.

18
  Designing computer output should proceed in an organized, well
thought out manner; the right output must be developed while
ensuring that each output element is designed so that people will
find the system can use easily and effectively. When analysis design
computer output, they should Identify the specific output that is
needed to meet the requirements.

 Select methods for presenting information.

 Create document, report, or other formats that contain information

produced by the system.

The output form of an information system should accomplish one or more of

the following objectives.

o Convey information about past activities, current status or projections of

the Future.

o Signal important events, opportunities, problems, or warnings.

o Trigger an action.

o Confirm an action.

5.6 Data Flow Diagram:

A data flow diagram (DFD) is a graphical representation of the "flow" of data

through an information system, modeling its process aspects. Often they are a
preliminary step used to create an overview of the system which can later be
elaborated. DFDs can also be used for the visualization of data
processing (structured design).

19
A DFD shows what kinds of information will be input to and output from the
system, where the data will come from and go to, and where the data will be
stored. It does not show information about the timing of processes, or
information about whether processes will operate in sequence or in parallel
(which is shown on a flowchart).the basic notation used to create a DFD’s are
as follows:

1. Dataflow: data moves in a specific from an origin to a destination.

2. Process: People ,procedures or device that use or produce data. The

physical components not identified.

3. Source: external sorce or destination of data, which may be people

programs, organizations or other entities.

4 .Data source: here data are store and referenced by a process in the
system.

20
DATABASE DESIGN:
6. Database

A database is an organized mechanism that has the capability of storing

information through which a user can retrieve stored information in an
effective and efficient manner. The data is the purpose of any database and
must be protected.

The database design is a two level process. In the first step, user requirements
are gathered together and a database is designed which will meet these
requirements as clearly as possible. This step is called Information Level Design
and it is taken independent of any individual DBMS.

In the second step, this Information level design is transferred into a design for
the specific DBMS that will be used to implement the system in question. This
step is called Physical Level Design, concerned with the characteristics of the
specific DBMS that will be used. A database design runs parallel with the
system design. The organization of the data in the database is aimed to achieve
the following two major objectives.

o Data Integrity

o Data independence

Normalization is the process of decomposing the attributes in an

application, which results in a set of tables with very simple structure. The

21
purpose of normalization is to make tables as simple as possible. Normalization
is carried out in this system for the following reasons.

 To structure the data so that there is no repetition of data , this

helps in

saving.

 To permit simple retrieval of data in response to query and

report request.

 To simplify the maintenance of the data through updates,

insertions,

Deletions.

 To reduce the need to restructure or reorganize data which new

application Requirements arise.

22
TABLES STRUCTURE
DATA BASE TABLE DESIGN

Table Name: customer Entry

Table Name: Product Entry

Table Name: Purchase Entry

23
Table Name: Purchase Return Entry

24
Table Name: Purchase Return Entry

25
Software Environments
7. JAVA

Java is a small, simple, safe, object oriented, interpreted or dynamically optimized,

byte coded, architectural, garbage collected, multithreaded programming language
with a strongly typed exception-handling for writing distributed and dynamicaly
extensible programs.

Java is an object oriented programming language. Java is a high-level, third

generation language like C, FORTRAN, Small talk, Pearl and many others. You can use
java to write computer applications that crunch numbers, process words, play
games, store data or do any of the thousands of other things computer software can
do.

Special programs called applets that can be downloaded from the internet and
played safely within a web browser. Java a supports this application and the follow
features make it one of the best programming languages.

 It is simple and object oriented

 It helps to create user friendly interfaces.

 It is very dynamic.

 It supports multithreading.

 It is platform independent

 It is highly secure and robust.

 It supports internet programming

26
Java is a programming language originally developed by Sun Microsystems and released in
1995 as a core component of Sun's Java platform. The language derives much of its syntax
from C and C++ but has a simpler object model and fewer low-level facilities. Java
applications are typically compiled to byte code which can run on any Java virtual machine
(JVM) regardless of computer architecture.

The original and reference implementation Java compilers, virtual machines, and class
libraries were developed by Sun from 1995. As of May 2007, in compliance with the
specifications of the Java Community Process, Sun made available most of their Java
technologies as free software under the GNU General Public License. Others have also
developed alternative implementations of these Sun technologies, such as the GNU
Compiler for Java and GNU Class path.

The Java language was created by James Gosling in June 1991 for use in a set top box
project. The language was initially called Oak, after an oak tree that stood outside Gosling's
office - and also went by the name Green - and ended up later being renamed to Java, from
a list of random words. Gosling's goals were to implement a virtual machine and a language
that had a familiar C/C++ style of notation.

Primary goals

There were five primary goals in the creation of the Java language:

1. It should use the object-oriented programming methodology.

2. It should allow the same program to be executed on multiple operating

systems.

3. It should contain built-in support for using computer networks.

4. It should be designed to execute code from remote sources securely.

5. It should be easy to use by selecting what were considered the good parts of
other object-oriented languages.

27
 The Java platform is the name for a bundle of related programs, or
platform, from Sun which allow for developing and running programs written in the
Java programming language. The platform is not specific to any one processor or
operating system, but rather an execution engine (called a virtual machine) and a
compiler with a set of standard libraries which are implemented for various
hardware and operating systems so that Java programs can run identically on all of
them.

Different "editions" of the platform are available, including:

 Java ME (Micro Edition): Specifies several different sets of libraries (known as

profiles) for devices which are sufficiently limited that supplying the full set of
Java libraries would take up unacceptably large amounts of storage.

 Java SE (Standard Edition): For general purpose use on desktop PCs, servers
and similar devices.

 Java EE (Enterprise Edition): Java SE plus various APIs useful for multi-tier
client-server enterprise applications.

The Java Platform consists of several programs, each of

which provides a distinct portion of its overall capabilities. For example, the Java
compiler, which converts Java source code into Java bytecode (an intermediate
language for the Java Virtual Machine (JVM)), is provided as part of the Java
Development Kit (JDK). The sophisticated Java Runtime Environment (JRE),
complementing the JVM with a just-in-time (JIT) compiler, converts intermediate
bytecode into native machine code on the fly. Also supplied are extensive libraries
(pre-compiled into Java bytecode) containing reusable code, as well as numerous
ways for Java applications to be deployed, including being embedded in a web page
as an applet.There are several other components, some available only in certain
editions.

28
The essential components in the platform are the Java language compiler, the
libraries, and the runtime environment in which Java intermediate bytecode
"executes" according to the rules laid out in the virtual machine specification.

29
Java Virtual Machine

The heart of the Java Platform is the concept of a "virtual machine" that executes
Java bytecode programs. This bytecode is the same no matter what hardware or operating
system the program is running under. There is a JIT compiler within the Java Virtual
Machine, or JVM. The JIT compiler translates the Java bytecode into native processor
instructions at run-time and caches the native code in memory during execution.

The use of bytecode as an intermediate language permits Java

programs to run on any platform that has a virtual machine available. The use of a JIT
compiler means that Java applications, after a short delay during loading and once they have
"warmed up" by being all or mostly JIT-compiled, tend to run about as fast as native
programs. Since JRE version 1.2, Sun's JVM implementation has included a just-in-time
compiler instead of an interpreter.

Although Java programs are Platform Independent, the code of

the Java Virtual Machine (JVM) that execute these programs are not. Every Operating
System has its own JVM.

Class libraries

In most modern operating systems, a large body of reusable code is provided

to simplify the programmer's job. This code is typically provided as a set of dynamically
loadable libraries that applications can call at runtime. Because the Java Platform is not
dependent on any specific operating system, applications cannot rely on any of the existing
libraries. Instead, the Java Platform provides a comprehensive set of standard class libraries,
containing much of the same reusable functions commonly found in modern operating
systems.

The Java class libraries serve three purposes within the Java Platform. Like
other standard code libraries, they provide the programmer a well-known set of functions to
perform common tasks, such as maintaining lists of items or performing complex string

30
parsing. In addition, the class libraries provide an abstract interface to tasks that would
normally depend heavily on the hardware and operating system. Tasks such as network
access and file access are often heavily dependent on the native capabilities of the platform.
The Java java.net and java.io libraries implement the required native code internally, then
provide a standard interface for the Java applications to perform those tasks. Finally, when
some underlying platform does not support all of the features a Java application expects,
the class libraries can either emulate those features using whatever is available, or at least
provide a consistent way to check for the presence of a specific feature.

31
Performance

Java's performance has improved substantially since the early versions, and performance of
JIT compilers relative to native compilers has in some tests been shown to be quite
similar.The performance of the compilers does not necessarily indicate the performance of
the compiled code; only careful testing can reveal the true performance issues in any
system.

Java Runtime Environment

The Java Runtime Environment, or JRE, is the software required to run any application
deployed on the Java Platform. End-users commonly use a JRE in software packages and
Web browser plug-in. Sun also distributes a superset of the JRE called the Java 2 SDK (more
commonly known as the JDK), which includes development tools such as the Java compiler,
Java doc, Jar and debugger.

One of the unique advantages of the concept of a runtime engine is that errors
(exceptions) should not 'crash' the system. Moreover, in runtime engine environments such
as Java there exist tools that attach to the runtime engine and every time that an exception
of interest occurs they record debugging information that existed in memory at the time the
exception was thrown (stack and heap values). These Automated Exception Handling tools
provide 'root-cause' information for exceptions in Java programs that run in production,
testing or development environments.

Java Script

JavaScript is a programming language that allows scripting of events, objects, and actions
to create Internet applications. A website development environment that will allow the
creation of Interactive Web Pages. The coding techniques capable of accepting a client's
requests and processing these requests.

The web site development environment should also provide the facility for 'validating' user
input. With JavaScript, forms are a consideration in nearly every page you design. Capturing
user requests is traditionally done via a 'form'. So the web site needs to have facilities to
create forms. Text fields and text areas can dynamically change in response to user
responses.

32
TOMCAT 5.0

Tomcat is a servlet container and Java Server Pages implementation it may be used stand
alone ,or in conjunction with several popular web servers .

o Apache version 1.3 or later

o MS Internet Information Server ,version 4.0 or later

o MS personel web server, version 4.0 or later

o NetScape enterprise server , version 3.0 or later

Tomcat is a security update release. This release closes a whole that potentially allowed
access to resources protected by a <security constraint > in web.xml.

Installing and Running Tomcat 5.0

Tomcat requires a Java Runtime Environment (JRE).Conformant to JRE 1.1 or later including
any Java2 platform system. If one wishes to develop applications you will need a java
compiler , such as the one included in a java development kit 1.1 or later environment
including JDKs conformant with Java2.

FEATURES OF O.S :

This project work is done on the windows 2000 professional, which is the operating
system. An operating system is a set of software tools designed to make it easy for people or
programmers to make optimum use of the computer. People who use computers have
different levels of needs and interest. These peoples can be separated can be two groups,
users and programmers. The user wants a convenient set of commands to manage files of

data or programs, copy and run application package while a programmer used as a set of
tools that can be held together and debug programs.

No matter where you are working, your computer will be easier to use and manage,
because Microsoft Windows 2000 Professional is more compatible and more powerful than
any workstation you’ve used before. The main features of Windows 2000 Professional
operating system are

33
  Easier to use.

 Easier to manage

 More compatible

 More powerful

Easier to use

With Windows 2000 Professional, you have faster access to information, and you are
able to accomplish tasks more quickly and easily.

Windows 2000 Professional makes it easier to:

 Work with files.

 Find information.

 Personalize your computing environment.

 Work on the web.

 Work remotely

Easier to manage

You and your network administrators can work more efficiently now, because many of
the most common computer-management tasks are automated are streamlined with
Windows 10 Professional.

With Windows 10, your workstation will be easier to:

 Set up.

34
  Administrator

 Support.

More Compatible:

Windows 10 Professional offers increased compatibility with different types of network

and with a wide array of legacy hardware and software.

Windows 10 also provides:

 Improved driver support.

 Increased support for new-generation hardware multimedia technologies.

More Powerful:

For all your computing needs, Windows 10 Professional provides:

 Industrial-strength reliability

 The highest level of security

 Powerful performance

Windows 10 also contains the following features:

PORTABILITY:

 Windows file protection protects core system files from being overwritten by
application installs.

35
  Driver certification provides safeguards to assure you that device drivers have not
been tampered with and reduces your risk of installing non-certified drivers.

 Full 64 bit operating system minimizes the chance of application failures and
unplanned reboots.

MOBILITY

 Hibernate turns off your computer and monitors after a predetermined time while
retaining your desktop on disk.

 Offline viewing makes entire WebPages with graphics available for viewing offline

 Synchronization manager allows you to compare and update your offline files and
folders with those on the network.

 Smart battery gives you a more accurate view of your battery’s life enabling you to
reduce power to specify functions to extend your battery power.

 Hot docking tells you dock or undock your notebook computer without changing
hardware configuration or rebooting.

 Universal Serial Bus (USB) lets you connect and disconnect a wide array of
peripherals such as joysticks, scanners and camcorders without configuring or
rebooting your computer.

 J2EE 1394 provides a higher band width connection for devices that require faster
data transfer.

36
MAINTAINABILITY

 System preparation tool (sys prep) helps administrators clone computer

configuration systems and applications.

 Set up manager provides a graphical wizard that guides administrators in designing

installation scripts.

 Multilingual support allows users to easily create, read and edit documentation in
hundreds of languages.

 Windows 2000 server offers 25% faster performance than Windows 95 or Windows
98 on systems with 64MB or more of memory.

 32 bit architecture allows you to run more programs and perform more faster at the
same time than Windows 95 or 98.

 Windows 2000 can support to 4GB of Ram and two symmetric multiprocessors.

 Encrypting file system (EFS) encrypts each file with a randomly generated key.

 IP Security (IP Sec) support protected data transmitted across a network.

 Kerberos support provides industry standard high-strength authentication with a

fast, single login to windows 2000 enterprise resources.

INTERNET CAPABILITY

 Internet Information Services (IIS) 5.0 includes web and FTP server support, as well
as support for Front-page transactions, Active Server Pages (ASP) and database
connections.

37
 Windows 2000 has strong development platform support for dynamic HTML
behaviors and XML.

 Intelliforms alleviates the tedious of filling out forms on the web by automatically
entering your name, address or other information that you have securely stored on
your computer.

 Automated proxy automatically locates a proxy server configures Internet Explorer

5.0 to connect to the internet through the server.

38
Testing :
8. Testing

Software Testing is the process of executing software in a controlled manner, in order to

answer the question - Does the software behave as specified?. Software testing is often
used in association with the terms verification and validation. Validation is the checking or
testing of items, includes software, for conformance and consistency with an associated
specification. Software testing is just one kind of verification, which also uses techniques
such as reviews, analysis, inspections, and walkthroughs. Validation is the process of
checking that what has been specified is what the user actually wanted.

Validation : Are we doing the right job?

Verification : Are we doing the job right?

Software testing should not be confused with debugging. Debugging is the process of
analyzing and localizing bugs when software does not behave as expected. Although the
identification of some bugs will be obvious from playing with the software, a methodical
approach to software testing is a much more thorough means for identifying bugs.
Debugging is therefore an activity which supports testing, but cannot replace testing.

Other activities which are often associated with software testing are static analysis and
dynamic analysis. Static analysis investigates the source code of software, looking for
problems and gathering metrics without actually executing the code. Dynamic analysis

looks at the behavior of software while it is executing, to provide information such as

execution traces, timing profiles, and test coverage information.

39
 Testing is a set of activity that can be planned in advanced and conducted systematically.
Testing begins at the module level and work towards the integration of entire computers
based system. Nothing is complete without testing, as it vital success of the system testing
objectives, there are several rules that can serve as testing objectives. They are

 Testing is a process of executing a program with the intend of findingan error.

 A good test case is one that has high possibility of finding an undiscovered error.

 A successful test is one that uncovers an undiscovered error.

If a testing is conducted successfully according to the objectives as stated above, it would

uncovered errors in the software also testing demonstrate that the software function
appear to be working according to the specification, that performance requirement appear
to have been met.

There are three ways to test program.

 For correctness

 For implementation efficiency

 For computational complexity

Test for correctness are supposed to verify that a program does exactly what it was
designed to do. This is much more difficult than it may at first appear, especially for large
programs.

8.1 TEST PLAN

A test plan implies a series of desired course of action to be followed in accomplishing

various testing methods. The Test Plan acts as a blue print for the action that is to be

40
followed. The software engineers create a computer program, its documentation and
related data structures. The software developers is always responsible for testing the
individual units of the programs, ensuring that each performs the function for which it was
designed. There is an independent test group (ITG) which is to remove the inherent
problems associated with letting the builder to test the thing that has been built. The
specific objectives of testing should be stated in measurable terms. So that the mean time
to failure, the cost to find and fix the defects, remaining defect density or frequency of
occurrence and test work-hours per regression test all should be stated within the test plan.

The levels of testing include:

 Unit testing

 Integration Testing

 Data validation Testing

 Output Testing

8.1.1 UNIT TESTING

Unit testing focuses verification effort on the smallest unit of software design – the
software component or module. Using the component level design description as a guide,
important control paths are tested to uncover errors within the boundary of the module.
The relative complexity of tests and uncovered scope established for unit testing. The unit
testing is white-box oriented, and step can be conducted in parallel for multiple
components. The modular interface is tested to ensure that information properly flows into
and out of the program unit under test. The local data structure is examined to ensure that
data stored temporarily maintains its integrity during all steps in an algorithm’s execution.
Boundary conditions are tested to ensure that all statements in a module have been
executed at least once. Finally, all error handling paths are tested.

41
 Tests of data flow across a module interface are required before any other test is
initiated. If data do not enter and exit properly, all other tests are moot. Selective testing of
execution paths is an essential task during the unit test. Good design dictates that error
conditions be anticipated and error handling paths set up to reroute or cleanly terminate
processing when an error does occur. Boundary testing is the last task of unit testing step.
Software often fails at its boundaries.

Unit testing was done in Sell-Soft System by treating each module as separate entity and
testing each one of them with a wide spectrum of test inputs. Some flaws in the internal
logic of the modules were found and were rectified.

8.1.2 INTEGRATION TESTING

Integration testing is systematic technique for constructing the program structure while
at the same time conducting tests to uncover errors associated with interfacing. The
objective is to take unit tested components and build a program structure that has been
dictated by design. The entire program is tested as whole. Correction is difficult because
isolation of causes is complicated by vast expanse of entire program. Once these errors are
corrected, new ones appear and the process continues in a seemingly endless loop.

After unit testing in Sell-Soft System all the modules were integrated to test for any
inconsistencies in the interfaces. Moreover differences in program structures were removed
and a unique program structure was evolved.

42
8.1.3 VALIDATION TESTING OR SYSTEM TESTING

This is the final step in testing. In this the entire system was tested as a whole with all
forms, code, modules and class modules. This form of testing is popularly known as Black
Box testing or System tests.

Black Box testing method focuses on the functional requirements of the software. That
is, Black Box testing enables the software engineer to derive sets of input conditions that
will fully exercise all functional requirements for a program.

Black Box testing attempts to find errors in the following categories; incorrect or missing
functions, interface errors, errors in data structures or external data access, performance
errors and initialization errors and termination errors

43
9. SCREEN SHOTS :

when the software is open

all thing are shown which are required to manage the stock

44
Product Entry

45
when we click on save

and successfully save the data

46
when we want to modify the data

and the rate is successfully modified

47
when the particular entry is deleted

48
when we want to review the stock

like this there are different different types of window for different uses these
are

Customer Entry

the window showing details related to customer

49
window for Purchase return

50
51
DataBase view

52
10. Conclusion :

The project titled as “Inventory Management system” is a GUI based application. This
software provides facility for, create ,update and delete record of the stock . The software is
developed with modular approach. All modules in the system have been tested with valid
data and invalid data and everything work successfully. Thus the system has fulfilled all the
objectives identified and is able to replace the existing system.

The project has been completed successfully with the maximum satisfaction of the
organization. The constraints are met and overcome successfully. The system is designed as
like it was decided in the design phase. The project gives good idea on developing a full-
fledged application satisfying the user requirements.

The system is very flexible and versatile. This software has a user-friendly screen that
enables the user to use without any inconvenience. Validation checks induced have greatly
reduced errors. Provisions have been made to upgrade the software.

53
11. BIBLIOGRAPHY AND REFERENCES

Websites referred

 www.slideshare.net

 www.youtube.com

 www.javaTpoint.com

 www.tutorialspoint.com

 www.w3schools.com

 www.stackoverflow.com

1. Search Engine

 www.google.com

54