1.

INTRODUCTION
Inventory management is primarily about specifying the size and placement of stocked
goods. Inventory management is required at different locations within a facility or within
multiple locations of a supply network to protect the regular and planned course of production
against the random disturbance of running out of materials or goods. The scope of inventory
management also concerns the fine lines between replenishment lead time, carrying costs of
inventory, asset management, inventory forecasting, inventory valuation, inventory visibility,
future inventory price forecasting, physical inventory, available physical space for inventory,
quality management, replenishment, returns and defective goods and demand forecasting.
Balancing these competing requirements leads to optimal inventory levels, which is an on-going
process as the business needs shift and react to the wider environment.
Inventory management involves a retailer seeking to acquire and maintain a proper
merchandise assortment while ordering, shipping, handling, and related costs are kept in check.
The technique of inventory proportionality is most appropriate for inventories that remain
unseen by the consumer. As opposed to "keep full" systems where a retail consumer would like
to see full shelves of the product they are buying so as not to think they are buying something
old, unwanted or stale; and differentiated from the "trigger point" systems where product is
reordered when it hits a certain level; inventory proportionality is used effectively by just-in-time
manufacturing processes and retail applications where the product is hidden from view.
One early example of inventory proportionality used in a retail application in the United
States is for motor fuel. Motor fuel (e.g. gasoline) is generally stored in underground storage
tanks. The motorists do not know whether they are buying gasoline off the top or bottom of the
tank, nor need they care. Additionally, these storage tanks have a maximum capacity and cannot
be overfilled. Finally, the product is expensive. Inventory proportionality is used to balance the
inventories of the different grades of motor fuel, each stored in dedicated tanks, in proportion to
the sales of each grade. Excess inventory is not seen or valued by the consumer, so it is simply
cash sunk (literally) into the ground.
The word 'inventory' can refer to both the total amount of goods and the act of counting
them. Many companies take an inventory of their supplies on a regular basis in order to avoid
running out of popular items. Others take an inventory to insure the number of items ordered
matches the actual number of items counted physically. Shortages or overages after an inventory
can indicate a problem with theft (called 'shrinkage' in retail circles) or inaccurate accounting
practices. To avoid these manual discrepancies we use computerized inventory system.

1
1.1 PURPOSE OF PROJECT

Inventory is the total amount of goods and/or materials contained in a store or factory at
any given time. Store owners need to know the precise number of items on their shelves and
storage areas in order to place orders or control losses. Factory managers need to know how
many units of their products are available for customer orders. Restaurants need to order more
food based on their current supplies and menu needs. All of this business relies on an inventory
count to provide answers.
The word 'inventory' can refer to both the total amount of goods and the act of counting
them. Many companies take an inventory of their supplies on a regular basis in order to avoid
running out of popular items. Others take an inventory to insure the number of items ordered
matches the actual number of items counted physically. Shortages or overages after an inventory
can indicate a problem with theft (called 'shrinkage' in retail circles) or inaccurate accounting
practices. To avoid these manual discrepancies we use computerized inventory system.

The proposed “INVENTORY MANAGMENT” is economically feasible because

 The system requires very less time factors.

 The system will provide fast and efficient automated environment instead of slow and
error prone manual system, thus reducing both time and man power spent in running the
system.
 The system will have GUI interface and very less user-training is required to learn it.
 The system will provide service to view various information for proper managerial
decision making.

1.2 PROJECT AND PRODUCT OVERVIEW

Inventory Management is designed to meet the dictates of market place and support the
company’s Strategic Plan.
Inventory management is primarily about specifying the size and placement of stocked
goods. Inventory management is required at different locations within a facility or within
multiple locations of a supply network to protect the regular and planned course of production
against the random disturbance of running out of materials or goods. The scope of inventory
management also concerns the fine lines between replenishment lead time, carrying costs of
inventory, asset management, inventory forecasting, inventory valuation, inventory visibility,
future inventory price forecasting, physical inventory, available physical space for inventory,
quality management, replenishment, returns and defective goods and demand forecasting.

2
1.3 INTENDED AUDIENCE

This text belongs to all the team workers and is intended for the project in-charge, Zensar
Technologies and the people who want knowledge about various modules of Inventory
Management System. This report contains the overview of the whole system in which each
feature is examined according to its precedence.

1.4 TEAM ARCHITECTURE

There were five teams and each team had five members. Complete project was divided in
five modules and each module was given to a team

 TEAM 1

PLANNING AND MAINATENANCE

Planning identifies all deliverable products and services, describes the products, and
defines the process to make the products and deliver the services.
Manufacturing planning and control address decisions on the acquisition, utilization and
allocation of production resources to satisfy customer requirements in the most efficient and
effective way. Typical decisions include work force level, production lot sizes, assignment of
overtime and sequencing of production runs. Any planning problem starts with a specification of
customer demand that is to be met by the production plan. In most contexts, future demand is at
best only partially known, and often is not known at all. Consequently, one relies on a forecast
for the future demand.

In many planning contexts, an important construct is to set a planning hierarchy. Namely, one
structures the planning process in a hierarchical way by ordering the decisions according to
their relative importance.
The identification of the relevant costs is also an important issue. For production
planning, one typically needs to determine the variable production costs, including setup
related costs, inventory holding costs, and any relevant resource acquisition costs. There might
also be costs associated with imperfect customer service, such as when demand is backordered.
A planning problem exists because there are limited production resources that cannot be
stored from period to period. Choices must be made as to which resources to include and how to
model their capacity and behavior, and their costs. Also, there may be uncertainty associated
with the production function, such as uncertain yields or lead times. One might only include the
most critical or limiting resource in the planning problem.

3
Production planning is usually done at an aggregate level, for both products and resources.
Distinct but similar products are combined into aggregate product families that can be planned
together so as to reduce planning complexity. Similarly production resources, such as distinct
machines or labor pools, are aggregated into an aggregate machine or labor resource.
Planning can be divided into four categories. The first planning category is sales. The
second is inventory, commonly called stock, or beginning-of-month stock. The third is other
reductions, which typically includes markdowns, employee discounts and shortages. Last are
planned purchases.
The factors that may affect planning decisions are of two types namely external variables
and internal variables. External variables are factors that cannot be controlled, but that do have
an impact on the operation. A significant external variable is the weather. Internal variables are
those factors that can be controlled. These are the decisions may help in increasing the sales. For
example, an increase in the advertising budget could result in an increase in sales.

 TEAM 2

SALES AND PURCHASE

Selling is the most important and the most difficult function in any organization. Without
the sales function, a firm cannot stay in business for long. Therefore, managing sales in an
organization is a critical activity. A sales manager needs to ensure that the salespeople are
motivated to perform the selling function in a way that will help the organization attain its goals.

