Mobile Store Managment

MOBILE STORE MANAGEMENT SYSTEM
1.INTRODUCTION
pg. 1
1. INTRODUCTION
The Mobile Store Management System is developed for desktop systems to facilitate
mobile shop owners’ management of customer details and inventory data, which will include
mobile phones and accessories. It can be used efficiently for physically separated shops in
different locations. This software will provide in a simple and easy to operate user interface,
which can be managed by any user without having prior in-depth knowledge of the computer
system. One can use this software to get a sales report. Administrators can pull data, from any
location from the server. This software is a complete package for small organizations which will
allow them to keep track of their sales and inventory, and provide a computerized billing
system. There are various applications with more complex implementation and features
available in the market, but they are generally very expensive. Therefore, creating an
application with the basic requirement of low cost is essential for small organizations. This
application will allow stores to manage customer details, keep inventory of all products and
purchase information, in a very simple way, using a state-of the-art software application. It will
automatically generate invoices and update inventory.
The rest of this document is organized into the following chapters:
• Chapter 2: Background- This chapter discusses the background of mobile store
management system and targeted market.
• Chapter 3: History, Relevant Literature and Survey- This chapter discusses the history of
mobile store management system. It also discusses different approaches for mobile
store management. At the end of chapter Survey results are included for the possible
use of the application by different businesses.
• Chapter 4: Requirements- This chapter describes different requirements for this
application.
• Chapter 5: Technology- This chapter provides an overview of the software and tools
used to develop this application.
• Chapter 6: Design & Implementation- This chapter discusses the design approach for the
database and application.
• Chapter 7: Source Code- This chapter contains the source code used in the application
• Chapter 8: Implementation and Testing- It includes the implementation method for this
application and the testing process.
• Chapter 9: Screen Shots- This chapter includes the pictures of the interface of the
application.
• Chapter 10: Future Work and Limitations. This chapter includes limitations of the
existing application and future scope.
• Chapter 11: Conclusion.
pg. 2
2.BACKGROUND
pg. 3
2. BACKGROUND
2.1 NEED FOR A MOBILE STORE MANAGEMENT SYSTEM
In today’s market, retailers and wholesale outlets should quickly adapt to the ever
changing technology to minimize overhead, lower cost of operation, and help to stay
competitive. Everybody needs software, which can facilitate store operations and make their
day-to-day lives much easier. Mobile Store Management System is application software
designed to take advantage of today’s technology and reduce or avoid the burden of storing
data on paper and in files. This facilitates moving purchase, sales, and customer information, as
well as supplier and company data, from paper to digital media on a secured server. Sales and
purchase bills can be generated as needed. Each store has an option to store their data on one
remote central database server. This will also allow stores to access information from other
partner stores. This would in turn lead to information sharing, so that all the stores are aware of
each other’s current inventory. It will be useful when ordering new purchases to avoid
overstocking.
2.2 BACKGROUND AND MOTIVATION

The concept of the Mobile Store Management system has been around for a long Time,
but it is still in the phase of discussion and design. Initially, all inventory and billing reports were
managed manually by shop owners/employers using ledger- based systems. This requires a
significant amount of time due to repeated access of the data. There is a high risk of lost or
stolen data in that system. Storing old data is also one big factor. Stores have to spare one
separate room to store this information. Paper- based documents might lose their information
with time, and after some years we can’t really read them at all. So the Mobile Store
Management System is designed to reduce paper- based data storage system and provide
digital touch to billing and inventory system.
2.3 MARKET
This software application is targeted for small and medium retail stores who want to
transform their paper- based inventory, sales, and procurement system to a computerbased
system. This is an inexpensive and easy-to-use software application for easy transition to digital
media. Also, this system is simple to install and maintain in PC/Laptops, thus avoiding huge
investments on enterprise or other types of servers. Currently, there is only one user for this
application, who will also be the administrator. The system administrator will have complete
access to the system configuration and data. The system administrator will also have access to
other partner stores. The benefits drawn from the system and low cost for installation and
maintenance come as a huge advantage. The possible retail shops are cell phone shops, The
Mobile Store Management System requires working network to communicate with mobile
location. This does add some cost to the application. To gain an advantage of managing
inventory from a mobile location, the store would have the expense of an internet service cost,
if they do not have already.
pg. 4
3. HISTORY, RELEVANT
LITERATURE AND
SURVEY
pg. 5
3. HISTORY, RELEVANT LITERATURE AND SURVEY
3.1 TRANSFORMATION FROM PAPER TO

