1.

2 PROJECT OVERVIEW

Title of Project:

Electronic Shop Management System

Objective of the Project

Buy ‘N’ Save Inventories with a vision for the future decided to have all its
operations computerized. To start with they decided to take up the inventory first.

Project Category:

This is a project which can be placed in the category of RDBMS & OOPS.

1.3 Tools / Platform, Hardware & Software requirement

specifications
Platform – Windows 7
Front End – MS Visual Basic.Net
Back End – SQL Server 2005

Hardware Requirements:
Minimum Configuration:
Intel Dual Core Processor

2 GB RAM

10 GB HDD
Mouse

Keyboard
Monitor

Printer

IIS WEB SERVER (Internet Information Server 7.5)

Software Requirements:
Vb 6.0
SQL Server 2005
MS Windows 7
For the Front-End I intend to use Visual Basic and for the Backend SQL Server 2005
will be used.

1.4 Tools Information:

Overview of Visual Studio 2008 (As a Front-End Tool)

It is the fastest and easiest way to create applications for Microsoft

Windows. Whether you are an experienced professional or brand new to
Windows programming, Visual Basic provides you with a complete set of tools
to simplify rapid application development.

So what is Visual Basic? The "Visual" part refers to the method used to
create the graphical user interface (GUI). Rather than writing numerous lines
of code to describe the appearance and location of interface elements, you
simply add prebuilt objects into place on screen. If you've ever used a drawing
program such as Paint, you already have most of the skills necessary to
create an effective user interface.

The "Basic" part refers to the BASIC (Beginners All-Purpose Symbolic

Instruction Code) language, a language used by more programmers than any
other language in the history of computing. Visual Basic has evolved from the
original BASIC language and now contains several hundred statements,
functions, and keywords, many of which relate directly to the Windows GUI.
Beginners can create useful applications by learning just a few of the
keywords, yet the power of the language allows professionals to accomplish
anything that can be accomplished using any other Windows programming
language.
Whether your goal is to create a small utility for yourself or your work group, a
large enterprise-wide system, or even distributed applications spanning the
globe via the Internet, Visual Basic has the tools you need.

 Data access features allow you to create databases, front-end

applications, and scalable server-side components for most popular
database formats, including Microsoft SQL Server and other enterprise-
level databases.

 ActiveX technologies allow you to use the functionality provided by

other applications, such as Microsoft Word processor, Microsoft Excel
spreadsheet, and other Windows applications. You can even automate
applications and objects created using the Professional or Enterprise
editions of Visual Basic.
 Internet capabilities make it easy to provide access to documents and
applications across the Internet or intranet from within your application,
or to create Internet server applications.
 Your finished application is a true .exe file that uses a Visual Basic
Virtual Machine that you can freely distribute.

 Visual studio 2008 Editions

Visual Basic is available in three versions, each geared to meet a specific set
of development requirements.

 The Visual Basic Learning edition allows programmers to easily create

powerful applications for Microsoft Windows and Windows NT. It
includes all intrinsic controls, plus grid, tab, and data-bound controls.
  The Professional edition provides computer professionals with a full-
featured set of tools for developing solutions for others. It includes all
the features of the Learning edition, plus additional ActiveX controls,
the Internet Information Server Application Designer, integrated Visual
Database Tools and Data Environment, Active Data Objects, and the
Dynamic HTML Page Designer.
 The Enterprise edition allows professionals to create robust distributed
applications in a team setting. It includes all the features of the
Professional edition, plus Back Office tools such as SQL Server,
Microsoft Transaction Server, Internet Information Server, Visual
SourceSafe, SNA Server, and more.

1.5 Overview of MY SQL Server 2005 (As a Back-End

Tool)

Database Management System

A database management system is a software package
designed to store and manages databases.

SQL (Structured Query Language)

It allows users to access data in the relational database

