CHAPTER FOUR

SYSTEM DESIGN
4.1 INTRODUCTION
This chapter we will discusses about the system design of the blood bank system.
Designing is the most significant phase of software development, it require a careful
planning and philosophy on the part of the58 system designer.

The design phase involves converting the System Requirement Specification (SRS)
identified during the initiation and planning phases in to a logical design and then into
Physical design that the technical programmer can follow to develop the project during
the development phase. Design will play a bigger role in every project, therefore;
developing a good design is needed and related to have enough information (Konrad, M.
1994).

4.2 DESIGN PHASE

Design goals are the activities involved in specifying how the software will actually
work. This phase frequently described as being divided into two main phases, which
might be described as "business design" and "technical design" (Konrad, M. 1994).

The following goals were kept in mind while designing the system:

Make system easy and flexible for users: End users who aren’t programmers should be
apple to have an extreme amount of control over their purposes, this could be used
efficiently and system could act as catalyst in achieving objectives.

Make the system compatible: it should fit in the total integrated system, future

maintenance an enhancement must less.

Efficiency: It is generally considered to be the most important. Given a piece of exporter

on which the system will run and a piece of software to run it, the design should make
full and efficient use of the facilities provided. The users should interact with the system
without any delay.
Integrity: this means that the system should be accurate as possible. The problem of
preserving the integrity of data can be viewed at a number of levels. At a low level, it
concerns ensuring that the data are not corrupted by hardware or software errors. At
higher level, the problem of preserving integrity concerns maintaining and accurate
representation of the real world. to better59 maintainability. The components could be
then implemented and tested in isolation before being integrated to form a desire system.

Reliability: The system is able to perform a required function under stated conditions for
a specified period of time. The system, once loaded, should be safe from physical
corruption whether from hardware or software failure or from unauthorized access.

Extensibility: New capabilities can be added to the system without major changes to the
underlying architecture.

4.3 DATABASE DESIGN

Database design process integrates relevant data in such a manner that is can be
processed through a mechanism for recording the facts. A database of an organization is
an information repository that represents facts about the organization. The database
design is a complex process (Dušan Petković. 2005).

Design is the processing way of producing and retrieved data from multiple columns in
the database. This logically design contains all the needed of logical and physical design.
Physical it needs to generate data definition language, data manipulation language and
data control language. This can then be used to create a database. The attributed data
model that contains detailed entities.
4.4 ENTITY RELATIONSHIP DIAGRAM (ERD)

ER diagram is used to represent database schema. ERD is a detailed, logical

representation of the entities, associations and data elements for an organization or
business. ERD is a graphical modeling tool to standardize ER modeling; the modeling
can be carried out with the help of pictorial representation of entities, attributes and
relationships. The basic building blocks of ERD are Entity, Attributes, Relationship and
lines. Entity is an object that exists and is distinguishable from other object in other
words (Ould, M. A. 1995).

ERD Symbols ER diagram

is used to represent database schema.
1. A rectangle represents an entity set.
2. A Diamond represents Relationship.
3. An ellipse/ Lines represent an attributes.

L ine
Entity Set Relationship Attribute

Figure 4. 1 ERD Basic Symbols

4.4.1 De-normalization of entity relational diagram

The word ‘de-normalization’ is used to describe changes to the table design that cause the
physical tables to differ from the normalized entity relationship diagram.

4.4.2. Normalization

Normalization is the process of organizing data in a database. This includes creating

tables and establishing relationships between those tables according to rules designed
both to protect the data and to make the database more flexible
by eliminating two factors: redundancy and inconsistent dependency. Redundant data
wastes disk space and creates maintenance problems (Osterweil, L. 1987).

Most popular Normalization stages include:

1. First Normal Form ( 1st NF )

2. Second Normal Form ( 2nd NF )
3. Third Normal Form ( 3rd NF )

Table 4. 1 Un-normalized form of data

That entered data in the above table is un-normalized since a relation model does not
permit this. the table has to be normalized first. It stores details of the Product purchasing.

