DEPARTMENT OF COMPUTER SCIENCE

Dr.SNS RAJALAKSHMI COLLEGE OF ARTS AND SCIENCE

(AUTONOMOUS)

Re-accredited with “A” Grade by NAAC

(Affiliated to Bharathiyar University)

COIMBATORE-641 049

BONAFIDE CERTIFICATE

This is to certify that this project work entitled

(PHARMACY MANAGEMENT SYSTEM)

is the bonafide record of project work done by

JEEVITHA. K

(16BCS0116)

In partial fulfillment of the requirements for the award of the

Degree of Bachelor of Science in Computer Science

GUIDE HEAD OF THE DEPARTMENT

Submitted for viva-voce Examination held on_____________

INTERNAL EXAMINER EXTERNAL EXAMINER

DECLARATION
 DECLARATION
I hereby declare that this project work is entitled as “PHARMACY
MANAGEMENT SYSTEM” submitted to Dr.SNS Rajalakshmi College of
Arts and Science,Coimbatore is the record of the original work done by
myself under the guidance of Mr.B.MURUGESAN .MCA.,M.Phil., Assistant
professor in Department of Computer Science, Dr.SNS Rajalakshmi
College of Arts and Science, Coimbatore and this work has not formed the
basis for the award of any degree to any candidate in any university.

Signature of the student

JEEVITHA. K

(16BCS0116)

Date:

Place: Coimbatore
ACKNOWLEDGEMENT
 ACKNOWLEDGEMENT

I convey my sincere thanks to all people who have contributed a lot for the
successful completion of this project. I wish to convey my profound gratitude and
special thanks to our respected Chairman Dr.S.N.SUBRAMANIAN
M.Tech.,Ph.D.,MBA.,Ph.D., Dr.SNS Rajalakshmi College of Arts & Science,
Coimbatore for giving an opportunity to take up this project.

I warmly acknowledge my sincere and devoted thanks to our beloved Correspondent

CONTENT
 CONTENT

CHAPTER PAGE NO\

ACKNOWLEDGEMENT

SYNOPSIS

1.INTRODUCTION

1.1 Organization profile

1.2 Overview of the system

2. SYSTEM ANALYSIS

2.1 System specification

2.1.1 Software specification

2.1.2 Hardware specification

2.2 Application specification

3. SYSTEM DESIGNING

3.1 Input design

3.2 Output design

3.3 Database Design

4.TESTING METHODOLOGIES

4.1 Unit Testing

4.2 Integration Testing

5.IMPLEMENTATION

6.CONCLUSION

7.SCOPE OF FUTURE ENHANCEMENT

8.APPENDIX

A: Data flow diagram

B: E-R Diagram

C: Tables

D: Screen Shots

E: Report

F: Sample Code

9.BIBILIOGRAPHY
 SYNOPSIS

SYNOPSIS

The project entitled “PHARMACHY MANAGEMENT SYSYTEM” is exclusively

designed and developed to override the problem prevailing in the practicing manual system.
This Software is support to eliminate and in some cases reduce the hardships faced by the
existing system. More over this system is design for the particular need of the company to
carryout operations in a smooth and effective manner.

The Application is to reduce as much as possible to avoid errors while entering the data.it also
provided error message while entering the invalid data. No formal knowledge is need for the user
to use the system.
Thus by this all it is user friendly. Pharmacy management system as describe above, can let to
error free, secure, reliable and fast management system. It can assist the user to concentrate on
their activities rather to concentrate on the record keeping. Thus it will help organization in better
utilization of the resources
Every organization whether big or small has changes to overcomes and management going the
information of medicines, pharmacy, company sales, inventory. Every pharmacy management
has different needs, therefore we design accordingly. The project has been developed using
VB.Net as Front end and SQL Server as Back end Pharmachy Management is a sample System
uses to manage the farm daily undertakings in monitoring their inventory. With this system, it
can help farm to the speed-up transactions and supervised their products effectively. And for the
company Sale Quickly their Product. And for the Customer, to pay easily automatically. make
this program to improve their cashiering System.

Features:

For the Customer to pay easily automatically.

To compute the quantity or product of the company.

To help the company improve their cashiering system, therefore to overcome these
inconveniences the proposed system is developed. The information gathered from the above
organization are analyzed and grouped under following modules,

 LOGIN
 CUSTOMER DETAILS
 STOCK
 TRANSACTION
 VIEW CUSTOMER
 REPORTS
 1.INTRODUCTION

1.1 About the Project

The project entitled “PHARMACHY MANAGEMENT SYSYTEM” is exclusively

designed and developed to override the problem prevailing in the practicing manual system.
This Software is support to eliminate and in some cases reduce the hardships faced by the
existing system. More over this system is design for the particular need of the company to
carryout operations in a smooth and effective manner.