Some of the trends that have shaped the sales function include shorter product life cycles,
longer and more complex sales cycles, reduced customer loyalty, intense competition among
manufacturing firms, rising customer expectations, increasing buyer expertise, electronic
revolution in communications, and the entry of women into the sales force. With continuing
advances in technology, the sales function continues to evolve, even in the twenty-first century
In addition to helping an organization achieve its business goals, the selling function
performs various other roles as well, such as that of enhancing knowledge about both the internal
and external environments, such as customers, suppliers, distributors, employees and other
people; developing a positive relationship with the customers, suppliers and distributors; and
negotiating with customers to sell the company's products profitably. The sales team of an
organization can play these roles effectively only when it receives the required support from
other departments. All the roles of the sales team are interdependent and the success of one role
depends upon the success of the others.

 TEAM 3

4
 INVENTORY

Inventory is a quantity or store of goods that is held for some purpose or use (the term may also
be used as a verb, meaning to take inventory or to count all goods held in inventory). Inventory
may be kept "in-house," meaning on the premises or nearby for immediate use; or it may be held
in a distant warehouse or distribution center for future use. With the exception of firms utilizing
just-in-time methods, more often than not, the term "inventory" implies a stored quantity of
goods that exceeds what is needed for the firm to function at the current time (e.g., within the
next few hours).

Inventory Management

Inventory management is required at different locations within a facility or within multiple

locations of a supply network to protect the regular and planned course of production against the
random disturbance of running out of materials or goods. Inventory management involves a
retailer seeking to acquire and maintain a proper merchandise assortment while ordering,
shipping, handling, and related costs are kept in check. Management of the inventories, with the
primary objective of determining/controlling stock levels within the physical distribution
function to balance the need for product availability against the need for minimizing stock
holding and handling costs.

1. Acquisitions require “Purchase Orders” to track and authorize the purchase, while the
actual installation of equipment is performed by the Infrastructure or Facilities
Management Department. Once added to the environment, a Master Inventory record is
created to describe the newly added equipment and its components (i.e., Pentium IV PC
with 512 MB or RAM, a 40 GB Hard Drive, CD Drive, Floppy Drive, Sound and Video
Cards, a 56 KB Modem and a 10/100 Ethernet Connection, etc.). Inventory records can
be used to calculate the resale price of existing equipment, when planning for an
upgrade / replacement or reduction in size. The Inventory Report can be used to inform
buyers of your stock and obtain bids on the purchase of your surplus equipment.
2. Redeployment procedures are responsible for ensuring that assets are tracked when
moved from one location to another and that budgetary considerations are adjusted as
needed. Should a product be moved in from its original owner, then the Inventory
System is updated to reflect the new location and owner. In this case, the old product is
deleted from the original owner's budget and added to the new owner's budget. If
equipment is being deployed from one person, or location, to another, then a data wipe
operation must be performed to insure that sensitive business, personal and/or medical
information has been deleted.
3. Termination is responsible for deleting the asset from the inventory when it is
discontinued, or replaced. The owner's budget will be updated to reflect the asset
termination and the asset will no longer be listed when location reports are generated.

5
 Whenever equipment is being terminated (even if for donation to charities or employees)
a data wipe operation must be performed to eliminate any sensitive information from the
hard drive. Additionally, a certified vendor must be utilized to insure that the computers
components are disposed of in an environmentally friendly manner.

 TEAM 4

FINANCE

Finance is the science of funds management. The general areas of finance are business
finance, personal finance, and public finance.Finance includes saving money and often
includes lending money. The field of finance deals with the concepts
of time, money, risk and how they are interrelated. It also deals with how money is spent
and budgeted

Let us See some Example of Finance management:

 A mother is trying to decide whether to buy her daughter a new dress now, or wait until
next summer so that she does not grow out of the dress too soon.
 A school governing body is working out how much money they have, they want to buy
new desks for the Grade 1 classroom.
 The treasurer of the soccer club is working out how much it will cost to take the club to a
regional tournament.

Financial management is about planning income and expenditure, and making decisions that will
enable you to survive financially.

Financial management includes

 financial planning and budgeting,

 financial accounting
 financial analysis,
 financial decision-making and
 action

Financial planning is about:

 Making sure that the organisation can survive.

6
  Making sure the money is being spent in the most efficient way.
 Making sure that the money is being spent to fulfil the objectives of the organisation.
 Being able to plan for the future of the organisation in a realistic way.

Financial Accountability

In non-profit organisations, the money that you are using is held in trust – on behalf of the
community that you serve. The money is not the personal possession of the individual staff
members. They have to account for how they used the money, to show that it was used to
benefit the community.
In a profit-making organisation, it is easy to hold management accountable. We simply ask: did
they make a profit? In a non-profit making organisation we ask: did they use the money to
benefit the community in the best possible way?Financial accountability can be broken down
into two components:

Financial Accountability :

Being able to account for the way the money is spent to:
 donors
 boards and committees
 members, and
 the people whom the money is meant to benefit

Financial Responsibility:

 Not taking on obligations the organisation cannot meet

 Paying staff and accounts on time
 Keeping proper records of the money that comes into the organisation and goes
out of the organisation

In this module we have learnt about finance management.In this we have shown the working of
finance department in an organization.
It shows all the flow of cash that how a business is started using capital and the transaction
related to cash are recorded.
It shows the number of books in the account process where all transactions are recorded and
how balance sheet is prepared to show the real condition of the organization.View of different
different books are also shown.

Broad Aim

7
The aim of this module is to give participants an overview of the role of managers in controlling
financial resources.

Training outcomes

By the end of this module, participants will be able to:

 Identify the main elements of financial management and assess whether the financial
management in their station is adequate
 Identify the financial policies needed in a radio station
 Develop a budget
 Do a cash flow projection
 Develop and interpret a variance report

 TEAM 5

HUMAN RESOURCE MANAGEMENT

Human Resource Management (HRM) is the term used to describe formal systems
devised for the management of people within an organization. The goal of human resource
management is to help an organization to meet strategic goals by attracting, and maintaining
employees and also to manage them effectively .These human resources responsibilities are
generally divided into three major areas of management: staffing, employee compensation, and
defining/designing work.

Essentially, the purpose of HRM is to maximize the productivity of an organization by

optimizing the effectiveness of its employees. This mandate is unlikely to change in any
fundamental way, despite the ever-increasing pace of change in the business world.

An organization's human resources department was often consigned to lower rungs of the
corporate hierarchy, despite the fact that its mandate is to replenish and nourish the company's
work force, which is often cited—legitimately—as an organization's greatest resource. But in
recent years recognition of the importance of human resources management to a company's
overall health has grown dramatically. This recognition of the importance of HRM extends to
small businesses, for while they do not generally have the same volume of human resources
requirements as do larger organizations, they too face personnel management issues that can
have a decisive impact on business health. In the other words we can explain Human resource
management (HRM) as the strategic and coherent approach to the management of an
organization's most valued assets - the people working there who individually and collectively
contribute to the achievement of the objectives of the business. The terms "human resource
management" and "human resources" (HR) have largely replaced the term "personnel

8
management" as a description of the processes involved in managing people in organizations. In
simple words, HRM means employing people, developing their capacities, utilizing, maintaining
and compensating their services in tune with the job and organizational requirement.

1.5 OVERALL DESCRIPTION

