Beruflich Dokumente
Kultur Dokumente
CHAPTER 1
INTRODUCTION
The main aim of the project is to effectively manage the blood banking system. This project
enables the users to access nearest blood bank with GPS, it also checks the availability of the
required blood group, provides necessary information about the volunteer blood donors who have
registered by installing the application.
1.2 OBJECTIVE
The main objective of this application is to automate the complete operations of the
blood bank. They need maintain hundreds of thousands of records. Also searching
should be very faster so they can find required details instantly.
1.3 SCOPE
This application is built such a way that it should suits for all type of blood banks
in future. So every effort is taken to implement this project in this blood bank, on
successful implementation in this blood bank, we can target other blood banks in
the city.
CHAPTER 2
SYSTEM ANALYSIS
This project has been developed to automate data handling in Blood Bank Management. The
different forms have been used to input data, make changes to the existing data, delete some
records according to the requirements. The different reports give the user a Firth and knowledge
about various details.
This project opens with a splash screen clicking on which takes the user to the screen having login
form by clicking on it, the respective password entry form opens. On entering the correct password
the main MDI form is invoked, where the user can select the desired form or report from the menu.
The Cancel button associated with every form cancels the currently performed operation
and not the form.
To exit from the form click the “x” button available on the top corner of every Form.
It has not been possible to cater to all the possible quires and the project can be upgraded
according to the requirements.
There are some important modules in the purpose system, which are:
Login for admin: This module will allow the administrator to enter their respective forms.
Donor details: This module will enable admin to add new donor and to change their
details.
Hospital details: This module will enable the Administrator to add new Hospital details,
modify their details. The Hospital ID is generated automatically. He can also generate
Hospital transaction and allows printing.
Employee details: This is maintained by the administrator. He can modify the details of
the employee, salary of the employees.
Outsider details: This module enables the administrator to add new outsider details,
modify their details. The Outsider ID is generated automatically. He can also generate
Outsider transaction and allows printing.
In the manual system, firstly the Blood bank and its staff have to manage information regarding
the donor details of all the donors manually. Doing this manual transaction was really tedious job.
Secondly information regarding Hospital transactions, employee details was to be maintained. This
process is time consuming and it requires a great manual effort.
Disadvantages:
More time is consumed.
More hard work to maintain all records.
Bulk of paper is to be searched for a single search.
CHAPTER 3
TOOLS INFORMATION
Hardware Requirement
Software Requirement
CHAPTER 4
UML DIAGRAMS
The Unified Modeling Language (UML) was created to forge a common, semantically and
syntactically rich visual modeling language for the architecture, design, and implementation of
complex software systems both structurally and behaviorally. UML has applications beyond
software development, such as process flow in manufacturing.
It is analogous to the blueprints used in other fields, and consists of different types of diagrams. In
the aggregate, UML diagrams describe the boundary, structure, and the behavior of the system and
the objects within it.
UML is not a programming language but there are tools that can be used to generate code in various
languages using UML diagrams. UML has a direct relation with object-oriented analysis and
design.
A use case diagram at its simplest is a representation of a user's interaction with the system. A
use case is a list of steps that define interaction between an actor (a human who interacts with the
system or an external system) and the system itself. Use case diagrams depict the specifications of
a use case and model the functional units of a system. These diagrams help development teams
understand the requirements of their system, including the role of human interaction therein and
the differences between various use cases. A use case diagram might display all use cases of the
system, or just one group of use cases with similar functionality.
1. To begin a use case diagram, add an oval shape to the center of the drawing.
2. Type the name of the use case inside the oval.
3. Represent actors with a stick figure near the diagram, then use lines to model relationships
between actors and use cases.
Donation camp,
Reception table,
Donate blood,
Process & test blood,
Store blood,
Order blood,
purchase blood.
A class diagram in the 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 objects. Class diagrams represent the static structures of a system, including
its classes, attributes, operations, and objects. A class diagram can display computational data or
organizational data in the form of implementation classes and logical classes, respectively. There
may be overlap between these two groups.
1. Classes are represented with a rectangular shape that is split into thirds. The top section displays
the class name, while the middle section contains the class' attributes. The bottom section
features the class operations (also known as methods).
2. Add class shapes to your class diagram to model the relationship between those objects. You
may need to add subclasses, as well.
3. Use lines to represent association, inheritance, multiplicity, and other relationships between
classes and subclasses. Your preferred notation style will inform the notation of these lines.
Donor,
Receptionist,
Doctor,
Nurse,
Lab technician,
Blood,
Blood bank,
Hospital.
Idle,
Donor registration,
Donor checking,
Take blood,
Test and process blood,
Send blood to blood bank,
Verify and store blood,
Delivery to hospital.
The process of activity diagram is same as state diagram, there are mainly two differences;
second: synchronized bar which use to split and merge activities/state of diagram.
1. To create a sequence diagram, write the class instance name and class name in a rectangular
box.
2. Draw lines between class instances to represent the sender and receiver of messages.
3. Use solid arrowheads to symbolize synchronous messages, open arrowheads for asynchronous
messages, and dashed lines for reply messages.
A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that
live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order
in which they occur.This allows the specification of simple runtime scenarios in a graphical
manner.
CHAPTER 5
CONCLUSION
REFERENCES
[1] https://www.geeksforgeeks.org/unified-modeling-language-uml-state-diagrams/
[2] https://www.lucidchart.com/pages/what-is-UML-unified-modeling-language
[3] https://www.smartdraw.com/uml-diagram/
[4] https://www.slideshare.net/HDarji/blood-bank-management-system-including-uml-diagrams
[5] https://www.phptpoint.com/projects/blood-bank-management-system/