The Application is to reduce as much as possible to avoid errors while entering the data.it also
provided error message while entering the invalid data. No formal knowledge is need for the user
to use the system.
Thus by this all it is user friendly. Pharmacy management system as describe above, can let to
error free, secure, reliable and fast management system. It can assist the user to concentrate on
their activities rather to concentrate on the record keeping. Thus it will help organization in better
utilization of the resources
Every organization whether big or small has changes to overcome and management going the
information of medicines, pharmacy, company sales, inventory. Every pharmacy management
has different needs , therefore we design accordingly . The project has been developed using
VB.Net as Front end and SQL Server as Back end Pharmachy Management is a sample System
uses to manage the farm daily undertakings in monitoring their inventory. With this system, it
can help farm to the speed-up transactions and supervised their products effectively. And for the
company Sale Quickly their Product. And for the Customer, to pay easily automatically. make
this program to improve their cashiering System.

Features:

For the Customer to pay easily automatically.

To compute the quantity or product of the company.

To help the company improve their cashiering system., therefore to overcome these
inconveniences the proposed system is developed. The information gathered from the above
organization are analyzed and grouped under following modules,

 LOGIN
 CUSTOMER DETAILS
 STOCK
 TRANSACTION
 VIEW CUSTOMER
 REPORTS
2. SYSTEM SPECIFICATION
2.1 Hardware Specification

This project is developed using following hardware specification.

PROCESSOR : INTEL CORE I5 2.60 MHZ

HARD DISK CAPACITY : 250 GB

MONITOR : 14 “SAMTRON MONITOR

PRINTER : TVS 80 COLOR

INTERNAL MEMORY CAPACIT : 1 GB

KEYBOARD : LOGITECH OF 104 KEYS

MOUSE : LOGITECH MOUSE

2.2Software Specification

FRONT END : ASP.NET

BACK END : SQL SERVER

2.3 FRONT END
About VB.net

.Net supplies a standard security mechanism, available to all parts of your application. It provides
a possible solution to DLL Hell, and removes much of the complexity of dealing with com and the
registry. It allows you to run components locally, without requiring the calling applications to go to the
registry to find components. It allows you to create windows services natively for the first time by
providing windows service project type. It lets VB developers build truly free-threaded components and
applications for first time.

The .Net framework is a collection of services and classes. It exists as a layer between the
applications you write and the underlying operation system. This is a powerful concept. Its framework
moves to any operation system. It provides many features, like garbage collection for freeing up
resources, true inheritance for the first time, debugging that works across languages and against running
applications, and the ability to create windows services and console applications. VB.Net can be
debugged with the single debugger, even if one part of your application is written in VB.Net and calls
another part written or any other language built to target the .Net framework.

Microsoft .NET Framework is a computing platform for developing distributed applications for
the Internet. Following are the design goals of.NET Framework:

 To provide a very high degree of language interoperability

 To provide a runtime environment that completely manages code execution

 To provide a very simple software deployment and versioning model

 To provide high-level code security through code access security and strong type
checking
 To provide a consistent object-oriented programming model

 To simplify Web application development

Inheritance

Visual Basic .Net supports inheritance by allowing you to define classes that serve as the basis for
derived classes. Derived classes inherit and can extend the properties and methods of the base class.
They can also override inherited methods with new implementation. All classes created with Visual Basic
.NET are inheritable by default. Because the forms are really classes, user can use inheritance to define
new forms based on existing one.

Exception Handling

Visual Basic .Net supports structured exception handling, using an enhanced version of the
Try…Catch…Finally syntax supported by other languages such as C++. Structured exception handling
combines a modern control structure (Similar to Select Case or While) with exceptions, protected blocks
of code, and filters. Structured exception handling makes it easy to create and maintain programs with
robust comprehensive error handlers.
Overloading

Overloading is the ability to define properties, methods or procedures that have the same name
but use different data types. Overloaded procedures allow you to provide as many implementations as
necessary to handle different kinds of data, while giving the appearance of a single, versatile procedure.

Overriding Properties and Methods

The Overrides keyword allows derived objects to override characteristics inherited from parent
objects. Overridden members have the same arguments as the members inherited from the base class, but
different implementations. A member’s new implementation can call the original implementation in the
parent class by preceding the member name with My Base.

Constructors and Destructors

Constructors are procedures that control initialization of new instances of a class. Conversely,
destructors are methods that free system resources when a class leaves scope or is set to nothing. Visual
Basic .NET supports constructors and destructors using the sub new and sub finalize procedures.

Data Types
Visual Basic .NET introduces three new data types. The char data type is an unsigned 16-bit
quantity used to store Unicode characters. It is equivalent to the .NET Framework System. Char data
type. The short data type, a signed 16-bit integer, was named Integer in earlier versions of Visual Basic.

Interfaces
Interfaces describe the properties and methods of classes, but unlike classes, do not provide
implementations. The Interface statement allows you to declare interfaces, while implements statement
lets you write code that puts the items described in the interface into practice.
2.4 BACK END
Microsoft SQL Server