Time Saving: Our Inventory Management System is developed with a primary aim of 'Saving
Time'. The customer can view all the products and can register themselves to purchase the
products online. User can send their feedbacks and comments via emails.

No Complication: Major complication part for Inventory Systems is adding product or

managing products section. In our inventory management system no complicated part is involved
in product sections; we have took immerse care in this section and nullified all complications
which make this system accurate and unique. It is easy to add products and manage complete
Product section in our system. Online inventory management system is a secure way to manage
inventory and it avoids manual Inconsistencies.

Supply and Demand: Having an adequate supply of a particular product to meet customer
demand is crucial to both sales increases and customer service. If a customer comes to a business
to purchase a product and it is out of stock, the sale is lost forever and the customer will probably
go to a competitor to find what they need. A good inventory management system, whether
computerized or manual, will identify sales trends and prepare for customer needs.

Cost Effective: It's cheaper. You don't have to purchase multiple copies of software to install on
multiple computers. Multiple copies often require you to pay multiple licensing fees, but since
you aren't actually purchasing any software with an online system, that's not a concern.

Security: Online systems are just as secure. Most online inventory programs allow you to create
multiple user accounts with various levels of access. Your data is stored on secure, protected
servers that feature firewalls and other online security programs.

1.6 PRODUCT PERSPECTIVE

What is the advantage of creating the website? Nowadays everything is becoming

computerized. Previously all the information of various schemes of companies were either stored
in registers or excel sheets. This was really a manual work. Employees had to maintain the
database separately which was a time consuming job. Sometimes data is not updated when the
results are declared and hence the chances of incomplete or wrong information getting stored in
the database, increases. In this project the main perspective was to make the administrator,

9
employees and user’s easy access to the necessary details so that the functions and activities
carried out in a company can run smoothly.

10
2. PROBLEM STATEMENT

Inventory Management system provides information to efficiently manage the flow of

materials, effectively utilize people and equipment, coordinate internal activities and
communicate with customers. Inventory Management does not make decisions or manage
operations; they provide the information to managers who make more accurate and timely
decisions to manage their operations.
The software is leveraging the powers of the internet to increase its usability. It helps the
company to manage its products, services over the internet via a website.

2.1 BUSINESS REQUIREMENTS:

2.1.1 ENTRY POINT

The system is required to have two entry points:

1) Vendor Direct: A “Vendor Direct” entry point is where the vendor can manage the
inventory and service the customer requests.

2) Customer Linking: A “Customer Linking” entry point is where a prospective

customer can view the details of products and place their order.

2.1.2 SELECTION OF PRODUCT

Based upon the customer’s request the feasibility of supplying product is evaluated. The
customer request is fulfilled according to the placed order.

2.1.3 REPORTS
 Annual reports

 Monthly reports

 Sales reports

 Customer trends

2.2 SYSTEM REQUIREMENT

Performance and Scalability: The system is required to scale to support transaction

volume. WebPages should be light and render fast.

11
2.2.1 USABILITY

The web forms should be self explanatory and usable. We do not want prospective clients
dropping of the website because they cannot understand the forms and find them cumbersome.

12
3. PROJECT UNDERSTANDING DOCUMENT

3.1 PURPOSE OF PROJECT

The purpose of an effective inventory management initiative is to manage products,

vendors, and customers, increase visibility, and improve the general attitudes of potential clients
and the public at large for future business development.
While simple in scope, different products as per vendors can be managed for effective Business
prospects .Interactions and subsequent actions and create a variety of potential outcomes, both
productive and counterproductive to business development.

3.2 OBJECTIVE

Our objective is to make a platform independent application to maintain a database of all

products created from various sources and all the different services required by each of them.
Once the product information is collected and distributed, it is then transferred to planning and
maintenance department, who will continue to implement inventory management practices in
pursuit of completion of a management of products. Established inventory management practices
should provide the needed connectivity and accountability between those two operational units,
and when managed properly, enhances the effectiveness of both operations.

 Planning and Maintenance

 Stock Management

 Sales And Purchase

 Finance

 Human Resource

The above are the modules of inventory management system.

3.3 MIS REPORTS:

 Dashboard with live report summaries
 Automated report generation and automated report distribution
 Automated report triggers on specified event
 Supported report formats:

13
  New: Direct interface with MS Office - Excel reports
 Text files
 Graphics / Flash Charts
 Database files

 Some of the key reports are:

 Inventory Report
 Inventory Report by Location
 Inventory Report by Low Level Stock

14
 4. DURATION

4.1 Timeline

Sr. Project Phase Phase No. Category Total

No Period of person
(Working Cons days
Days) ultan (1) * (2)
(1) ts (2)
Business Requirement Study 12 3 Business Consultant
1. 36
Low Level/Application 22 4 Technical Associates and
2.
Design Design Specialists 88
Development and Unit 30 8 Database Administrator 240
3.
Testing /Technical Associates and
Project manager
Test & Bug Fixing 13 5 Tester & Technical
4.
Associates 65
Documentation 10 2 Technical Associates
5. 20
Deployment User 10 3 Project Leaders &
6.
Acceptance Testing Technical Associates 30
10 Project Leaders
7. User Training/handover
2 20
Project Management 120 1 Project Leader/Manager
8. 120
Total 619

15
5. REQUIREMENTS

5.1 SPECIFIC REQUIREMENTS

5.1.1 EXTERNAL INTERFACE REQUIREMENTS

 The external system is to assume full responsibility for storage functions as well as
warehouse management and warehouse control for an entire warehouse. The interfaces
in this section are specified by documenting: the name and description of each scheme,
source or input, destination or output, ranges, accuracy and tolerances, units of measure,
timing, display formats and organization, and data formats.The interfaces in this section
are specified by documenting: the name and description of each scheme, source or input,
destination or output, ranges, accuracy and tolerances, units of measure, timing, display
formats and organization, and data formats.
The user interface required to be developed for the system should be user
friendly and attractive. The interface between the user and the system will be WIMP
(Windows, Icons, Menu, Pointers) keeping in mind that the system is to be run through
web browser. All operations will be of point and click nature with all navigations
performed through windows of the system specifically buttons and menus:

Buttons: The button is activated when the user will click with the left click of the mouse
within the bounds of the button. And thus the action associated with it will be carried out.

Menu: All the operations will be arranged.

5.1.2 HARDWARE INTERFACE

Here's What You Need to Use the inventory management system system:

• 20 GB HDD
• 256 MB RAM
• Pentium IV Processor
• Input Devices: Keyboard, Mouse
• Output Devices: Monitor, Printer

5.1.3 SOFTWARE INTERFACE

16
 • Supporting Tools : Blue print foundry 4.0,Microsoft @ Word 2007,
Microsoft@PowerPoint 2007.

5.2 NON-FUNCTIONAL REQUIREMENTS

• Performance Criteria: Time. The elapsed time between the submission of documents
process between customer to vendor that between vendor to company should be as minimum as
possible. Similarly, there is being a minimal gap between all information about products.

• User friendly: Our Inventory Management system should be more users friendly. The user
interface should be kept simple and uncluttered. Since different type of people will interact in
this process so our project should be very easy to them to understand.

