In this project, PHARMACY MANAGEMENT SYSTEM is systematic approach made towards maintaining purchase details, stock details, order

details, sales details, sales return details, payment details, buyer details, the record with low security maintained ids provide lots of problem. Hence we need of data to be better computerized. This Master module has of Buyer form, suppler form, product informations form; purchase form, stock form, sales form, sales return form, and payment detail form are also maintained within this. Purchase Form deal with purchase order of Medicine based on the stock. The level is increased when some purchase can be done and it can be monitored frequently by the stock. Stock Form deals with the details of the stock maintained in the stores. The system provide some message to indicate if the stock reach its level and tit is easy tom increase level of the stock. The system can increase its stock level when some purchase and sales return is done and its stock reduces level some sales done. Sales Details deals with sales order of medicine based on the stock, the level is decreased when some sales can be done and it can be monitored frequently by the stock level. The sales return details system can increase the stock level when some sales return. The reports are generating automatically. This is maintained and calculated accurately. The reports are displayed in neat formats. The Buyer, supplier, sales purchase sales, sales return, purchase return and stock will have a separate report.

1. INTRODUCTION TO THE PROJECT

Today management is one of the most essential features of all form. Management provides sophistication to perform any kind of task in a particular form. This is Visual-Basic Projects on Simple Pharmacy Management System, which provided a lot of facility to their user. The objective and scope of my Project Simple Pharmacy Management System is to record the details various activities of user. It will simplifies the task and reduce the paper work. During implementation every user will be given appropriate training to suit their specific needs. Specific support will also be provided at key points within the academic calendar. Training will be provided on a timely basis, and you will be trained as the new is Simple Pharmacy Management System rolled out to your area of responsibility. At the moment we are in the very early stages, so it is difficult to put a specific time on the training, but we will keep people informed as plans are developed. The system is very user friendly and it is anticipated that functions of the system will be easily accessed by administrators, academics, students and applicants. Hence the management system for the College management has been designed to remove all the deficiency from which the present system is suffering and to ensure. The client uses MS Access, and maintains their records, however it is not possible them to share the data from multiple system in multi user environment, there is lot of duplicate work, and chance of mistake. When the records are changed they need to update each and every excel file. There is no option to find and print previous saved records. There is no security; anybody can access any report and sensitive data, also no reports to summary report. This Simple Pharmacy Management System is used to overcome the entire problem which they are facing currently, and making complete atomization of manual system to computerized system.

1.1.

HARDWARE SPECIFICATION
Processor Name Speed Main Memory Cache Memory Hard Disk Keyboard Mouse Monitor : : : : : : : : Pentium Dual Core 2.664 GHz 512 MB 1024 KB 80 GB 110 Keys Optical Mouse 15 CRT Color Monitor

1.2.

SOFTWARE SPECIFICATION
: : : Visual Basic 6.0 MS Access 2000 Windows 2000 Professional

Front-End Back-End Operating System

SYSTEM STUDY

2.1.

EXISTING SYSTEM
System study plays an important role of software development life cycle

where the present system is studied and requirement for the proposed system are finalized. In existing system it has many problems, the major difficulties existing systems are tedious. Referring the sales details of day-to-day process and calculating the transaction is very tedious. It requires more time, cost consuming and the mistakes may occur. It is becomes a barrier of the bunk. It has low accuracy. The requirements are not fulfilled in correct time it yields more man power and maintenance cost is high in the fast moving world. While preparing reports, they have to refer an account of transaction book, this becomes a hard process.

2.2.

DRAWBACKS When the user uses ordinary system, it consumes more time. It needs more man power. Updating the Buyer details allocated section is not easy; hence it results in bad approaching manner of the bunk. It works slowly.

2.3.

PROPOSED SYSTEM
The proposed system has been developed to eliminate the above drawbacks.

The details of the members are stored in a database. Using these details, the daily transactions are updated and the management can view the details of the transaction tables, user balances are maintained and fuel rates can be changed in an appropriate way. To give a user friendly system. To reduce the processing time and large database can be easily maintained. Reduce errors and malpractices.