Microsoft SQL Server 2005 extends the performance, reliability, quality, and ease-of-use
of Microsoft SQL Server version 2000. Microsoft SQL Server 2005 includes several new
features that make it an excellent database platform for large-scale online transactional
processing (OLTP), data warehousing, and e-commerce applications.

Features of SQL Server

Internet Integration

The SQL Server database engine includes integrated XML support. It also has the
scalability, availability, and security features required to operate as the data storage component
of the largest Web sites. The SQL Server 2000 programming model is integrated with the
Windows DNA architecture for developing Web applications, and SQL Server supports features
such as English Query and the Microsoft Search Service to incorporate user-friendly queries and
powerful search capabilities in Web applications.

Scalability and Availability

The same database engine can be used across platforms ranging from laptop computers
running Microsoft Windows® 98 through large, multiprocessor servers running Microsoft
Windows 2000 Data Center Edition. SQL Server Enterprise Edition supports features such as
federated servers, indexed views, and large memory support that allow it to scale to the
performance levels required by the largest Web sites.
Enterprise-Level Database Features

The SQL Server relational database engine supports the features required to support
demanding data processing environments. The database engine protects data integrity while
minimizing the overhead of managing thousands of users concurrently modifying the database.
SQL Server distributed queries allow you to reference data from multiple sources as if it were a
part of a SQL Server database, while at the same time, the distributed transaction support
protects the integrity of any updates of the distributed data. Replication allows you to also
maintain multiple copies of data, while ensuring that the separate copies remain synchronized.

Data warehousing

SQL Server includes tools for extracting and analyzing summary data for online
analytical processing. SQL Server also includes tools for visually designing databases and
analyzing data using English-based questions.
3. SYSTEM ANALYSIS

3.1 EXISTING SYSTEM

The existing system is computerized system with Foxpro. It involves preliminary

storages only. Even though it is computerized system the cost estimation and other calculative
works are done by referring the purchase and service reports. And also it is worked in CUI
environment so new user can’t easily adopt with the system. They have to learn to work on the
system. So, the new system is decided to develop under the visual environment.

Drawbacks of the Existing System

 As the details are recorded, the work becomes tedious.

 Partially computerized
 Reports are not well formatted
 CUI environment
 New user can’t easily adopt with the system

The above disadvantage would put the system in trouble. To overcome the hurdles,
computerization is the only source available at present.

3.2 PROPOSED SYSTEM

The main objective of the proposed system is to reduce the manpower and time
consumption and to make the system more user friendly, efficient, accurate and fast processing.

The proposed system reduces more paper work and it stores the records in data tables.
Data tables are interrelated and it provides various kinds of information as when required. The
form entries are validated to avoid data entry error. The system is very convenience to made the
process easy.
Advantages of Proposed System

 Since all the possible options are given in the menu, it is user-friendly, interactive and it
will be very useful to the concern.
 Faster retrieval of any stored data.
 Performs continuous flow of information and it keeps in touch of good service and
maintenance.
 Accuracy and time saving are two main factors of this system.
 It helps to increase the efficiency of the management.
4. SYSTEM STUDY AND DESIGN

The system design was started reviewing the study phase activities and making
discussions about which functions are to be performed by the software, hardware and human
were. Finally, the generalized system explained to management for approval. The steps involved
in the system design were,

 The functions to be performed are identified.

 The input, output and final design were performed.
 The system and component cost requirements were specified.
 The system design report.

4.1 INPUT DESIGN

Input design is the process of converting the user-oriented. Input to a computer based
format. The goal of the input design is to make the data entry easier, logical and free error. Errors
in the input data are controlled by the input design. The quality of the input determines the
quality of the system output.

The entire data entry screen is interactive in nature, so that the user can directly enter into
data according to the prompted messages. The user is also can directly enter into data according
to the prompted messages. The users are also provided with option of selecting an appropriate
input from a list of values. This will reduce the number of error, which are otherwise likely to
arise if they were to be entered by the user itself.

Input design is one of the most important phases of the system design. Input design is the
process where the input received in the system are planned and designed, so as to get necessary
information from the user, eliminating the information that is not required. The aim of the input
design is to ensure the maximum possible levels of accuracy and also ensures that the input is
accessible that understood by the user.
 The input design is the part of overall system design, which requires very careful
attention. If the data going into the system is incorrect then the processing and output will
magnify the errors.

The objectives considered during input design are:

 Nature of input processing.
 Flexibility and thoroughness of validation rules.
 Handling of properties within the input documents.
 Screen design to ensure accuracy and efficiency of the input relationship
with files.
 Careful design of the input also involves attention to error handling,
controls, batching and validation procedures.
Input design features can ensure the reliability of the system and produce result from
accurate data or they can result in the production of erroneous information.

Data Flow Diagram (DFD)