• Flexibility: Our project should be so flexible that whenever we want to make changes in it
very easily it can be done on

• Extensibility:
It should be able to accommodate the variations like:
> Different schemes should be handled easily.
> Client interaction after sending his/her details.
> It should be able for direct money transfer from one place to another.

• Portable: Our project should be portable on any platform and available on websites easily
and at a faster speed than others.

• Reusable: All the client web pages that are being used for client information should be
easily get processed so that many clients can interact with us very easily and very fast without
any information destroy.

5.3 SOFTWARE SYSTEM ATTRIBUTES

• Reliability: The health insurance process on the project should be easy and without any
mistakes so that clients should take information about all the policies and their interest rate and
update by company should be very easy and safe.

• Availability: The project should be available 24 hours a day, 7 days a week. The
availability can be measured in terms of MTTR (Mean Time to Repair) and MTBF (Mean Time
Between failures). The system will be available to the user whenever the user needs it.

• Maintainability: Our project should be easy to maintain by administrators or by our

17
company. After certain of time system should be added a new policies and our user interactive
schemes so that we can deal with our users according to market and time.

18
6. DESIGN TECHNIQUES

Design of the site has been done using the following technologies:-
 HTML
 JAVA NetBeans
 SQL YOG

6.1 HTML: HYPER TEXT MARKUP LANGUAGE

In computing, Hypertext Markup Language (HTML) is a markup language designed for

creation of web pages with hypertext and other information to be displayed in a web browser.
HTML is used to structure information denoting certain text as headings, paragraphs, lists and so
on and can be used to describe, to some degree, the appearance and semantics of a document.
HTML’s grammar structure is the HTML DTD that was created using SGML syntax.
The HTML document format is used on the Web. Web pages are built with HTML tags
(codes) embedded in the text. HTML defines the page layout, fonts and graphic element as well
as the hypertext links to other documents on the web. Each link contains the URL, or address, of
a Web page residing on the same server or any server worldwide, hence “World Wide Web”.
HTML 2.0 was defined by the Internet Engineering Task Force (IETF) with a basic set of
features, including interactive forms capability. Subsequent versions added more features such as
blinking text, custom backgrounds and tables of contents. However, each new version requires
agreement on the tags used, and browsers must be modified to implement those tags.
HTML is a markup language (the ML in HTML) that uses a fixed set of markup tags. A
markup language can also be thought of as a “Presentation Language”, but it is not a
programming language. You cannot “if this-do that” like you can in Java, Javascript or C++.
However, in order to make pages interactive, programming code can be embedded in an HTML
page. For example, Javascript is widely interspersed in Web pages (HTML pages) for that
purpose. HTML was conceived as a simple markup language to render research documents. No
one envisioned Web pages turning into multimedia extravaganzas. HTML pages have been
reworked, jury-rigged and extended into full-blown applications.
As a result, the source code behind today’s Web pages is often a hideous concoction of
tags and scripting.

6.2 JAVA

Java is an object-oriented programming language with a built-in application

programming interface (API) that can handle graphics and user interfaces and that can be used to
create applications or applets.

19
 We have used the following properties of Java:

 Variable Declaration: The types of all variables must be declared. The primitive types
are byte, short, int, long (8, 16, 32, and 64 bit integer variables,
respectively), float and double (32 and 64-bit floating point variables), boolean (true or
false), and char. Boolean is a distinct type rather than just another way of using integers.
Strings are not a primitive type, but are instances of the Stringclass. Because they are so
common, string literals may appear in quotes just as in other languages.
 Naming Conventions: Java distinguishes between upper and lower case variables. The
convention is to capitalize the first letter of a class name. If the class name consists of
several words, they are run together with successive words capitalized within the name
(instead of using underscores to separate the names). The name of the constructor is the
same as the name of the class. All keywords (words that are part of the language and
cannot be redefined) are written in lower case.
 Instance variables and methods can be accessed from any method within the class.
The x in the argument list of the above constructor refers to the local value of the
parameter which is set whenParticle is called. We use the this keyword to refer to those
variables defined for the entire class in contrast to those defined locally within a method
and those that are arguments to a method. In the above example, this.x refers to the
variable x which is defined just after the first line of the class definition
 Classes are effectively new programmer-defined types; each class defines data (fields)
and methods to manipulate the data. Fields in the class are template for the instance
variables that are created when objects are instantiated (created) from that class. A new
set of instance variables is created each time that an object is instantiated from the class.
 The members of a class (variables and methods) are accessed by referrring to an object
created from thr clas using the dot operator. For example, suppose that a
class Particle contains and instance variable x amd a method step. If an object of this
class is named p, then the instance variable in p would be accessed as p.x and the method
accessed as p.step.
 A semicolon is used to terminate individual statements.
 Comments. There are three comment styles in Java. A single line comment starts
with // and can be included anywhere in the program. Multiple line comments begin
with /* and end with */; these are also useful for commenting out a portion of the text on
a line. Finally, text enclosed within /** ... */ serves to generate documentation using
the javadoc command.

20
6.3 MySQL

Modern day web sites seem to be relying more and more on complex database systems.
These systems store all of their critical data, and allow for easy maintenance in some cases.

The Structured Query Language (SQL) is a very popular database language, and its
standardization makes it quite easy to store, update and access data. One of the most powerful
SQL servers out there is called MySQL and surprisingly enough, its free.

Some of the features of MySQL Include: Handles large databases, in the area of
50,000,000+ records. No memory leaks. Tested with a commercial memory leakage detector
(purify). A privilege and password system which is very flexible and secure, and which allows
host-based verification. Passwords are secure since all password traffic when connecting to a
server is encrypted.

21
7. TIER ARCHITECTURE.

The various classes as obtained from the business class diagram is categorized as
follows-

Form of the project Class Class

Application or Business Layer Data Layer or

Presentation or Logical Layer Data Access
Layer Layer

The 3 tier architecture consists of three layers:

Presentation Layer - The web site or windows forms application is called the
presentation layer. The presentation layer is the most important layer simply because it’s the one
that everyone sees and uses. Even with a well structured business and data layer, if the
presentation layer is designed poorly, this gives the users a poor view of the system.Presentation
layer is the form where we design using the controls like textbox, labels, command buttons etc.

Business Layer - Though a web site could talk to the data access layer directly, it usually
goes through another layer called the business layer.
This layer is a class which we use to write the function which works as a mediator to
transfer the data from Application or presentation layer data layer. In the three tier architecture
we never let the data access layer to interact with the presentation layer.

This layer is also a class where we declare the variable corresponding to the fields of the
database which can be required for the application and make the properties so that we can get or
set the data using these properties into the variables. These properties are public so that we can
access its values.

One of the best reasons for reusing logic is that applications that start off small usually
grow in functionality. For instance, a company begins to develop a web site, and as they realize
their business needs, they later decide to add a smart client application and windows service to
supplement the web site. The business layer helps move logic to a central layer for “maximum
reusability.”

Business layer have been presented having two roles

