1

CHAPTER 1

INTRODUCTION

1.1 COMPANY PROFILE

Rapha Pharmacies was started in the year 2001 by 2 leading pharma distributors with the
objective of providing a world class pharmacy at the lowest possible price. Rapha has many
firsts to its credit:

• first pharmacy with spacious interiors where customers can come inside the
pharmacy and buy medicines.
• first pharmacy to air condition the pharmacy since most of the modern medicines
are to be stored below 25°.
• first to appoint full time pharmacists to man the pharmacies.
• first to introduce patient counseling.
• first to introduce own label prescription medicines at half the prize of the branded
medicines.

Rapha now has 50 branches in 17 cities with an annual turnover of more than
RS.130.00 crores. Rapha has more than 6 lakh regular customers.
The company believe in maintaining high ethical standards in business with a strong sense
of serving the community at large through various social service activities.

The Pharmacy have channelized more 2500 blood donations in the past 4 years
through Rapha blood donors association and also planted more than 3000 trees in various
places. The pharmacies have been continuously conducting medical and health awareness
camps.
The pharmacy also supports various organizations in conducting health, medical
camps.
 2

1.2 OBJECTIVE

The project “Textile Management System” is about the computerization of Textille

Shop. It is the complete Textile management software designed to ease the work load of
Textile shop professionals. If we want particular report according to the date wise, we can
view the particular report on the system.

The users of particular shop needs to login by entering user name and password. If the
user name and password are incorrect the system will not allow the person to access the
information.

Purchase details and customer details refer to the items which are currently
maintained. To maintain the purchase detail item code, supplier id, company name, and
product no, etc. If any information is incorrect then update function is used to correct it.
 3

CHAPTER 2

SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

The Textile Management System built using PHP and MySQL
comprises three main modules: Admin, Worker, and Supplier. The Admin
module serves as the central control point with functionalities such as login
authentication, managing workers (adding, editing, deleting), overseeing
worker attendance records, product management (adding, editing, deleting),
generating invoices, viewing bills, and updating passwords for security.
Workers are provided with specific credentials by the Admin to access the
system, enabling them to log in and record their attendance. They can also view
their attendance history within the system. Suppliers have their own module
where they can register, login, and manage their product listings. This includes
adding new products to their inventory and viewing existing ones. This system
streamlines various processes within a textile management environment,
enhancing efficiency in worker management, product tracking, and supplier
interactions. By centralizing these operations, it offers a comprehensive
solution for textile businesses to effectively manage their resources and
operations.

DRAWBACKS OF EXISTING SYSTEM

• The system is not centralized.
• Tedious to update new items in the database
• The system is not user friendly.

2.2 PROPOSED SYSTEM

The Admin module manages workers, monitors attendance, and handles product and billing
tasks. The Worker module allows staff to manage their attendance. The Supplier module
facilitates secure product management and procurement. This system enhances efficiency,
 4

transparency, and security, ultimately boosting productivity and profitability.

ADVANTAGES OF PROPOSED SYSTEM
• System is centralized.
• Keep record of daily customer
• Keep records of salesmen
• Manages counter sale
 5

CHAPTER 3

SYSTEM SPECIFICATION

3.1 HARDWARE REQUIREMENTS

Processor : Intel Pentium®4, 2.3 GHz.

RAM : 2 GB.

HDD : 50 GB.

CD-ROM Drive : 32 Hz

Monitor : 15 Inch Colour Monitor.

Keyboard : 108 Keys Standards.

Mouse : Optical Mouse.

3.2 SOFTWARE REQUIREMENTS

Operating System : Windows 7/8/10

Front End : HTML, CSS, JAVASCRIPT, BOOTSTRAP

Back End : MySQL

 6

CHAPTER 4

SOFTWARE SPECIFICATION

4.1 FRONT END

VB.NET
HTML (Hyper Text Markup Language) is the standard markup language used to create
the structure of web pages, consisting of elements like headings, paragraphs, links, and
images. CSS (Cascading Style Sheets) is used to style and layout these web pages, allowing
you to control the visual presentation through colors, fonts, spacing, and positioning.
JavaScript is a scripting language that adds interactivity and dynamic content to web pages,
enabling features such as responsive user interfaces, event handling, form validation, and
manipulation of HTML and CSS. Bootstrap, a popular front-end framework, simplifies web
development by providing a collection of pre-designed components like navigation bars,
buttons, forms, and grid systems, all built with HTML, CSS, and JavaScript. This
framework makes it easier to create responsive and mobile-first websites.