The first step is to draw a data flow diagram (DFD). The DFD was first developed by
Larry Constantine as a way of expressing system requirements in graphical form.

A DFD also known as a “bubble chart” has the purpose of clarifying system requirements
and identifying major transformations that will become programs in system design. So, it is the
starting point of the design phase that functionally decomposes the requirements specifications
down to the lowest level of detail. A DFD consists of series of bubbles join by the data flows in
the system.

The purpose of data flow diagrams is to provide a semantic bridge between users and
systems developers. The diagrams are:

 Graphical, eliminating thousands of words;

  Logical representations, modeling WHAT a system does, rather than physical models
showing HOW it does it;
 Hierarchical, showing systems at any level of detail; and jargon less, allowing user
understanding and reviewing.
The goal of data flow diagramming is to have a commonly understood model of a system.
The diagrams are the basis of structured systems analysis. Data flow diagrams are supported by
other techniques of structured systems analysis such as data structure diagrams, data dictionaries,
and procedure-representing techniques such as decision tables, decision trees, and structured
English.
External Entity

An external entity is a source or destination of a data flow, which is outside the area of
study. Only those entities, which originate or receive data, are represented on a business process
diagram. The symbol used is an oval containing a meaningful and unique identifier.

Process

A process shows a transformation or manipulation of data flows within the system. The
symbol used is a rectangular box, which contains 3 descriptive elements: Firstly an identification
number appears in the upper left hand corner. This is allocated arbitrarily at the top level and
serves as a unique reference. Secondly, a location appears to the right of the identifier and
describes where in the system the process takes place.

Data Flow

A data flow shows the flow of information from its source to its destination. A data flow
is represented by a line, with arrowheads showing the direction of flow. Information always
flows to or from a process and may be written, verbal or electronic. Each data flow may be
referenced by the processes or data stores at its head and tail, or by a description of its contents.

Data Store

A data store is a holding place for information within the system: It is represented by an
open ended narrow rectangle. Data stores may be long-term files such as sales ledgers, or may be
short-term accumulations: for example batches of documents that are waiting to be processed.
Each data store should be given a reference followed by an arbitrary number.

Resource Flow

A resource flow shows the flow of any physical material from its source to its destination.
For this reason they are sometimes referred to as physical flows. The physical material in
question should be given a meaningful name. Resource flows are usually restricted to early,
high-level diagrams and are used when a description of the physical flow of materials is

considered to be important to help the analysis.

4.2 OUTPUT DESIGN
Output design is very important concept in the computerized system, without reliable
output the user may feel the entire system is unnecessary and avoids using it. The proper output
design is important in any system and facilitates effective decision-making. The output design of
this system includes various reports.

Computer output is the most important and direct source of information the user.
Efficient, intelligible output design should improve the system’s relationships with the user and
help in decision making. A major form of output is the hardcopy from the printer.

Output requirements are designed during system analysis. A good starting point for the
output design is the data flow diagram. Human factors reduce issues for design involved
addressing internal controls to ensure readability.

An application is successful only when it can provide efficient and effective reports.
Reports are actually presentable form of the data. The report generation should be useful to the
management for future reference. The report is the main source of information for user’s
operators and management. Report generated are a permanent record of the transaction occurred.
After any valid transactions; have commenced the report of the same is generation and: filed for
future reference. Great care has been taken when designation the report as it plays an important
role in decision-marking.

DATABASE DESIGN

A well database is essential for the good performance of the system .several tables are
referenced or manipulated at various instance. The table also knows as relation; provide
information pertaining to a specified entity. Normalization of table is carried out to extent
possible, while the normalizing tables, care should be taken to make sure that the number of
tables do not exceed the optimum level, so that table maintenance. Is convenient and effective

The process of doing database design generally consists of a number of steps which will be
carried out by the database designer. Not all of these steps will be necessary in all cases. Usually,
the designer must:
Determine the data to be stored in the database

Determine the relationships between the different data elements

Superimpose a logical structure upon the data on the basis of these relationships. Within the
relational model the final step can generally be broken down into two further steps that of
determining the grouping of information within the system, generally determining what are the
basic objects about which information is being stored, and then determining the relationships
between these groups of information, or objects. This step is not necessary with an Object
database.

In a majority of cases, the person who is doing the design of a database is a person with
expertise in the area of database design, rather than expertise in the domain from which the data
to be stored is drawn e.g. financial information, biological information etc. Therefore the data to
be stored in the database must be determined in cooperation with a person who does have
expertise in that domain, and who is aware of what data must be stored within the system.

CODE DESIGN

Code is an order collection of symbols designed to provide unique identification of an

entry or attribute. Sometimes used in the place of name of the item they can be specified all
object’s physical or performances characteristics or operational instructions. They can also show
inter relationship and may sometime be used to achieve secrecy or confidentiality.