22
  client application
 server component

EXAMPLE OF BUSINESS LAYER-

The Business layer has functions of which takes the parameters from the example given
in the presentation layer .As the user inputs the data values, corresponding functions are called
in the business layer which are further passed on through the data layer where corresponding
procedures are called and the data is been updated.

Business layer is the class where we write the functions which get the data from the application
layer and passes through the data access layer.

Data layer - The key component to most applications is the data. The data has to be
served to the presentation layer somehow. The data layer is a separate component whose sole
purpose is to serve up the data from the database and return it to the caller. This layer is also a
class which we use to get or set the data to the database back and forth. This layer only interacts
with the database. We write the database queries or use stored procedures to access the data from
the database or to perform any operation to the database.

ADVANTAGE OF 3 TIER ARCHITECTURE

 Client-Server architecture is 2-Tier architecture because the client does not distinguish
between Presentation layer and business layer.
 The increasing demands on GUI controls caused difficulty to manage the mixture of
source code from GUI and Business Logic .
 Further, Client Server Architecture does not support enough the Change Management.
Let suppose that the government increases the Entertainment tax rate from 4% to 8 %,
then in the Client-Server case, we have to send an update to each clients and they must
update synchronously on a specific time otherwise we may store invalid or wrong
information.
 The Client-Server Architecture is also a burden to network traffic and resources. Let us
assume that about five hundred clients are working on a data server then we will have
five hundred ODBC connections and several ruffian record sets, which must be
transported from the server to the clients .
 This categorization of the application makes the function more reusable easily and it
becomes too easy to find the functions which have been written previously. If
programmer wants to make further update in the application then he easily can
understand the previous written code and can update easily.

DISADVANTAGES

23
 Increase complexity /effort
 More difficult to built 3 tier architecture rather then a 2 tier.
 Points of communication are doubled
 Maintenance tools are currently inadequate for maintaining server libraries.

24
8. SOFTWARE PROCESS MODEL

8.1 Why not Evolutionary models?

These models are best suited where requirements are fuzzy. These models are best suited
for the systems where requirements keep on changing. But for our system requirements are
crystal clear so it is not feasible to adopt any of the evolutionary models.

8.2 Why not Waterfall model?

Waterfall model can be adopted because in our case because requirements are known in
advance but there are some limitations of waterfall model due to which it is not feasible to adopt:

 No parallelism of work.

 Time consuming

8.3 Why Incremental RAD model?

Incremental model is advisable where requirements are clear and the development time is
less. The striking feature of incremental model is that each module can be completed and
released as and when requirement arises because of lack of time.

As in our system many of the modules are not inter-related so can be released in
isolation. The user can thus get a feel of these modules and give his feedback which can be
utilized for making the software more user friendly and in line with the user requirements.

Not only that the deadline set for this project is 3 months and we need a high
adaptation model and again will be concentrating on parallelism because our team will be
working on different module on same time. Moreover we will be using latest tools such as Visio,
Project Manager as a result of which we can work much faster. So looking into all these
requirements we find Incremental RAD model is best suited for our system because it enables
the development team to create a fully functional system within very short period of time.

8.4 Observation

25
 We have observed that our system that is Inventory Management and Costing would be
of immense help to the client as currently everything is done manually, which results in a lot of
time consumption, is error prone and also increases economic burden in the form of salaries paid
to the workers. Moreover such a manual system of managing inventory is quite unstructured. Our
system would be efficient, accurate and easy to use.

8.5 Determining Project Feasibility

The feasibility study is not a full-blown systems study. Rather, the feasibility study is
used to gather broad data to make a decision on whether to proceed with system study. System
project feasibility is assessed in three principal ways:

 Economically
 Technically
 Operationally
 Economical Feasibility

The organization has evaluated cost of software and hardware required for the system
including the storage of data. The benefits expected from the system are studied to assess the
reduced cost due to the new system.

Technical Feasibility:

Organization has shown willingness to purchase all hardware and software tools which
we recommend to successfully implement the system. Hence technically there are no limitations
for the development of the system. Thus the project is technically feasible.

Operational Feasibility:

Operational feasibility is dependent on the humans who will be using the software once
it’s ready and installed for use. The software will have a user friendly interface which will be
much convenient as compared to the current manual procedure. Thus the project is operationally
feasible

26
 9. DESIGN

9.1 BPMN

The Business Process Modeling Notation (BPMN) specification provides a graphical

notation for specifying business processes in a Business Process Diagram (BPD).

1. Login

Fig 1.1.1 BPMN Diagram for Login

27
 Planning And Maintenance
a) Maintenance

Fig 1.1.2 BPMN Diagram showing process Maintenance

b) Forecasting

Fig 1.1.3 BPMN Diagram showing process Forecasting

28
2. Stock Management

Fig 1.2 BPMN Diagram showing process Stock Management

29
3.Sales And Purchase

a)

Fig 1.3.1 BPMN Diagram showing process for Sales

b)

Fig 1.3.2 BPMN Diagram showing process for Purchase

30
4.Finance
a)

Fig 1.4.1 BPMN Diagram showing major process for Finance

31
b)

Fig 1.4.2 BPMN Diagram showing minor process for Finance

32
5. Human Resource

a)

Fig 1.5.1 BPMN Diagram showing major process for Human Resource

33
b)

Fig 1.5.2 BPMN Diagram showing minor process for Human Resource

34
9.2 Use Case Diagram

A use case is a description of how end-users will use a software code. It describes a task
or a series of tasks that users will accomplish using the software, and includes the responses of
the software to user actions.

1. Planning & Maintainance

a) Login

Fig 2.1.1 Use Case Diagram for Login Module

35
b)

Fig 2.1.2 Use Case Diagram for Maintenance Module

36
c)

Fig 2.1.3 Use Case Diagram for Forecasting Module

37
2. Stock Management

Fig 2.2 Use Case Diagram for Stock Management Module

38
3. Sales and Purchase

Fig 2.3 Use Case Diagram for Sales Module

39
4. Finance

a)

Fig 2.4 Use Case Diagram for Major Process of Finance Module

40
5. Human Resources

a)

Fig 2.5.1 Use Case Diagram for Major process of HR Module

41
b)

Fig 2.5.2 Use Case Diagram for Minor Process of HR Module

42
6.3 Class Diagram

In the Unified Modeling Language (UML), a class diagram is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their attributes,
and the relationships between the classes.

1. Login

Fig 3.1.1 Class Diagram for Login Module

43
Planning And Maintainance

Fig 3.1.2 Class Diagram for Planning and Maintenance

Module

44
2. Stock Management

Fig 3.2 Class Diagram of Stock Management

45
3. Sales And Purchase

Fig 3.3 Class Diagram for Sales and Purchase Module

46
4. Finance
a)

Fig 3.4.1 Accountant Class Diagram

47
b)

Fig3.4.2 Manager Class Diagram

48
5. Human Resource

Fig 3.5 Class Diagram for HR Module

49
9.4 Object Diagram

