PHARMACY MANAGEMENT SYSTEM

An Internship Report submitted to

The Principal, Sree Vidyanikethan Engineering College
(AUTONOMOUS)

in partial fulfilment of the requirements for

the award of the degree of

MASTER OF COMPUTER APPLICATIONS

By
SEELAM MANJUNATH REDDY
[19121F0037]

IN
BRAIN O VISION SOLUTIONS(INDIA)PVT.LTD

SREE VIDYANIKETHAN ENGINEERING COLLEGE

(Autonomous)
(Affiliated to JNTUA, Anantapuramu)
Sree Sainath Nagar, A. Rangampet-517 102. Chittoor (Dist), A.P
2021–2022
Company Internship Completion Letter/Certificate
 Certificate
This is to certify that this Internship work entitled

‘‘ PHARMACY MANAGEMENT SYSTEM ”

is a bonafide work done by

SEELAM MANJUNATH REDDY

[19121F0037]
in partial fulfilment of the requirements for the award of

MASTER OF COMPUTER APPLICATIONS

SREE VIDYANIKETHAN ENGINEERING COLLEGE

(Autonomous)

Head of the Department

Dr. M. Lavanya
HOD, MCA Department

(Internal Examiner) (External Examiner)

 ACKNOWLEDGEMENTS

This acknowledgement transcends the reality of formality when we would

like to express deep gratitude and respect to all those people behind the
screen who guided, inspired and helped us for the completion of my project
work.

I express my deep sense of gratitude to our beloved chairman Dr. M.

Mohan Babu Padma Shri awardee for his encouragement throughout the
course.

I owe my gratitude and special thanks to Principal Dr. B.M.Satish, for his
special encouragement and advice to shape ourselves for the future career.

I am extremely thankful to Dr. M. Lavanya, HOD, and Department of

Master of Computer Applications for all provisions made and for her
constant encouragement throughout my work.

I wish to express our deep sense of gratitude to my Internship supervisor

Ms.C.N.Rajalakshmi, Assistant Professor, company name for extending her
valuable co-operation, moral support, kind attention, guidance, suggestions
and encouragement to complete my internship successfully.

I thank all our beloved Faculty, Department of MCA for giving their
valuable suggestions and maximum co-operation.

I owe a deep sense of gratitude to my beloved Parents in extending their

moral support in this Endeavour. We would like to thank all my friends who
extended their help, encouragement and moral support either directly or
indirectly in completing my project work.
 DECLARATION
I, Seelam Manjunath Reddy hereby declare that, the internship “Title of
Internship Work” done by me at BRAIN O VISION SOLUTIONS(INDIA) PVT.LTD
during the academic year 2021-2022 and submitted to the Principal, Sree Vidyanikethan
Engineering College (Autonomous) for partial fulfillment for the award of Master Of
Computer Applications (MCA).

I also declare that, the Internship is done by my own effort and that it has not been
copied from any one and not been submitted by anybody in any of the university or
institution or research center.

Place : Tirupati.
Date : S.MANJUNATH REDDY
(19121F0037)
 ABSTRACT

Pharmacy management System consists of PHP, JavaScript, Bootstrap, and CSS. Talking
about the project, it contains an admin side and other staffs section. All the management are done
from the admin side like adding staffs to deleting their records. This project has only a single
agenda, that is, to allow the shop owner to maintain his business efficiently. The user sign up in
order to perform the CRUD operations. After sign up then user can view the admin dashboard.
From there user can manage your all the necessary activities.such as See Dashboard, See all
Manager, Add Manager, Edit Manager, Delete Manager, See all Pharmacist, Add Pharmacist, Edit
Pharmacist, Delete Pharmacist, See all Salesman, Add Salesman, Edit Salesman, Delete Salesman,
Modify Profile, Change Password.

,
 DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS

PROGRAM EDUCATIONAL OBJECTIVES (PEOS)

After few years of completion of the Program, the graduates of MCA would be:

PEO1: Enrolled or completed higher education/research studies in the core and allied areas of
computer science.
PEO2: Successful entrepreneurs and professionally excelled in diverse application skills in the
core or allied area of computer science of societal importance.
PEO3: Professionals in industry, academia and organizations with ability to adapt to evolving
technologies in the core and allied areas of computer science.
PROGRAM OUTCOMES (POs)

After completion of the program, a successful student will be able to:

PO1. Apply knowledge of computing fundamentals, computing specialization, mathematics, and

domain knowledge appropriate for the computing specialization to the abstraction and
conceptualization of computing models from defined problems and requirements.
(Computational Knowledge)
PO2. Identify, formulate, research literature, and solve complex computing problems reaching
substantiated conclusions using fundamental principles of mathematics, computing
sciences, and relevant domain disciplines. (Problem Analysis)

PO3. Design and evaluate solutions for complex computing problems, and design and evaluate
systems, components, or processes that meet specified needs with appropriate
consideration for public health and safety, cultural, societal, and environmental
considerations.

(Design /Development of Solutions)

PO4. Use research-based knowledge and research methods including design of experiments,
analysis and interpretation of data, and synthesis of the information to provide valid
conclusions.
(Conduct Investigations of Complex Computing Problems)

PO5. Create, select, adapt and apply appropriate techniques, resources, and modern
computing tools to complex computing activities, with an understanding of the limitations.
(Modern Tool Usage)

PO6. Understand and commit to professional ethics and cyber regulations, responsibilities, and
norms of professional computing practices.( Professional Ethics)
PO7. Recognize the need, and have the ability, to engage in independent learning for continual
development as a computing professional.( Life-long Learning)

PO8. Demonstrate knowledge and understanding of the computing and management principles
and apply these to one’s own work, as a member and leader in a team, to manage
projects and in multidisciplinary environments.(Project management and finance)

PO9. Communicate effectively with the computing community, and with society at large, about
complex computing activities by being able to comprehend and write effective reports,
design documentation, make effective presentations, and give and understand clear
instructions. (Communication Efficacy)

PO10.Understand and assess societal, environmental, health, safety, legal, and cultural issues
within local and global contexts, and the consequential responsibilities relevant to
professional computing practices.( Societal and Environmental Concern)

PO11.Function effectively as an individual and as a member or leader in diverse teams and in

multidisciplinary environments.( Individual and Team Work)

