ABSTRACT
In this paper, we present a complete blood bank management
information system. The analysis and design of the system has been
done using Unified Modeling Language (UML). Implementation
has been done using Model View Controller (MVC) architecture
and Microsoft Visual Studio .NET framework. And Oracle 8i has
been used as database server. Throughout the whole development
process Unified Process (UP) methodology has been followed.
Keywords: Blood Bank Management, Information System,
Unified Process, Model View Controller, Unified Modeling
Language.
1. INTRODUCTION
Blood Bank is a humanitarian organization for meeting the demand
for blood in various emergency conditions from traumas to major
operations and diseases that necessitate regular insertion of blood.
That is why it is one of the major components of a hospital,
concerned with various related activities including donor
registration, physical examination, blood grouping, blood infectious
tests, component separation, blood requisition and cross match. To
replace the existing manual process of collecting, storing and
managing data for this system with a complete and automated
Management Information System, Blood Bank Management
Information System (BBMIS) has been introduced. The BBMIS
provides ready information about blood reserve/stock, daily crossmatched
details, total daily blood requisitions and information
regarding blood and donor. All through the design and
implementation phases in the process of development we have
adopted the Unified Process (UP) [2, 5] Methodology providing a
comprehensive object-oriented approach which eliminates the
intricacy included in the Structural Analysis and Design by
substituting the need to produce a complete final design and
implementation for an iterative procedure where multi-versioning
makes it possible to restyle the design and implementation meeting
user feed-back leading to a user-adapted, refined-system suiting the
needs for real stake-holders. Also in the implementation, to
segregate the user interface from the core model of the software
Model View Controller [3, 4] architecture is employed.
The rest of this paper is organized as follows. Section 2 presents
some preliminary ideas, section 3 presents the proposed design,
section 4 presents design issues, section 5 presents some
implemented snapshots.
2. PRELIMINARIES
In this section brief but essential ideas about UML & MVC are
provided:
2.1 UNIFIED MODELING LANGUAGE (UML)
The UML is a language for visualizing, specifying, constructing,
documenting the artifacts of a software intensive system as well as
other non-software systems. It simplifies the complex process of
software design making a blueprint for construction and is now the
standard notation for software architecture. UML provides both the
structural and behavioral views of the system. The UML includes
nine different diagrams – for the sake of grasping the most
representative aspects of the design of BBMIS only the following
diagrams are analyzed in this paper:
Use Case Diagram [1, 2] shows a set of use cases and actors (a
special kind of class) and the relationships addressing the static use
case view and modeling the behaviors of a system. Class Diagram
[1, 2] shows the static design view of a set of classes, interfaces,
collaborations and their relationships .Interaction Diagram [1, 2]
shows an interaction consisting of a set of objects and their
relationships including he messages that may be dispatched among
them. It addresses the dynamic view of a system. A Sequence
Diagram [1, 2] is an interaction diagram emphasizing the time
ordering of messages whereas Collaboration diagram [1, 2] is an
interaction diagram emphasizing the structural organization of
objects that send and receive messages. State Chart Diagram [1,
2] shows a state machine, consisting of states, transitions, events
and activities – especially useful in modeling reactive systems.
Component Diagram [1, 2] shows the static implementation view
of organizations and dependencies among a set of components.
Deployment Diagram [1, 2] shows the static deployment view of
the configuration of run-time processing nodes and the components
that live on them.
2.2 MODEL VIEW CONTROLLER ARCHITECTURE
The model represents enterprise data and the business rules that
govern access to and updates of this data & all the applied
operations. The View object renders the contents of a model &
accesses enterprise data specifying how that data should be
presented. A controller translates interactions with the view into
actions to be performed by the model
In this paper, we present a complete blood bank management
information system. The analysis and design of the system has been
done using Unified Modeling Language (UML). Implementation
has been done using Model View Controller (MVC) architecture
and Microsoft Visual Studio .NET framework. And Oracle 8i has
been used as database server. Throughout the whole development
process Unified Process (UP) methodology has been followed.
Keywords: Blood Bank Management, Information System,
Unified Process, Model View Controller, Unified Modeling
Language.
1. INTRODUCTION
Blood Bank is a humanitarian organization for meeting the demand
for blood in various emergency conditions from traumas to major
operations and diseases that necessitate regular insertion of blood.
That is why it is one of the major components of a hospital,
concerned with various related activities including donor
registration, physical examination, blood grouping, blood infectious
tests, component separation, blood requisition and cross match. To
replace the existing manual process of collecting, storing and
managing data for this system with a complete and automated
Management Information System, Blood Bank Management
Information System (BBMIS) has been introduced. The BBMIS
provides ready information about blood reserve/stock, daily crossmatched
details, total daily blood requisitions and information
regarding blood and donor. All through the design and
implementation phases in the process of development we have
adopted the Unified Process (UP) [2, 5] Methodology providing a
comprehensive object-oriented approach which eliminates the
intricacy included in the Structural Analysis and Design by
substituting the need to produce a complete final design and
implementation for an iterative procedure where multi-versioning
makes it possible to restyle the design and implementation meeting
user feed-back leading to a user-adapted, refined-system suiting the
needs for real stake-holders. Also in the implementation, to
segregate the user interface from the core model of the software
Model View Controller [3, 4] architecture is employed.
The rest of this paper is organized as follows. Section 2 presents
some preliminary ideas, section 3 presents the proposed design,
section 4 presents design issues, section 5 presents some
implemented snapshots.
2. PRELIMINARIES
In this section brief but essential ideas about UML & MVC are
provided:
2.1 UNIFIED MODELING LANGUAGE (UML)
The UML is a language for visualizing, specifying, constructing,
documenting the artifacts of a software intensive system as well as
other non-software systems. It simplifies the complex process of
software design making a blueprint for construction and is now the
standard notation for software architecture. UML provides both the
structural and behavioral views of the system. The UML includes
nine different diagrams – for the sake of grasping the most
representative aspects of the design of BBMIS only the following
diagrams are analyzed in this paper:
Use Case Diagram [1, 2] shows a set of use cases and actors (a
special kind of class) and the relationships addressing the static use
case view and modeling the behaviors of a system. Class Diagram
[1, 2] shows the static design view of a set of classes, interfaces,
collaborations and their relationships .Interaction Diagram [1, 2]
shows an interaction consisting of a set of objects and their
relationships including he messages that may be dispatched among
them. It addresses the dynamic view of a system. A Sequence
Diagram [1, 2] is an interaction diagram emphasizing the time
ordering of messages whereas Collaboration diagram [1, 2] is an
interaction diagram emphasizing the structural organization of
objects that send and receive messages. State Chart Diagram [1,
2] shows a state machine, consisting of states, transitions, events
and activities – especially useful in modeling reactive systems.
Component Diagram [1, 2] shows the static implementation view
of organizations and dependencies among a set of components.
Deployment Diagram [1, 2] shows the static deployment view of
the configuration of run-time processing nodes and the components
that live on them.
2.2 MODEL VIEW CONTROLLER ARCHITECTURE
The model represents enterprise data and the business rules that
govern access to and updates of this data & all the applied
operations. The View object renders the contents of a model &
accesses enterprise data specifying how that data should be
presented. A controller translates interactions with the view into
actions to be performed by the model
No comments:
Post a Comment