Most computer systems are stable from the compiler down to the execution of binary
instructions. Therefore, it's natural to think of "product" as the artifact just above that base. That's
language source code. The system that produces that artifact is still quite unpredictable, so it's
not likely we'll shift our orientation. Artifacts more abstract, be they whatever, will constitute a
nebulous range of "designs" or "specifications". I think it's the lack of a direct and strictly
repeatable translation of these artifacts that characterizes them.
4.3 DATA FLOW DIAGRAM

DIAGRAM

DFD

LEVEL 0;

ADMIN PHARMACHY MANAGEMENT SYSYTEM

LEVEL 1;
4.4 E-R DIAGRAM
5. SYSTEM TESTING
5.1 SYSTEM TESTING

It is the stage of implementation, which ensures that system works accurately and
effectively before the live operation Commences. It is a confirmation that all are correct and
opportunity to show the users that the system must be tested with text data and show that the
system will operate successfully and produce expected results under expected conditions.

Before implementation, the proposed system must be tested with raw data to ensure that
the modules of the system work correctly and satisfactorily. The system must be tested with valid
data to achieve its objective.

The purpose of system testing is to identify and correct errors in the candidate system. As
important as this phase is, it is one that is frequently compromised. Typically, the project the
schedule or the user is eager to go directly to conversion. Actually, testing is done to achieve the
system goal. Testing is vital to the parts of the system are correct; the goal will be successfully
achieved. Inadequate testing or non-testing leads to errors that may not appear until months later
Appearance of the problem.

SYSTEM IMPLEMENTATION

The purpose of System Implementation can be summarized as follows:

It making the new system available to a prepared set of users (the deployment), and
positioning on-going support and maintenance of the system within the Performing Organization
(the transition). At a finer level of detail, deploying the system consists of executing all steps
necessary to educate the Consumers on the use of the new system, placing the newly developed
system into production, confirming that all data required at the start of operations is available and
accurate, and validating that business functions that interact with the system are functioning
properly. Transitioning the system support responsibilities involves changing from a system
development to a system support and maintenance mode of operation, with ownership of the new
system moving from the Project Team to the Performing Organization.
System implementation is the important stage of project when the theoretical design is tuned into
practical system. The main stages in the implementation are as follows:

 Planning
 Training
 System testing and
 Changeover Planning

Planning is the first task in the system implementation. Planning means deciding on the
method and the time scale to be adopted. At the time of implementation of any system people
from different departments and system analysis involve. They are confirmed to practical problem
of controlling various activities of people outside their own data processing departments. The
line managers controlled through an implementation coordinating committee. The committee
considers ideas, problems and complaints of user department, it must also consider;

 The implication of system environment

 Self selection and allocation form implementation tasks
 Consultation with unions and resources available
 Standby facilities and channels of communication
The following roles are involved in carrying out the processes of this phase. Detailed
descriptions of these roles can be found in the Introductions to Sections I and III.

 _Project Manager
 _Project Sponsor
 _Business Analyst
 _Data/Process Modeler
 _Technical Lead/Architect
 _Application Developers
 _Software Quality Assurance (SQA) Lead
 _Technical Services (HW/SW, LAN/WAN, TelCom)
 _Information Security Officer (ISO)
 _Technical Support (Help Desk, Documentation, Trainers)
  Customer Decision-Maker
 Customer Representative
 Consumer
The purpose of Prepare for System Implementation is to take all possible steps to
ensure that the upcoming system deployment and transition occurs smoothly, efficiently, and
flawlessly. In the implementation of any new system, it is necessary to ensure that the Consumer
community is best positioned to utilize the system once deployment efforts have been validated.
Therefore, all necessary training activities must be scheduled and coordinated. As this training is
often the first exposure to the system for many individuals, it should be conducted as
professionally and competently as possible. A positive training experience is a great first step
towards Customer acceptance of the system.

During System Implementation it is essential that everyone involved be absolutely

synchronized with the deployment plan and with each other. Often the performance of
deployment efforts impacts many of the Performing Organization’s normal business operations.
Examples of these impacts include:

Consumers may experience a period of time in which the systems that they depend on to
perform their jobs are temporarily unavailable to them. They may be asked to maintain detailed
manual records or logs of business functions that they perform to be entered into the new system
once it is operational.

Technical Services personnel may be required to assume significant implementation

responsibilities while at the same time having to continue current levels of service on other
critical business systems.

Technical Support personnel may experience unusually high volumes of support requests
due to the possible disruption of day-to-day processing.

Because of these and other impacts, the communication of planned deployment activities
to all parties involved in the project is critical. A smooth deployment requires strong leadership,
planning, and communications. By this point in the project lifecycle, the team will have spent
countless hours devising and refining the steps to be followed. During this preparation process
the Project Manager must verify that all conditions that must be met prior to initiating
deployment activities have been met, and that the final ‘green light’ is on for the team to
proceed. The final process within the System Development Lifecycle is to transition ownership
of the system support responsibilities to the Performing Organization. In order for there to be an
efficient and effective transition, the Project Manager should make sure that all involved parties
are aware of the transition plan, the timing of the various transition activities, and their role in its
execution.