FEATURES OF VB.NET

• HTML (Hyper Text Markup Language) features elements such as headings,

paragraphs, links, images, lists, forms, and tables, which provide the basic structure
and content of web pages.
• CSS (Cascading Style Sheets) offers features like selectors, properties, and values that
enable precise control over the layout, color schemes, fonts, spacing, and overall
visual design of a website.
• JavaScript's features include variables, data types, operators, functions, loops, event
handling, and the Document Object Model (DOM) manipulation, allowing for
dynamic content, interactive elements, form validation, and responsive behaviors on
web pages.
• Bootstrap, a comprehensive front-end framework, includes a responsive grid system,
pre-designed components such as buttons, navbars, and modals, and utilities for
typography, forms, and spacing, all of which streamline the development of modern,
responsive, and mobile-first web applications.
 7

4.2 BACK END

SQL Server

A database management, or DBMS, gives the user access to their data and helps them
transform the data into information. Such database management systems include dBase,
paradox, IMS, SQL Server and SQL Server. These systems allow users to create, update
and extract information from their database.

A database is a structured collection of data. Data refers to the characteristics of

people, things and events. SQL Server stores each data item in its own fields. In SQL
Server, the fields relating to a particular person, thing or event are bundled together to form
a single complete unit of data, called a record (it can also be referred to as raw or an
occurrence). Each record is made up of a number of fields. No two fields in a record can
have the same field name.

During an SQL Server Database design project, the analysis of your business needs
identifies all the fields or attributes of interest. If your business needs change over time,
you define any additional fields or change the definition of existing fields.
 8

CHAPTER 5

PROJECT DESCRIPTION

5.1 PROBLEM DEFINITION

Computers and mobile phones have become essential part of organizational

information processing because of the power of technology and the volume of data to be
processed. As this is generating software it can be used by a wide variety of outlets (retailers
and wholesalers) to automate the process of manually maintain the records related to the
subject of maintaining the stock and cash flows. Hence the inception of computers had a
great role in reducing large tasks to simpler one.

5.2 OVERVIEW OF THE PROJECT

The project is about the computerization of “Textile Management System” to

automate the Textile shop management system. It is the complete medical shop management
software is so designed as to ease the work load of Textile shop professionals.

The main objectives are

• Speedier customer service
• Accurate and systematic maintenance of reports
• Easy accessing of data
• Checking and processing of reports are very easy
 9

5.3 MODULE DESCRIPTION

A module is defined as a collection of program statements with four basic attributes,

input and output function, mechanism and internal data. A module also has other attributes
it has a name by which can be referenced as a whole unit. Further a module can invoke by
other modules.

Module includes procedures, subroutines and function modularization allows the

designer to decompose a system into functional units in order to impose a hierarchical
ordering, implement data abstraction and develop independently useful subsystems. Formal
module interface definition may be especially helpful in organizing a bottom up design or a
two stage design first bottom up and then top down.

Admin Module:

• Login: This module allows the administrator to log in to the system

securely using their username and password.
• Manage Workers: Admin can add new workers, view existing workers,
update worker details, and delete workers if necessary.
• View Workers Attendance: Admin can view the attendance records of
all workers to track their punctuality and presence.
• Manage Products: Admin can add new products to the system, update
existing product details, and delete products if necessary.
• Make Invoice: This feature enables the admin to generate invoices for
products sold or services rendered to clients.
• View Bills: Admin can view the bills generated for products purchased
or services availed from suppliers.
• Update Password: Admin can update their login password for security
purposes.
 10

Worker Module:

• Login: Workers can log in to the system using the credentials provided
by the admin.
• Add & View Attendance: Workers can mark their attendance by logging
into the system. They can also view their own attendance records.
• Update password: Workers can update their password.

Supplier Module:

• Register: Suppliers can register themselves in the system by providing

necessary details like company name, contact information, etc.
• Login: Registered suppliers can log in to the system using their
credentials.
• Add & View Products: Suppliers can add new products they offer to the
system, along with details like product name, description, price, etc.
They can also view the products they have added.
 11

5.4 DATAFLOW DIAGRAM

Level 0
Worker

Textile Admin
Supplier
Management
System

FIGURE 5.1 DATAFLOW DIAGRAM LEVEL-0

Level 1

FIGURE 5.2 DATAFLOW DIAGRAM LEVEL-1

 12

Level 2

FIGURE 5.3 DATAFLOW DIAGRAM LEVEL-2

 13

5.5 ER Diagram