An object diagram in the Unified Modeling Language (UML), is a diagram that shows a
complete or partial view of the structure of a modeled system at a specific time.
An Object diagram focuses on some particular set of object instances and attributes, and
the links between the instances. A correlated set of object diagrams provides insight into how an
arbitrary view of a system is expected to evolve over time. Object diagrams are more concrete
than class diagrams, and are often used to provide examples, or act as test cases for the class
diagrams. Only those aspects of a model that are of current interest need be shown on an object
diagram.
1. Planning & Maintenance
a)Login

Fig 4.1.1 Object Diagram for Login Module

50
b)

Fig 4.1.2 Object Diagram for Planning Module

51
2. Sales and Purchase

a)

Fig 4.2.1 Object Diagram for Sales Module

52
b)

Fig 4.2.2 Object Diagram for Purchase Module

53
3. Finance

Fig 4.3 Object Diagram for Finance Module

54
4. Human Resource

Fig 4.4 Object Diagram for HR Module

55
9.5 Sequence Diagram :
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order. It is a construct of
a Message Sequence Chart.Sequence diagrams are sometimes called event diagrams, event
scenarios, and timing diagrams.

1. Planning and Maintenance

a)

Fig5.1.1 Sequence Diagram for Login

56
b)

Fig 5.1.2 Sequence Diagram for Planning and Maintenance

57
2. Sales and Purchase
a)

Fig5.2.1: Sequence Diagram for Sales

58
b)

Fig5.2.2: Sequence Diagram for Purchase

59
3. STOCK MANAGEMENT:
a)

Fig5.3.1: Place Order Sequence Diagram for stock management

60
b)

Fig5.3.2: Received Order Sequence Diagram for stock management

61
c)

Fig 5.3.3: Recycle Of Goods Sequence Diagram for stock management

62
4. Finance
a)

Fig5.4.1: Accountant SequenceDiagram

63
b)

Fig5.4.2: Manager Sequence Diagram

64
5. Human Resource

Fig 5.5 : Sequence Diagram for Human Resource

10. DATABASE

65
Account

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Account_No int(20) (NULL) NO PRI (NULL) select,insert,update,references

Account_Type varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Bank_Id varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

account 0 PRIMARY 1 Account_No A 0 (NULL) (NULL) BTREE

Bank

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Bank_Id varchar(20) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Bank_Name varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

Address varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

City varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

State varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Country varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

Email varchar(40) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes

66
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

bank 0 PRIMARY 1 Bank_Id A 0 (NULL) (NULL) BTREE

Bill_Details

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Bill_No int(20) (NULL) NO PRI (NULL) select,insert,update,references

Order_No varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Total_Amount float (NULL) NO (NULL) select,insert,update,references

Bill_Date date (NULL) YES (NULL) select,insert,update,references