To increase growth and profit for the organization. Multiple companies with different financial year can be created. We can view report of past financial year. Backup and restore facility. Keep record of daily customers. Keep records of salesmen. Tracking sales done by a particular salesman. Manage counter sale. Keep track of instant collecting medicines from nearby medical shop and selling directly. Reminders for product low stock, product short expiry. Keeps track of all payment, receipt of company. Creating different users with different privilege level for providing high security. Handle financial accounting. Provides around 100 reports with maximum filtering option Better search option for finding available products of company Search can be filtered by product group, product, shelf, Manufacture etc.

FILE DESIGN:
System design phase is a transition from a user-oriented document to on the methods adopted for developing the system. Design part is the pivotal point in the system development life cycle. A dataflow-based approach, which is a structured design methodology, had been adopted. This approach begins with system specification that identifies inputs and outputs and describes the functional aspects of the system.

INPUT DESIGN:
Very careful attention had to be given to input design, which is a major part of the overall system design. In order to make the data entry as easy, logical and error free as possible, specific standards had been followed. Validation checks, provided in the system prevented the user in entering incorrect, erroneous data. This made sure that, only valid data had been available for data processing. If valid data was entered, then meaningful error messages had been prompted to enter correct data. The interactive screen formats facilitate the entry of valid data.

VALIDATIONS:
Some fields are having only number, as an I/P. For this key ASCII is checked. If they entered characters, it would display the message to enter number only. Exchange rates field will be validated for number and dot symbols. 3.2.2 INPUT DESIGN OBJECTIVES: The numbers of clear objectives of input design are, To produce a cost effective method of input To achieve the highest possible level of accuracy To ensure that the input is acceptable to and understand by the user staff

3.2.3 INPUT

TYPE:

External, which is the prime input for the system Internal, which is user communication with the system. Operational, which is the computer departments communication with the system. Computerized, which are inputs in the computer media coming from other internal systems. Interactive, which are inputs entered during a dialogue, with the computer.

3.2.4 THE NATURE OF INPUT PROCESSING: Flexibility and thoroughness of validation rules. Handling of priorities within the input procedures. Use of composite input documents to reduce the number odd ones Scheduling of input runs in case of large rejection rates at validation

3.3 OUTPUT DESIGN: Output, as you probably know, generally refers to the results and information that are generated by the system. For many end-users, output is the main reason for developing the system and the basis on which they will evaluate the usefulness of the application. Most end-users will not actually operate the information system or enter data through workstations, but they will use the output from the system. When designing output, systems analysts must accomplish the following. Determine what information to present Decide whether to display, print, or speak the information and select the output medium. Arrange the presentation of information in an acceptable format. Decide how to distribute the output to intended recipients. That alignment of information on a display or printed document is termed as layout.

Accomplishing the general activities listed above will require specific decisions, such as whether to use preprinted forms when preparing reports and documents, how many lines to plan on a printed page, or whether to use graphics and color. The output design is specified on layout performs, sheets that describe the location characteristics, and format of the column headings and pagination. As we indicated at the beginning of this discussion, these elements are analogous to an architects blue print that shows the location of the each component.

DATABASE DESIGN :
The general theme behind a database is to handle information as an integrated whole. A database is a collection of inter-related data stored with minimum redundancy to serve single users quickly and efficiently. The general objective is to make information necessary, quick, inexpensive and flexible for the user. Our database consists of employee details, reports to view the progress of the Assigned task, activity of the employee and also about the project details, login Information, Item Detail, Stock Detail, Staff Detail, etc. each table contains the related Fields to store the details of the given entity. In a database environment, through RDBMS is the software that provides the Interface between the data files on the disk and the program that request the data. Microsoft SQL Server 2000 is the RDBMS, which stores the table related to the proposed System.

MODULES :
Login User Administrator Purchase Sales Billing Stocks

3.5 DATAFLOW DIAGRAM DFD is a graphical tool used to describe and analyse the movement of data through a system-manual or automated the process, stores of data, and delays in the system. They are the central tool and the from which other components associated with the system. They are termed logical data flow diagrams. In contrast, physical data flow diagrams show the actual implementation and the movement of the data between people, departments and workstations.
3.7 SYMBOL: Data Flow

Processes

Source or Destination Data

Data store

3.8

MODULES

DESCRIPTION 3.8.1 USER LOGIN

Candidates who has not yet registered can register through this login with user id and password
USER LOGIN Password User Info

User User Information

Check for User Existence