COMPUTERBASED SYSTEM
A modern digital inventory management system must have the ability to keep track of
sales and inventory. It should also provide communication means to contact suppliers as
needed. It should also allow the incorporating shop owner’s ideas to be implemented into the
system. Implementing the idea of the previous section is practical for an inventory system, and
requires combining many technologies into one common approach. The time taken by a
customer care representative of any mobile store to enter information in the computer
represents a base of the modern Mobile Store Management System.
Merchants used to write down inventory and sales details. They had to search their
paper records to estimate future needs and retrieve old sales information. They had to spend
significant amount of time every day for such work.
After the Industrial Revolution, efficiency and accuracy became the major factors of
business, along with significant change in positive customer care to increase sales. A team at
Harvard University designed the first modern check-out system in the early 1930s. That system
needed punch cards associated with items details. A system would gather information from the
punch card and send it to stored data. As the system that was used by that time was too
expensive for general merchants, this was the first time a store management system was
transformed to a computerized system. Although it was very expensive, as computer systems
during that time were relatively new and too expensive, this new innovation opened new
dimensions to a store management system. Yet, the shop owners knew that they would need a
better management system, and then different ideas for management systems were
introduced, such as bar code scanner, RFID- based scanning systems. Merchants knew they
needed a better system, and researchers created the forerunner of the modern bar-coding
system in the late 1940s and early 1950s. Bar code Scanners used ultraviolet ink and a reader to
detect items at the time of sale. But this system also required a significant computer
contribution, which was also expensive. The development of affordable laser technology in the
1960s revived the concept, and lasers allowed smaller, faster and cheaper readers, or scanners.
The modern bar code, or the Universal Product Code (UPC), was born and caught on just before
the 1970S. The computers became cheaper and more affordable to support UPC codes and
manage inventory systems with a significant improvement.
During the mid to late 1990s, retailers began implementing modern inventory
management systems, made possible in large part by advances in computer and software
technology. The proper inventory management system ensures that customers would get all
their needs met, and merchants would get their profit at same time.
pg. 6
3.2 WHY COMPUTERIZATION IS REQUIRED?

Accuracy and efficiency are very important to be competitive in this ever-changing
market, given the advantages of technology. Computerization of any system will improve
efficiency and reduce the cost of operation. For every business, effective management of
inventory is one of the most important factors for success. Inventory management has
significance for any enterprise in an industry because effective practices in inventory
management will allow an enterprise to minimize inventory costs, and therefore avoid the dire
consequences that come with a shortage of resources.
Mantho (1994) classified inventory management into three broad areas:
1. Inventory record keeping: due to the availability of computers at a reasonable price, it is
appropriate to automate inventory records through computerization.
2. Inventory decision-making: many models can be integrated into computer-based
inventory systems.
3. Material requirement planning (MRP) system: MRP is an IM information system
concerned with getting the right materials to the right place at the right time. (This factor
is not applicable for Mobile Store Management System).
The use of formal practices for managing inventories was also inadequate. Poor inventory
management practices are characterized by the lack of an integrated approach in the form of the
absence of links between physical stock and accounting system. Lack of appreciation for
inventory management among the entrepreneurs and lack of qualified staff are the two major
factors contributing to low inventory management practices.
Considering the above factors, we can conclude that formal practices for
inventory management are not efficient and accurate. At same time, they consume a lot of time,
which lowers the performance of store keepers. Use of a computerized inventory system will
help small businesses to grow and make good benefits from their efforts.
3.3 SURVEY OF CURRENT INVENTORY SYSTEMS IN

STORES
A survey was undertaken to find out the existing inventory systems used in the stores by the
different merchants. Each of these stores is using different software based on their requirements.
Although there are several benefits, many small businesses don't track their inventory using software.
Some of the small businesses don't track their inventory manually at all. In a survey conducted by
"WAPS Barcode" company 23% of the customers had not used any kind of inventory tracking system.
30% turned to pen and paper based inventory tracking system and 32% are using excel or other general
purpose database to track their inventory. The complete survey chart can be seen in Figure with
different methods currently used by other small businesses. The above survey states that there are still
around 53% of small businesses can be transformed to the digital inventory system.
pg. 7
Many advanced stores use the software, which are modified as per their requirements, but
they still have not fully functional software as per
Figure 3.2. Survey of types of inventory system used by small businesses. Source:
WASP BARCODE TECHNOLOGIES, Taking stock of you inventory. Wasp Barcode Technologies,
http://www.waspbarcode.com/pdf/inventory_whitepaper.pdf, accessed October, 2012, August
2010.
Their needs. Some of the stores are not using any kind of software and used to keep inventory
manually, while some of the stores do not even track their inventory.
3.4 PROJECT NEEDS

The Mobile Store Management System is a software that can be integrated with
multiple stores' requirements with some customizations as per store type and needs. We do
not need to create new software for different businesses. Many stores surveyed either didn't
have a proper inventory management or they do not track their inventory at all due to high cost
of available software in market. The store would just need a decent internet connection to use
this software. Each store can track their inventory status in real-time with the use of this
software from remote location as well. The Mobile Store Management System is cost effective
and very easy to implement on computer system.
pg. 8
4. REQUIREMENTS
pg. 9
4. REQUIREMENTS
This project is targeted to help small companies to organize their inventory and billing
system in digital form. There are several categories of requirements associated with this
project.
4.1 TECHNOLOGICAL REQUIREMENTS

The technological requirements include the frontend programming tool and the
backend database system. The application should be easy to use, and it should be easily
managed by any person with little knowledge of computers. The database should be easy to
install and configure. At the same time, it should be portable and independent so that we can
use the database anywhere and install it on any laptop or PC. This application should be very
easy to install on any machine. Finally, this application should not require higher configuration
on any machine.
4.2 USER INTERFACE REQUIREMENTS

The application should be very simple and easy to use by any employee. Below are the
basic requirements of general user interface:
• The application shall be easy to use.
• The application shall take few inputs from user.
• The understanding time of the application shall be very small.
4.3 FUNCTIONAL REQUIREMENTS