Due to the number of project participants in this phase of the SDLC, many of the
necessary conditions and activities may be beyond the direct control of the Project Manager.
Consequently, all Project Team members with roles in the implementation efforts must
understand the plan, acknowledge their responsibilities, recognize the extent to which other
implementation efforts are dependent upon them, and confirm their commitment.

SYSTEM TESTING

System testing of software is testing conducted on a complete, integrated system to

evaluate the system's compliance with its specified requirements. System testing falls within the
scope of black box testing, and as such, should require no knowledge of the inner design of the
code or logic.

As a rule, system testing takes, as its input, all of the "integrated" software components
that have successfully passed integration testing and also the software system itself integrated
with any applicable hardware system(s). The purpose of integration testing is to detect any
inconsistencies between the software units that are integrated together (called assemblages) or
between any of the assemblages and the hardware. System testing is a more limiting type of
testing; it seeks to detect defects both within the "inter-assemblages" and also within the system
as a whole.
UNIT TEST

The first test in the development process is the unit test. The source code is normally
divided into modules, which in turn are divided into smaller units called units. These units have
specific behavior. The test done on these units of code is called unit test. Unit test depends upon
the language on which the project is developed. Unit tests ensure that each unique path of the
project performs accurately to the documented specifications and contains clearly defined inputs
and expected results.

SYSTEM TEST

Several modules constitute a project. If the project is long-term project, several

developers write the modules. Once all the modules are integrated, several errors may arise. The
testing done at this stage is called system test.

System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.

FUNCTIONAL TEST

Functional test can be defined as testing two or more modules together with the intent of
finding defects, demonstrating that defects are not present, verifying that the module performs its
intended functions as stated in the specification and establishing confidence that a program does
what it is supposed to do.
ACCEPTANCE TESTING

Testing the system with the intent of confirming readiness of the product and customer
acceptance.

VALIDATION TESTING

Software validation is achieved through a serious of testes that demonstrate conformity

with requirements. Thus the proposed system under consideration has been tested by validation
& found to be working satisfactory.

INTEGRATED TESTING

Integrated testing is a systematic technique for constructing tests to uncover errors

associated with interface.

Objective is to take unit tested modules and build a program structure that has been
dictated by design.
6. SYSTEM IMPLEMENTATION AND MAINTENANCE

SYSTEM MAINTENANCE

All system is dynamic and subjects to constantly changing requirements. Effort must be
devoted to adapting them and design must be flexible specified so that such changes can be
easily implemented. This activity is called system maintains. It includes improvement of system
functions and correction of errors.

Back up for the entire database files are taken and stored in secondary storage devices
like magnetic tapes and disks so that is possible to restore the system at the earliest. If there is a
breakdown or collapse, then the system gives provision to restore database files. Storing data in a
separate secondary device leads to an effective and efficient maintains of the system.

The master file has flags for maintains. After the mentioned period, the rejection
suppliers, unused data in the files will be deleted in the master file. This method is the increasing
the memory to store the data.
7. CONCLUSION

The “Pharmacy Management System” has been developed to satisfy all proposed
requirements. The system is highly scalable and user friendly. Almost all the system objectives
have been met. The system has been tested under all criteria. The system minimizes the problem
arising in the existing manual system and it eliminates the human errors to zero level. The design
of the database is flexible ensuring that the system can be implemented. It is implemented and
gone through all validation.

All phases of development were conceived using methodologies. User with little training
can get the required report. The software executes successfully by fulfilling the objectives of the
project. Further extensions to this system can be made required with minor modifications.
8. FUTURE SCOPE OF THE PROJECT

SCOPE OF FUTURE ENHANCEMENTS

Nothing will be useful until it is update & enhanced timely just like IT field. In such a
way that this software can have more future enhancement such as

 Authentication on administrator side can be moved over to biometrics for

more secure access
 Database used has limited storage, Which can be switched to SQL etc
 Virtual auction can be enabled through web cams.
 Virtual reality for the products can be achieved with the development of
technology
 It can be enhanced according to the client user friendliness
 Can be enhanced with blogs in future for tie up with different organization.
 Further the remote monitoring can be done for this project.
APPENDIX

9. APPENDIX

9.1 Tables

Table Name : Customer details

Primary Key : CusId
Field Name Data Type Width Description
CusId Integer 7 Customer Id
CusName Varchar 25 Customer Name
Addr Varchar 150 Address
Mobile Varchar 15 Mobile Number

Email Varchar 30 Email – ID

Gender Varchar 7 Gender

Table Name : Product Details
Primary Key : MedCode
Field Name Data Type Width Description
MedCode Varchar 7 MedicalCode