CustId varchar(10) latin1_swedish_ci YES (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

bill_details 0 PRIMARY 1 Bill_No A 0 (NULL) (NULL) BTREE

Bill_Item

Fields
Field Type Collation Null Key Default Extra Privileges Comment

67
Bill_No int(20) (NULL) NO PRI (NULL) auto_increment select,insert,update,references

Product_Id varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Qty int(4) (NULL) NO (NULL) select,insert,update,references

Price float (NULL) NO (NULL) select,insert,update,references

Total_Amount float (NULL) NO (NULL) select,insert,update,references

Order_No varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

CustId varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Bill_Date date (NULL) NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

bill_item 0 PRIMARY 1 Bill_No A 5 (NULL) (NULL) BTREE

Cash_Book

Fields
Field Type Collation Null Key Default Extra Privileges Comment

cashbookid int(11) (NULL) NO PRI (NULL) auto_increment select,insert,update,references

Head varchar(20) latin1_swedish_ci YES (NULL) select,insert,update,references

Discount_Amt float (NULL) YES (NULL) select,insert,update,references

68
Cash_Amt float (NULL) YES (NULL) select,insert,update,references

Bank_Amt float (NULL) YES (NULL) select,insert,update,references

CB_Date date (NULL) YES (NULL) select,insert,update,references

Voucher_No varchar(20) latin1_swedish_ci YES MUL (NULL) select,insert,update,references

Type varchar(10) latin1_swedish_ci YES (NULL) select,insert,update,references

Contra int(4) (NULL) YES 0 select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

cashbook 0 PRIMARY 1 cashbookid A 4 (NULL) (NULL) BTREE

cashbook 1 FK_cashbook 1 Voucher_No A 4 (NULL) (NULL) YES BTREE

Challan_Header

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Challan_Header int(8) (NULL) NO PRI (NULL) select,insert,update,references

Sales_Order_No varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Challan_Date date (NULL) NO (NULL) select,insert,update,references

Billed_Y_N char(1) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

challan_header 0 PRIMARY 1 Challan_Header A 0 (NULL) (NULL) BTREE

69
City

Fields
Field Type Collation Null Key Default Extra Privileges Comment

City_Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes

Country

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Country_Name varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes

Customer

Fields
Field Type Collation Null Key Default Extra Privileges Comment

CustID varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Gender varchar(8) latin1_swedish_ci NO (NULL) select,insert,update,references

DOB date (NULL) NO (NULL) select,insert,update,references

Country varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

State varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

City varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

70
Address varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

ContactNo varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

Email varchar(40) latin1_swedish_ci NO (NULL) select,insert,update,references

Password varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

SecurityQuestion varchar(100) latin1_swedish_ci NO (NULL) select,insert,update,references

Answer varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

Confirmation_Mail varchar(20) latin1_swedish_ci NO NOT select,insert,update,references

SENT

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

customer 0 PRIMARY 1 CustID A 0 (NULL) (NULL) BTREE

Customer_Invoice

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Date date (NULL) NO (NULL) select,insert,update,references

CustID varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

71
Invoice_No varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Sales_Order_No varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Amount float (NULL) NO (NULL) select,insert,update,references

Discount float (NULL) NO (NULL) select,insert,update,references

Owing float (NULL) NO (NULL) select,insert,update,references

Posted tinyint(1) (NULL) NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

customer_invoice 0 PRIMARY 1 CustID A 0 (NULL) (NULL) BTREE

Customer_Master

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Customer_Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Address varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

Contact_No varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

Email varchar(40) latin1_swedish_ci NO (NULL) select,insert,update,references

Fax varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

City varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

State varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Nationality varchar(8) latin1_swedish_ci NO (NULL) select,insert,update,references

Balance_Due decimal(10,0) (NULL) NO (NULL) select,insert,update,references

72
Password varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

CustId varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Country varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

customer_master 0 PRIMARY 1 CustId A 0 (NULL) (NULL) BTREE

Daily_Attendence

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Emp_Id varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Present tinyint(1) (NULL) NO (NULL) select,insert,update,references

Late tinyint(1) (NULL) NO (NULL) select,insert,update,references

Date date (NULL) NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

daily_attendence 0 PRIMARY 1 Emp_Id A 0 (NULL) (NULL) BTREE

Dept_Master

73
Fields
Field Type Collation Null Key Default Extra Privileges Comment

Dept_Id varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Dept_Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Dept_Manager varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references refers emp_id

from
emp_master

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

dept_master 0 PRIMARY 1 Dept_Id A 0 (NULL) (NULL) BTREE

Emp_Personal_Master

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Emp_Id varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Emp_Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Gender varchar(8) latin1_swedish_ci NO (NULL) select,insert,update,references

DOB date (NULL) NO (NULL) select,insert,update,references

DOJ date (NULL) NO (NULL) select,insert,update,references

74
Role varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Address varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

Country varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

State varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

City varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Contact_No varchar(15) latin1_swedish_ci YES (NULL) select,insert,update,references

Email varchar(40) latin1_swedish_ci NO (NULL) select,insert,update,references

Password varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

emp_personal_master 0 PRIMARY 1 Emp_Id A 0 (NULL) (NULL) BTREE

Emp_Salary_Master

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Emp_Id varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Basic_Salary decimal(10,0) (NULL) NO (NULL) select,insert,update,references

HRA decimal(2,0) (NULL) NO (NULL) select,insert,update,references

TA decimal(2,0) (NULL) NO (NULL) select,insert,update,references

DA decimal(2,0) (NULL) NO (NULL) select,insert,update,references

Income_Tax float (NULL) NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment

75
 unique name in name part type
index

emp_salary_master 0 PRIMARY 1 Emp_Id A 0 (NULL) (NULL) BTREE

Employee_Personal_Details

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Emp_Id varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

First_name varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Last_name varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

gender varchar(8) latin1_swedish_ci NO (NULL) select,insert,update,references

DOB date (NULL) NO (NULL) select,insert,update,references

Address1 varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

Address2 varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

Country varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

State varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

City varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Contact_No varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

Email varchar(40) latin1_swedish_ci NO (NULL) select,insert,update,references

DOJ date (NULL) NO (NULL) select,insert,update,references

designation varchar(20) latin1_swedish_ci YES (NULL) select,insert,update,references

bloodgroup varchar(4) latin1_swedish_ci YES (NULL) select,insert,update,references

76
bankac int(20) (NULL) YES (NULL) select,insert,update,references

pancard varchar(15) latin1_swedish_ci YES (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

employee_personal_details 0 PRIMARY 1 Emp_Id A 0 (NULL) (NULL) BTREE

Head_Creation_Master

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Head varchar(20) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Head_Type varchar(30) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

77
head_creation_master 0 PRIMARY 1 Head A 2 (NULL) (NULL) BTREE

Journal

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Voucher_No varchar(20) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

J_Date date (NULL) NO (NULL) select,insert,update,references

Head varchar(20) latin1_swedish_ci NO MUL (NULL) select,insert,update,references

Dr_Amt decimal(6,2) (NULL) NO (NULL) select,insert,update,references

Cr_Amt decimal(6,2) (NULL) NO (NULL) select,insert,update,references

Description varchar(30) latin1_swedish_ci NO (NULL) select,insert,update,references

Type varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

journal 0 PRIMARY 1 Voucher_No A 0 (NULL) (NULL) BTREE

journal 1 FK_journal 1 Head A 0 (NULL) (NULL) BTREE

Foreign Key Relationships

FK Id Reference Table Source Column Target Column Extra Info

journal_ibfk_1 head_creation_master `Head` `Head`

Leave_Master

Fields
Field Type Collation Null Key Default Extra Privileges Comment

78
Emp_Id varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Cl_Available decimal(2,0) (NULL) NO 10 select,insert,update,references

Pl_Available decimal(2,0) (NULL) NO 20 select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

leave_master 0 PRIMARY 1 Emp_Id A 0 (NULL) (NULL) BTREE

Login_Info

Fields
Field Type Collation Null Key Default Extra Privileges Comment

LoginID varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Password varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Role varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

logininfo 0 PRIMARY 1 LoginID A 3 (NULL) (NULL) BTREE

Make_Payment

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Date date (NULL) NO (NULL) select,insert,update,references

Vendor_Id varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

79
MOP varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

Cheque_No int(20) (NULL) YES (NULL) select,insert,update,references

Bank_Name varchar(50) latin1_swedish_ci YES (NULL) select,insert,update,references

Amount float (NULL) NO (NULL) select,insert,update,references

Invoice_No varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes

Order_Receive

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Order_No varchar(20) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

CustId varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Order_Date date (NULL) NO (NULL) select,insert,update,references

Shipping_Address varchar(80) latin1_swedish_ci NO (NULL) select,insert,update,references

Product_No varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Quantity int(4) (NULL) NO (NULL) select,insert,update,references

Total_Amount float (NULL) NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

order_receive 0 PRIMARY 1 Order_No A 0 (NULL) (NULL) BTREE

Payment_Details

Fields

80
 Field Type Collation Null Key Default Extra Privileges Comment

Payment_Id varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Bill_No int(20) (NULL) NO (NULL) select,insert,update,references

To_Account varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

From_Account varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Amount float (NULL) NO (NULL) select,insert,update,references

Date date (NULL) NO (NULL) select,insert,update,references

Transaction_Id varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

Posted varchar(3) latin1_swedish_ci NO No select,insert,update,references

CustID varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

payment_details 0 PRIMARY 1 Payment_Id A 0 (NULL) (NULL) BTREE

Place_Order_Details

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Order_No varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references foriegn key

Product_Id varchar(20) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Product_Qty int(4) (NULL) NO (NULL) select,insert,update,references

Unit_price float (NULL) NO (NULL) select,insert,update,references

Description varchar(30) latin1_swedish_ci YES (NULL) select,insert,update,references

Indexes

81
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

place_order_details 0 PRIMARY 1 Product_Id A 1 (NULL) (NULL) BTREE

Product_Detail

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Product_Id varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Product_Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Product_Category varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Warehouse_Id varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references refes

warehouse
master

Shelf_No varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Date_In varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Manufacturing_Date date (NULL) NO (NULL) select,insert,update,references

Product_Qty int(4) (NULL) NO (NULL) select,insert,update,references

Warn_Qty int(4) (NULL) NO (NULL) select,insert,update,references

Ideal_Qty int(4) (NULL) NO (NULL) select,insert,update,references

Unit_Price float (NULL) NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

82
product_detail 0 PRIMARY 1 Product_Id A 6 (NULL) (NULL) BTREE

Purchase_Order_Inv

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Order_No varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Product_Id varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Qty int(4) (NULL) NO (NULL) select,insert,update,references

Price float (NULL) NO (NULL) select,insert,update,references

Total_Amount float (NULL) NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

purchase_order_inv 0 PRIMARY 1 Product_Id A 0 (NULL) (NULL) BTREE

83
Purchase_Order_Vender

Fields
Field Type Collation Null Key Default Extra Privileges Comment

POV_Id varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Order_Id varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Vender_Id varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

POV_Date date (NULL) NO (NULL) select,insert,update,references

Expected_Delivery_Date date (NULL) NO (NULL) select,insert,update,references

Actual_Reciving_Date date (NULL) NO (NULL) select,insert,update,references

Emp_Id varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

purchase_order_vender 0 PRIMARY 1 POV_Id A 0 (NULL) (NULL) BTREE

Receive_Order_List

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Order_No varchar(20) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Sales_Mgr_Id varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Receive_Date date (NULL) NO (NULL) select,insert,update,references

Date_Out date (NULL) NO (NULL) select,insert,update,references

84
Total_qty int(4) (NULL) NO (NULL) select,insert,update,references

Total_Amount float (NULL) YES (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

receive_order_list 0 PRIMARY 1 Order_No A 0 (NULL) (NULL) BTREE

Receive_Payment

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Date date (NULL) NO (NULL) select,insert,update,references

CustID varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

MOP varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

Cheque_No int(20) (NULL) YES (NULL) select,insert,update,references

Bank_Name varchar(50) latin1_swedish_ci YES (NULL) select,insert,update,references

Amount float (NULL) NO (NULL) select,insert,update,references

Invoice_No varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment

85
 unique name in name part type
index

receive_payment 0 PRIMARY 1 CustID A 0 (NULL) (NULL) BTREE

Recycle_Info

Fields
Field Type Collation Null Key Default Extra Privileges Comment

RecycleInfo_Id varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Product_Id varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Qty int(4) (NULL) NO (NULL) select,insert,update,references

Issue_Date date (NULL) NO (NULL) select,insert,update,references

ServiceProvider_Id varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Check&Date date (NULL) NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

recycleinfo 0 PRIMARY 1 RecycleInfo_Id A 0 (NULL) (NULL) BTREE

Salary_Details

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Emp_Id varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Salary_Paid decimal(10,0) (NULL) NO (NULL) select,insert,update,references

86
Date date (NULL) NO (NULL) select,insert,update,references

Indexes
Sales_Order_Detail

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Sales_Order_No varchar(20) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Order_Product_No varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Qty_Ordered decimal(25,0) (NULL) NO (NULL) select,insert,update,references

Qty_Dispatched decimal(20,0) (NULL) NO (NULL) select,insert,update,references

Product_Id varchar(10) latin1_swedish_ci YES MUL (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collatio Cardinalit Sub Packe Null Index Commen
uniqu name in name n y part d type t
e inde
x

sales_order_deta 0 PRIMARY 1 Sales_Order_N A 0 (NULL) (NULL) BTRE

il o E

sales_order_deta 1 FK_sales_order_deta 1 Product_Id A 0 (NULL) (NULL) YES BTRE

il il E

Service

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Service_Id varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

CustID varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Product_Id varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Problem_Description varchar(40) latin1_swedish_ci NO (NULL) select,insert,update,references

87
Solution varchar(40) latin1_swedish_ci NO (NULL) select,insert,update,references

Assign_To varchar(40) latin1_swedish_ci NO (NULL) select,insert,update,references

Expected_Delivery_Date date (NULL) NO (NULL) select,insert,update,references

Product_Status varchar(40) latin1_swedish_ci NO (NULL) select,insert,update,references

Charges float (NULL) NO (NULL) select,insert,update,references

Tax float (NULL) NO (NULL) select,insert,update,references

Total_Amount float (NULL) NO (NULL) select,insert,update,references

In_Date date (NULL) NO (NULL) select,insert,update,references

Out_Date date (NULL) NO (NULL) select,insert,update,references

Given_To varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

service 0 PRIMARY 1 Service_Id A 0 (NULL) (NULL) BTREE

Service_Provider

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Service_Id varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

mob varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

office varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

88
Email varchar(40) latin1_swedish_ci NO (NULL) select,insert,update,references

Address varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

city varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

state varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

country varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes

State

Fields
Field Type Collation Null Key Default Extra Privileges Comment

State_Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes

Stock_Details

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Product_Id varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Warehouse_Id varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

Shelf_No int(20) (NULL) NO (NULL) select,insert,update,references

Date_IN date (NULL) NO (NULL) select,insert,update,references

Date_OUT date (NULL) NO (NULL) select,insert,update,references

89
Manufactuing_Date date (NULL) NO (NULL) select,insert,update,references

Indexes

Training_Info

Fields
Field Type Collation Null Key Default Extra Privileges Comment

trainingID varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

StartDate date (NULL) NO (NULL) select,insert,update,references

EndDate date (NULL) NO (NULL) select,insert,update,references

trainingManager varchar(10) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes

Traning

Fields
Field Type Collation Null Key Default Extra Privileges Comment

traningID varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

traningName varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

duration int(4) (NULL) NO (NULL) select,insert,update,references

unsigned

description varchar(30) latin1_swedish_ci NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

traning 0 PRIMARY 1 traningID A 0 (NULL) (NULL) BTREE

90
 vendor_Details

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Supplier_ID varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Supplier_Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Address varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

Contact_No varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

Email varchar(40) latin1_swedish_ci NO (NULL) select,insert,update,references

Fax varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Nationality varchar(8) latin1_swedish_ci NO (NULL) select,insert,update,references

Bank_Account_No int(20) (NULL) NO (NULL) select,insert,update,references

Balance_Due decimal(20,0) (NULL) NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

vendor_details 0 PRIMARY 1 Supplier_ID A 0 (NULL) (NULL) BTREE

Vendor_Invoice

Fields
Field Type Collation Null Key Default Extra Privileges Comment

Date date (NULL) NO (NULL) select,insert,update,references

Vendor_Id varchar(10) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Invoice_No varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

91
Purchase_Order_No varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

Amount float (NULL) NO (NULL) select,insert,update,references

Paid float (NULL) NO (NULL) select,insert,update,references

Posted varchar(30) latin1_swedish_ci NO (NULL) select,insert,update,references

Discription varchar(30) latin1_swedish_ci NO (NULL) select,insert,update,references

Owing float (NULL) NO (NULL) select,insert,update,references

Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

vendor_invoice 0 PRIMARY 1 Vendor_Id A 0 (NULL) (NULL) BTREE

Warehouse_Description

Fields
Field Type Collation Null Key Default Extra Privileges Comment

warehouse_ID varchar(15) latin1_swedish_ci NO PRI (NULL) select,insert,update,references

warehouse_Name varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

country varchar(15) latin1_swedish_ci NO (NULL) select,insert,update,references

state varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

city varchar(20) latin1_swedish_ci NO (NULL) select,insert,update,references

address varchar(50) latin1_swedish_ci NO (NULL) select,insert,update,references

warehouse_Capacity int(11) (NULL) NO (NULL) select,insert,update,references

total_Qty int(4) (NULL) NO (NULL) select,insert,update,references

No_Of_Shelf int(4) (NULL) NO (NULL) select,insert,update,references

92
Indexes
Table Non Key Seq Column Collation Cardinality Sub Packed Null Index Comment
unique name in name part type
index

warehouse_description 0 PRIMARY 1 warehouse_ID A 1 (NULL) (NULL) BTREE

BIBLIOGRAPHY

 BPF 3.0 (Blue Print Foundry)

It is open source software which is helpful for designing the modules of software.
With the help of BPF we were able to design

 BPMN Diagrams
 UML Diagrams (use case, class, sequence, activity diagrams)

93