management systems, such as Oracle, Sybase, Informix, Microsoft
SQL server, Access and others by allowing users to describe the
data the user wishes to see. Technically speaking, SQL is a data
sub language. That is to say, the purpose of SQL is to interface to a
relational database such as Oracle, and all SQL statements are
instructions to the database. Among the features of SQL are the
following:
 It processes sets of data as groups rather than individual units.
 It provides automatic navigation to the data.
  It uses statements that are complex and powerful individually,
and hence stand alone.
SQL provides commands for a variety of tasks including
 Querying data.
 Inserting, updating, and deleting rows in a table.
 Creating, replacing, altering, and dropping objects.
 Controlling access to the database and its objects.
 Guaranteeing database consistency and integrity.

SQL unifies all of the above tasks in one consistent language.

SQL is accepted as the protocol that enables databases build under
different DBMS and/or running on different machines architectures
to communicate, so forming true distributed systems.

Database Language

The database is an intermediate link between the physical

database, the computer and the operating system, and on the
other hand, the users. Different DBMS provide different database
languages although a language called SQL has recently taken on
the role of standard.

A language is needed to describe the database to the

DBMS as well as provide facilities for changing the database and
for defining and changing physical data structure. Another
language is needed for manipulating and retrieving data stored in
the DBMS. These languages are called Data Definition
Languages (DDL) and Data Manipulation Languages (DML)
respectively.

The storage structure and access methods used by the

database system are specified by a set of definitions called data
storage and definition language. DDL statements are compiled;
resulting in a set of tables stored in a special file called a data
dictionary or data directory, which contains metadata.
DML enables users to access and manipulate data. The
goal is to provide efficient human interaction with the system.
 Data manipulation is retrieving, inserting, deleting or modifying
information in the database.

It’s been a busy year for MySQL. Perhaps you've heard. Here
are some recent improvements to the speed, scalability, and user-
friendliness of the MySQL database and the InnoDB storage engine
that we think deserve their own headlines. Now is a great time to beta
test release and give feedback to the MySQL engineering team.

Improved Performance and Scalability

Database Becomes Default Storage Engine

MySQL sometimes gets knocked about features such as ACID-

compliant transactions, foreign key support, and crash recovery. These
features are strongest in the InnoDB storage engine, but MyISAM has
always been the default, so new users could get the wrong impression.
Starting in MySQL 5.5, InnoDB is the default storage engine, so that
everyone can see this reliability and stability out of the box. As a bonus,
the level of InnoDB in MySQL 5.5 is InnoDB 1.1, a architected InnoDB
with many performance and scalability features over and above the
built-in InnoDB in 5.1 and before. (Since we are unifying the InnoDB
within MySQL using the best and fastest technology, we are phasing
out the Plugin versus Built-In distinction; MySQL 5.5 comes with the
latest and greatest InnoDB 1.1.)

Better Metadata Locking within Transactions

If a table is referenced within a transaction, no other transaction can

perform DDL such as DROP TABLE or ALTER TABLE until the first
transaction commits. Previously, the lock was released at the end of a
statement rather than the whole transaction.
Improved Performance and Scale on Win32 and Win64

If your company uses Windows by itself or in a mixed environment, you

probably want to deploy MySQL databases on Windows. To make that
a reality, the MySQL team has incorporated a number of Windows-
specific features for speeding up and scaling up.

 Windows API calls for much of the I/O done inside MySQL (a
community contribution, hat tip to Jeremiah Gordy).
 Ability to build engines and other plugging as DLLs on Windows.
 Network support for auto-detecting the MAC addresses (a
community contribution, hat tip to Chris Runyan).
 Much clean-up and simplifying of threading code.

1.6 STRUCTURE OF THE PROGRAM

Analysis:

Electronic Store management system becoming an essential to efficiently

manage inventories in computer age.
Electronic Shop Management System is a workable application for retail store
inventory and accounts management. It keeps a list STOCKS and products at a store
and can do operations on them. The most important operation is a "PURCHASE", all
the transactions and billing details and stock purchasing details involved on it.

Why We Want to Hold Inventories

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

