Contents

1. INTRODUCTION
1.1 Pharmacy Database Management System
1.2 Application
2. FUNCTIONAL REQUIREMENTS
2.1 Feasibility study
2.1.1 Functional requirements
2.1.2 Non- functional Requirements
2.2 System Analysis
2.3 Hardware Requirements
2.4 Software Requirement
3. ERD DATA FLOW DIAGRAMS AND
NORMILIZATION & TABLES.
3.1 ERD Diagram
3.2 Data-Flow-Diagram
3.2.1 Context DFD
3.2.2 First Level DFD
3.2.3 Second Level DFD
3.3 Tables
4. DATABASE DESIGN WITH FEW FORMS AND SQL
QUERIES & CODING
4.1 System design
4.2 Sql Queries and Coding.
5. ADVANTAGES, WEAKNESSES AND
IMPROVEMENTS OF THE SYSTEM
5.1 Advantages
5.2 Weaknesses
5.3 Improvement of the system
6. CONCLUSION AND FUTURE SCOPE
COMPLEX ENGINEERING PROBLEM

Chapter 1

INTRODUCTION
1.1 Pharmacy Database Management System
Introduction:
The main aim of the project is the management of the database of the pharmaceutical
shop. This is done by creating a database of the available medicines in the shop. The
database is then connected to the main program by using interconnection of the Visual
Basic program and the database already created.

1.2 Application:
This program can be used in any pharmaceutical shops having a database to maintain.
The software used can generate reports, as per the user’s requirements. The software
can print invoices, bills, receipts etc. It can also maintain the record of supplies sent in
by the supplier
 Chapter 2

FUNCTIONAL REQUIREMENTS
2.1 Feasibility Study
A feasibility analysis involves a detailed assessment of the need, value and
practicality of a proposed enterprise, such as systems development. The process of
designing and implementing record keeping systems has significant accountability
and resource implications for an organization. Feasibility analysis will help you make
informed and transparent decisions at crucial points during the developmental process
to determine whether it is operationally, economically and technically realistic to
proceed with a particular course of action.

2.1.1 Functional Requirements

 The system should be able to respond to searches by the medical personnel or

even other users of the system.
 The System should be able to summarize the reports to the administrators
about what is happening on daily basis or after every minute.
 Administrative Interface should allow for proper interpretation of data through
the use of graphs and reports.

2.1.2 Non-functional Requirements

 System must ensure right format is followed while interacting with the system
and only valid date should be sent to the system.
 The system should use more informative error messages to help the user
understand what to do next.
 For the administrative interface, only administrators can add or remove other
administrators but there should be at least one administrator of the system.
 The system should allow future expansion and modification.

2.2 System Analysis

It is the most creative and challenging phase of the system life cycle. The analysis
phase is used to design the logical model of the system whereas the design phase is
used to design the physical model.
Many things are to be done in this phase .we began the designing process by
identifying forms, reports and the other outputs the system will produce. Then the
specify data on each were pinpointed. we sketched the forms or say, the displays, as
expected to appear, on paper, so it serves as model for the project to began finally we
design the form on computer display, using one of the automated system design tool,
that is VISUAL BASIC 2016.
2.3 Hardware Requirements:

Hardware Minimum Specifications

Server - Random Access Memory(RAM): 512 MB or higher
- Processor Speed: 1.3 GHz and above
- Hard Disk Space: 10GB
- 1 year uptime
System Unit - Processor: Pentium III and above
- Memory: 512 MB of RAM or higher
- Hard Drive space-10 GB
Monitor display -1024 × 768 High color-16 bit Recommended

2.4 Software Requirements:

Software Specifications
Operating - Windows 7, Windows 2000, Windows NT, Windows XP and
System Windows Server 2005 Enterprise Edition
Database MySQL

Server Apache
 Chapter 3

ERD , DATAFLOW DIAGRAMS AND NORMILIZATION

OF THE DFD & TABLES
3.1 ERD DIAGRAM:

3.2 Data Flow Diagrams

A data flow diagram is a graphical representation or technique depicting information
flow and transform that are applied as data moved from input to output. The DFD are
partitioned into levels that represent increasing information flow and functional
details. The processes, data store, data flow, etc are described in Data Dictionary.

3.2.1 Context Diagram

Fig. 0th Level DFD

