A REPORT ON SIMPLE PHARMACY MANAGEMENT SYSTEM

by

Satyam (0809110064) Shailesh Kumar(0809110066) Sudhanshu Kr. Verma (0809110072) Tarun Kumar(0809110079)

Department of COMPUTER SCIENCE & ENGINEERING

JSS ACADEMY OF TECHNICAL EDUCATION C-20/1, Sector- 62, Noida 201301(U.P.)

MAY, 2011

SIMPLE PHARMACY MANAGEMENT SYSTEM

by Satyam (0809110064) Shailesh Kumar(0809110066) Sudhanshu Kr. Verma(0809110072) Tarun Kumar(0809110079)

Submitted to the Department of COMPUTER SCIENCE & ENGINEERING in partial fulfillment of the requirements for the degree of Bachelor of Technology in COMPUTER SCIENCE

JSS ACADEMY OF TECHNICAL EDUCATION M.M. Technical University May, 2011

DECLARATION

We hereby declare that this submission is our own work and that, to the best of our knowledge and belief, it contains no material previously published or written by another person nor material which to a substantial extent has been accepted for the award of any other degree or diploma of the university or other institute of higher learning, except where due acknowledgment has been made in the text.

Signature: Name :Satyam Roll No.:0809110064 Date :02-May-2011

Signature : Name : Shailesh Kumar Roll No: 0809110066 Date : 02-May-2011

Signature: Name :Sudhanshu Kr. Verma Roll No.: 0809110072 Date :02-May-2011

Signature : Name : Tarun Kumar Roll No.: 0809110079 Date : 02-May-2011

CERTIFICATE

This is to certify that Project Report entitled SIMPLE PHARMACY MANAGEMENT SYSTEM which is submitted by Satyam, Shailesh Kumar, Sudhanshu Kr. Verma, Tarun Kumar in partial fulfillment of the requirement for the award of degree B. Tech. in Department of COMPUTER SCIENCE & ENGINEERING of U. P. Technical University, is a record of the candidate own work carried out by him under my/our supervision. The matter embodied in this thesis is original and has not been submitted for the award of any other degree.

Supervisors : Mr. Manoj Kumar & Miss Ankita Thakur

Date : 02-May-2011

ACKNOWLEDGEMENT
5

It gives us a great sense of pleasure to present the report of the B. Tech Project undertaken during B. Tech. Third Year(6th semester). We owe special debt of gratitude to Mr.Manoj Kumar & Miss Ankita Thakur Department of Computer Science & Engineering, JSS Academy of Technical Education, Noida for their constant support and guidance throughout the course of our work. There sincerity, thoroughness and perseverance have been a constant source of inspiration for us. It is only his cognizant efforts that our endeavors have seen light of the day. We also take the opportunity to acknowledge the contribution of Professor S. S. Prasad, Head, Department of Computer Science & Engineering, JSS Academy of Technical Education Noida for his full support and assistance during the development of the project. We also do not like to miss the opportunity to acknowledge the contribution of all faculty members of the department for their kind assistance and cooperation during the development of our project. Last but not the least, we acknowledge our friends for their contribution in the completion of the project.

Signature: Name : Satyam Roll No.:0809110064 Date : 02-May-2011

Signature : Name : Shailesh Kumar Roll No: 0809110066 Date : 02-May-2011

Signature: Name :Sudhanshu Kr. Verma Roll No.:0809110072 Date :02-May-2011

Signature : Name : Tarun Kumar Roll No. : 0809110079 Date : 02-May-2011

ABSTRACT
6

This document is intended to flush out the requirements by the customer of a Pharmacy Management Firm which will play an important role in a pharmacy management system. The customer can review this document to ensure their needs along with the needs of their users are being met in this program. The development team will also use this document for guidance on overall design and implementation of the Web Store system. The test and verification team can reference this to ensure the requirements are being meet for the customer. Finally, the tech writer will use this to assist with user documentation. This document is designed to be review from beginning to end. Earlier no system existed to cater to the needs of Secure Infrastructure Implementation System. The current system developed is technically feasible. It is a user interface for audit workflow at a Pharmacy Department of a hospital or for that fact this can also lead for a single Pharmacy Firm. Thus it provides an easy access to the users. The databases purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and security. The software and hard requirements for the development of this project are not many . The work for the project is done with the current equipment and existing software technology. Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number of users using the system. The conclusion which can be thought of as the development of a very apt and able software which can be used in any simple Pharmacy firm. The software as it intends to does the very simple work of calculating the amount of medicines stored in a pharmaceutical department And also does the total work of updating the same.

TABLE OF CONTENTS
DECLARATION ................................................................................................... CERTIFICATE ..................................................................................................... ACKNOWLEDGEMENTS .................................................................................. ABSTRACT ........................................................................................................... LIST OF FIGURES................................................................................................ CHAPTER 1-INTRODUCTION CHAPTER 2-SOFTWARE REQUIREMENTS SPECIFICATION............

Page

4 5 6 7 9 10 11

2.1 Product Perspective 2.1.1 System Interfaces 2.1.2 Interfaces 2.1.3 Hardware Interfaces 2.1.4 Software Interfaces 2.1.5 Communications Interfaces 2.1.6 Memory Constraints 2.1.7 Operations 2.1.8 Site Adaptation Requirements 2.2 Product Functions 2.3 User Characteristics 2.4 Constraints
2.5 Use Case Model 2.6 Sequence Diagram CHAPTER 3-SYSTEM DESIGN.......................................................... CHAPTER 4 IMPLEMENTATION AND RESULTS................................................

11 11 11 12 12 13 13 13 13 13 14
14 14-15 16 17-22 23-26