The software project is initiated by the client needs. In the beginning, these
needs are in the minds of various people in the client organization. The requirement
analyst has to identify the requirements by talking to these people and understanding
their needs. For such systems, the requirements problem is complicated by the fact
that the needs and requirements of the system many not to be known even to the user-
they have to be visualized and created. Hence, identifying requirements necessarily
involves specifying what some people have in their minds. When inputs from multiple
people are to be gathered, as is often the case, these inputs are likely to be inconsistent
as well.

2.1.1 Purpose:

This project is aimed at providing an economically feasible security and

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

2.1.2 Scope:

The project could be implemented in an average sized organization. An

average company will not be very keen on spending loads of money on ledgers.
Where as our project will greatly reduce the costs which is using common and cheap
office items like database and desktop application. And also there is no requirement to
store books or accounts. The data is directly stored in the database in the hard disk of
the PC.
2.1.3 Definitions, Acronyms, Abbreviations

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

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

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

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

 Update and delete products

This module will update and delete products.

 Update and delete customers

This module will be able to update and delete customers

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

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

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

 The needed requirements for this project has been obtained from the
stock by observing manual records and also gathered some of the
information by asking questions.

 Vb 6.0

2.1.5 Overview

Electronic Shop is a process of storing the products which is capable of

maintaining storage of large amount of products. The primary purpose of this
application is to implement the above stated functionality. The application should be
capable enough to store the products and also perform some updating on the products
that is stored. It will be having user friendly GUIs that will guide the user to easily
achieve the same. The application shall also have some features like reports
displaying in the same window. In addition to this the application also supports
feature to search products. It can also search products based on criteria so that the
employees will be able to view the same. The application is to be fully developed
under vb platform using Visual Basic 6.0

2.2 OVERALL DESCRIPTION

2.2.1 Product Perspective

The product will be developed completely independent and standalone. Each

user will have to have an individual copy of the product.
2.2.2 Product Functions

The product functions will include the following areas:

The application is capable enough to store different products and also perform
some editng on them that is added.It will be having user friendly GUI’s that will guide
the user to easily achive the same.
 AdminForm
 User Form
 Adding users
 Adding products
 Updating users
 Updating products
 Searching users and products
 Report generations

2.2.3 User Characteristics

The user of this product is supposed to be fairly educated about the usage of
the computers. He should understand how to store products and he should have
knowledge about various products so that they could be saved. A person who has no
knowledge of computers will find it difficult to understand the system. But with a
little knowledge it will be very easy to handle the project.

2.2.4 General Constraints

Designed to run on Windows xp and further versions.
2.2.5 Assumption and Dependencies
Assumptions:
 The code should be free with compilation errors/syntax errors.
 The product must have an interface which is simple enough to understand.

Dependencies:
 All necessary hardware and software are available for implementing and use
of the tool.
 The proposed system would be designed, developed and implemented based
on the software requirements specifications document.
 End users should have basic knowledge of computer and we also assure that
the users will be given software training documentation and reference
material.

2.3 SPECIFIC REQUIREMENTS

2.3.1 Functional Requirements

i. The application should be able to handle all the tasks in an efficient manner.
ii. The application should be able to provide up-to-date information.
iii. The application should be able to handle all the changes made.

2.3.2 External Interface Requirements

2.3.2.1 User Interfaces

The user interface is designed in Visual Basic.Net. The developer will have to
study the designing of the product. The use of the controls and the component from
the Add items feature of the Vb 6.0. The user of the product will get very user friendly
forms which will be very easy to work with.
2.3.3 Performance Requirements

The system is supposed to be having good memory space and a Bigger Ram
above 256 MB preferably. The sound card and graphics card will have to be of good
quality and capacity.

2.3.4 Design Constraints

Software Constraints:
Operating system Windows 7
Microsoft Visual Basic 6.0
SQL Server 2005

Hardware constraints:
Computer: INTEL compatible
256 MB RAM or higher
Pentium III
A CD Writer / Reader
A Color Monitor

2.3.5 Other Requirements