3.2.2 First Level DFD
 NORMILIZATION AND DATA FLOW DIAGRAMS

Fig. 1st Level DFD

In level one of the DFD the client select the mode of the action i.e. whether he wants
to buy a medicine or general store product. If he selects mode as medicine than the
flow of data will be as follows:
The process 2.0 i.e. medicine can enter the medicine information into the Database or
can retrieve the information from the Database. If the medicine has to soled, than the
sales process will check the stock whether the requested medicine is available or not,
this will be done by checking the availability of the medicine and the stock process
will reply by giving the status of the available stock.. If the requested medicine is
available than the client will pay the bill and the account process will generate the bill
for the purchased medicine.
If the medicine is purchased than, first the supplier’s information is retrieved from the
suppliers Database. After purchasing the bill amount of the purchased medicine is
paid by the account process and the stock Database is updated automatically after the
new medicines are purchased.
If the product is purchased than the information of the supplier from whom the
product is purchased is retrieved from the supplier process by the purchase process
and if the supplier is new than the supplier information is entered in the suppliers
database.
The Account process also keeps all the details of the stock.
3.2.3 Second Level DFD

Fig. 2nd Level DFD

Further in the second level DFD the process 5.0 i.e. sales process is elaborated.
In the sale process, after selecting the mode i.e. medicine or general store the further
operation is performed. The 5.1 process is the Medicine sale process in this process
the patient’s information can be retrieved from the patient Database. If the patient is
visiting for the first time than his information or detail is entered in the patient
database.
Similarly the Doctor’s information or detail is also entered in the Doctor Database,
who referred to the patient. If the patient is referred by the new Doctor than his
information can be entered in the doctor’s Database.
With the help of the medicine sales process the patient’s and Doctor’ information can
be entered or retrieved from the respective Database.

3.3 Required Tables:

Some important tables have vitial role:
 Chapter 4

DATABASE DESIGN WITH FEW FORMS AND SQL

QUERIES & CODING
4.1 System Design

Functionalities:

 Update (Only Admin can Update)

 Delete (Only Admin can Delete data)
 Insert (Admin and User both can insert Data)
 Create account (Admin and User Both can create account )

When the system loaded the below screen appears.

Admin adding the data of a new user for its account.

Fig. Main Screen

RESULTS:
1. Data (User Passward) Updating with respect to Name
2. From 031 to 0333
OUTPUT:

Following Changes Occurred in the Tables:

 Fig. Master Menu

The above screen displays the option available under the Master menu.
The options are:
 Purchase
 Item details
 Customer
 Update order
 Delete order
 Clear order
 Enter new Order

Updating the Data:

Fig. Updated Menu

The above screen displays the updated Data options under the given menu.
Following Changes Will occurred in the Tables:

Deleting The Account:

Fig. Deleted menu

The above screen displays the deleted Account.

Following changes will occurred in the tables:

Purchasing:
User enters the data of required purchasing in the required fields.
  Here we see the “RESERVATION” message which is successfully done. We can
also see the option of “ADD”. We can also Add more items , during our
purchasing.

Following changes occurred in the tables.

Deleting Stock Name Immad:

Following changes occurred in the table

Signing the Account:

  Now Signing In My account
 Note While Signing in we only write password

Now Buying PanadolExtra from (User) Immad account

  The following item is successfully ADDED.
 Here we can see ITEM CONFORMATION message.

Here we can the stock (Panadol) is removed from Admin stock Table, if we want to
delete.
Buying the item Again

 Now If we Buy again It will show!

4.2 SQL QUERIES AND CODING:

For Sign in and SignUp

private void Enter_Click(object sender, EventArgs e)

