Atmanand Saraswati Science College

Bachelor of Computer Application (BCA)

Programme

Project Report
T.Y.B.C.A. SEMESTER – V
AY 2024-25

INFIRMARY
By

Exam No Name of Student

BCA22178 PATEL KRISH KAUSHIKBHAI

Guided by:
PRIYA PATEL

1|Page
 Atmanand Saraswati Science College

C E R T I F I CAT E

This is to certify that Mr./Ms. __PATEL KRISH KAUSHIKBHAI

___________________________________________ examination number
_____BCA22178______ has satisfactorily completed his / her project work entitled
INFIRMARY____________________________________________________as
partial fulfilment of requirements for T.Y.B.C.A. Semester – V, during the academic
year 2024-25.

Date:
Place: Surat

Examiner sign Head of department

Ms. Eeva Sheladiya

2|Page
 ACKNOWLEDGEMENT

I would like to express my gratitude and appreciation to all those

who gave me the possibility to complete this project. Special thanks are to
my mentor <mentor name> whose help, stimulating suggestions and
encouragement helped me in all time of fabrication process and in writing
this report. I also sincerely thanks for the time spent proofreading and
correcting my many mistakes.
I would also like to acknowledge with much appreciation the crucial
role of the staff in B.C.A. Laboratory, who gave me a permission to use
the lab equipment and also the machine and to design the drawing and
giving a permission to use all the necessary tools in the laboratory.
Many thanks go to the all lecturers who have given their full effort in
guiding me in achieving the goal as well as their encouragement to
maintain our progress in track. My profound thanks go to all classmates,
especially to my friends for spending their time in helping and giving
support whenever I need it in fabricating my project.

3|Page
 ABSTRACT
The worlds of infirmary agency are trying to provide more reliable and accurate
services in their field, offering services to the customers and employees with all
the available choices in their interest. It may be a leading many different
infirmary shops. Every Shop now a days is trying to computerized its activities
to provide better services to its customers. The aim is to automate its existing
manual system by the help of computerized equipment, and full-fill their
requirements, so that their valuable data/information can be stored for a longer
period with easy accessing and manipulation. This system enables to manage
and record the activities of whole infirmary shop. It enables the other staff to
provide their services in a more systematic and efficient manner, hence
improving the good will of concerned institute. This helps the administrator to
analyse upon the performance of institute. This system organized their daily
activities like billing, tablets information, stock details and more. In infirmary
present trend this application is used in every infirmary shop. This system will
save time and increase work efficiency.
Infirmary Shop Management System is a web application project
developed for infirmary shop. This system is a field concerned with purchasing
and generating reminders sales invoices and generating reminders of expiry
date about medicines. It requires more time and effort when all procedures are
performed manually. To reduce time consumption and human effort the
“Infirmary Shop Management System” web application can be applied in
infirmarys. Where the manual procedure is existing. The purpose of this project
is to reduce time consumption and human effort. This application provides user
friendly interface.

4|Page
 TABLE OF CONTENTS

Chapter 1: Introduction

1.1 Background 10

1.2 Objectives 10

1.3 Purpose , Scope & Applicability 11

1.3.1 Purpose

1.3.2 Scope

1.3.3 Applicability

1.4 Achievements

1.5 Organisation of Report

Chapter 2: SURVEY OF TECHNOLOGIES

2.1 Existing System 12

2.2 Propose System 13

2.3 Feasibility Study 13

Chapter 3: REQUIREMENT AND ANALYSIS

3.1 Problem Definition

3.2 Requirement Analysis

3.2 Hardware Requirement

3.3 Software Requirement

3.4 Planning and Scheduling

3.5 Justification of Selection Of Technology

Page 2
 Chapter 4: System Design

4.1 Module Division 19

4.2 Data Dictionary 20

4.3 ER Diagram 22

4.4 DFD/UML Diagram 24

Page 3
 LIST OF FIGURES

Sr. Figures Name

No.

1 Entity Relationship Diagram 22

2 Data Flow Diagram 24

3 Use-Case Diagram 27

4 Class Diagram 34

5 Object Diagram 36