PO12. Identify a timely opportunity and using innovation to pursue that opportunity to create
value and wealth for the betterment of the individual and society at large. (Innovation
and Entrepreneurship

PROGRAM SPECIFIC OUTCOMES (PSOs)

On successful completion of Program, MCA graduates will be able to:

PSO1: Design, implement and test applications for complex computing problems for desired
specifications through modern tool usage, appropriate technologies and programming
skills.
PSO2: Use managerial and domain Skills of Information Management to model an application’s
data requirements using domain specific modeling tools, Transaction & Query processing,
Indexing & Searching techniques, and extract information for interpreting the datasets
for Decision Making.
PSO3: Apply suitable techniques and algorithms to Integrate Operating System, Services,
Network devices, Security mechanisms and Infrastructure to meet the requirements for
the deployment of an application and to communicate on computer networks.
 MCA V-SEMESTER
(19MC50133) INTERNSHIP

COURSE OUTCOMES

After successful completion of the course, the students will be able to:

CO1: Analyze latest tools, and technologies that are used in industry to solve
complex computing problems following relevant standards, codes, policies and
regulations.
CO2: Analyze safety, health, societal, environmental, legal, economical and
managerial factors considered in industry in solving complex computing
problem relevant to professional computing practices.
CO3: Perform individually or in a team besides communicating effectively in written,
oral and graphical forms on computing practices.
 Table of Contents

1. Introduction.................................................................................................................1
2. Literature suevey.........................................................................................................2

3. Problem Definition......................................................................................................4
4. Data Collection............................................................................................................5

5. System Analysis...........................................................................................................6

5.1. Proposed system............................................................................................6

5.2. Modules.........................................................................................................7

5.4 System architecture.........................................................................................10

6. System Environment...................................................................................................11
6.1.Hardware Requirements...........................................................................................11

6.2.................................................................................................Software Requirements
..................................................................................................................................11

7. System Design.............................................................................................................12

7.1. High Level Design documentation(HLD).............................................................12

7.1.1 Usecase diagram..........................................................................................13

7.1.2 Class diagram...............................................................................................14

7.1.3 Sequence diagram.......................................................................................16

7.1.4 Collaboration diagram................................................................................17

7.1.5 Activity diagram..........................................................................................18

7.1.6 Statechart diagram........................................................................................19

7.1.7 Component diagram.....................................................................................19

7.1.8 Deployment diagram....................................................................................20

8. Implementation.............................................................................................................22
8.1. Description of technology..............................................................................22
8.1. Screen shots....................................................................................................24
9. SystemTesting...............................................................................................................30

9.1. Introduction....................................................................................................30

9.2. Types ofTests................................................................................................30

10. Conclusion..................................................................................................................33

10.1. Future Enhancement.....................................................................................34

BIBLIOGRAPHY.............................................................................................................35

List of Figures
7.1.1 Usecase diagram..........................................................................................12

7.1.2 Class diagram..............................................................................................14

7.1.3 Sequence diagram.......................................................................................16

7.1.4 Colloberation diagram................................................................................17

7.1.5 Activity diagram..........................................................................................18

7.1.6 Statechart diagram.......................................................................................19

7.1.7 Component diagram.....................................................................................19

7.1.8 Deployment diagram....................................................................................20

 List of Screenshots
1 Screen1: Home Page..............................................................................24

2 Screen2: Admin Home Page...................................................................24

3 Screen3: Admin login page.....................................................................25

4 Screen4:Upload data set..........................................................................25

5 Screen5: view datasets.............................................................................26

6 Screen6: Pre-processed dataset................................................................26

7 Screen7: User login page.........................................................................27

8 Screen8:User home page.........................................................................27

9 Screen9:User search page........................................................................28

10 Screen10: Searched results......................................................................28

11 Screen11: Remove unwanted url............................................................29

12 Screen12:Final Output............................................................................29
 PHARMACY MANAGEMENT SYSTEM

1. INTRODUCTION

One of the core roles of a pharmacy management is to oversee the pharmacy staff and manage
the people in order to maintain positive work relations and results. Each of these roles are vital
in the running of the pharmacy, which should be communicated by the manager. The social and
administrative sciences include three strategic areas related to healthcare and pharmacy
Economics of pharmaceuticals and other health interventions. Marketing of pharmaceuticals and
health services. Management of healthcare resources. An effective pharmaceutical management
information system (PMIS) can synthesize the large volume of data generated by pharmaceutical
management operations A good PMIS also alerts staff to problems and triggers critical actions.
Another important function is to improve health system accountability.

SVEC-2021
Page 1
 PHARMACY MANAGEMENT SYSTEM

2. LITERATURE SURVEY

REVIEW OF SELECTED SRI LANKAN COST STUDIES A. HOSPITAL COSTING

Attanayake et al (2005) clearly illustrates the importance of step‐ down cost accounting but
argues that such a procedure is only possible after undertaking an in‐depth review of all the
activities of the institution. De Silva, Samarage and Somanathan (2006) conclude that outpatient
hospital costs in tertiary care settings are higher than for lower level hospitals. Costing studies
done on the specific hospitals where costing procedures were implemented, the Teaching
Hospitals of Sri Jayawarenapura (SJH) and Kurunegala (KTH) and the Base Hospital
Kuliyapitiya, are limited, so this review of cost studies widened its scope to consider studies
done in all Teaching Hospitals and Base Hospitals including the above. With regard to inpatient
care, Kasturiratne (2003) finds the hospital ‘hotel’ costs (without considering treatment costs)
that relate to the male and female wards of the Professorial Medical Unit of the Colombo North
Teaching Hospital to be Rs. 505.70 per patient day. Costs of treating specific diseases
(medication, investigations and therapeutic procedures) at this hospital per episode range from a
median cost of Rs. 4919.20 for an average 5.2 day stay for Myocardial infarction to Rs. 678.40
for a 2.7 day stay for Asthma, with the average length of stay and costs for Ischemic Heart
Disease, Stroke and Cirrhosis coming in between.

B. DISEASE COSTING In Disease Costing, the five diseases examined in Attanayake (2005)
were considered. Bias due to the non homogeneity of patients, use of multiple sources of
treatment, complexity arising from patients co‐morbidity, difficulty of finding patient samples in
the private sector hospitals for diseases such as asthma and Resource Book I: Costing for
Hospital Management

Note: A: Asthma H : Hypertension VF : Viral Fever HD : Heart Disease D

: Diarrhoea NCMH WGF : National Commission on Macroeconomics and Health Working
Group on Financing diabetes and difficulties in accurately determining indirect costs,
particularly in the subsistence sector were some of the problems encountered. The Costs
estimated in each study and the methodology adopted are summarized.

SVEC-2021
Page 2
 PHARMACY MANAGEMENT SYSTEM

PROBLEM DEFINITION

A pharmacy was always more than just a place to get your prescription. Patients treated
pharmacists as consultants, someone to help them choose an over-the-counter medicine or make
sense of a prescription’s dosage and instructions. Always happy to oblige, they rarely had
enough information about a person’s medical history, allergies, or treatment plans to give more
complete advice. This, however, is changing. The healthcare industry is experiencing
transformations and pharmacies are no exception.

Patients have access to their medical data and ability to securely share it. Hospitals are
encouraged — if not forced — to become interoperable and connect with all the other players in
the field. Valuable data is collected and transformed into insights that help make life or death
decisions with more confidence. Basically, it’s much easier to abandon manual processes and
participate in patient care instead, all the while growing as a business and staying competitive on
the growing

SVEC-2021
Page 3
 PHARMACY MANAGEMENT SYSTEM

DATA COLLECTION
Data collection is defined as the procedure of collecting, measuring and analyzing accurate
insights for research using standard validated techniques. A researcher can evaluate their
hypothesis on the basis of collected data. In most cases, data collection is the primary and most
important step for research, irrespective of the field of research. The approach of data collection
is different fields of study, depending on the required information

The Pharmacy management system is developed using PHP, JavaScript, Bootstrap, and
CSS. It’s easy to operate and understand by users. The design is pretty simple and the user won’t
find it difficult to understand, use and navigate. Talking about the project, it contains admin and
staff side. All the management are done from the admin side like adding other staffs, removing
them.

3. SYSTEM ANALYSIS

5.1 Existing System

SVEC-2021
Page 4
 PHARMACY MANAGEMENT SYSTEM

A pharmacy management software is any system used in a pharmacy that helps automate the
pharmacy workflow. This includes such tasks as reviewing physician orders and preparing
medications, controlling the inventory and making drug orders, handling billing and insurance,
providing counseling, identifying incompatibilities, and more — all while following legal
protocols and compliances.
And these are just the traditional functions that can be automated. Many more features can give
the pharmacy a competitive edge by providing better customer experience and attract patients
with more personalized and engaging service. We will talk in detail about such features in the
following section. Now, let’s go through the main benefits a pharmacy management system will
help you get.
5.1.1. Disadvantages of Existing System
One of the biggest disadvantages of the online pharmacy model is the lack of physical evaluation
capability. In some cases, physical evaluations can be made and situation analysis can be done
very effectively. Even if the online evaluation process is done, this process will not be done by
licensed healthcare professionals.
One of the disadvantages of E-Pharmacy is that there is no one you can contact face to face. When
patients want to ask questions about the drugs they are taking, it is very difficult for them to reach a
licensed pharmacist. For this reason, it may not be possible for patients to access their medication on the
same day.
Some online pharmacies can dispense medicines to patients without requiring a prescription. In
such a case, patients can get sick much more severely instead of healing. Therefore, when

Advantages of Existing System

It is very easy to order prescription drugs through E-Pharmacy. Especially for people who live
far away from a traditional pharmacy, the elderly, disabled people, and those who work very
intensively, this system is both a very easy and a very fast method of obtaining medicine.
Additionally, the shipping cost is much cheaper than the travelling to a traditional pharmacy.
2. One of the most important advantages of the E-Pharmacy application is time saving. You can
order your medication within minutes and get your prescription medicines very quickly. All you
have to do is to place an order by entering the prescription through the mobile application or
website. You do not have to go to the pharmacy and you will not be faced with waiting in line at
the pharmacy.
3• Buying drugs on the internet also saves money. Studies show that buying drugs online can
save a third of money in total.
4. Buying drugs on the internet also saves money. Studies show that buying drugs online can

SVEC-2021
Page 5
 PHARMACY MANAGEMENT SYSTEM
save a third of money in total.
5. Buying drugs on the internet also saves money. Studies show that buying drugs online
can save a third of money in total.
6. Buying drugs on the internet also saves money. Studies show that buying drugs online can
save a third of money in total.

5.2 MODULES

This project has main module such as,

1. Admin
2. Manager

 Admin has six sub modules as

following, 1.See Dashboard
2. See all Manager, Add Manager, Edit Manager, Delete Manager
3. See all Pharmacist, Add Pharmacist, Edit Pharmacist, Delete
Pharmacist 4.See all Salesman, Add Salesman, Edit Salesman, Delete
Salesman 5.Modify Profile
6.Change Password
5.2.1 Admin

Login
Admin should login our own account with username and password. The
username and password must authenticate. If username and password are not match with the
exist user, he is not the valid user.

5.2.2 Manager
Manger has accessibility of all the sales and pharmasists. Manager
should login our own account with username and password.Manager can manage the
availability of the pharmacist and sales.

SVEC-2021
Page 6
 PHARMACY MANAGEMENT SYSTEM

5.3 System architecture:

SVEC-2021
Page 7
 PHARMACY MANAGEMENT SYSTEM

6. SYSTEM ENVIRONMENT

6.1 Hardware Requirements:-

1. System : Pentium IV 2.4 GHz.

2. Hard Disk : 40 GB.
3. Floppy Drive : 1.44 Mb.
4. Ram : 512 Mb.

6.2 Software System Configuration:-

1. Operating system : Windows 7

2. Coding Language : JAVA/J2EE
3. IDE : Netbeans 7.4
4. Front End : HTML, Jsp, Css

SVEC-2021
Page 8
 PHARMACY MANAGEMENT SYSTEM

SYSTEM DESIGN

7.1 UML DIAGRAMS:UML stands for Unified Modeling Language. UML is a standardized
general-purpose modeling language in the field of object-oriented software engineering. The
standard is managed, and was created by, the Object Management Group.
The goal is for UML to become a common language for creating models objectoriented
computer software. In its current form UML is comprised of two major components: a Meta-
model and a notation. In the future, some form of method or process may also be added to; or
associated with, UML.
The Unified Modeling Language is a standard language for specifying, Visualization,
Constructing and documenting the artifacts of software system, as well as for business
modeling and other non-software systems.
The UML represents a collection of best engineering practices that have proven successful in
the modeling of large and complex systems.
The UML is a very important part of developing objects oriented software and the software
development process. The UML uses mostly graphical notations to express the design of
software projects.

7.1.1 USE CASE DIAGRAM:

A use case diagram in the Unified Modeling Language (UML) is a type of behavioral
diagram defined by and created from a Use-case analysis. Its purpose is to present a graphical
overview of the functionality provided by a system in terms of actors, their goals
(represented as use cases), and any dependencies between those use cases. The main purpose
of a use case diagram is to show what system functions are performed for which actor. Roles
of the actors in the system can be depicted.

SVEC-2021
Page 9
 PHARMACY MANAGEMENT SYSTEM

SVEC-2021
Page 10
 PHARMACY MANAGEMENT SYSTEM

7.1.2 CLASS DIAGRAM:

In software engineering, a class diagram in the Unified Modeling Language (UML) is

a type of static structure diagram that describes the structure of a system by showing the
system's classes, their attributes, operations (or methods), and the relationships among the
classes. It explains which class contains information.

Database
+add data
+retrive data
+store and retrive
data()
+updata data()

Admin
+id
+Password
User
+Login() +id
+view users()
+Add salesman() +password
+delete salesman() +give request()
+add pharmasicts() +Search results()
+delete pharmacistst()
+filter spam tweets()

SVEC-2021
Page 11
 PHARMACY MANAGEMENT SYSTEM

7.1.3 SEQUENCE DIAGRAM:

A sequence diagram in Unified Modelling Language (UML) is a kind of interaction

diagram that shows how processes operate with one another and in what order. It is a
construct of a Message Sequence Chart. Sequence diagrams are sometimes called event
diagrams, event scenarios, and timing diagrams.

Admin Database

1 : Upload datasets()

2 : give request()

3 : View all details()

6:

8 : modify all

SVEC-2021
Page 12
 PHARMACY MANAGEMENT SYSTEM

7.1.4 . Collaboration Diagram:

In collaboration diagram the method call sequence is indicated by some numbering

technique as shown below. The number indicates how the methods are called one after
another. We have taken the same order management system to describe the collaboration
diagram. The method calls are similar to that of a sequence diagram. But the difference is that
the sequence diagram does not describe the object organization where as the collaboration
diagram shows the object organization.

SVEC-2021
Page 13
 PHARMACY MANAGEMENT SYSTEM

7.1.5 ACTIVITY DIAGRAM:

Activity diagrams are graphical representations of workflows of stepwise activities

and actions with support for choice, iteration and concurrency. In the Unified Modelling
Language, activity diagrams can be used to describe the business and operational step-by-step
workflows of components in a system. An activity diagram shows the overall flow of control.

SVEC-2021
Page 14
 PHARMACY MANAGEMENT SYSTEM

State chart Diagram

State chart diagram is used to find out the state of the object and we can define state
chart diagram is define flow of states from one object to another object.

SVEC-2021
Page 15
 PHARMACY MANAGEMENT SYSTEM

7.1.6. COMPONENT DIAGRAM

Component diagrams are used to describe the physical artifacts of a system. This
artifact includes files, executables, libraries etc. So the purpose of this diagram is different,
Component diagrams are used during the implementation phase of an application. But it is
prepared well in advance to visualize the implementation details. Initially the system is
designed using different UML diagrams and then when the artifacts are ready component
diagrams are used to get an idea of the implementation.

SVEC-2021
Page 16
 PHARMACY MANAGEMENT SYSTEM

7.1.7. DEPLOYMENT DIAGRAM

Deployment diagram represents the deployment view of a system. It is related to the

component diagram. Because the components are deployed using the deployment diagrams.
A deployment diagram consists of nodes. Nodes are nothing but physical hardwires used to
deploy the application.

SVEC-2021
Page 17
 PHARMACY MANAGEMENT SYSTEM

8.IMPLEMENTATION

8.1 Description of technology:

For larger organizations and businesses, Web development teams
can consist of hundreds of people (Web developers) and follow standard methods like
Agile methodologies while developing Web sites. Smaller organizations may only require a
single permanent or contracting developer, or secondary assignment to related job positions
such as a graphic designer or information systems technician. Web development may be a
collaborative effort between departments rather than the domain of a designated
department. There are three kinds of Web developer specialization: front-end developer,
back-end developer, and full-stack developer. Front-end developers are responsible for
behavior and visuals that run in the user browser, while back-end developers deal with the
servers.

PHP:PHP started out as a small open source project that evolved as more and more people
found out how useful it was. Rasmus Lerdorf unleashed the first version of PHP way back in
1994.

PHP is a recursive acronym for "PHP: Hypertext Preprocessor".

PHP is a server side scripting language that is embedded in HTML. It is used to manage
dynamic content, databases, session tracking, even build entire e-commerce sites.

It is integrated with a number of popular databases, including MySQL, PostgreSQL,

Oracle, Sybase, Informix, and Microsoft SQL Server.

PHP is pleasingly zippy in its execution, especially when compiled as an Apache

module on the Unix side. The MySQL server, once started, executes even very complex
queries with huge result sets in record-setting time

SVEC-2021
Page 18
 PHARMACY MANAGEMENT SYSTEM

Screenshots:
Admin Login PageScreenshots:

Admin Login
Page

FIGURE 8.1.1ADMIN LOGIN PAGE

FIGURE 8.1.2Admin Home Pag

SVEC-2021
Page 19
 PHARMACY MANAGEMENT SYSTEM

FIGURE 8.1.3 UPLOAD DATASET PAGE

SVEC-2021
Page 20
 PHARMACY MANAGEMENT SYSTEM

View Dataset Page

FIGURE 8.1.4 VIEW DATASET PAGE

FIGURE 8.1.5 PRE-PROCESSED DATA PAGE

SVEC-2021
Page 21
 PHARMACY MANAGEMENT SYSTEM

9.SYSTEM TESTING

9.1 INTRODUCTION

The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionality of components, sub assemblies, assemblies and/or a finished product It is the
process of exercising software with the intent of ensuring that the

Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific
testing requirement.

9.2 TYPES OF TESTS

9.2.1 Unit testing

Unit testing involves the design of test cases that validate that the internal program
logic is functioning properly, and that program inputs produce 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.
This is a structural testing, that relies on knowledge of its construction and is invasive. Unit
tests perform basic tests at component level and test a specific business process, application,
and/or system configuration. Unit tests ensure that each unique path of a business process
performs accurately to the documented specifications and contains clearly defined inputs and
expected results.

9.2.2 Integration testing

Integration tests are designed to test integrated software components to determine if

they actually run as one program. Testing is event driven and is more concerned with the
basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the
combination of components is correct and consistent. Integration testing is specifically aimed
at exposing the problems that arise from the combination of components.

9.2.3 Functional test

SVEC-2021
Page 22
 PHARMACY MANAGEMENT SYSTEM

Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user
manuals.

Functional testing is cantered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be

exercised. Systems/Procedures: interfacing systems or procedures must be

invoked.

Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to identify
Business process flows; data fields, predefined processes, and successive processes must be
considered for testing. Before functional testing is complete, additional tests are identified
and the effective value of current tests is determined.

9.2.4 System Test

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

9.2.5 White Box Testing

White Box Testing is a testing in which in which the software tester has knowledge
of the inner workings, structure and language of the software, or at least its purpose. It is
purpose. It is used to test areas that cannot be reached from a black box level.

9.2.6 Black Box Testing

Black Box Testing is testing the software without any knowledge of the inner
workings, structure or language of the module being tested. Black box tests, as most other
kinds of tests, must be written from a definitive source document, such as specification or
SVEC-2021
Page 23
 PHARMACY MANAGEMENT SYSTEM

requirements document, such as specification or requirements document. It is a testing in

which the software under test is treated, as a black box .you cannot “see” into it. The test
provides inputs and responds to outputs without considering how the software works.

9.3 Test strategy and approach

Field testing will be performed manually and functional tests will be written in detail.

9.4 Test objectives

 All field entries must work properly.

 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.

9.5 Features to be tested

 Verify that the entries are of the correct format

 No duplicate entries should be allowed
 All links should take the user to the correct
page. Sample Testcases

No. Test case Title Description Expected Outcome Result

1 Successful User The login to the system Login should be Successful

Verification should be tried with the successful and the user
login assigned by the admin should enter in to the
and the correct password system
2 Unsuccessful Login to the system with a Login should fail with Successful
User Verification wrong password an error ‘Invalid
due to wrong Password’
password
3 Unsuccessful Login to the system with a Login should fail with Successful
User Verification invalid login id an error ‘Invalid user
due to invalid id’
login id
4 Unsuccessful Login to the system without Login Should Fail with Successful
User Type due to Selecting a valid user type an error ‘Invalid user
non selection of Type’
User Type
5 Successful Page Navigation of Pages after It Should Display a Successful
Navigation Clicking ‘Register’ option Registration Page For
to a Registration/sign up New User Group
Page
SVEC-2021
Page 24
 PHARMACY MANAGEMENT SYSTEM

10.CONCLUSION

Pharmacy management system is actually a software which handle the essential data and save
the data and actually about the database of a pharmacy and it's management.This software help
in effectively management of the pharmaceutical store or shop.It provide the statistics about
medicine or drugs which are in stocks which data can also be updated and edited.It works as per
the requirement of the user and have options accordingly.It allow user to enter manufacturing as
well as the expiry date of medicine placing in stock and for sales transaction.This software also
have ability to print the bill and invoices etc.The record of suppliers supplies can also be saved
in it.There are other function available too . The main purpose is effectively and easily handling
of pharmacy data and it's management.

10.1 FUTURE ENHANCEMENT

1. Analysis of spammers network to unearth different types of coordinated spam

campaigns run by the spambots seems one of the promising future directions of
research.
2. In Future, Add Images, Videos for identifying the spam attacks.
3. Moreover, analyzing the temporal evolution of spammers’ followers may reveal some
interesting patterns that can be utilized for spammers characterization at different
levels of granularity.

SVEC-2021
Page 25
 PHARMACY MANAGEMENT SYSTEM
BIBILOGRAPHY

REFERENCES

[1] Anwar and M. Abulaish, “Ranking radically influential web forum users,” IEEE
Transactions on Information Forensics and Security, vol. 10, no. 6, pp. 1289–1298, 2015.
[2] Boshmaf, I. Muslukhov, K. Beznosov, and M. Ripeanu, “Design and analysis of social
botnet,” Computer Networks, vol. 57, no. 2, pp. 556– 578, 2013.
[3] CFletcher, “A brief history of spam,” TIME, Tech. Rep., 2009.
[4] CBoshmaf, M. Ripeanu, K. Beznosov, and E. Santos-Neto, “Thwarting fake osn accounts
by predicting their victims,” in Proc. AISec., Denver, 2015, pp. 81-89.
[5] Caverlee, and S. Webb, “Uncovering social spammers: Social honeypots + machine
learning,” in Proc. SIGIR, Geneva, 2010, pp. 435– 42.
[10] Gao, J. Hu, C. Wilson, Z. Li, Y. Chen, and B. Y. Zhao, “Detecting and characterizing
social spam campaigns,” in Proc. IMC, Melbourne, 2001, pp. 35–47.
[11] Sahami, S. Dumais, D. Heckerman, and E. Horvitz, “A Bayesian approach to filtering
junk e-mail,” in Proc. of Workshop on Learning for Text Categorization, Madison, Wisconsin,
1998, pp. 98–105.
[12] Schafer, “Detection of compromised email accounts used by a spam botnet with country
counting and theoretical geographical travelling speed extracted from metadata,” in Proc.
ISSRE, Naples, 2014, pp. 329–334.
[13] Tsikerdekis, “Identity deception prevention using common contribution
network data,” IEEE Transactions on Information Forensics and Security, vol. 12, no.
1, pp. 188–199, 2017.

[14] Yang, R. C. Harkreader, and G. Gu, “Die free or live hard? empirical evaluation and
new design for fighting evolving twitter spammers,” in Proc. RAID, Menlo Park,
California, 2011, pp. 318–337.

SVEC-2021
Page 26
 PHARMACY MANAGEMENT SYSTEM

WEBSITES

Open a browser and go to URL http://localhost/phpmyadmin/

After creating database click Open a browser and go to URL
“http://localhost/pharmacy_Management_System/

Text Books

1. "Social Media Brand Community and Consumer Behavior: Quantifying the

Relative Impact of User- and Marketer-Generated Content," Information Systems
Research.
2. “We're all connected: The power of the social media ecosystem,” Business Horizons.
3. Review of Discussions on Internet of Things (IoT): Insights from Twitter
Analytics," Journal of Global Information Management (JGIM),.
4. "Do social media marketing activities enhance customer equity? An empirical
study of luxury fashion brand," Journal of Business Research.

SVEC-2021
Page 27