The functional requirements of the application are as follows:
• The application shall have all required functionality which is necessary for mobile store
inventory and billing system management.
• The application shall have ability to print bills and invoices.
• The application shall have functionality to be used by different stores from one location.
• The application shall have user name and password protected security system.
pg. 10
5. TECHNOLOGY
pg. 11
5. TECHNOLOGY
Selecting technologies to develop any application is the very first step in order to
complete an application successfully. After considering various factors, I have decided to use
Visual Basic and SQL Server to develop Mobile Store Management System. Many low cost
projects employ Visual Basic to develop application and access database. However, SQL Server
is chosen as the technology for this project because of the needs to centralize data storage
when used by multiple stores. SQL Server Express is freely available from the Microsoft website.
5.1 VISUAL BASIC

VISUAL BASIC is a high level programming language evolved from the earlier DOS
version called BASIC. BASIC stands for Beginners' All-purpose Symbolic Instruction Code. The
program codes in Visual Basic resemble English language. VISUAL BASIC is a visual and events
driven Programming Language. These are the main divergences from the old BASIC. In BASIC,
programming is done in a text-based environment, and the Program is executed sequentially. In
VISUAL BASIC, programming is done in a graphical Environment.
Visual Basic is sometimes called Rapid Application Development (RAD) system because it
enables programmers to quickly build prototype applications.
Advantages of Visual Basic: The graphical user interface of the VB-IDE provides
intuitively appealing views for the management of the program structure in the large scale and
the various types of entities (classes, modules, procedures, forms).
Powerful Front-End Tool: Event driven concept equipped with advanced features of
object oriented programming along with user friendly IDE makes Visual Basic a powerful
programming and front-end tool. Visual Basic can accomplish simple to complex business
requirements in a very productive and efficient manner. It has wonderful chemistry with
multiple databases, including DBMS (Database Management System), like Microsoft Access,
RDBMS (Relational Database Management System), like Microsoft SQL Server and Sybase, and
ORDBMS (Object Relational Database Management System) like Oracle. It can also work with
Flat Text file and Microsoft Excel data files.
Standalone and Distributed Applications: You can create standalone as well as distributed
application with Visual Basic. Standalone refers to a program, which runs on your single
desktop, and your machine acts as both server and client. In distributed types, you can install
multiple copies of your program or work with single installation in COM+ environment on
corporate network.
pg. 12
5.2MICROSOFT OFFICE
Microsoft Access is a powerful program to create and manage your databases. It has many
built in features to assist you in constructing and viewing your information. Access is much more
involved and is a more genuine database application than other programs such as Microsoft Works.
The keywords involved in the process are: Database File, Table, Record, Field, Data-type. Here is the
Hierarchy that Microsoft Access uses in breaking down a database.
Database File: This is your main file that encompasses the entire database and that is saved to your hard-
drive or floppy disk.
Example: StudentDatabase.mdb
Table:A table is a collection of data about a specific topic. There can be multiple tables in a database.
Field: Fields are the different categories within a Table. Tables usually contain multiple fields.
Datatypes: Datatypes are the properties of each field. A field only has 1 datatype.
FieldName) Student LastName
Datatype) Text.
pg. 13
6.DESIGN
pg. 14
6.DESIGN
In this chapter we will discuss a variety of different diagrams such as data flow diagram,
activity diagram and entity-relationship diagram, which are relevant to the development phase
of this application. These diagrams explain this application flow and its logical construction very
well. These diagrams are part of background research during development phase. They helped
to develop connection between different modules of the application, which is very helpful for
any development.
6.1 E-R DIAGRAM

An Entity-Relationship Diagram (E-R Diagram) classically serves as the main deliverable for an
intangible data model. An E-R Diagram is logical exemplification data, and consists of three
chief components:
• Entity: It is a piece in the real world that is distinct from other objects.
• Attributes: It is an asset of an entity.
• Relationships: It is a linkage between two entities or attributes.
An E-R Diagram is important to demonstrate design of a database and used to plan database as
well.
pg. 15
6.2 DATA FLOW DIAGRAM

We can represent a system with graphical symbols showing data flow, data process, database,
and data sources in a Data Flow Diagram. Using this diagram, we can eliminate explaining this in
words and explain it in a graphical form instead.
pg. 16
7.SOURCE CODE
pg. 17
Login Form
Dim s1 As String
Dim s2 As String
Private Sub cmdexit_Click()
Unload Me
End Sub
Private Sub Form_Load()
Image3.Enabled = False
End Sub
Private Sub Label4_Click()
If txtusername = "" Or txtpassword = "" Then
MsgBox " please enter all details"
txtusername.SetFocus
Exit Sub
End If
s1 = txtusername.Text
s2 = txtpassword.Text
adologin.RecordSource = "select *from Login where username='" + s1 + "' and password='" + s2 + "'"
adologin.Refresh
If adologin.Recordset.RecordCount = 0 Then
Call Admin
Else
main.Visible = True
main.Image2.Visible = False
Exit Sub
End If
pg. 18
txtusername.Text = ""
txtpassword.Text = ""
End Sub
Public Sub Admin()
s1 = txtusername.Text
s2 = txtpassword.Text
Adodc2.RecordSource = "select *from Adminlogin where username='" + s1 + "' and password='" + s2 +