None
3.1 INTRODUCTION

The purpose of the Design Phase is to a solution of the problem

specified in the requirements document. This is the first step in moving from the
problem domain to the solution domain. The design of a system is perhaps the most
critical factor affecting the quality of the software; it has a major impact on the later
phases is the Design Document. This Document is similar to a blueprint or a plan for
the solution and is used later during implementation, testing and maintenance.

The Design activity is often divided into separate phases – System Design and
Detailed Design. System Design is sometimes also called Top-Level Design. This
system design aims to identify and modules that should be in the system, the
specifications of these modules, and how they interact with each other to produce the
desired result. At the end of the System Design all the major data structures, file
formats, and the major modules in the system and their specifications are decided.

3.2 APPLICABLE DOCUMENTS

The document used for preparing system design is software requirement

specification (SRS) for Inventory Management System.

3.3 FUNCTIONAL DECOMPOSITION

The main functional component of Inventory Management System is:

i) Admin
3.4 DESCRIPTION OF PROGRAMS

3.4.1 Context Flow Diagram (CFD)

A Context Flow Diagram is a top level (also known as level 0) data flow
diagram. It only contains one process node (process 0) that generalizes the function of
the entire system in relationship to external entities. In context diagram the entire
system is treated as a single process and all its inputs, outputs, sinks and sources are
identified and shown.

NOTATIONS USED IN FLOW DIAGRAM:

Bubble  The Bubble represents a process or transformation that is applied to the

data which changes in some way. Each bubble is assigned a number.

Box  The Box is called an entity which represents a producer or a customer of the
Information

Arrow  The Arrow represents the data flow. All arrows in the data flow diagram are
labeled. The arrowhead indicates the direction of data flow.

Parallel Lines  Represents a repository of data that is to be stored for use by one or
more processes.
CFD OF INVENTORY MANAGEMENT SYSTEM:

Administrator Customer Information

Report
Login
Update
Customer /
Products / User

Electronic
Shop Mgt
System
Customer /
Product /
Update Transaction

Purchase / Report Generation

Activities Transaction
3.4.2 Data Flow Diagram (DFD):

A Data Flow Diagram (DFD) is a graphical representation of the "flow" of

data through an Information System. A data flow diagram can also be used for the
visualization of Data Processing. It is common practice for a designer to draw a
context-level DFD first which shows the interaction between the system and outside
entities. This context-level DFD is then "exploded" to show more detail of the system
being modeled.

A DFD represents flow of data through a system. Data flow diagrams are
commonly used during problem analysis. It views a system as a function that
transforms the input into desired output. A DFD shows movement of data through the
different transformations or processes in the system.

Dataflow diagrams can be used to provide the end user with a physical idea of
where the data they input ultimately has an effect upon the structure of the whole
system from order to dispatch to restock how any system is developed can be
determined through a dataflow diagram. The appropriate register saved in database
and maintained by appropriate authorities.
 Data Flow Diagram Notation

Function

File/Database

Input/output

Flow
 Data Flow Diagram of the Inventory Management

Level 0:

Input Output
Admin/User
System Data Base

Level 1:

Admin/User

Login
Not Valid

Valid

Main Screen
Level 2:

Logged in
Admin Storekeeper

New
customr/prodcts
details DB

Customer
details

Sell to
Transactions customer/take
Of products from supplier

List of
Transactions DB
And customers

A B
 A B

Search
products
DB

Reports DB

Display

Logout
Level 3:

Login Admin

Add/View/
Update Delete the
DB
Items

Reporting

Pending
Report
Paid
Report
4.1 ER DIAGRAM

BuyAm
t PayAmt
Price
Purchase
ProductDes date
c

Name

Item Transaction
Code

1
Purchas
1
e

Customer

Confirm Has
Purchas Detail
e s
CID Add
N
Name
Has Product
Detail
s

Sino Bill Details

IName
PId
Unit
Price
UPrice Tota
Quantity
l
Pric
e
Amoun Quantity
t

Area State