First Normal Form (1NF):

the following table shows the First normal form of Normalization.
Table 4. 2 Table First normal form
Second Normal Form (2NF):
Table 4. 3 second normal form (a)

Table 4. 4 second normal form (b)

Table 4. 5 second normal form (c)

Third Normal Form (3NF) :

to be in Third Normal Form (3NF) the relation must be in 2NF and no transitive
dependencies may exist within relation.

Table 4. 6 third normal form (a)

Table 4. 7 third normal form (b)

Table 4. 8 third normal form (c)

4.5 DATA DICTIONARY

Data dictionary, or data repository, is central store house of information about System’s
data. We will use it to collect, document, and organize specific facts about system include
the data flows, data stores, external entities, and processes. 64 The data dictionary also
defines and describes all data elements and meaningful combinations of data elements.

Table 4. 9 User registration table

Attributes Description
DataType and length
The ID of user PK

Member username

User password

Password confiramtion

Table 4. 10 Blood donors table

Attributes DataType and length Description
The ID of donor PK
Member donor name
Donor age
Table 4. 11 Patients table Donor gender
Donor phone
Donor address
Donor blood group
Table 4. 11 Patients table

DataType and length Description

Attributes
The ID of patients PK
Member patient name
Patient age
Patient gender
Patient phone
Patient address
Patient blood group

Table 4. 12 Blood stock table

Attributes DataType and length Description

Blood group PK
Speciefices blood stock
Speciefices blood amount

Table 4. 13 Blood transfusion table

Attributes DataType and length Description

Patient ID FK
Patient name
Patient blood group
Speciefices blood amount

Table 4. 14 View transfusion table

Attributes DataType and length Description

Patient ID FK
Date of transfusion accur
Pupose of transfusion
Patient blood group
Speciefices blood amount
4.6 TABLE DESIGN
Table 4. 15 User table

Table 4. 16 Blood donors table

Table 4. 17 Patients table

Table 4. 18 Blood stock table

Table 4. 19 Blood transfusion table

Table 4. 16 View transfusion table

4.7 FORM DESIGN

The most effective method of desktop data entry is a form filling, in which a blank form
that duplicates or resembles the source document is completed on the screen. The user
enters the data and then moves to the next field. The form can have many control features
such as menu bars, toolbars, dialog boxes, text boxes, command buttons, list boxes,
scrollbars, drop-down, group boxes, check boxes, and more others. The design of data
entry screens shall consist of the following forms:-

1. Progress bar
2. Login form
3. Forget password
4. Admin login
5. Admin panel
6. Mainform / user panel
7. Blood donor
8. View donor
9. Donate
10. Patients
11. View patients
12. Blood stock
13. Blood transfer
14. View transfer
15. Blood count
16. Dashboard
17. Setting
a. Change password
b. Reports
c. Backup and restore

-Progress-bar Form
Figure 4. 2 Progress bar
-Login Form

Figure 4. 3 Login
-Forget Password Form
Figure 4. 4 Forget password
-Admin Login Form

Figure 4. 5 Admin login

-Admin Panel Form
Figure 4. 6 Admin panel
-Main Form (user panel)

Figure 4. 7 Mainform

-Blood Donor Form

Figure 4. 8 Blood donors
-View Donor Form

Figure 4. 9 View donors

-Donate Form
Figure 4. 10 Donate
-Patients Form

Figure 4. 11 Patients

-View Patients Form

Figure 4. 12 View patoents
-Blood Stock Form

Figure 4. 13 Blood stock

-Blood Transfusion Form

Figure 4. 14 Blood transfusion
-View Transfusion Form

Figure 4. 15 View transfusion

-Blood Count Form

Figure 4. 16 Blood count
-Dashboard Form

Figure 4. 17 Dashboard

-Setting Form
Figure 4. 18 Setting
-Change Password Form

Figure 4. 19 Change password

-Reports Form

Figure 4. 20 Reports
-Blood Donors Report Form

Figure 4. 21 Blood donors report