MedName Varchar 20 Medical Name

Type Varchar 5 Model

Ac Varchar 20 Brand / Company

Price Numeric 10 Vehicle Cost on road

Quantity Integer 10 Quantity
Total amounts Numeric 15 Total amounts

Table Name : Distributor Details

Primary Key : DisID
Field Name Data Type Width Description
Dis ID Integer 7 Distributor id
Agency Name Varchar 20 Agency Name
Dis Name Varchar 7 Distributor Name

Phone No Varchar 10 Phone No

Email Varchar 15 Email ID

Gender Varchar 2 Gender

Address Varchar 10 Address

Table Name : Sales Details
Reference Key: MedNo
Field Name Data Type Width Description
Med No Varchar 5 Medical Number

Med Name Varchar 20 Medical Name

Med Type Varchar 5 Medical Type

Ac Numeric 20 Ac
Price Numeric 10 Price
Quantity Integer 10 Quantity
Total Amount Numeric 30 Total Amount
Dis Id Integer 7 Distributor ID
Agency Name Varchar 20 Agency Name
Dis Name Varchar 20 Distributor Name
Phone No Varchar 15 Phone No
Email ID Varchar 15 Email ID
Gender Varchar 6 Gender
Address Varchar 150 Address

Table Name : Payment details

Primary Key : DisID
Field Name Data Type Width Description
Dis ID Integer 7 Distributor ID
Med Name Varchar 20 Medicine Name
Type Varchar 5 Type

AC Varchar 20 Ac

Price Numeric 10 Price

Quantity Integer 10 Quantity
Total Amount Numeric 30 Total Amount
9.2 Sample Code
Imports System.Data.SqlClient
Imports System.Data
Public Class customer
Dim con As New SqlConnection
Dim cmd As New SqlCommand
Dim adp As New SqlDataAdapter
Dim ds As New Data.DataSet
Dim i, j As Integer
Dim count As String
Dim tot As String
Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Button4.Click
Me.Close()
End Sub