FIGURE 5.3 ER DIAGRAM

 14

5.6 DATABASE DESIGN

It is the process of producing a detailed data model of a database.

Table Name : Admin _Table
Primary Key : id
Description : This table contains information about the login table
Table 5.1 Admin _Table

Field Name Data Type Constriants Description

User_id varchar(20) Primary Key Userid
Password varchar(10) Not null Password

Table Name : Attendance _table

Primary Key : id
Description : This table contains information about the Attendance table

Field Name Data Type Constriants Description

Id Int (11) Primary key Id number

Worker _id Int (11) Not null Worker id

M date date Not null Date

Category Varchar (50) Not null Product name

In _time Varchar (50) Not null In time

Out _time Varchar (50) Not null Out time

Table 5.2 Attendance _Table

 15

Table Name : Invoice_table

Foreign Key : id
Description : This table contains information about the Invoice table

Field Name Data Type Constriants Description

In _id Int (11) Primary key Bill number

Product _id Int (11) Not null Item code

Quantity Int (11) Not null Total product

Varchar
Invoice _id Not null Invoice number
(50)

Table 5.3 Invoice _Table

Table Name : Products _table

Primary Key : Product_id
Description : This table contains information about the Products table

Field Name Data Type Constriants Description

Product _id varchar(10) Primary Key Product id

Name varchar(20) Not null product name

Price Int(11) Not null Product price

Brand varchar(60) Not null Product Brand

Category varchar(60) Not null Product category

Quantity Int(11) Not null Product total

Description text Not null About product

My _image varchar(80) Not null Product image

Table 5.4 Products_Table

 16

Table Name : Workers_Table

Primary Key : Id
Description : This table contains information about the Worker tables

Field Name Data Type Constraints Description

Id Int (10) Primary Key Id number

Name varchar(10) Not null Worker name

Email varchar(20) Not null Worker email

Worker phone
Phone varchar(20) Not null
number

Password number Not null Worker password

Worker_id number Not null Worker id

Table 5.5 Workers _Table

17
 18

CHAPTER 6

TESTING

Testing is vital to the success of the system. System testing makes a logical that if
all part of the system are correct, then the goal is successfully achieved. In the real sense it
is the phases which helps to bring out the creativity of the phases and makes it shine.

6.1 UNIT TESTING

Unit testing involves the design of test cases that validate that the internal program
logic is functioning properly, and that program input produces valid outputs.

All decision branches and internal code flow should be validated. It is the testing of
individual software units of the application .it is done after the completion of an individual
unit before integration. (Refer figure 9.1 and 9.2)

• Module Name : Admin

• Test Title : To check the username and password

6.2 INTEGRATION TESTING

Testing of integration modules to verify combined functionally after integration.

Modules are typically code modules, individual application.
(Refer to figure 9.3)
• Module Name : Sales Form
• Test Title : To check the database and display the billing page

6.3 VALIDATION TESTING

Validation testing is used to check the given username and password is correct and
whether the given data is correct and the process will be done .if the given data is incorrect
and the error message will be displayed.(Refer figure 9.1)

• Module Name : stock Return

• Test Title : To check the all field are entered or not.
 19

6.4 TEST CASE

Table 6.1 Test Case

Type of testing Input Sample Expected result Actual result Status

System should
validate the
User login username and
Username: System validates
using password are
kams and navigates to
Unit Testing username correct and Success
Password: home page as
and should navigates
kams expected.
password to the home
page.(Refer
figure9.1)

Without
enter
System should As expected
anything
validate the login system validates
on login Without
form and should the login form
Validate Testing form enter any Success
display the error and display the
screen user values
message.(Refer error message.
click on ok
figure9.1)
button

System should
validate the bill
number are
Bill Detail of the bill
Integration Billnumber: correct and
transaction should be Success
Testing 12 should navigates
form displayed.
to the bill detail
page.(Refer
figure9.3)
System should
display the error System validate
User login
Username: message stating as per the
using Success
kams that either conditions and
Unit Testing username
Password: username and display the error
and
k123 password is Message on the
password
wrong. same login page.
(Refer figure9.2)
 20

CHAPTER 7

SYSTEM IMPLEMENTATION

7.1 SYSTEM IMPLEMENTATION

• “Pharamacy Management System” Admin can login to home page through login
page.
• Admin can add the details of Purchase Details, Sales Details, supplier Details, Stock
Details and Customer Details.
• Admin can able to delete and modify the details of Purchase Details, Sales Details,
supplier Details, Stock Details and Customer Details.
• After saving the project, the build option is clicked to completely build the project,
once the build is completed, the .exe file is stored in the …\bin\debug folder which
can be copied and pasted in the client machine and thus deployment is made.
.
 21