{
Form1 f1 = new Form1();

if (textBox2.Text == "Admin" && comboBox1.Text == "Admin" )

{
this.Hide();
Home home = new Home();
home.Show();
}

if ((textBox2.Text != "Admin" && comboBox1.Text == "Admin"))

{
MessageBox.Show("Sorry Invalid Passward");
}
if(comboBox1.Text == "User")
{
 SqlConnection cn = new SqlConnection(connectionstring);
cn.Open();
SqlCommand cmd = new SqlCommand("SELECT COUNT(Passward) FROM Accounts
where Passward=" + textBox2.Text.ToString() + "", cn);

int i = cmd.ExecuteNonQuery();
if (i != 0)
{
f1.Close();
UserHome home2 = new UserHome();
home2.Show();
}
else
{
MessageBox.Show("Sorry Account Not Found");
}
cn.Close();

}
}

For Creating an Account

private void Create_Click(object sender, EventArgs e)
{
SqlConnection cn = new SqlConnection(connectionstring);
cn.Open();
if (cn.State == System.Data.ConnectionState.Open)
{

SqlCommand cmd = new SqlCommand("INSERT INTO

Accounts(Name,Passward)VALUES('" + textBox1.Text.ToString() + "','" +
textBox3.Text.ToString() + "')", cn);
int i = cmd.ExecuteNonQuery();
if (i != 0)
{
textBox1.Text = textBox3.Text = "";

MessageBox.Show("Account is created");
}
else
{
MessageBox.Show("ERROR");
}
cn.Close();
}
}

For Deleting a purchased Data

private void Delete_Click(object sender, EventArgs e)

{
SqlConnection cn = new SqlConnection(connectionstring);
cn.Open();
SqlCommand cmd = new SqlCommand("DELETE From purchase where Name='" +
textBox1.Text.ToString() + "'", cn);

int i = cmd.ExecuteNonQuery();
if (i != 0)
 {
MessageBox.Show("DATA DELETED");
}
else
{
MessageBox.Show("ERROR");
}
cn.Close();
}

Code For Updating the Password with respect to Name of a User by Admin

private void Update_Click(object sender, EventArgs e)

{
SqlConnection cn = new SqlConnection(connectionstring);
cn.Open();
SqlCommand UpdateCommand = new SqlCommand("UPDATE Accounts SET Passward =
@Passward WHERE Name='" + textBox1.Text + "'", cn);
UpdateCommand.Parameters.Add("@Passward", SqlDbType.VarChar).Value =
textBox4.Text;

int i = UpdateCommand.ExecuteNonQuery();
if (i != 0)
{
MessageBox.Show("User Passward Updated");
}
else
{
MessageBox.Show("ERROR");
}
cn.Close();
}

Summery

Admin Add a stock of a drugs and set a price and other stuff. Admin Can update delete
and Insert a record any times he wants .User can Signup the Account for Buying Drugs
but User can only buy the drugs he can not do other Operations like Admin.
Multiple User can SignUp but There is Only One Admin.
 Chapter 5

ADVANTAGEES , WEAKNESSES AND IMPROVEMENET

OF THE SYSTEM
5.1 Advantages:

 Dispensing Workflow Management

 Updating the new stock
 Deleting the stock
 Less Expensive
 Easily understandable by the lay-man
 Usage-Based Ordering
 Prevent over-writing the stock
 Takes less Hard-disk Space
 Compatible for every Operating System
 Easily creating the new Account for New users
 Accounts Receivable
 Reporting
 Advanced searching
 User-customizable reporting

5.2 Weaknesses:

 It was realized that the current system does not allow the Admin to view previous
prescriptions pertaining made pertaining the disease thus prone to making
mistakes due to fatigue.
 The current system does not enable to record and store Customer’s information in
an organized way for easy retrieval.
 It was noted that prescriptions are given to patients who in the long run goes away
with them thus a challenge in retaining similar information for future reference.
 Retrieval of needed information by management was not enhanced in the current
system.
 There was no information sharing and dissemination by Admin in the current
system that will enhance easy identification of new symptoms and prescriptions

5.3 Proposed Improvements

 Admin and Customer’s be able to view the rate of common diseases and their
percentages.
 Management to be able to know the number of Customers has attended to within a
particular specified period of time thus making it easier for Admin to view and
know how much the currently working employes is supposed to be paid at the end
of the month.
 Chapter 6

CONCLUSION AND FUTURE SCOPE

Conclusion and Future Scope

 Detailed information gathering has to be done. Without that the purpose

for using the software wont be satisfied properly.
 However it can give good profits in the long run.
 Implementing the software requires change in the business practices.
 Efficient organization of all knowledge is the analysis company and easy
analysis access and retrieval of information is possible.
 In this project we can also include BAR CODE facility using the bar code
reader, which will detect the expiry date and the other information about the
related medicines.
 Company using this software will always be able to plan in future and
always be aware of their financial position in the market.
 It leads to streamling of business processes.
 The implementation and maintence costs run very high (about 2 to 3 % of
the company’s revenue