Medical Shop Report

Published on May 2016 | Categories: Types, School Work | Downloads: 28 | Comments: 0 | Views: 241
of 19
Download PDF   Embed   Report

Comments

Content

A
Project Synopsis
on

MEDICAL SHOP MANAGEMENT SYSTEM
Bachelor of Science ( Software Engineering )
Submitted By:

Mane Pandurang Sandipa

: 24

Mumane Ganesh Satish

: 26

Salunke Ganesh Pravin

: 30

Academic Year: 2015 – 2016
Submitted to:

Swami Ramanand Teerth Marathwada University, Nanded

Royal Education Society’s

College of Computer Science and Information Technology, Latur

Guided By
( Mr.I.M.Kazi )

Head of Department
(Mr. I.M.Kazi)

Index
Sr. No.

Contents

Page
No.
1

1

Abstract

2

Introduction to Project

2

3

Project Plan (Gantt chart)

4

4

Hardware and Software Requirements

5

5

Context Level DFD

8

6

E-R Diagram

11

7

Conclusion

12

8

References

14

Abstract
Medical Management System

is a complete medician fully integrated medical shop dealer

management software. The software covers all the areas required for an Medical shope including
Tablet sales, medicine , chemist/Service Station Management, Financial Accounting. This software
is best suited for medical deals of LCV, HCV, , ASC & Authorized medical dealers. This project is
developed to manage the medical in the medicals dealer company. The main module in this project
are login, product management, customer management, sales, complaints and reports.

1

INTRODUCTION OF THE PROJECT
Today the world's most forward looking medical 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 medical shops. Every Shop
nowadays is trying to computerize its activities to provide better services to its customers. The aim
is to automate its existing manual system by the help of computerized equipments and full-fledged
computer software, fulfilling their requirements, so that their valuable data/information can be
stored for a longer period with easy accessing and manipulation of the same.
This project, “MEDICAL STORE SYSTEM” also a step towards offering more or less the similar
features. This system enables to manage and record the activities of whole medical Shop of multifacility skills only.
It enables the other staff to provide their services in a more systematic and efficient manner, hence
improving the goodwill of concerned institution. This helps the administrator to analyze upon the
performance of institution.

Purpose
The purpose of this document is to specify requirements and to give guidelines for the development
of above said project. In particular it gives guidelines on how to prepare the above said project.
This document is intended to be a practical guide for people who developing this software.

Scope
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.

Goal
The main goal of the application is to maintain the records of purchase, Sales and stock details with
cash transaction maintenance.
2

Overview
Medical Store Management software is very needy for Medical Store . This software help them
maintain day to day transactions in computer.

Existing System
At present Medical Stores maintain their day to day transactions manually. These have shops
thousands of products they need to track of all these products to check the stock, expiry date etc., If
they are not return the expiry products to the distributor in time then they loose that much amount.
So it is very essential to track expiry items prior one month or before, then only they can able to
return these products back. To find the product is also another risky job. So proper system is
required. They need a full pledged software to maintain their day to day transactions. Apart from
this regular update on stock. Supplier wise cash transaction. Daily sales report. Etc.,

Proposed System
The proposed system help them in many ways. It help them do billing very easily. Account
maintenance also become easier. They can keep track of their purchases, sales, stocks and account
details. The software is provided with all the master entries to enter any new product, or supplier, or
customer to add or modify and delete.

3

Project Plan (Gannt chart)
Gantt chart is a simple and effective scheduling technique. Gantt chart uses a calendaroriented chart to represent the schedule. Gantt chart is also called a Timeline Chart. A Gantt
chart can be developed for the entire project. Each activity is represented as a bar in the
calendar, starting from the date of the activity and ending at the ending date for that activity.
The start and end of each activity becomes milestone for the project.

The Gantt chart in the figure is actually an enhanced version of standard Gantt charts. The
white part of the bar shows the length of time each task is estimate to take. The gray part
shows the slake time that is, the latest time by which a task must be finished. One way to
view the slake time is that, of necessary, we can slide the white area over the gray area
without forcing the start if next activity to be delayed.
The Gantt chart for this system is shown in figure:

Scope of work to be done:
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.

RISK MANAGEMENT
RISK
Risk is a problem that could cause some loss or threatens the success of the project, but
which has not happened yet.

The risks should be managed by addressing some of these risk factors:
 Inadequate planning and task identification
The project should be planned properly how the task will be done and as well as
distributed the task among teammates and assigning them the duties to be performed by
them.
 Unclear project ownership and decision making
Project ownership is very clear as there is one project leader and is very cooperative.
She is very good at decision making. Due to which our project is going smoothly.
 Unrealistic commitments made, sometime for the wrong reasons
