We have created Component, Sequence, Activity, Use Case, and Data Flow Diagrams(DFD) for the Blood Donation System Project.
The blood donation application will help to manage the Users, Donors, and Blood banks. The whole idea behind the application is to manage the donors’ or Blood banks and user details.
UML Diagram for Blood Donation System
We’ve compiled structural UML diagrams i.e. component diagrams, and three types of behavioural UML diagrams i.e. activity, sequence, and use case diagrams for the Blood Donation Project.
Here, the Admin can manage the user, blood bank, and donor details. Admin can view the details of users in the user list. Admin can manage the blood bank list. Whereas, users can search for blood banks, and donors, and donate blood.
Component diagram for Blood Donation Project
The diagram below shows the structural relations between components in an online Blood Donation System. The connected components by dotted lines represent relationships within the systems.
In the diagram, it can be seen that there are components named User, Donor, and Blood bank. We can see how different components interact with each other.
Here, the User can search donors, Blood Banks, and see all the donor and blood bank details. Users can contact the selected donors. Users can search for blood as per the locations also.
Activity diagram for Blood Donation Project
Activity diagrams in UML are a leading subset of behavioural diagrams. They display the functionalities of various activities and flows in management processes and software systems. The flow in the activity diagram can be sequential, branched, or concurrent.
For, it can be seen that it has to first apply for a volunteer role. If accepted, can process further and perform operations like adding/viewing applications, viewing blood banks, and feedback. For to perform functions, it must be approved by the Admin.
Admin being the primary user, have to register on the system to carry out further operations of managing the system. Admin is can accept and reject users’ requests. Admin will solely be responsible for adding donors, and blood banks.
Users after logging in can search donors, and blood banks by using search filters. A list of donors and blood banks will appear and then the user can select a particular donor and blood bank.
Sequence diagram for Blood Donation Project
Sequence diagrams in UML are used to get a better idea of how tasks within a project will function, overlap, and move between objects or components. Sequence diagrams display step-by-step interactions between objects and the order in which those interactions occur.
Users can search for specific donors or blood banks according to their preferences and select likewise. Upon selecting a particular donor, the user can contact the donor for blood donations.
Use Case Diagram for Blood Donation Project
A UML use case diagram can create a broad, high-level view of the relationship between use cases, actors involved, and systems being performed.
As you can see from the examples below, use cases are represented by oval shapes, and the lines then show at which point an actor/user participates and interacts with their corresponding use case. You can see where each actor is involved within the entire process (and where they’re excluded).
In the below diagram, we can see that the admin have the access to add donors and blood banks. Whereas, Users have the ability to search the donor and blood bank.
On the other hand, both Admin and User can manage their profile and can log in/log out of the system.
DFD Diagram for Blood Donation Project
A data flow diagram (DFD) maps out the flow of information for any process or system. It gives a basic overview of the whole system or process being analyzed. It shows the system with its relationship to external entities.
The diagram below gives us an outlook of how the system and its users work. Here, there are Admin, Donors, and Blood Banks.
Click here to get the source code