-Patients Report Form

Figure 4. 21 Patients report

-Blood Transfusion Form

Figure 4. 22 Blood transfusion report

-Blood Stock Form

Figure 4. 23 Blood stock report

-Backup & Restore Form

Figure 4. 24 Backup
 Figure 4. 24 Restore

CHAPTER SUMMARY

This chapter discusses about the design and the implementation of the project. Software
and database design were the following steps of this chapter which was the conversion of
the requirement analysis, to show the interior design of the system. After that we
discussed. The database Design, ERD, Data Dictionary, Table Design, Form design and
etc, although we have covered majority of the project still we are going to the coding step
of the project.
 CHAPTER FIVE
SYSTEM DEVE LOPMENT

5.1 INTRODUCTION

When the system was tested, the implementation phase started. An important phase in the
system development life cycle is successful implementation of new system design.
Implementations simply mean converting new system design into operation. This is the
moment of fact the first question that strikes in every one’s mind that whether the system
will be able to give all the desires results as expected from system. The implementation
phase is concerned with user training and file conversion. The goal of the implementation
phase is to implement a system correctly, efficiently, and quickly on a particular set or
range of computers, using particular tools and programming languages in Blood bank
system , no person can log in without any user account.

5.2 CODING PHASE

This phase is devoted to providing access to most the computer programs that we used to
prepare the data and apply the programming techniques Instructions on how to construct
this application project using the software is available on the attached compact disk (CD).
The project implementation part will discuss the details process of system component.

5.3 TYPES OF TESTING

Unit testing

The testing of individual program or module is called Unit testing. The objective
is to identify and eliminate execution errors that could cause the program to
terminate abnormally, and errors that could have been missed during the
checking. Testing is more than just debugging. The purpose of testing can be
quality assurance, verification and validation, or reliability estimation.
Correctness testing and reliability testing are two major areas of testing.
 B.Integration testing

Integration testing is the phase in software testing in which individual software

modules are combined and tested as a group. It occurs after unit testing and
before testing. Testing more than one program that depends on each other is
called integration testing, or link testing.

C. System testing

After completing integration testing, System testing will perform, which involves
the entire information. An acceptance test includes all typical processing
situations and is intended to assure users, developers. During System testing, user
enter data including samples of actual, or live, data, perform queries, and produce
report to simulate actual operating condition.

5.4 USER DOCUMENTATION

Documentation describes an information system and helps the users who must interact
with it. Accurate documentation can reduce system downtime, cut cost, and speed up
maintenance task. Documentation is essential for successful system operation and
maintenance.

User documentation consists of instructions and information to users who will interact
with the system and includes user manuals help screen. It includes:

• A system overview that clearly describes all major system features, capabilities,
and limitations.
• The user documentation describes each feature of the program, and assists the
user in realizing these features.
• Explanation of how to get help and procedures for updating user manual.

• Overview of menu and data entry screen options, contents, and processing.
5.5 IMPLEMENTATION

The Implementation Phase is changing the configuration and operation of the

organization's information systems to make them more secure; the goal of the
implementation phase is to implement a system correctly, efficiently, and quickly on a
particular set or range of computers, using particular tools and programming languages.
The implementation of the system will start staff training with skilled employee in the
early days of the system implementation. It starts logging form and it may be as ADMIN
and USER. The employee of the hospital can work the system with credential (user name
and password).

CHAPTER SUMMARY

After the completion of the system, all function will be tested as a complete system to
make sure that it meets its requirements and objectives. The project implementation part
was discussed the details process of system component and tests. The testing of
individual program or module is called Unit testing. The phase in software testing in
which individual software modules are combined and tested as a group Integration is
called integration testing. After completing integration testing, System testing will
perform.
 CHAPTER SIX
RECOMMANDATION & CONCULSION
6.1 INTRODUCTION
This chapter contains the works that have been completed during the previous
documentations of this project. In addition, the chapter will cover the objectives of the
project and demonstrates how the works of this project come across the project’s
objectives. The main purpose of the study is to develop Maan-Maal libarary Management
System which is a Desktop based application that replaces the manual procedure to
increase accuracy and reduces the need to spend much time on generating reports relating
to the production activities.