There is no chance of making unrealistic commitments as we are the students of
BCA V sem and working for our project which equally important to each of the team
member. Hence there is no chance of risk in terms of any wrong reasons.
 Managers or customers with unrealistic expectations

There is no chance of such type of risk because we have studied the scenario of
present system and preparing the software according to that, hence there is no chance of
any unrealistic expectation from the side of customer.
 Staff personality conflicts
There are no such conflicts as all the team members are very cooperative and
understand each other. They understand their responsibility and perform them up to their
max.
 Poor communication
No such poor communication exists in our team. Everybody work together in a very
healthy environment.
As you can see from the above points we have stated that there is a very less possibility
of risk in out project.

4

Hardware Requirements
Processor

:

Pentium IV 2GHz and Above

RAM

:

2GB RAM

Monitor

:

15” Color Monitor

Keyboard
Mouse

Software Requirements
Operating System. :

Windows XP

Developing Tool

:

VB6

Database

:

MS Access

5

Objectives of the Project Medical Shop Management System
The main objectives behind the development of this project are as follows:


To assist the medical 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 medical shop’s activity
right from their own desktop. This will let them 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.



Helps in keeping track of all the activities of the medical agency like login/logout time,
security related activities, etc. and thus helps in finding out the performance level of the centre.

Thus, there is a number of objectives behind developing the “MEDICAL STORE SYSTEM” and it
reduces a lot of burden of the managers by simplifying the tasks of reporting etc.

INPUT IN THE PROJECT MEDICAL SHOP MANAGEMENT SYSTEM


To store the information of the customer.



To store the information of the supplier.



To store the information of the medicines.



To store the information Employees.



To store the information of the worker.



To store the information of the worker salary.



To store the information of the worker salary details.

6

OUTPUT OF THE PROJECT MEDICAL SHOP MANAGEMENT SYSTEM


To store the information of the customer.



To store the information of the supplier.



To store the information of the medicines.



To store the information Employees.



To store the information of the worker.



To store the information of the worker salary.



To store the information of the worker salary details.

7

Project Planning and scheduling

Project Development Approach
To solve actual problems in an industry setting, a software development strategy must be
incorporated that encompasses the process, methods and tools for software engineering. This
strategy is often referred to as software process model and software engineering paradigm.
Asoftware process model for software engineering is chosen based on the nature of project and
application, the methods and tool to be used and the controls and deliverables that are required.
For the development and implementation of windows based module several distinct
approaches are in practice occurs. Among them, a very popular one is the classical system
development life cycle model (SDLC) orthe waterfall model. The waterfall model has following
phase of its development:

1)

System/Information Engineering and modeling

2)

Software Requirement Analysis

3)

System Analysis and Design

4)

Code Generation

5)

Testing and Maintenance

8
 System Information Engineering and Modeling:
As software is always of a large system (or business), work begins by establishing
requirements for all system elements and then allocating some subset of these requirements to
software. This system view is essential when software must interface with other elements such as
adware, people and other resources. System is the basic and very critical requirement for the
existence of software in any entity. So if the system is not in place, the system should be
engineering and put in place. In some cases to extract the maximum output, system should be reengineered and spices up.

Pert Chart Representation:

9

Data Flow Diagram

10

Er-Diagram

11

TECHNICAL ARCHITECT/ DESIGNER:-

A member will be appointed as Technical Architect and Designer.
He/she will performed all the task of a system designer. Some of them are as follows:

 Functional analysis and system design.
 Ensured that the module completion deadlines are met.
 Ensured that individual team member adheres to deadlines
 Ensured periodic backups.
 Managed time and resources within group.
 Ensured that quality systems are being followed by group.
 Implementation support.
 Maintenance Support.

TASK TO BE DONE :
 Being the main point of contact for client projects and lead internal teams.
 Extract a deep understanding of the client’s business model, online goals and key
performance indicators.
 Provide strategic insights and craft a unique solution “vision” that exceeds each
client’s expectation and goals.
 Construct and maintaine project budgets, detailed project plans and manage on-time,
on-budget deliverables.
 Proactively managed and negotiated team and client risks / conflicts.
 Anticipated and solved problems.
 Defined project scope.
 Facilitating technical/operational requirements and definition for technology
initiatives.
 Developing detailed baseline project plans.

 Presentation of project plans to management.

References
Website(s) –
1) http://gnu.inflibnet.ac.in
2) https://www.google.co.in
3)

http://www.kashipara.com

Books –
1)complete reference book vb 6.0 / richard man
2)complete reference book ms access

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close