6 Activity Diagram 39

7 Sequence Diagram 42

Page 4
 LIST OF TABLES
Sr. Table Name
No.

1 Customer Information 20

2 Medicine Information 20

3 Infirmary Information 20

4 Place Order 21

5 Stock 21

6 Bill Payment 21

Page 5
 Chapter 1
Introduction
In today’s the world’s of infirmary agency are trying to provide more reliable and
accurate services in their field, offering services to the customers and employees with all the
available choices in their interest. It may be a leading many different infirmary shops. Every
Shop now a days is trying to computerized its activities to provide better services to its
customers. The aim is to automate its existing manual system by the help of computerized
equipment, and full-fill their requirements, so that their valuable data/information can be stored
for a longer period with easy accessing and manipulation. This system enables to manage and
record the activities of whole infirmary shop. It enables the other staff to provide their services
in a more systematic and efficient manner, hence improving the good will of concerned
institute. This helps the administrator to analyse upon the performance of institute. This system
organized their daily activities like billing, tablets information, stock details and more. In
infirmary present trend this application is used in every infirmary shop. This system will save
time and increase work efficiency.
Infirmary Shop Management System is a web application project developed for infirmary
shop. This system is a field concerned with purchasing and generating reminders sales invoices
and generating reminders of expiry date about medicines. It requires more time and effort when
all procedures are performed manually. To reduce time consumption and human effort the
“Infirmary Shop Management System” web application can be applied in infirmarys. Where
the manual procedure is exists. The purpose of this project is to reduce time consumption and
human effort. This application provides user friendly interface.

The software to be produced is on “Infirmary Shop Management System”. There are 2

users. First is the admin who enters all the different types of masters. He also can update or
delete the information added by him. The admin has the highest authority than any other normal
user.
Admin provides username and password to other unauthorized person. Unauthorized
persons can log into the system using id and password given by the admin. The master details
will not be available to the normal user. The total amount will be displayed in the form and the
record will be saved in the database. A report will be printed for the manufacturers as to which
product and how many products need to be manufactured..

Page 6
 The entire project has been developed keeping of the Distributed client server
computing technology. The user interfaces are browser specific to give distributed access for
the overall system. The internal database has been selected as My SQL Server. The My SQL
Server was a choice as it provides the constructs of high level of reliability and security. The
total front end dominated using HTML standards applied with the dynamism of PHP. The client
communicates using PHP. designed. The database connectivity was planned using the PHP
Database Connectivity. The user level access has been restricted into two zones the
administrative and the normal user zone.

1.1 Background
Various health care provider and actors are uncertain of which rules that shall apply
when it comes to information systems that are used in health care. The Infirmary Products
Agency often gets questions about whether various software, intended to be used in health
care organisations, should be defined as infirmary devices. An increasing number of
incidents have been noted with the involvement of computerized information systems.
Many systems are without any doubt, to considered as infirmary devices according to
the infirmary device directives.
It is necessary to clarify that software in its own right when specifically intended by the
manufacturer to be used for one or more of the infirmary purposes set out in the definition
of a infirmary device.

1.2 Objective
 To assist the infirmary shop keeper and wholesalers in capturing the effort spent on
their respective working areas.
 To utilize human resource of the institution in an efficient manner by increasing their
productivity through automation.
 Being provided on the intranet the administrators can monitor the infirmary shop’s
activity right from their own desktop. This will let them 4.take managerial decisions.
 The system generates a number of types of reports that can be then used for various
managerial and administrative purposes. It also gives a brief picture of the institution’s
progress.

Page 7
  Helps in keeping track of all the activities of the infirmary agency like login/logout
time, security related activities, etc. and thus helps 8. In finding out the performance
level of the center.

1.3 PURPOSE & SCOPE

1.3.1 Purpose:

The objective of Infirmary Shop Management System providing the medicines to the
customers according to their request which contains the type of the medicine and the quality.
The manufactures and manufacture the medicine requested and the same will be sent to the
dealers. All the records will be saved systematically and not manually through paper work to
solve further confusions and to make life easy. Database is cleared yearly or depending on
certain span of time. It is an error free system and user friendly. It reduces paper work.