Exit when Invalid 3.8.2 ADMINISTRATOR The administrators view the all reports and also make changes to Product and

add Product. Can add new employees and also add new clients.

ADMINISTRATOR Add New Item

Home Page

User (Administrator)

View New
itemdetl

Item Information

Add Staff

View Staff

View Emp-Detail

staff details

Logout

Report viewed by user

User User_Info Information Exit from User Information

3.8.3 PURCHASE It gives details about the purchase of product. The purchase details view shows all of the purchase item and also update the stock in the stock. PURCHASE
Add New Products Home
User

view Page

Purchase Item

Prod Detail

Back to user page

3.8.4 SALES It gives details about the sales of product. The sales details view shows the entire sales item and also update the stock in the stock. It gives the detail of customer. SALES

Store sales data Home Page view

Sales Item

Sales Detail

Back to user page

3.8.5 REPORTS It shows the report of all transaction for particular period.

REPORTS Request the purchase Details

Purchase Detl View the purchase Details Request sales Details View the sales Details Request stock Details View the stock. Details Stock Detl Sales Detl

CONCLUSION Hence the result of the Pharmacy Management are easily handled, Navigation through windows is possible, It is reliable, protected and highly secure, Report generation is easy, Security is provided. Hence the proposed system is complete automation. Thus Proposed System attempts to solve all the drawbacks of the existing system. The result that have achieved by this new system are User-friendly screens for data accessing and retrieving, Since the number of drawbacks evident in the existing system, an automated solution is proposed. The Proposed System aims to remove most of the drawbacks found extensively in the existing system. The PS is aimed to simply the complex and redundant process. The proposed system being developed as a replacement for the existing system is a graphical user interface with good interactions with the database. The proposed system has certain Modules .These are as below, Login User, Administrator, Purchase, Sales, Billing and Stock.

The Pharmacy management system really helps the user to add the transactions and is used to view the reports. The security of the database and each module is highly managed. The system provides different ways to retrieve any specific information required for different user. Obviously, the limitations of the existing systems are eliminated from the proposed system.

E-R DIAGRAM

Mid

Mnam e

Qty

Admin

Purchase Medicine
Mid Rid

tblPurchase

Sid

Mnam e

Qty

tblPurReturn

Update

tblSales

Sales

tblStock

Mid

Qty

Payment

tblSalesReturn

tblPayment

Sid

Rid

Date Bid Amt

3.2 DATABASE STRUCTURE

Pharmacy Management System is developed using Access as Back end with several tables such as Buyer Details, Supplier Details, Medicine Purchase Details, Stock Details, Medicine Sales Details, Return Details,etc.

Login Form
Field Name Username Password Data Type(Size) Varchar2(25) Varchar2(30)

Purchase Item
Field name record no Agencynm item type Item nm Entrydt Mfgdt Expdt Ppr Qty Total Data type(size) Number(5) Varchar2(30) Varchar2(20) Varchar2(30) Varchar2(10) Date Date Number(8,2) Number(5) Number(8,2)

 Sale Item
Field name record no Doctor Custnm Addr City Agencynm Item type Itemnm Entrydt Mfgdt Expdt Ppr Qty Total Data type(size) Number(5) Varchar2(30) Varchar2(30) Varchar2(55) Varchar2(25) Varchar2(30) Varchar2(30) Varchar2(30) Date date date Number(8,2) Number(5) Number(8,2)

 item detail
Field name record no Agencynm item name batch no Mfgdt Expdt Data type(size) Number(5) Varchar2(30) Varchar2(30) Varchar2(10) date date

Agency bill
Field name record no Billno Itemnm Mfgdt Expdt Qty Ppr Total Data type(size) Number(5) Number(5) Varchar2(30) Date Date Number(5) Number(8,2) Number(8,2)

 customer bill
Field name record no Billno Agencynm Doctornm Itemnm Mfgdt Expdt Qty Ppr Total Data type(size) Number(5) Number(5) Varchar2(30) Varchar2(30) Varchar2(30) Date Date Number(5) Number(8,2) Number(8,2)

 stock
Field name Agencynm Item type Itemnm Mfgdt Expdt Ppr Qty Data type(size) Varchar2(30) Varchar2(20) Varchar2(30) date date Number(8,2) Number(5)