CHAPTER 5 CONCLUSIONS.26-27 REFERENCES... .................................................................................................... 27

LIST OF FIGURES
1. 2. 3. 4.

Page 12 15 16 17 18 19 20 22 23,24,25

External Interface Use-Case Diagram Sequence Diagram Architecture Diagram

5. Class Diagram 6. Data Flow Diagram 7. Activity Diagram 8. E-R Diagram 9. Interface Diagram

CHAPTER 1 INTRODUCTION
This system has been designed to manage the various medicines and drugs for a general purpose pharmacy(Medical Store) and to reduce the complexity of dealing with medicinal stock, various medicine records like their name, composition, pharmaceuticals name as well as the statistical records regarding their availability, prices including tax. Ordinarily what a medical store man does to manage his pharmacy? He keeps a register with himself adding, editing the medicine records into that. Is it always possible to remember all the drugs which he has to reorder as if they are in minimul stock condition? Although it could be but the computers are more better and reliable resource to handle with. A software makes these kind of management more easy. So this software has been designed to keep track of the medicinal information to deal with the pharmacy management complexity and saving of time to invest in some other directions to enhance the development of the pharmacy. Save of time pleases customers too, so they would be more greedy towards such an advanced pharmacy.

10

CHAPTER 2 Software Requirement Specification

2.1 Product Perspective

The product is based on the simple pharmacy management system and is totally independent and self contained . Detailed perspective of the product comes under the scope of following subsections . The following subsections also describe how the software operates inside various constraints.

2.1.1 System Interfaces

JDBC-ODBC Bridge connection is the only interface used to join the internal modules ( project software ) with external module Microsoft Access to utilize the database facility provided by Microsoft Corporation as well as reduced line of codes of project software.

2.1.2 Interfaces
The interface between the software and the user has the following characteristics: The interface consists of GUI interaction, it is a Graphical User Interface where the user can interact with the system.
The interface provides the platform for the user to do as directed from a visual menu

available to him from the screen. The visual interface will be as follows:

11

2.1.3 Hardware Interfaces

The system has no hardware interface requirements.

2.1.4 Software Interfaces

The software interface will consist of dealing with the required software tools which are: JDK 1.6 (Development Tool) Microsoft Access (Database) Windows(200/XP/Vista/7) (Operating System)
12

2.1.5 Communications Interfaces

None

2.1.6 Memory Constraints

There are no memory constraints.

2.1.7 Operations
The following initial operations should be performed by user before the task begins -: Click on the command prompt icon. Type java PMSSwing (name of the running module). Now user can begin his/her task.

2.1.8 Site Adaptation Requirements

None

2.2 Product Functions

This simple pharmacy management system software performs the tasks such as addition , deletion , editing and updation of the information regarding medicines name ,composition , price, stock quantity etc.

13

2.3 User Characteristics

User must have the basic knowledge of operating computer and experience of working in the windows environment.

2.4 Constraints

There are following constraints on the software which can be used -: Software has been built upon of jdk 1.6 Microsoft office 2007. Windows 2000 or XP or Vista.

2.5

Use case

Use case Model

The use case diagram for the Pharmacy Management System interface consists of the following features: The actors are : 1. The Employees 2. The Administrator The entity as the name of the software itself suggests is the medicines, the record of which will be kept by the software.

14

2.6 Sequence diagrams

The sequence diagram for the Pharmacy Management system is as follows:
15

Chapter 3 System Design

16

Architecture diagrams

Figure 3.1 2-Tier Architecture Diagram of Pharmacy Management System

17

Class diagrams

Figure 3.2 Class Diagram for Pharmacy Management System

18

3.1.

Data Flow Diagram

Figure 3.3 Data Flow Diagram For Pharmacy Management System

3.2.

Activity Diagram

19

Figure 3.4 Activity Diagram for Pharmacy Management System

20

ER Diagrams

21

22

CHAPTER 4 Implementation and Results 4.1. Software and Hardware Interfaces

It contains all the interfaces to be performed on data as follows:

Medicine To perform the updation on medicines. The range of the information to be added is fairly high. Accuracy measurements have been applied All measurements are in base units. Other inputs are related as they correspond to the same entity which is medicine. Screen formats/organization Window formats/organization

4.2.

Assumptions and dependencies

23

There are no such assumptions and constraints applicable on the piece of code.

4.3.

Constraints( if applicable)
None.

4.4. 4.4.1.

Implementation Details Snapshots Of The Implemented Interfaces (If

Applicable)

4.4.2.

Test Cases

The test cases used to test the software are in the figure:

24

4.4.3. Results The result of the project can be picturised as follows:

25

CHAPTER 5 Conclusion

5.1.

Performance Evaluation

The performance requirements are as follows: The system shall be able to handle 1000 medicines for storage. The system shall be able to retrieve the products per second. The system shall be able to add medicine to database in less than 2ms. The system shall be able to delete medicine to database in less than 2ms. The system shall be able to update medicine to database in less than 2ms.

26

5.2.

Comparison with existing State-of-the-Art Technologies

This work is in great accordance with all the softwares of this particular kind in the field as it ably performs the function of management of medicines in a Pharmacy System.

5.3.

Future Directions

The project has all the makings of a very good Pharmacy Management System and has all the scope of future improvement: The system shall utilize the data supplied. The system shall be easily updatable for fixes and patches. The system shall create logs of all changes, updates, or fixes that are done to the software. The system shall be easy to upgrade.

References
The references from the following sources have been taken: www.google.com www.wikipedia.com

K.K Aggarwal, Software Engineering. Pankaj Jalote, Software Engineering.

27