1.3.2 Scope:

The system is helpful in keeping the records of the product requested by the dealer, the number
of products manufactures, the no of product sent to the dealer.

Page 8
 Chapter 2
Survey of Technologies
2.1 EXISTING SYSTEM

The Existing system of the infirmary shop records just goes through maintaining the
files according to the medicine companies. Like the records of the particular company, product
etc. then the records of that each company schemes. The sections are created on the basis of a
company are maintained on separate page, that of shops on the section of shops.

It becomes very tedious job to maintain medicine stock manually.

In the existing system, all the basic information was gathered from manually in
spreadsheet format using files.

2.1.1 Problem Analysis

 To develop the computerized management system of infirmary shop from the manual
system implemented at present.
 To maintain the record of the shop.
 To maintain the information of items being purchased.
 To maintain the records of customers billing and stock.

2.1.2 Limitations of existing system

 It requires a lot of human time and thus is time consuming.

 The job of maintaining the records manually is very tedious.
 Voluminous data cannot be handled accurately.
 We cannot find a record of particular product, company or bill.
 Outstanding bills cannot be provided at proper time manually because it requires a lot
of time.
 In existing system, accuracy is low because of computational errors and inability to
process some transactions or errors committed due to fatigue in repetitive clerical tasks.
To avoid all such problems an existing system requires computerized system.

Page 9
2.2 Proposed System:

The proposed system can overcome all the limitations of the existing system. The
system provides proper security and reduces the manual work. The proposed system tries to
eliminate or reduce these difficulties up to some extent. The Minimize manual data entry

 Better services
 User friendliness and interactive

Minimum time required proposed system will help the user to reduce the workload and
mental conflict. The proposed system helps the user to work user to work user friendly and he
can easily do his jobs without time lagging. It has got following features.

 Ensure data accuracy

 Secure data accuracy
 Proper control of the higher officials
 Minimum time needed for the various processing

2.3 FEASIBILITY STUDY

Feasibility study is a survey of possibility of computerization based on the next

management of objectives related to an analysis of the existing facilities within the company.

The information collection that occurs during preliminary investigation examines

system feasibility and the like hood that the system will be beneficial to the organization. In
this system the test, which were carried out for feasibility study were technical feasibility and
economic feasibility.

1. Economic Feasibility.
2. Behavioural Feasibility.
3. Technical Feasibility.
4. Operational Feasibility.

1. Economic Feasibility:
Page 10
 Cost_benefit analysis is used for this feasibility. Also we have to consider about
recurring cost. It includes-

i. Rental purchase of equipment.

ii. Salary of person (who operate this system)
iii. Equipment maintenance.

Thus this system when compare on economical grounds proves to be more cost but
acceptable. Hence we say that it economically feasibile system.

2. Technical Feasibility:

The proposed system requires hardware and software for its implementation. The
computer system with printer is available in the mentioned construction organization. The
computerized system follows all technical parts affected to technical views. The
computerized system does not require any specific type of hardware. No additional
hardware is required by the system. So we say that system is technically feasible.

3. Behavioural Feasibility:

This is dependent upon determining human resources of project. All workers,

who are employed not, dismissed. We suggest that the eligible supervisors will be
employed in the firm as computer operator, after training them. Rest of them will be
given job to other section of department whether the helpers are required.

4. Operational Feasibility:

This study deals with the following issues:

Is there sufficient for the project for the infirmary shop management and user has been
in planning and development of project. When the proposed system was tested for
above mentioned issues. It was found that result tending towards being positive and
leading the system to make operationally feasible.

Page 11
 Chapter 3

REQUIREMENT ANALYSIS
3.1 Problem Definition:

Drawbacks of System

1. Time consuming…
2. More expensive…
3. Searching problem…
4. Maintains problem of all registers…
5. Less accuracy…
6. Problem for marking of not normal value…
7. More stationary…
8. Display multiple reports…

3.2 System Requirement & Specification:

System analysis is a process of gathering and interpreting facts, diagnosis problems and
the information about the Infirmary Shop Management System to recommend improvements
on the system. It is a problem solving activity that requires intensive communication between
the system users and system developers. System analysis or study is an important phase of any
system development process. The system is viewed as a whole and traced to the various
processes. Such system analysis is concerned with becoming aware of the problem, identifying
the relevant and decisional variables.

Advantages of computerized system

1. Time saving…
2. Less expensive…
3. Powerful searching…
4. Solve the problem of maintains register…
5. More accuracy…

Page 12
 6. Easy generate report…
7. Not display multiple reports…

3.2 HARDWARE REQUIREMENTS

 Processor: Intel dual core or above

 Processor Speed: 0GHZ or above
 RAM: 1GB RAM or above
 Hard Disk: 20GB hard disk or above

3.3 SOFTWARE REQUIREMENT

 Language: HTML CSS JavaScript bootstep php
 Database: SQL Server
 Operating System: Windows XP

Page 13
3.4 Planning & Scheduling

Gantt Chart:

Names of the Phase Expected Actual Date Signature of Guide

Date of of
Completion Completion

Project search

Finalization & Allocation

Investigation of system
Requirement

System Design

Program Design

Program Coding & Unit

Testing

System Integration

Project Reviews By guide

System Implementation

Acceptance testing

Feedback for improving

correcting Modifying the
project

Page 14
3.5 Justification of platform

 All the fields such as Infirmary shop, Stocks, Inventory are justify and does not take
invalid values.
 Avoiding errors in data.
 Controlling amount of input.
 Integration of all the modules/ forms in the system.
 Preparation of test cases.
 Preparation of the possible test data with all validation checks.
 Actual testing code manually.
 Modifications done for the errors found during testing.
 Prepared the test result scripts after rectification of the errors.
 Validates for the user inputs.
 Checking of the Coding standards to be maintained during coding.
 Front end is HTML CSS JavaScript
 Back end is PHP SQL

Page 16
 Chapter 4

SYSTEM DESIGN
4.1 Module of the software

 Login: Admin can choose his own username and password. After logging into the

system, he can provide username and password to other unauthorized users.

 Master: Product master contain the name of the product and the rate for each product.

Product rate differs for dealer and adhoc sales. Employee master contains the complete

details of the employee working in the factory. Dealers master contains the information

of the daily dealers.

 Order: The order from the dealer is taken through phone and the products, quality is

entered by an employee. It will be saved in the database and a crystal report will

generated for billing purpose.

 Manufacturing: At the end of the today, total number of products to be manufactured

report will be sent to the manufacturing department.

 Stock: After manufacturing, the products will be sent to the stock. Here we can get the

total number of products available.

 Sales: This is a type of sale where the dealer or the customer can visit and buy the

products normally.

 Distribution: Through transportation the products will be distributed to the dealer

according to their request.

 Reports: Stock reports, shop inventory reports, dealer reports, manufacturer reports,

products returned reports, refunded amount, paid amount reports can be generated.

Page 17
4.2 Data Dictionary

Customer Information

Field Name Data Type Description

Cust_id Auto Number Hold’s Cust_id

Name Varchar Hold’s Cust_Name

Address Varchar Hold’s Add

City Varchar Hold’s City

Phone No Varchar Hold’s Phone No

Email Nvarchar Hold’s Email

Medicine Information

Field Name Data Type Description

Medicine_id Auto Number Hold’s Mdcn_id

Name Varchar Hold’s Mdcn_Name

Comp_Name Varchar Hold’s Comp_Name

Mfg_Date Date Hold’s Mfg_Date

Exp_Date Date Hold’s Mfg_Date

Price Varchar Hold’s Price

Infirmary Information

Field Name Data Type Description

Page 18
 Infirmary_Reg_No Number Hold’s Mdcl_Reg_No

Infirmary_Name Text Hold’s Mdcl_Name

Address Text Hold’s Add

Infirmary_Owner Text Hold’s Owner

Phone_No Number Hold’s Phone_No

Email Text Hold’s Email

Fax Number Hold’s Fax

Place Order

Field Name Data Type Description

Order_No Number Hold’s Order_No

Order_Date Date/Time Hold’s Order_Date

