Professional Documents
Culture Documents
ON
Medical Store Management System
SUBMITTED TO
MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION, MUMBAI
SUBMITTED BY
GUIDED BY
Prof. G.M.Lodha
ABSTRACT
Thus, in order to reduce time consumption and human effort the Medical Store
Management System application can be applied in medical stores where manual
procedure exists. The purpose of this project is to reduce time consumption and
human effort. This application provides user friendly interface as well.
3
1. INTRODUCTION
5
being sold and proving solution. This project will prompt the pharmacist about
drugs that are about to expire, preventing those drugs from begin sold and proving
solution to it.
6
3. SCOPE OF PROJECT
The main aim of the project is to create automated software which is purely used to
serve complete Medical Inventory Management, Control Stocks, Expiry & Claims,
Effective Purchase Management; it implies an Integrated Accounting
"PAPERLESS MEDICAL SHOP". Developing a MEDICAL STORE
MANAGEMENT SYSTEM would benefit the chemist shop management. Since it
is Software driven following well-organized approach the quality of services can
be enhanced considerably.
As this is generic software it can be used by a wide variety of outlets (Retailers and
Wholesalers) to automate the process of manually maintaining the records related
to the subject of maintaining the stock and cash flows.
This software helps you to track all the products of medical shop moreover it's a
medical shop accounting software. Flexible and adaptive software suited to
medical shops or stores or pharmacies of any size.
PROJECT CHARACTERISTIC –
Customer management
Transition Management
Sales management
Reporting
The main goal of the application is to maintain the records of purchase, sales and
stock deals with cash transaction maintenance.
Medical store management software is very needy for medical store. This software
helps them to maintain day-to-day transaction in computer
8
4. MODEL IMPLIMENTATION
9
5. SOFTWARE REQUIREMENT
SPECIFICATION ( SRS )
Administrator –
Client –
SQL –
VB.NET –
11
5.3 Project Features
There will be two users accessing the Software System –
Cashier can only search the product and make the bill
Can see the list of products
Staff can make their attendance
12
7.3 Safety Requirements
The database may get crashed or damaged due to virus or operating system
requirements. Therefore, it is mandatory to have a backup for your data.
UPS/INVERTER facility should be there in case of power failure.
Staff can just see the product & mark their attendance. They cannot edit or modify
anything accept their personal information.
Proper user identification will be provided. There should be separate account for
Admin & User. So that no one else can access the database except Admin.
15
9.2 Use Case Diagram
18
13.2 Estimation Using COCOMO Model
COCOMO model uses LOC for calculations. COCOMO has been defined for three
classes of software and we are going to use “Semi-Detached” because the project is
of rigid as well as flexible requirements.
Assumptions:
1. Programming language is .Net Core.
2. Average LOC by a developer in a day is 60. According to estimates made by
experts.
3. Person working are 6.
4. Project is to be completed in 5 months so approx. 120 days of working.
5. Cost per person per day 25$.
24