CHAPTER 8

CONCLUSION AND FUTURE ENHANCEMENTS

8.1 CONCLUSION
The “PHARMACY MANAGEMENT SYSTEM” is successfully designed and
developed to fulfill the necessary requirements, as identified in the requirements analysis
phase, such as the system is very much user friendly.

The “PHARMACY MANAGEMENT SYSTEM” is found to be much faster and

reliable and user friendly than the existing system, the system has been designed and
developed step by step and tested successfully. The system has been tested for all possible
combination of inputs and results were found to be in accordance with the expected results.

8.2 FUTURE ENHANCEMENT

“PHARMACY MANAGEMENT SYSTEM” is developed in a flexible way such

that future enhancement can be made without affecting the present system functionality to
the maximum event. The system can be enhanced based on the customers requirement.
 22

CHAPTER 9

APPENDICES
9.1 Source Code

Admin Page

Public Class adminmain

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

As System.EventArgs) Handles StockDetailsToolStripMenuItem.Click
stockdet.Show()
End Sub

Private Sub OrderReportToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles PurchaseReportToolStripMenuItem.Click
purchaserep.Show()
End Sub

Private Sub SalesReportToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles SalesReportToolStripMenuItem.Click
salesrep.Show()
End Sub

Private Sub StockDetailToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles StockPurchaseToolStripMenuItem.Click
stkpurchase.Show()
End Sub

Private Sub BillTransactionToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles StockReturnToolStripMenuItem.Click
stkreturn.Show()
End Sub

Private Sub ChangePasswordToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles ChangePasswordToolStripMenuItem.Click
chngpass.Show()
End Sub

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

System.EventArgs) Handles ExitToolStripMenuItem1.Click
Dim ans As Integer
ans = MsgBox("Are you sure you want to exit this application?", vbYesNo + vbQuestion,
"Exit ")
If ans = MsgBoxResult.Yes Then
End
 23

Else
Exit Sub
End If

End Sub

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

As System.EventArgs) Handles AboutToolStripMenuItem.Click
AboutBox1.Show()
End Sub

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

System.EventArgs) Handles Timer1.Tick
Label1.ForeColor = System.Drawing.ColorTranslator.FromOle(RGB(Rnd() * 255,
Rnd() * 255, Rnd() * 255))
End Sub

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

System.EventArgs) Handles Timer2.Tick

End Sub

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

System.EventArgs) Handles MyBase.Load
MenuStrip1.Focus()
End Sub

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

System.EventArgs) Handles Button1.Click
Shell("calc.exe", AppWinStyle.NormalFocus)

End Sub

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

System.EventArgs) Handles Button2.Click
Shell("Notepad.exe", AppWinStyle.NormalFocus)
End Sub

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

System.EventArgs) Handles Button3.Click
billing.Show()
End Sub

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

System.EventArgs) Handles Button4.Click
stockdet.Show()
End Sub
 24

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

System.EventArgs) Handles Button5.Click
stkpurchase.Show()
End Sub

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

As System.EventArgs) Handles BillTransactionToolStripMenuItem.Click
billtnsdet.Show()
End Sub

Private Sub ReturnReportToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles StockReturnReportToolStripMenuItem.Click
stkreturnrep.Show()
End Sub

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

System.EventArgs)

End Sub

Private Sub ReturnDetailsToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles BillToolStripMenuItem.Click
billing.Show()
End Sub

Private Sub PurchaseDetailsToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles CustomerMedicineToolStripMenuItem.Click
custmed.Show()
End Sub

Private Sub CustomerReturnToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles StockReturnDetailToolStripMenuItem.Click
stkretdet.Show()
End Sub

Private Sub CustomerReturnReportToolStripMenuItem_Click(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles
CustomerMedicineReturnReportToolStripMenuItem.Click
custmedrep.Show()
End Sub

Private Sub DateTimePicker1_ValueChanged(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles DateTimePicker1.ValueChanged

End Sub

Private Sub CustomerReturnDetailsToolStripMenuItem_Click(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles
CustomerMedicineDetailsToolStripMenuItem.Click
custmeddet.show()
 25

End Sub

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

As System.EventArgs) Handles SupplierToolStripMenuItem.Click
supplier.Show()
End Sub

Private Sub SupplierDetailsToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles SupplierDetailsToolStripMenuItem.Click
supplierdetail.Show()
End Sub

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

System.EventArgs) Handles FileToolStripMenuItem.Click
End Sub

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

System.EventArgs) Handles ToolToolStripMenuItem.Click
End Sub

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