Mfg_Lic_No Text Hold’s Mfg_Lic_No

Medicine_Name Text Hold’s Mdcn_Name

Stock

Field Name Data Type Description

Medicine_Name Text Hold’s Mdcn_Name

Qty Number Hold’s Qty

Bill Payment

Field Name Data Type Description

Sales Bill_No Number Hold’s Sales Bill_No

Medicine_Name Text Hold’s Mdcn_Name

Order_Bill Number Hold’s Order_Bill

Page 19
 Paid_Amt Number Hold’s Paid_Amt

Pending_Amt Number Hold’s Pending_Amt

4.3 ENTITY RELATIONSHIP DIAGRAM

Entity Relationship Diagram

ER-Diagram is designed tool. It is graphical representation of database system & entity

described by its various attributes. Two entity related with one another. If there is some
association present between them this relationship is shown with help of diagram.

*Shape Of Entity Relationship Diagram*

This Represent Entity Set

This Represent Attributes Page 20

 ER Diagram of Infirmary Shop Management System:

Mdcn_name
Cst_add
Mdcn_id
Mdcn_cost

Cst_id Cust_name

Customer Request Medicine

Cst_email Mdcn_com
Ms_email
Sal
es
Mdcn_type
Cst_mobile
Ms_id

Check
Ms_add
Infirmary
Shop
Pay
Stocks Stk_id
Ms_name

Bill_no Stk_no Stk_items

Stk_type
Comp_name

Bill Generate Order

Odr_id Cst_name
Send_date Amount

Cst_name Ord_mdcn
Mdcn_name Ord_type
_name

Page 21
4.4 Data Flow Diagram

1) Zero Level DFD:

Req. for Medicine Response for Medicine

Customer Infirmary Medicine
Shop
Req. for Stock Management Response for Stock
Supplier Stock

Access Update

Infirmary Shop

Page 22
2) First Level DFD:

Req. for Purchase Update

Customer Check Medicine
Stock Access

Access Check Rate info.

Price Information
Medicine

Update Bill info.

Bill Bill Detail Print Bill

Page 23
3) Second Level DFD:

Show Item Check for stock

m Search
User Medicine_mst
Item
Response
Response accept/reject

Request for Registration Check for Registration

Register
Response accept/reject Response

User_mst
Request for Login Check for Login
Login
Response accept/reject Response

Request for Food Order Check for Order Detail

Place
Order
Response accept/reject Response

Order_mst

Request for Add to Cart Check for cart

Add to
Cart
Response accept/reject Response

Check for Payment

Request for Payment
Payment Payment_mst

Page 24
Use Case Diagram for Medicine Distributors System:

Manage Customer
Record

Manage Supplier
Record

Manage Medicine
Record

Manage Purchase
Clerk
Record

Manage Sale’s
Record

Manage Report

Page 25
Use Case Diagram for Customer Subsystem:

Add New
Customer Record

Update Customer
Record
<<Uses>>

Lookup for
Customer record

<<Uses>>
Clerk Delete Customer
Record <<Uses>>

Display Customer
Record

Page 26
Use Case Diagram for Supplier Subsystem:

Add New Supplier

Record

Update Supplier
Record
<<Uses>>

Lookup for
Supplier Record

<<Uses>>
Delete Supplier
Clerk
Record
<<Uses>>

Display Supplier
Record

Page 27
Use Case Diagram for Medicine Subsystem:

Add New
Medicine Record

Update Medicine
Record
<<Uses>>

Lookup for
Medicine Record

<<Uses>>
Delete Medicine
Clerk
Record
<<Uses>>

Display Medicine
Record

Page 28
Use Case Diagram for Purchase Order Subsystem:

Place Order

<<Uses>>

Lookup for Medicine

availability

Receive Order
and Bill

<<Uses>>
Update Stock
Clerk
Record
<<Uses>>

Display
Bill

Page 29
Use Case Diagram for Sales Order Subsystem:

Take Order

<<Uses>>

Lookup for Medicine

availability

Sales Order

<<Uses>>
Update Stock
Clerk
Record
<<Uses>>

