EYE BANK MANAGEMENT SYSTEM

ABSTRACT :

The “Eye Bank Management System” is a software application to maintain day to day
transactions in an Eye Bank. This software help to register all the donors, Eye Tissue collection
details, Eye Tissue issued details etc The main objective of this application is to automate the
complete operations of the Eye Bank. They need to maintain hundreds of thousands of records.
Also searching should be very faster so they can find required details instantly. This application
is built such a way that it should suits for all type of Eye Banks in future. So every effort is taken
to implement this project in this Eye Bank, on successful implementation in this Eye Bank, we
can target other Eye Banks in the city.

We develop format to make use of eye tissues that are donated by users from various
location. It helps to provide eye needs for a people on emergency time and mean to provide
maintenance record on eye requirements in the eye bank. It also enables the user to register the
details who are interested in donating eye. It helps to manage the data about eye and its tissue
types. The time where the people attacked by corneal blindness which means this the significant
cause of visual impairment of worldwide especially in developing countries. The number of
patients waiting for corneal transplantation is growing due to insufficient number of eye
donations in India. Eye Donation is dependent on people who are willing to donate their eyes and
on relatives to honor that pledge upon the death of the person.
 2. REQUIREMENT SPECIFICATIONS

2.1 Hardware Specification:

The hardware specification is necessary to support the proposed system, which have
been identified, ordered, delivered, installed and tested at the time of installation.

 Processor : Pentium IV
 Hard Disk : 40GB
 RAM : 512MB or more
 Mouse : Optical
 Printer : HP Laser

2.2 Software Specification:

The software specification is the one says about the development environment of the
package.

 Operating System : Windows 7

 Programming Language : VB.Net
 IDE Tool : Micro Soft Visual Studio 2019
 Database : My SQL
 3. SYSTEM ANALYSIS

3.1 Existing System:

The existing system has some disadvantages that the system is manual hence it is time
consuming more time is required for the work. The eye bank details, donor details and the
employee details are managed separately. These details are entered and edited by the
administrator. Most of the existing system is manual, so data manipulations are not accurate and
also processing time is slow.

Drawbacks of the Existing System:

 Takes much time for searching particular eye donor details.

 Difficult to maintain employee details
 Even though some existing systems are computerized, there occur redundancy
problems due to duplication of entries.
 Existing system is not accurate.
3.2 Proposed System:

The system as the name suggest maintains the detail information about the Eye Bank
activity and management. Administrative users log-in the system with authentication then all the
details of eye donor & employees is stored in master file. Camp details are also maintained in the
database system. To develop a system that provides functions to support donors to view and
manage their information conveniently. The proposed system maintain records of eye donors,
eye donation information and eye tissue stocks in a centralized database system.

Advantage of the Proposed System:

 Prepares and produces accurate outputs

 Reduces the time needed and expenses
 Makes the information flow efficient
 Easy report generation is possible
 Provides attractive user interface.
 Minimize the working stress and can keep essential documents related to the eye bank
and the donor details as a softcopy.
3.3 Module Description:

 Login : It is used for logging in the automobile spare part management system. It is used
for verifying the user. Once the user is authenticated, they can access the system.
 Registration : Here the donors can register by filling all the details like Phone email id,
username, password, date of birth, address, phone number etc.
 Donor details : It is used for adding eye donor details. The admin enters all the details of
the donor such as name, address, contact number, blood group, date, time etc.
 Recipient details : This module helps user to find eye. When user searches eye bank by
providing the city name, the system search for the availability of the eye bank in that
particular city and give him the list of the donors.
 Camp details : Admin can schedule a camp by giving all the details like venue, date,
time, offers etc.
 Reports : Here the Admin can view all the reports like eye bank employee report, donors
reports, eye tissue reports etc, here the admin can take a print of any records.
 4. DATA FLOW DIAGRAM

A Data Flow Diagram (DFD) is a diagram that describes the flow of data and the
processes that change data throughout a system. It’s a structured analysis and design tool that can
be used for flowcharting in place of or in association with information. Oriented and process
oriented system flowcharts. Four basic symbols are used to construct data flow diagrams. They
are symbols that represent data source, data flows, and data transformations and data storage.
The points at which data are transformed are represented by enclosed figures, usually circles,
which are called nodes.

Data Flow Diagram Symbols

- Source or Destination of data

- Data Flow

- Process

- Storage
 When analysts prepare the Data Flow Diagram, they specify the user needs at a level of
detail that virtually determines the information flow into and out of the system and the required
data resources. The network is constructed by using a set of symbols that do not imply physical
implementations. The Data Flow Diagram reviews the current physical system, prepares input
and output specification, and specifies the implementation plan.

Steps to Construct Data Flow Diagrams

Four steps are commonly used to construct a DFD

 Process should be named and numbered for easy reference. Each name should be
representative of the process.
 The destination of flow is from top to bottom and from left to right.
 When a process is exploded in to lower level details they are numbered.
 The names of data stores, sources and destinations are written in capital letters.