Private Sub customer_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles MyBase.Load
con = New SqlConnection("Data Source=GALAXY1\SQLEXPRESS;Initial
Catalog=pharma;User ID=sa;password=sql")
autoid()
End Sub
Private Sub autoid()
Try
con.Open()
tot = "select max(cid) from customerdetails"
cmd = New SqlCommand(tot, con)
adp = New SqlDataAdapter(cmd)
ds = New DataSet()
 adp.Fill(ds)
If ds.Tables(0).Rows.Count > 0 Then
TextBox1.Text = ds.Tables(0).Rows(0)(0).ToString()
If TextBox1.Text = "" Then
TextBox1.Text = "1"
Else
TextBox1.Text = Convert.ToString(Convert.ToInt32(TextBox1.Text) + 1)
End If
End If
con.Close()
Catch ex As Exception
con.Close()
End Try
TextBox2.Focus()
End Sub

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

Handles Button1.Click
If TextBox1.Text = "" Or TextBox2.Text = "" Or TextBox3.Text = "" Or TextBox4.Text =
"" Then
MsgBox("Do not leave the Blank Field")
Else
Try
tot = "insert into customerdetails Values('" & TextBox1.Text & "','" & TextBox2.Text
& "','" & TextBox3.Text & "','" & TextBox4.Text & "','" & ComboBox1.SelectedItem & "','" &
TextBox5.Text & "')"
con.Open()
cmd = New SqlCommand(tot, con)
cmd.ExecuteNonQuery()
MsgBox("Saved Successfully", MsgBoxStyle.Information)
con.Close()
 clear()

Catch ex As Exception
con.Close()
End Try
End If
End Sub
Private Sub clear()
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
ComboBox1.SelectedIndex = 0
TextBox2.Focus()
autoid()
End Sub

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

Handles Button2.Click
Dim cid As String = InputBox("Enter Customer ID")
If Not cid = "" Then
Try
con.Open()
tot = "select * from customerdetails where cid='" + cid + "'"
cmd = New SqlCommand(tot, con)
adp = New SqlDataAdapter(cmd)
ds = New DataSet
adp.Fill(ds)
If ds.Tables(0).Rows.Count > 0 Then
 TextBox1.Text = ds.Tables(0).Rows(0)(0).ToString()
TextBox2.Text = ds.Tables(0).Rows(0)(1).ToString()
TextBox3.Text = ds.Tables(0).Rows(0)(2).ToString()
TextBox4.Text = ds.Tables(0).Rows(0)(3).ToString()
Dim gen As String = ds.Tables(0).Rows(0)(4).ToString()
If gen = "MALE" Then
ComboBox1.SelectedIndex = 0
Else
ComboBox1.SelectedIndex = 1
End If
TextBox5.Text = ds.Tables(0).Rows(0)(5).ToString()
End If
con.Close()
Catch ex As Exception
con.Close()
End Try
Else
MsgBox("Enter Customer ID")
End If
End Sub

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

Handles Button5.Click
If TextBox2.Text = "" Then
MsgBox("Click Find Button")
Else
Try
tot = "update customerdetails set cname='" & TextBox2.Text & "',pno='" &
TextBox3.Text & "',email='" & TextBox4.Text & "',gender='" & ComboBox1.SelectedItem &
"',address='" & TextBox5.Text & "' where cid='" & TextBox1.Text & "'"
con.Open()
 cmd = New SqlCommand(tot, con)
cmd.ExecuteNonQuery()
MsgBox("Updated Successfully", MsgBoxStyle.Information)
con.Close()
clear()
autoid()
Catch ex As Exception
con.Close()
End Try
End If
End Sub

Private Sub Button6_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles Button6.Click
Dim cid As String = InputBox("Enter Customer ID")
If Not cid = "" Then
Try
tot = "delete from customerdetails where cid='" & cid & "'"
con.Open()
cmd = New SqlCommand(tot, con)
cmd.ExecuteNonQuery()
MsgBox("Deleted Successfully", MsgBoxStyle.Information)
con.Close()
clear()
autoid()
Catch ex As Exception
con.Close()
End Try
Else
MsgBox("Enter Customer ID")
 End If
End Sub

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

Handles Button3.Click
clear()
End Sub
End Class
Imports System.Data.SqlClient
Imports System.Data
Public Class distributor
Dim con As New SqlConnection
Dim cmd As New SqlCommand
Dim adp As New SqlDataAdapter
Dim ds As New Data.DataSet
Dim i, j As Integer
Dim count As String
Dim tot As String
Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Button4.Click
Me.Close()
End Sub

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

Handles Button1.Click
If TextBox1.Text = "" Or TextBox2.Text = "" Or TextBox3.Text = "" Or TextBox4.Text =
"" Or TextBox5.Text = "" Or TextBox6.Text = "" Then
MsgBox("Do not leave the Blank Field")
Else
Try
tot = "insert into Distributordetails Values('" & TextBox1.Text & "','" & TextBox2.Text & "','" &
TextBox3.Text & "','" & TextBox4.Text & "','" + TextBox5.Text + "','" &
ComboBox1.SelectedItem & "','" & TextBox6.Text & "')"
con.Open()
cmd = New SqlCommand(tot, con)
cmd.ExecuteNonQuery()
MsgBox("Saved Successfully", MsgBoxStyle.Information)
con.Close()
clear()

Catch ex As Exception
con.Close()
End Try
End If
End Sub
Private Sub clear()
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
ComboBox1.SelectedIndex = 0
TextBox2.Focus()
autoid()
End Sub

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

System.EventArgs) Handles MyBase.Load
con = New SqlConnection("Data Source=GALAXY1\SQLEXPRESS;Initial
Catalog=pharma;User ID=sa;password=sql")
autoid()
End Sub
Private Sub autoid()
Try
con.Open()
tot = "select max(did) from Distributordetails"
cmd = New SqlCommand(tot, con)
adp = New SqlDataAdapter(cmd)
ds = New DataSet()
adp.Fill(ds)
If ds.Tables(0).Rows.Count> 0 Then
TextBox1.Text = ds.Tables(0).Rows(0)(0).ToString()
If TextBox1.Text = "" Then
TextBox1.Text = "1"
Else
TextBox1.Text = Convert.ToString(Convert.ToInt32(TextBox1.Text) + 1)
End If
End If
con.Close()
Catch ex As Exception
con.Close()
End Try
TextBox2.Focus()
End Sub

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

Handles Button3.Click
clear()
End Sub
End Class
Public Class Form1

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

Handles Button1.Click
If TextBox1.Text = "admin" And TextBox2.Text = "admin" Then
main.Show()
Me.Hide()
Else
TextBox1.Text = ""
TextBox2.Text = ""
TextBox1.Focus()
MsgBox("Your Username and Password are mismatch")
End If
End Sub

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

Handles Button2.Click
TextBox1.Text = ""
TextBox2.Text = ""
TextBox1.Focus()
End Sub
End Class
9.3 Screen shot

Login Page

PHARMACHY MANAGEMENT SYSTEM

BIBLIOGRAPHY

10. BIBLIOGRAPHY

 Elias M.Awad, “System Analysis and Design”, Galgotia Publication private

limited,1994.

 Fred Barwell, Richard Blair, Bill Forgey, Bill Sheldon, “Professional VB.Net”Wrox
Press Ltd., Shroff Publishers & Distributors Pvt., Ltd., 2nd Edition.

 R. Shapire“Microsoft SQL Server 2005 Complete Reference”, Tata McGrawHill,

Second Edition.

 Roger S. Pressman “Software Engineering”, A Practitioners Approach, sixth edition.

 Steven Holzner“Visual Basic .Net Programming”, Paraglyph Press, 2005 Edition.