Generate Sales
Bill

Page 30
Use Case Diagram for Medicine Report Subsystem:

Customer Report

Supplier Report

Medicine Report

Clerk Sales Report

Purchase Report

Page 31
Class Diagram:

The UML activity diagram supplements the user case by providing a graphical
representation of the flow of interaction within a specific scenario similar to the flowchart, an
activity diagram uses rounded rectangles to imply a specific system function, arrow to
represent flow through the system, Decision diamonds to depict a branching decision & solid
horizontal lines to indicate that parallel activities occurs.

Indicator Meaning

1) 0..1 Zero to one.

2) One only.

3) 0..* Zero or more.

4) 1..* One or more.

 Symbols used in Class Diagram:

Name of class

Attributes

Methods

Page 32
 Service

Product Name:
Date
Person
Edit()
Name Display()
Address
Contact no.
Age

Get Name()
Get Address()
Get Contact no()
Get age

Medicine

Name
Address
Contact no.
E-mail ID
Age

Page 33
 Get Name ()
Get Address()
Get Contact no()
Get Email Id()
Get age()

Report
Bill
Customer Type
Date Customer Name
Name Dishes list
Address Edit() Total amount
Contact no. Display()
Get Name()
Cust_ID
Display()
Age

Get Name()
Get Address()
Get Contact no()
Get Cust1_Id()

Object Diagram:

Objects and links are illustrate n object diagram. It is also called as instance diagram.
Object diagram generally represents the static structure. For object diagram notation are
used derived from class diagrams. Instance are represented by underlines.

 Symbols:

Represent object and class name separated by

Page 34
Links by objects are connected

Page 35
Object Diagram:

C2:Customer
C1:Customer XYZ1:Medicine
Name :
Name : Product Id:
Gender:
Gender: Name:
DOB:
DOB: Price:
Add:
Add:
Tal:
Tal:
Dist:
Dist:
Contact No:
Contact No:

B1:Booking B2:Booking B2:Booking

Name : Name : Product Id:

Add: Add: Name: Samsung

Tal: Tal: Price:50000

Dist: Dist:

Date: Date:

Contact No: Contact No:

Time: Time:

Page 36
 R1:Report

Type:

Stock/Medicine/Crocine

Date:

M1:Medicine B1:Bill O1:Reorder

Medicine_No: Bill_No: Order No:
User_Name:Akshay User_Name: User_Name:
PdkDate: BillDate: OrderDate
Cust_ID: Cust_ID:

Page 37
Activity Diagram:

Activity Diagram System

Manager Decision

Activity

Yes

No
Starting Activity

Another

Decision Transition arrow

No Yes

Prepare Report Activity

Ending Activity

Page 38
Create Customer Record:

: Customer : Customer

Customer Fill Customer Save Change

information Detail

C : Customer C : Customer

Update Customer Record:

: Customer : Customer

Search Edit Customer Save change

records Record

C : Customer C : Customer

Page 39
Delete Customer Record:

: Customer : Customer

Search Remove Customer Save Change

Record Record

C : Customer C : Customer

Create Booking Report:

: Customer : Customer

Medicine Save change

Booking
Details

C : Customer C : Customer

Page 40
 Sequence Diagram :

Customer Medicine Stock Sell

Enquiry()

Medicine Info.

Medicine Request()

Select Medicine()

Generate Receipt()

Confirm()

Confirm Medicine()

Purchase Medicine()

Gives Bill()

Take Medicine()

Page 41
Sequence Diagram for Booking:

Customer Receptionlist Stock

Enquiry() Check availability

Assigning Medicine() Return Confirmation()

Advance Payment

Page 42
Sequence Diagram for Update Customer Record:

Receptionalist Customer

Search Record()

Return Record()

Edit()

Save Changes()

Page 43
Sequence Diagram for Delete Customer Record:

Receptionalist Customer

Search Customer Record()

Return Record()

Remove Customer Record()

Save Changes ()

Page 44
Report for Service:

Manager Service Bill Customer Report

Get Service()

Return()

Get Bill()

Return()

Get Customer Details()

Display Report()

Page 45