"'"
Adodc2.Refresh
If Adodc2.Recordset.RecordCount = 0 Then
MsgBox " invalid login"
Else
main.Visible = True
main.Image2.Visible = True
Exit Sub
End If
txtusername.Text = ""
txtpassword.Text = ""
End Sub
Main Form
Image1.Visible = True
Label4.Visible = False
End Sub
pg. 19
Private Sub Image2_Click()
emp_details.Show
End Sub
mob_service.Show
End Sub
mob_purchase.Show
End Sub
sim_card.Show
End Sub
Mob_Purchase Form
Private Sub add_Click()
addetails.Visible = True
End Sub
Private Sub Command2_Click()
Me.Hide
End Sub
Private Sub imgapple_Click()
apple.Visible = True
pg. 20
End Sub
Private Sub imghtc_Click()
htc.Visible = True
End Sub
Private Sub imgsamsung_Click()
samsung.Visible = True
End Sub
Private Sub imgsony_Click()
sony.Visible = True
End Sub
Private Sub microsoft_Click()
imgmicrosoft.Visible = True
End Sub
Apple Form
Me.Hide
End Sub
mobfeature.Label17.Caption = "IPHONE 4S"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\iphone\apple-iphone-4s.jpg")
mobfeature.Show
End Sub
pg. 21
mobfeature.Label17.Caption = "IPHONE 5C"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\iphone\apple-iphone-5c.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "IPHONE 5S"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\iphone\apple-iphone-5s.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "IPHONE 6"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\iphone\apple-iphone-6.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "IPHONE 6 PLUS"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\iphone\apple-iphone-6-plus.jpg")
mobfeature.Show
End Sub
pg. 22
Htc Form
Me.Hide
End Sub
mobfeature.Label17.Caption = "DESIRE 816 G"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\htc\htc-desire-816g-octa-core-
400x400-imaeyu35fbtfjtfp.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "hTC ONE M9"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\htc\htc-one-m9-m9-400x400-
imae74mbemgdn2kj.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "DESIRE 310"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\htc\htc-desire-310.jpg")
mobfeature.Show
End Sub
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\htc\htc-desire-326g-ds-na-
400x400-imae8aggdzgunugu.jpg")
mobfeature.Show
End Sub
pg. 23
mobfeature.Label17.Caption = "DESIRE 526 G"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\htc\htc-desire-526g.jpg")
mobfeature.Show
End Sub
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\htc\htc-desire-616-400x400-
imady3hpnn42dwzf.jpg")
mobfeature.Show
End Sub
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\htc\htc-desire-826-ds-na-
400x400-imae995edfpvesny.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "DESIRE X"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\htc\htc-desire-xds-400x400-
imadhskubsyanhem.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "hTC ONE E9+"
pg. 24
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\htc\htc-one-e9+.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "hTC ONE M8 EYE"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\htc\htc-one-m8-eye.jpg")
mobfeature.Show
End Sub
Microsoft Form
Me.Hide
End Sub
mobfeature.Label17.Caption = "LUMIA 430"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\microsoft\microsoft-lumia-
430.jpg")
mobfeature.Show
End Sub
532.jpg")
mobfeature.Show
End Sub
pg. 25
535.jpg")
mobfeature.Show
End Sub
540.jpg")
mobfeature.Show
End Sub
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\microsoft\microsoft-lumia-640-
xl.jpg")
mobfeature.Show
End Sub
Samsung Form
Frame1.Visible = True
Frame2.Visible = False
End Sub
Me.Hide
End Sub
pg. 26
End Sub
End Sub
mobfeature.Label17.Caption = "NOTE 3 NEO"
mobfeature.Image2.Picture =
LoadPicture("D:\mobile\MSM\database\Samsung\Samsung_Galaxy_Note3_Neo.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "GALAXY A8"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\Samsung\samsung-galaxy-
a8.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "GALAXY S6"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\Samsung\samsung-galaxy-
s6.jpg")
mobfeature.Show
End Sub
pg. 27
mobfeature.Label17.Caption = "NOTE 4"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\Samsung\galaxy note 4.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "GALAXY S6 EDGE"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\Samsung\Galaxy S6 Edge.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "GALAXY NOTE EDGE"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\Samsung\galaxy-note-edge.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "GALAXY S6 EDGE+"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\Samsung\galaxy-s6-edge+.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "OMNIA M"
LoadPicture("D:\mobile\MSM\database\Samsung\samsung_omnia_m.jpg")
pg. 28
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "GALAXY S5 MINI"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\Samsung\galaxy-s5-mini1.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "GALAXY J7"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\Samsung\samsung-galaxy-j7.jpg")
mobfeature.Show
End Sub
LoadPicture("D:\mobile\MSM\database\Samsung\samsung_galaxy_a5.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "GALAXY GRAND PRIME"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\Samsung\samsung-galaxy-grand-
prime-sm-g530h-1.jpg")
mobfeature.Show
End Sub
pg. 29
LoadPicture("D:\mobile\MSM\database\Samsung\Samsung_Galaxy_A3.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "GRAND 2"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\Samsung\galaxy grand 2.jpg")
mobfeature.Show
End Sub
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\Samsung\galaxy s4.jpg")
mobfeature.Show
End Sub
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\Samsung\galaxy s5.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "GALAXY E5"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\Samsung\galaxy e5.jpg")
mobfeature.Show
End Sub
pg. 30
Sony Form
Me.Hide
End Sub
mobfeature.Label17.Caption = "XPERIA M DUAL"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\sony\sony-xperia-m-dual.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "XPERIA M4 AQUA DUAL"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\sony\sony-xperia-m4-aqua-
dual.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "XPERIA C3"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\sony\sony-xperia-c3-400x400-
imadzdcxgzug6g8d.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "XPERIA C4"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\sony\sony-xperia-c4-dual-
sim.jpg")
pg. 31
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "XPERIA C5 ULTRA"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\sony\sony-xperia-c5-ultra-
dual.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "XPERIA E1 DUAL"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\sony\sony-xperia-e1-dual.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "XPERIA E4"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\sony\sony-xperia-e4.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "XPERIA Z3 COMPACT"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\sony\sony-xperia-z3-
compact.jpg")
mobfeature.Show
End Sub
pg. 32
mobfeature.Label17.Caption = "XPERIA Z ULTRA"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\sony\sony-xperia-z-ultra.jpg")
mobfeature.Show
End Sub
mobfeature.Label17.Caption = "XPERIA T2 ULTRA"
mobfeature.Image2.Picture = LoadPicture("D:\mobile\MSM\database\sony\sony-xperia-t2-ultra.jpg")
mobfeature.Show
End Sub
Mob_Service Form
Private Sub cmdadd_Click()
Adodc1.Refresh
Adodc1.Recordset.MoveLast
Adodc1.Recordset.addnew
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Label4.Caption = ""
Check1.Value = 0
Check2.Value = 0
Check3.Value = 0
Check4.Value = 0
Text1.SetFocus
cmdadd.Enabled = True
End Sub
pg. 33
Private Sub cmddel_Click()
Adodc1.Recordset.delete
End Sub
Private Sub cmdsave_Click()
Adodc1.Recordset("name") = Text1.Text
Adodc1.Recordset("contactno") = Text2.Text
Adodc1.Recordset("mobdetails") = Text3.Text
Adodc1.Recordset("received") = Text4.Text
Adodc1.Recordset("duedate") = Text5.Text
Dim strinfo As String
strinfo = ""
If Check1 = vbChecked Then strinfo = strinfo & "d" & ","
If Check2 = vbChecked Then strinfo = strinfo & "sk" & ","
If Check3 = vbChecked Then strinfo = strinfo & "s/w" & ","
If Check4 = vbChecked Then strinfo = strinfo & "misc" & ","
Adodc1.Recordset("problem") = strinfo
Adodc1.Recordset("amount") = Label4.Caption
Adodc1.Recordset.Update
DataGrid1.Refresh
cmdadd.Enabled = True
End Sub
Dim a As Integer
Dim b As Integer
Dim c As Integer
Dim d As Integer
pg. 34
Dim rs As Integer
a=0
b=0
c=0
d=0
If Check1.Value = 1 Then a = "999"
If Check2.Value = 1 Then b = "499"
If Check3.Value = 1 Then c = "599"
If Check4.Value = 1 Then d = "1899"
rs = a + b + c + d
Label4.Caption = rs
End Sub
Form1.Visible = True
Form1.DataGrid2.Visible = False
Form1.DataGrid1.Visible = True
End Sub
Form1.Visible = True
Form1.DataGrid1.Visible = False
Form1.DataGrid2.Visible = True
End Sub
Private Sub mnudetails_Click()
DataGrid1.Visible = True
End Sub
pg. 35
Private Sub mnuexit_Click()
main.Show
Unload Me
End Sub
Private Sub mnunew_Click()
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Label4.Caption = ""
Text1.Visible = True
Label4.Visible = True
Check1.Visible = True
pg. 36
Command1.Visible = True
cmdadd.Visible = True
cmdsave.Visible = True
DataGrid1.Visible = False
cmddel.Visible = True
End Sub
Private Sub print_bill_Click()
DataReport1.Show
End Sub
Private Sub Text2_keypress(keyascii As Integer)
If keyascii > 64 And keyascii < 123 And keyascii <> 8 Then
keyascii = 0
MsgBox "enter number only"
End If
End Sub
keyascii = 0
End If
End Sub
keyascii = 0
pg. 37
End If
End Sub
Mob_Feature Form
Private Sub cmdpurchase_Click()
bill.Show
bill.Text6.Text = Label18.Caption
bill.Text5.Text = Text3.Text
End Sub
Me.Hide
End Sub
Dim count As Integer
count = 0
Adodc1.Refresh
Adodc1.Recordset.MoveFirst
Do While Not Adodc1.Recordset.EOF
If Label17.Caption = Adodc1.Recordset("model") Then
Text1.Text = Adodc1.Recordset("brand")
Text2.Text = Adodc1.Recordset("modelid")
Text3.Text = Adodc1.Recordset("model")
Text4.Text = Adodc1.Recordset("touchscreen")
Text5.Text = Adodc1.Recordset("simtype")
Text6.Text = Adodc1.Recordset("simsize")
Text9.Text = Adodc1.Recordset("bluetooth")
Text10.Text = Adodc1.Recordset("threeG")
pg. 38
Text11.Text = Adodc1.Recordset("wifi")
Text12.Text = Adodc1.Recordset("usb")
Text13.Text = Adodc1.Recordset("tethering")
Text14.Text = Adodc1.Recordset("audiojack")
Text15.Text = Adodc1.Recordset("rear")
Text16.Text = Adodc1.Recordset("front")
Text7.Text = Adodc1.Recordset("videorec")
Text8.Text = Adodc1.Recordset("zoom")
Text17.Text = Adodc1.Recordset("other")
Text18.Text = Adodc1.Recordset("battType")
Text19.Text = Adodc1.Recordset("usermem")
Text20.Text = Adodc1.Recordset("expandable")
Text21.Text = Adodc1.Recordset("ram")
Text22.Text = Adodc1.Recordset("rom")
Label28.Caption = Adodc1.Recordset("photo")
Label18.Caption = Adodc1.Recordset("price")
count = MsgBox("view features")
If count = vbOK Then
Exit Sub
End If
Else
Adodc1.Recordset.MoveNext
End If
Loop
If count = 0 Then
MsgBox "out of stock"
End If
If count = 0 Then
Unload Me
pg. 39
End If
End Sub
Private Sub loadpic_Click()
Image2.Picture = LoadPicture(Label28.Caption)
End Sub
Sim_Card Form
Private Sub addnew_Click()
Text1.SetFocus
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
End Sub
Me.Hide
End Sub
Private Sub delete_Click()
End Sub
Private Sub exit_Click()
main.Show
pg. 40
Unload Me
End Sub
DataReport3.Show
End Sub
Private Sub save_Click()
Adodc1.Recordset("number") = Text1.Text
Adodc1.Recordset("cust_name") = Text2.Text
Adodc1.Recordset("cnct_num") = Text3.Text
Adodc1.Recordset("date") = Text4.Text
Adodc1.Recordset("Plan") = Text5.Text
Adodc1.Recordset("Adhaar no") = Text6.Text
End Sub
keyascii = 0
End If
End Sub
keyascii = 0
End If
End Sub
pg. 41
keyascii = 0
End If
End Sub
keyascii = 0
End If
End Sub
Emp_Details Form
Private Sub addnew_Click()
Text1.SetFocus
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
End Sub
Registration.Show
End Sub
pg. 42
Me.Hide
End Sub
End Sub
Adodc1.Recordset("empid") = Text1.Text
Adodc1.Recordset("empname") = Text2.Text
Adodc1.Recordset("phno") = Text3.Text
Adodc1.Recordset("salary") = Text4.Text
End Sub
keyascii = 0
End If
End Sub
keyascii = 0
End If
End Sub
pg. 43
keyascii = 0
End If
End Sub
Bill Form
Private Sub cmdadd_Click()
Adodc1.Refresh
Adodc1.Recordset.MoveLast
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
End Sub
Me.Hide
End Sub
End Sub
s1 = InputBox("enter customername")
pg. 44
Adodc1.RecordSource = "select * from bill where custname='" + s1 + "'"
Adodc1.Refresh
DataEnvironment1.Command2 Text2
DataReport2.Show
End Sub
Adodc1.Recordset("custname") = Text2.Text
Adodc1.Recordset("add") = Text3.Text
Adodc1.Recordset("ph_no") = Text4.Text
Adodc1.Recordset("model") = Text5.Text
Adodc1.Recordset("price") = Text6.Text
DataGrid1.Refresh
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
End Sub
keyascii = 0
End If
End Sub
keyascii = 0
pg. 45
End If
End Sub
Add_Mob Form
CommonDialog1.ShowSave
Image1.Picture = LoadPicture(CommonDialog1.FileName)
Adodc1.Refresh
End Sub
Me.Hide
mobile_purchase.Visible = True
End Sub
Adodc1.Recordset.Fields("brand") = Text1.Text
Adodc1.Recordset.Fields("modelid") = Text2.Text
Adodc1.Recordset.Fields("model") = Text3.Text
Adodc1.Recordset.Fields("touchscreen") = Text4.Text
Adodc1.Recordset.Fields("simtype") = Text5.Text
Adodc1.Recordset.Fields("simsize") = Text6.Text
Adodc1.Recordset.Fields("bluetooth") = Text9.Text
Adodc1.Recordset.Fields("wifi") = Text11.Text
Adodc1.Recordset.Fields("usb") = Text12.Text
Adodc1.Recordset.Fields("tethering") = Text13.Text
Adodc1.Recordset.Fields("audiojack") = Text14.Text
pg. 46
Adodc1.Recordset.Fields("rear") = Text15.Text
Adodc1.Recordset.Fields("front") = Text16.Text
Adodc1.Recordset.Fields("videorec") = Text7.Text
Adodc1.Recordset.Fields("zoom") = Text8.Text
Adodc1.Recordset.Fields("other") = Text17.Text
Adodc1.Recordset.Fields("usermem") = Text19.Text
Adodc1.Recordset.Fields("expandable") = Text20.Text
Adodc1.Recordset.Fields("rom") = Text22.Text
Adodc1.Recordset.Fields("ram") = Text21.Text
Adodc1.Recordset.Fields("threeG") = Text10.Text
Adodc1.Recordset.Fields("battType") = Text18.Text
Adodc1.Recordset.Fields("price") = Text23.Text
Adodc1.Recordset.Fields("photo") = CommonDialog1.FileName
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text9.Text = ""
Text11.Text = ""
Text12.Text = ""
Text13.Text = ""
Text14.Text = ""
Text15.Text = ""
Text16.Text = ""
Text7.Text = ""
Text8.Text = ""
pg. 47
Text17.Text = ""
Text19.Text = ""
Text20.Text = ""
Text10.Text = ""
Text18.Text = ""
Text23.Text = ""
Text22.Text = ""
Text21.Text = ""
End Sub
Aircel Form
sim_card.Text5.Text = aircel.Label3.Caption
sim_card.Show
End Sub
sim_card.Text5.Text = aircel.Label10.Caption
sim_card.Show
End Sub
Airtel Form
sim_card.Text5.Text = airtel.Label3.Caption
sim_card.Show
End Sub
pg. 48
sim_card.Text5.Text = airtel.Label10.Caption
sim_card.Show
End Sub
Idea Form
sim_card.Text5.Text = idea.Label7.Caption
sim_card.Text1.Text = Combo1.Text
sim_card.Show
End Sub
sim_card.Text5.Text = idea.Label9.Caption
sim_card.Show
End Sub
Jio Form
sim_card.Text5.Text = jio.Label7.Caption
sim_card.Show
End Sub
sim_card.Text5.Text = jio.Label9.Caption
sim_card.Show
End Sub
pg. 49
Tata Docomo Form

sim_card.Text5.Text = tatadocomo.Label3.Caption
sim_card.Show
End Sub
sim_card.Text5.Text = tatadocomo.Label10.Caption
sim_card.Show
End Sub
Vodafone Form
sim_card.Text5.Text = vodafone.Label3.Caption
sim_card.Text1.Text = vodafone.combo1.Text
sim_card.Show
End Sub
sim_card.Text5.Text = vodafone.Label10.Caption
sim_card.Show
End Sub
Welcome Form
Line2.X2 = 0
End Sub
pg. 50
Private Sub Timer1_Timer()
On Error Resume Next
If Timer1.Interval > 10 Then
Line2.X2 = Line2.X2 + 100
If Line2.X2 = 1000 Then
Label1.Caption = "Please wait..."
End If
End If
End If
End If
login.Show
Unload Me
End If
End If
End Sub
Sim_Offres Form
vodafone.Show
End Sub
pg. 51
idea.Show
End Sub
jio.Show
End Sub
airtel.Show
End Sub
tatadocomo.Show
End Sub
aircel.Show
End Sub
pg. 52
8. IMPLEMENTATION
AND TESTING
pg. 53
8. IMPLEMENTATION AND TESTING
Testing is a process of executing a program with the interest of finding an error. A good test is one
that has high probability of finding the yet undiscovered error. Testing should systematically
uncover different classes of errors in a minimum amount of time with a minimum amount of
efforts. Two classes of inputs are provided to test the process
1. A software configuration that includes a software requirement specification, a design
specification and source code.
2. A software configuration that includes a test plan and procedure, any testing tool and test
cases and their expected results.
Testing is divided into several distinct operations:
8.1. Unit Testing

Unit test comprises of a set tests performed by an individual program prior to the integration of
the unit into large system. A program unit is usually the smallest free functioning part of the whole system.
Module unit testing should be as exhaustive as possible to ensure that each representation handled by
each module has been tested. All the units that makeup the system must be tested independently to
ensure that they work as required. During unit testing some errors were raised and all of them were
rectified and handled well. The result was quiet satisfactory and it worked well.
8.2. Integration Testing

Integration testing is a system technique for constructing the program structure while at
the same time conducting tests to uncover errors associated with interfacing. The objective is to
take unit tested modules and build a program structure that has been dictated by design. Bottom-
up integration is the traditional strategy used to integrate the components of a software system
into functioning whole. Bottom-up integration consists of unit test followed by testing of the
entire system. A sub-system consists of several modules that communicated with other defined
interface.
The system was done the integration testing. All the modules were tested for their
compatibility with other modules .They test was almost successful. All the modules coexisted
very well, with almost no bugs. All the modules were encapsulated very well so as to not hamper
the execution of other modules.
pg. 54
8.3. Validation Testing

After validation testing, software is completely assembled as a package, interfacing errors
that have been uncovered and corrected and the final series of software test; the validation test
begins. Steps taken during software design and testing can greatly improve the probability of
Successful integration in the larger system. System testing is actually a series of different tests
whose primary purpose is to fully exercise the compute –based system.
8.4. Recovery Testing

It is a system that forces the software to fail in a variety of ways and verifies that the
recovery is properly performed.
8.5. Security Testing

It attempts to verify that protection mechanisms built into a system will in fact protect it
from improper penetration. The system’s security must of course be tested from in vulnerability
form frontal attack.
8.6. Stress Testing

Stress tools are designed to confront programs with abnormal situations. Stress testing
executes a system in a manner that demands resources in abnormal quantity and volume.
8.7. Black Box Testing

Black box testing is done to find out the following information as shown in below:
1. Incorrect or missing functions.
2. Interface errors.
3. Errors or database access.
4. Performance error.
5. Termination error.
The mentioned testing is carried out successfully for this application according to the user’s
requirement specification.
8.8. Test Data Output

After preparing test data, the system under study is tested using the test data. While
testing the system using test data, errors are again uncovered and corrected by using above
testing and corrections are also noted for future use.
pg. 55
9. SCREEN SHOTS
pg. 56
9.1USER INTERFACE
LOGIN FORM
MAIN FORM
pg. 57
MOBILE PURCHASE
FRMMICROSOFT FORM
pg. 58
FRMHTC FORM
FRMSAMSUNG FORM
pg. 59
FRMSONY FORM
pg. 60
FRMAPPLE FORM
MOBPURCHASE
pg. 61
BILL FORM
MOB_SERVICE FORM
pg. 62
SIMCARD FORM
pg. 63
EMPLOYEE DETAILS
9.2 DATABASE DESIGN

BILL
EMPLOYEE DETAILS
pg. 64
LOGIN
PHONE
MOBILE SERVICE
SIM CARD
pg. 65
9.3 DATA REPORT
SERVICE DETAILS
SIM CARD INFO
pg. 66
CUSTOMER/BILL DETAILS
pg. 67
10.FUTURE WORK AND

LIMITATION
pg. 68
10. FUTURE WORK AND LIMITATION

10.1 LIMITATION
The Mobile Store Management System has some flows and limitation due to different
requirements and time constrain. As this application will be used on the computers so the end
user must have the basic knowledge of the computers. Currently only one item’ information
can be enter in the system at a time. The user has to enter information for different items. The
system currently has only one combination of username and password credentials, every user
has to share same credentials. The search function only supports search using ID number. The
user has to get ID number of customer, sales, purchase, product, or supplier to search within
the system.
10.2 FUTURE EXPANSION
We can add multiple usernames and passwords with user- wise separate access and
authorities. We can implement search function using different information also. It is also
possible to integrate an employee’s time card and a payroll management system in this
application. There is another idea to implement SIM card management system. Using bar code
scanner and smart card reader, we can minimize manual data entry, which will potentially
decrease the amount of time to enter data. But at the same time it will increase the cost of this
application.
pg. 69
11.CONCLUSION
pg. 70
11. CONCLUSION
In this dissertation we have studied different management systems used during evaluation and
presented a low cost store management system application with the help of that study. A
survey was also conducted to get current needs of small businesses which could be willing to
migrate to the Mobile Store Management System application. The implementation of this
system as a single solution for different businesses was challenging. I have learned a lot about
document writing during this progression
The process of writing thesis document, which is a research paper, was not familiar to me, but
of great benefit. The application Mobile Store Management System is created to help small
businesses to transfer their records from paper-based system to computerized system, even
with a low budget. At the same time, the requirements of a basic store have been taken care
of, and a few features that can make the application easier to use and easy to understand to
the user with beginner level knowledge of computers have been added. I hope that Mobile
Store Management System fulfills all basic requirements for stores with intention of
transferring to computerized billing and inventory system. The survey of real world small
businesses helped me to understand current practice, and possible needs.
pg. 71
BIBILOGRAPHY
pg. 72

Mobile Store Managment

Uploaded by

Copyright:

Available Formats

Mobile Store Managment

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mobile Store Managment

Uploaded by

Copyright:

Available Formats

MOBILE STORE MANAGEMENT SYSTEM

2.2 BACKGROUND AND MOTIVATION

3. HISTORY, RELEVANT LITERATURE AND SURVEY

3.1 TRANSFORMATION FROM PAPER TO

3.2 WHY COMPUTERIZATION IS REQUIRED?

3.3 SURVEY OF CURRENT INVENTORY SYSTEMS IN

3.4 PROJECT NEEDS

4.1 TECHNOLOGICAL REQUIREMENTS

4.2 USER INTERFACE REQUIREMENTS

4.3 FUNCTIONAL REQUIREMENTS

5.1 VISUAL BASIC

FieldName) Student LastName

6.1 E-R DIAGRAM

6.2 DATA FLOW DIAGRAM

Private Sub cmdexit_Click()

Private Sub Form_Load()

Private Sub Label4_Click()

If txtusername = "" Or txtpassword = "" Then

MsgBox " please enter all details"

Public Sub Admin()

Adodc2.RecordSource = "select *from Adminlogin where username='" + s1 + "' and password='" + s2 +

MsgBox " invalid login"

Private Sub Image2_Click()

Private Sub Label2_Click()

Private Sub Label3_Click()

Private Sub Label4_Click()

Private Sub Command2_Click()

Private Sub imgapple_Click()

Private Sub imghtc_Click()

Private Sub imgsamsung_Click()

Private Sub imgsony_Click()

Private Sub microsoft_Click()

Private Sub Image2_Click()

mobfeature.Label17.Caption = "IPHONE 4S"

Private Sub Image3_Click()

mobfeature.Label17.Caption = "IPHONE 5C"

Private Sub Image4_Click()

mobfeature.Label17.Caption = "IPHONE 5S"

Private Sub Image5_Click()

mobfeature.Label17.Caption = "IPHONE 6"

Private Sub Image6_Click()

mobfeature.Label17.Caption = "IPHONE 6 PLUS"

Private Sub Image10_Click()

mobfeature.Label17.Caption = "DESIRE 816 G"

Private Sub Image11_Click()

mobfeature.Label17.Caption = "hTC ONE M9"

Private Sub Image2_Click()

mobfeature.Label17.Caption = "DESIRE 310"

Private Sub Image3_Click()

mobfeature.Label17.Caption = "DESIRE 326"

Private Sub Image4_Click()

mobfeature.Label17.Caption = "DESIRE 526 G"

Private Sub Image5_Click()

mobfeature.Label17.Caption = "DESIRE 616"

Private Sub Image6_Click()

mobfeature.Label17.Caption = "DESIRE 826"

Private Sub Image7_Click()

mobfeature.Label17.Caption = "DESIRE X"

Private Sub Image8_Click()