As System.EventArgs) Handles DetailToolStripMenuItem.Click

End Sub

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

System.EventArgs) Handles PictureBox1.Click

End Sub

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

System.EventArgs) Handles Label1.Click

End Sub
End Class
 26

Login Form

ImportsSystem.Data.SqlClient

PublicClasschngpass

PrivateSub Button1_Click(ByVal sender AsSystem.Object, ByVal e AsSystem.EventArgs)

Handles Button1.Click
Try
Dim con AsNewSqlConnection("Data Source=.\SqlExpress; Integrated Security=True;
AttachDbFilename=|DataDirectory|\stock.mdf; User Instance=true;")
DimunameAsString
DimpwdAsString
Dim da1 AsNewSqlDataAdapter
Dim ds1 AsNewDataSet
Dim cm AsNewSqlCommand

cm.Connection = con
cm.Connection.Open()
da1 = NewSqlDataAdapter("select * from login", con)
da1.Fill(ds1)

uname = Trim(ds1.Tables(0).Rows(0)(0))
pwd = Trim(ds1.Tables(0).Rows(0)(1))
If TextBox1.Text = ""Then
MsgBox("Enter Username")
TextBox1.Focus()
ElseIf TextBox2.Text = ""Then
MsgBox("Enter Your Old Password")
TextBox2.Focus()
ElseIf TextBox3.Text = ""Then
MsgBox("Enter Your New Password")
TextBox3.Focus()
ElseIfString.Compare(uname, TextBox1.Text) <> 0 Then
 27

MsgBox("Invalid Username")
TextBox1.Focus()
ElseIfString.Compare(pwd, TextBox2.Text) <> 0 Then
MsgBox("Invalid Old Password")
TextBox2.Focus()
Else
cm.CommandText = "Update login set name='"& TextBox1.Text &"',password='"&
TextBox3.Text &"'where name='"& TextBox1.Text &"'"
cm.ExecuteNonQuery()
MsgBox("Password Updated Successfully")
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox1.Focus()
EndIf

Catch ex AsException
MsgBox(ex.Message)
EndTry
EndSub

PrivateSub Button3_Click(ByVal sender AsSystem.Object, ByVal e AsSystem.EventArgs)

Handles Button3.Click
Me.Close()
EndSub
 28

9.2 Screen Shot

Description:This form is used to login the form.

Figure 9.1 Login Page

Description: This form is used to home page of the application.

Figure 9.2 Home Page

Description: This form is used to view bill transaction details.

 29

Figure 9.3 Bill Transaction

Description: This form is used to purchase new medicines from the company.

Figure 9.4 Stock Purchase

Description: This form is used to returning stocks.

 30

Figure 9.5 Stock Return

Description: This form is used to customer medicine details.

Figure 9.6 Sales bill

Description: This form is used to collect the supplier information.

 31

Figure 9.7 Supplier Information

Description: This form is used to show the remaining stock details.

Figure 9.8 Stock details

Description: This form is used to collect all the customer medicine details.
 32

Figure 9.9 Customer Medicine Details

Description: This form is used to view all supplier information.

Figure 9.10 Supplier Details

 33

CHAPTER 10

REFERENCES

Books Referred

1. Bill Evjen, Matt Gibbs, Dan Wahlin, Dave Reed, “Professional .NET”, Wrox
Publications, Second Edition ,2005
2. Brian Bischof,”The .NET Languages :A Quick Translation Guide”, Tata MC Graw
Hill Publications, Third Edition, 2007.
3. Gary Cornell, Jonathan Morrison, “Programming VB.NET: A Guide for
Experienced programmers” Second Edition, 2004.
4. Richard Fairley, “Software Engineering Concepts”, Tata MC Graw Hill
Publications, Second Edition, 1997.
5. Tom Barnaby, “Distributed .NET Programming in VB .NET”, Wrox Publications,
Fourth Edition, 2005.

Websites Referred

1. http://www.tutorialspoint.com/vb.net/vb.net_basic_syntax.htm
2. http://www.codeproject.com/Articles/488883/Zip-Rendering-Extension-for-SQL-
Server-Reporting-S
3. http://www.w3schools.com/sql/sql_syntax.asp

4. http://www.tutorialspoint.com/vb.net/vb.net_loops.htm