6.2 CONCLUSION
After the data were collected, analyzed and discussed, then the General aim is to develop
a system that will cover Blood Management activities of Daaru-Hanaan Hospital, so, this
project and will support to be high system that will handle problems of blood activities in
Daaru-Hanaan Hospital.

Achievements

Strengths: every project has some strengths and weaknesses; so, we would like to
mention some of the strengths and good features that Blood bank system will
provide to the users. This system is very friendly system and it has a good interface
that can be usable by every person who is computer literate. What is more, if the
user makes a mistake it generates an error message that easily understandable by the
user and it gives you the necessary utilities in you project, such as, Notepad, and
other tools that you may need while you are working with the project.
 Limitations
Weaknesses: On the other hand, every project has its own weaknesses, so, this
system can be used only blood departments of the hospital cannot use further.
Also, when using system, the problems that you might face is alerting messages
that appear whenever you misuse to the system, and if you are not familiar with
this system you might find it difficult to manage it, please don't confuse, just read
carefully what the message is carrying out and then click on the appropriate button.

F uture Enhancement
This project was developed by using different types of software, so, if someone
tries to develop this project, or enhance some of the its functionalities and features,
he/she should be able to know how to use Visual C#, Programming language, SQL
server 2014 Database. We have used Visual C# language as frontend and building
the application SQL Server 2014 as Back End.
The future enhancements of the system are as follows:

o To improve the security of the system

o To add face recognition feature.
o To extend scope of the project and including other modules.

6.3 CONCLUDING REMARKS

After a successful study conducted one of the selected blood bank management
enhancing the blood operation of blood stock by transforming the blood donors , updated
blood management systems and getting realtime reports.
The researchers are fully advised that the students who make study in this area of blood
bank management systems to enlarge their scope of research concerning Management
system other than blood divisions.
References

Vikas Kulshreshtha, Sharad Maheshwari. (2011).”Blood Bank Management Information

System in India”, International Journal of Engineering,1,2, 260-263.

Rational Unified Process, Best Practices for Software Development Teams. (2012). Core
Workflows Retrieved from www.ibm.com/developerworks/rational/.../
1251_bestpractices Noushin Ashrafi, & Hessam Ashrafi. (2008).

Object Oriented Systems Analysis and Design, Pearson Higher Ed USA. Lions Blood
Bank & Research Foundation. (2012).

Retrieved from http://www.lionsbloodbank.net/ Blood Bank India. (2012). Retrieved

from http://www.bloodbankindia.net

Voluntary blood donations rising in Oman. (2014, November 21). Retrieved

from https://timesofoman.com/article/435362. Teena, C.A, Sankar, K. and Kannan,
S. (2014).

A Study on Blood Bank Management.Retrieved from

https://www.idosi.org/mejsr/mejsr 19(8)14/21.pdf3. Kumar, R., Singh, S. and
Ragavi, V.A. (2017). ).

Blood Bank Management System.Retrieved from http://ijariie.com/Admin

UploadPdf/Blood_Bank_Management_System_ijariie6874.pdf4. Liyana, F. (2017).

Blood Bank Management System Using Rule-Based Method. Retrievedfrom

http://greenskill.net/suhailan/fyp/report/038077.pdf
 APPENDEX A

NO DESCRIPTION AMOUNTS

1 Communication Cost $40

2 Internet Cost $30

3 Transportation Cost $50

4 Stationery and Materials $40

5 Printing and Photocopy $40

Total Cost $200

BUDGE T OF TH E PROJE CT
 APPENDEX B
THE TIME FRAME WORK OF PROJECT

N ACTIVITIES May JUNE July

O
1 Proposal writing

2 Reading and correction by

Supervisor

3 Proposal submission

4 Data collection

5 Analysing project

6 Designing project and

conclusion

7 Thesis submission