JIMMA UNIVERSUTY

INSTITUTE OF TECHNOLOGY

DEPARTMENT OF COMPUTING

PROGRAM: COMPUTER SCIENCE

REQUIRMENT SPECIFICATION, ANALYSIS AND SYSTEM DESIGN

ON

WEB BASED BIOLOGICAL DATA MANAGEMENT SYSTEM FOR

ETIOPIAN INSTITUTE OF BIODIVERSITY

BY

Name ID No signature

1. Dawod Yimer -----------------03676/04 ----------------

2. Ahmed Hussien-------------- 03628/04 ----------------
3. Sofya Nuru--------------------03580/04 ----------------
4. Woldetinsae Thomas---------03875/04 ---------------

Advisors:

Name Signature

1. Mr. Behailu Shewandagn------------------------------------------------

2. Mrs. Melita Luke---------------------------------------------------------
SUBMITTED TO JIMMA INSTITUTE OF TECHNOLOGY DEPARTMENT OF
COMPUTING

FEB 04, 2015 JIMMA, ETHIOPIA

.
JIMMA UNIVERSITY
JIMMA INSTITUTE OF TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE

REQUIRMENT SPECIFICATION, ANALYSIS AND SYSTEM DESIGN

ON

WEB BASED BIOLOGICAL DATA MANAGEMENT SYSTEM FOR

ETIOPIAN INSTITUTE OF BIODIVERSITY

BY:
S. No STUDENT NAME ID No
1 Dawod Yimer 03676/04
2 Ahmed Hussien 03628/04
3 Sofya Nuru 03580/04
4 Woldetinsae Thomas 03875/04

NAME AND SIGNATURE OF THE EXAMINING BOARD

Name Signature

1. ----------------------------- ---------------------------

2. ----------------------------- ---------------------------

3. ----------------------------- ----------------------------

Project Viva – Voce held on

BDIMS BY GROUP 7 I
.
Contact Information
WEB BASED BIOLOGICAL DATA MANAGEMENT SYSTEM FOR

ETHIOPIAN INSTITUTE OF BIODIVERSITY

This project report is summited to Department of computing at Jimma

University in partial fulfillment of the requirements for the Degree of Bachelor
of science in computer science.

By Group 7

Name ID No Email

0376/04 Dawodyimer678@gmail.com
1. Dawod Yimer Abegaz
03628/04 ahmedhussien@gmail.com
2. Ahmed Hussien
Ebrahim
03580/04 sofyanuru@gmail.com
3. Sofya Nuru Ahmed
03875/04 woldetinsae@gmail.com
4. Woldetinsae Thomas
Abreham

Advisors:

1. Mr. Behailu Shewandagn

Email: behailu.shewandagn@ju.edu.et

Department Computing

2. Mrs. Melita Luke

Email: pmmelita@gmail.com

Department: Computing

Feb 04, 2015

Jimma, Ethiopia

BDIMS BY GROUP 7 II
.
Intellectual Right Property Declaration

This is to declare that the work under the supervision of Mr. Behailu Shewandagn and Mrs.
Melita Luke having title “Web Based Biological Data Management system for Ethiopian
Institute of Biodiversity” carried out in partial fulfillment of Bachelor Degree of Science in
Computer Science is the sole property of Jimma University and the respective supervisors
and is protected under the intellectual property laws and conventions. It can only use for
purposes like extension for further enhancement, product development, adaption for
organizational usage with the permission of the university supervisors.
The project is our own and has not been presented for a degree in any other university and
all the sources of materials used for the project/ thesis have been duly acknowledged.

Date: Feb 04 2015

Authors

No Name IdNo Signature

1. Dawod Yimer Abegaz--------------------- 03676/04 ---------------------
2. Ahmed Hussien Ebrahim------------------03628/04 ---------------------
3. Sofya Nuru Ahmed---------------------- -03580/04 --------------------
4. Woldetisae Thomas Abreham-------------03875/04 --------------------

BDIMS BY GROUP 7 III

.

Anti-Plagiarism Declaration

This is to declare that the above industrial project produced under the supervision of Mr.
Behailu Shewandagn and Mrs. Melita Luke having title Web based Biological Data
Management System for Ethiopian Institute of Biodiversity is the sole contribution of the
members and no hereof has been reproduced illegally which can be considered as
plagiarism. All referenced have been used to argue the idea and have been cited properly.
We will be responsible and liable for any consequence if violation of this declaration is
proven.

Date: Feb 04 2015

Authors
Name Id No
1. Dawod Yimer ----------------------03676/04
2. Ahmed Hussien---------------------03628/04
3. Sofya Nuru--------------------------03580/04
4. Woldetinsae Thomas---------------03875/04
signature
---------------------------
---------------------------
---------------------------
--------------------------

BDIMS BY GROUP 7 IV
.

I.Acknowledgement
First of all we heartily thanks our advisors Mrs. L. Melita Luke and Mr. Behailu
Shewandagn for their continuous support in every phase of the project and who continuously
provided us with their valuable advice to work on the project and this document. They also
help us by indicating different sources of information that supports our project and they
show their loyalty fatherly/motherly. Secondly we would like to express our thanks to all
computing department staff members who directly or indirectly helped us in this project
preparation. Thirdly we would like to acknowledge all our friends for their morals, idea,
materials and financial support during the preparation of the project. Lastly our thank goes
to Jimma university college of agriculture and veterinary medicine teachers who give
priceless constructive idea about the Ethiopian biodiversity by losing their time.

BDIMS BY GROUP 7 V
.
II. ABSTRACT
Conservation of biological diversity will be a major challenge for the ecologists in the
forthcoming century. In-situ conservation biotechnology tools to conserve and prospect
understanding genetic variability, species diversity and habitat relationship, and allowing
evolutionary process of speciation are some challenges. Ethiopia is one of the mega
biodiversity centers and is also known for its traditional knowledge of conservation. The
varied regions of the country with unique floral and faunal richness, their vastness,
endemism, heterogeneity and inaccessibility of large area have necessitated creation of
authenticated baseline on biodiversity. This information system is essential to monitor,
analyze and plan action oriented programs for conserving and preserving our biological
wealth.

Biological inventory and monitoring data should be stored and managed in computer
database to facilitate its effective analysis and use with regard to biological data
management. Biological data are data commonly stored in files or databases.

Biological data management system (BDIMS) is a software solution for storage,

management, analysis and publication of biological data and it can be the best choice for any
relevant research or industrial laboratory, culture collections and management. Service that
Biological Data Management System provides are registering biological entities including
microbial, plant and animal species with their specific behavior, identify the species whose
status is threatened and endemic in Ethiopian ecosystem. Biological Data Management
System also enables users to record samples for all of these entities of vectors, vectors borne
diseases and expressions information of diseases and traditional medicinal plants and other
production data. When new specimen name is published, a type specimen is designed. The
type specimen serves as an example of what the author means by the new specimen’s name
and it was permanently attached to the database. The label information from all our type
specimens has been registered and the data are available online through internet. BDIMS has
a site to visit flora and fauna, scientific research permit returns, comprehensive biological
survey program, and lists of endemic and threatened species, vector borne diseases and their
traditional medicines.

Our system contains the data of taxonomical differentiation of plants and animals exist in
Ethiopia ecology. Our database contains all animal and plant species including Endemic and
threatened species that exist in Ethiopian climax. The system also has the description of the
organisms in kingdom and regional locations in terms of longitude and altitudes. We will
design database for plants, animals, vectors, vector borne disease, traditional medicines, and
database for endemic, endanger species of Ethiopia.

BDIMS BY GROUP 7 VI
 .
III. TABLES OF CONTENTS

Contact Information .................................................................................................................................II

Intellectual Right Property Declaration ..................................................................................................III

Anti-Plagiarism Declaration .................................................................................................................. IV

I. Acknowledgement ............................................................................................................................ V

II. ABSTRACT .................................................................................................................................... VI

III. TABLES OF CONTENTS ............................................................................................................. VII

IV. Lists of Tables .................................................................................................................................. X

V. Lists of Figures ................................................................................................................................ XI

VI. ABBREVIATIONS ....................................................................................................................... XIII

CHAPTER ONE ......................................................................................................................................1

1.1.INTRODUCTION .............................................................................................................................1

1.2. BACKGROND .................................................................................................................................2

1.3. STATEMENT OF THE PROBLEM ................................................................................................3

1.4. PURPOSE OF THE SYSTEM .........................................................................................................3

1.5. OBJECTIVES OF THE PROJECT ..................................................................................................5

1.5.1. GENERAL OBJECTIVES ............................................................................................................5

1.5.2. SPECIFIC OBJECTIVES ..............................................................................................................5

1.6. METHODOLOGY ...........................................................................................................................5

1.7. SCOPE AND LIMITATION OF THE PROJECT ...........................................................................7

1.7.1. SCOPE OF THE PROJECT ..........................................................................................................7

1.7.2. LIMITATIONS OF THE PROJECT .............................................................................................7

1.8. FEASIBILITY STUDY ....................................................................................................................7

1.8.1. ECONOMICAL FEASLIITY........................................................................................................8

1.8.2. TECHNICAL FEASIBILITY .......................................................................................................8

1.8.3. TIME FEASIBILITY ....................................................................................................................8

1.9. SIGNIFICANCE OF THE PROJECT ..............................................................................................8

BDIMS BY GROUP 7 VII

 .
1.10. WORK FLOW ................................................................................................................................9

1.10.1. GANTT CHART .........................................................................................................................9

1.10.2. ORGANIZATION OF THE PROJECT ................................................................................... 10

CHAPTER TWO .................................................................................................................................. 11

2.1.ANALYSIS .................................................................................................................................... 11

2.2.EXISTING SYSTEM ..................................................................................................................... 11

2.3.NEW SYSTEM .............................................................................................................................. 13

2.4.NONFUNCTIONAL REQUIREMENTS AND CONSTRAINTS ................................................ 13

2.4.1Security Consideration.................................................................................................................. 13

2.4.2User Friendly Interface ................................................................................................................. 13

2.4.3 Good Performance ...................................................................................................................... 13

2.4.4System Modification and Maintainability .................................................................................... 14

2.4.5 Availability .................................................................................................................................. 14

2.4.6 Scalability .................................................................................................................................... 14

2.4.7Reliability ..................................................................................................................................... 14

2.5.FUNCTIONAL REQUIREMENTS ............................................................................................... 14

2.6.USE CASE DIAGRAM ................................................................................................................. 17

2.7.USE CASE DOCUMENTATION ................................................................................................. 19

2.8.SEQUENCE DIAGRAM ............................................................................................................... 35

2.9.STATE CHART DIAGRAM ......................................................................................................... 49

2.10.ACTIVITY DIAGRAM ............................................................................................................... 54

2.10. CLASS DIAGRAM ..................................................................................................................... 68

2.11. KEY ABSTRACTION WITH CRC ANALYSIS ....................................................................... 70

2.12. IDENTIFY CHANGE CASES ...................................................................................................... 71

2.13. USER INTERFACE PROTOTYPING ............................................................................................ 72

CHAPTER THREE .............................................................................................................................. 79

3.0.SYSTEM DESIGN ......................................................................................................................... 79

3.1.PURPOSE AND GOALS OF DESIGN ......................................................................................... 79

BDIMS BY GROUP 7 VIII

 .
3.2.Current Software Architecture ........................................................................................................ 80

3.3.Proposed System Architecture ........................................................................................................ 81

3.3.1 Subsystem Decomposition...................................................................................................... 83

3.3.2COMPONENT DIAGRAM ......................................................................................................... 89

3.3.3 DEPLOYMENT DIAGRAM ...................................................................................................... 90

3.3.4PERSISTENT DATA DESIGN ................................................................................................... 91

3.3.5ACCESS CONTROL AND SECURITY ..................................................................................... 92

BDIMS BY GROUP 7 IX
.
IV. Lists of Tables

Table 2.1 Use Cases and Actors Identification ......................................................................................... 17

Table: 2.2. Description for use case Authentication ................................................................................. 20

Table: 2.3. Description for use case create accounts ................................................................................ 21

Table 2.4 Description for use case Register New Data ............................................................................ 22

Table 2.5 Descriptions for Update Data Use case .................................................................................... 23

Table2.6.Description for Delete Data use case. ........................................................................................ 24

Table 2.7 Description for Access Data Use Case ..................................................................................... 25

Table 2.8 Description for View Data Use Case ........................................................................................ 26

Table 2.9 Descriptions for Query use case ............................................................................................... 27

Table2.10. Descriptions for Manage Profile use case............................................................................... 28

Table 2.11 Description for manage volunteers use case ........................................................................... 29

Table2.12 Description for Manage Forum use case ................................................................................. 30

Table2.13 Description for Manage Calendar Use Case ............................................................................ 31

Table2.14 Description for Participate in Forum Use Case ....................................................................... 32

Table2.15 Description for Manage Personal Profile Use Case ................................................................. 33

Table 3.1: Access control matrix for Biological Data Management System ............................................ 93

BDIMS BY GROUP 7 X
.
V. Lists of Figures

Figure1.1 Gantt chart ................................................................................................................................ 10

Figure2.1: Business rule Diagram ............................................................................................................ 12

Figure2. 3 Sequence Diagram for Create Account Use Case ................................................................... 36

Figure2.4: Sequence Diagram for Register Data use case ........................................................................ 37

Figure2.5: Sequence Diagram for Use Case Query Data ...................................................................... 38

Figure2.6: Sequence Diagram for Search Data use case .......................................................................... 39

Figure2.7: Sequence Diagram for View Data use case............................................................................. 40

Figure2.8: Sequence Diagram for Delete Data use case ........................................................................... 41

Figure 2.9: Sequence sDiagram for Manage Profile use case .................................................................. 42

Figure2.10: Sequence Diagram for Use Case Manage Forum ................................................................. 43

Figure2.11: Sequence Diagram for Manage Volunteers Use Case........................................................... 44

Figure2.12: Sequence Diagram for Manage Calendar Use Case .............................................................. 45

Figure2.13: Sequence Diagram for Update Data Use Case ...................................................................... 46

Figure2.14: Sequence Diagram for Manage Personal Profile Use Case................................................... 47

Figure2.15: Sequence Diagram for Change Password Use Case ............................................................. 48

Figure2.16: State chart Diagram for Authentication................................................................................ 49

Figure2.17: State Chart Diagram for User Management class ................................................................. 50

Figure2.18: State chart Diagram for Data Management .......................................................................... 51

Figure2.19: State chart Diagram for Query Builder ................................................................................ 52

Figure2.20: State chart Diagram for Forum Management ....................................................................... 53

Figure2.21: Activity Diagram for Authentication Use Case .................................................................... 54

Figure2.22: Activity Diagram for Create Account Use Case ................................................................... 55

Figure2.23: Activity Diagram for Register New Data Use Case .............................................................. 56

Figure2.24: Activity Diagram for query Data Use Case........................................................................... 57

Figure2.25: Activity Diagram for Update Data Use Case ........................................................................ 58

Figure2.26: Activity Diagram for Access Data Use Case ........................................................................ 59

BDIMS BY GROUP 7 XI
.
Figure2.27: Activity Diagram for Search Data Use Case ......................................................................... 60

Figure2.28: Activity Diagram for Delete Data Use Case ......................................................................... 61

Figure2.31: Activity Diagram for Manage Forum Use Case .................................................................... 62

Figure2.32: Activity Diagram for Manage Volunteers Use Case ............................................................. 63

Figure2.33: Activity Diagram for Manage Profile Use Case ................................................................... 64

Figure2.34: Activity Diagram for Manage Calendar Use Case ................................................................ 65

Figure2.35: Activity Diagram for change Password Use Case................................................................. 66

Figure2.36: Actors Functions Biological Data Management System ...................................................... 67

Figure2.37: CRC Diagram for Biological Data Management System...................................................... 70

Figure2.38 Database Client Home page (photo [9]) ................................................................................. 73

Figure2.39 User Interface to Create New Account (photo [9]) ................................................................ 74

Figure40 Traditional Medicines registration page (photo [8]).................................................................. 77

Figure 3.1 System Architecture Design Diagram of Biological Data Management System .................... 82

Figure3.2 Subsystem Decomposition for Biological Data Management System (BDIMS) ..................... 83

Figure3.3 subsystem Decomposition for Resource Management subsystem ........................................... 84

Figure3.4 subsystem Decomposition for Flora/Plants Data subsystem .................................................... 84

Figure3.5 subsystem Decomposition for Fauna/Animals Data subsystem ............................................... 85

Figure3.6 subsystem Decomposition for Insects Data subsystem ............................................................ 85

Figure3.8 subsystem Decomposition for Traditional Medicines Data subsystem .................................... 86

Figure3.9 Subsystem Decomposition for Query Builder subsystem ........................................................ 87

Figure3.10 Subsystem Decomposition for User Management subsystem. ............................................... 88

Figure3.11 Component Diagram of Biological Data Management system .............................................. 89

Figure3.12 Deployment Diagram for Biological Data Management system............................................ 90

Figure3.13 Database Schema Model of Biological Data Management System ....................................... 92

Figure3.14 Access control Model Diagram .............................................................................................. 92

BDIMS BY GROUP 7 XII

.
VI. ABBREVIATIONS
Name given to our project title Web Based Biological Data
BDIMS Management System for Ethiopian institute of biodiversity
Biological diversity
Biodiversity
Traditional Medicines
TraMed

Traditional medicines of Humans

TraMHuman

Traditional Medicines of Animals

TraMAnimal

Traditional Medicines of Plants

TraMPlant

Diseases of Human
DHuman

Diseases of Animals
DAnimal

Diseases of Plants
DPlant

class Responsibility Collaboration

CRC

The user id of the Administrator

AdminId

Unified Modeling Language

UML

My structured Query Language

MYSQL

Hypertext Preprocessor
PHP

: Cascading style sheet

CSS

Graphical User Interface

GUI

BDIMS BY GROUP 7 XIII

.

CHAPTER ONE

1.1. INTRODUCTION
Ethiopia is one of the richest countries in biological diversity which have different species of
flora and fauna. Biological inventory and monitoring data should be stored and managed in
computer database to facilitate its effective analysis and use with regard to biological data
management. Biological data management systems in academic settings were originally
confined to relatively small individual scientific groups or laboratories these systems were
often limited to specialized data sets and analysis operations and were developed by analyzing
workflows, heterogeneity, evolution, and scalability issues. Addressing such problems
requires a systematic process for analyzing the data structure and operations for application
domain. This process entails substantial digitization which is especially difficult to maintain
biological data whose semantics are complex and tend to evolve. These data are generated via
processes that involve multiple transformations between different levels of data granularity
and are based on evolving technology platforms and computational methods. In spite of this
complexity a systematic application domain analysis process and comprehensive
documentation are essential for providing effective data analysis support and to address this
frustration scientists often encounter in dealing with public biological data management
systems.

Our aim is to assist biologists, biological laboratory industries, researchers, biodiversity

institutes managers, and governmental or public organizations in their research through the
development of the web site for the integration of biological data distributed over the web, and
we placed in very particular context that is the study of different species of biodiversity in
Ethiopia ecosystem.

BDIMS BY GROUP 7 1
.
1.2. BACKGROND
Ethiopia institute of biodiversity is a national organization for the collection, collection
management, analysis and dissemination of Ethiopian biological diversity. Biological data are
key requirement for understanding our natural surroundings, for tracking change in our
environment and for gaining a greater insight on how we benefit from, impact upon the
ecosystem goods and services provided by the biological diversity. Biological data
management includes the traditional areas of data generation, acquisition, modeling,
integration, and analysis.
Web based biological data management system for Ethiopia institute of biodiversity is a web
based application for collection of species, vector bound diseases and traditional medicines
data, store, and manage of those data that are exist in Ethiopian ecosystem. BDIMS is web
based system that enables researchers, biologists, laboratory experiment workers to access the
biological data and record specific properties of species, diseases and traditional medicines.
Ethiopia is one of the richest country in fauna and flora species in the different parts of the
country. But those plenty of diverse life is not digitized in one system to share and manage
the biological data online through internet. In order to resolve this problem we will develop
Biological data management system for Ethiopian institute of Biodiversity.
The system will have the components of species (includes flora/plant biodiversity,
Fauna/animals biodiversity, which includes endemic and endanger species of Ethiopia),
traditional medicines that Ethiopian society use, vector Bourne diseases, microbial and insect
biodiversity.

BDIMS BY GROUP 7 2
.
1.3. STATEMENT OF THE PROBLEM
It is not secret that Ethiopia is country of many diverse fauna and flora species, bacteria,
lichens and mosses in the wild ecosystem. And also Ethiopia is known with its traditional
medicines in the rural society with different areas of the country. But many of those species
are not identified for use and management under one system. This makes hard to proof the
traditional medicines scientifically and to get information of those species easily. So as to
develop this system we identify the following problems;

 Ethiopia is country of biodiversity in all parts of the country and those biological diversity
data are not registered in database, and are not accessible through internet.
 Ethiopia has not an organized system that manage its biological data of its biodiversity
wealth exist in different ecosystem.
 High rate loss of genes, species, ecosystem and human knowledge by lack of well-defined
system for scientists and biological data initiative groups to conserve the gene of species.
 There is no system that helps to indicate species whose status is vulnerable to extinct,
endanger, normal and abundant and where it is.
 There is no web based system that guides investors, bio researchers, nongovernmental and
governmental organizations to distinguish species and their latitude and longitude
locations.
 No system which provides mechanism to assess the biological diversity of Ethiopian
ecosystem.
 There is no automated system for scientists that display the species information and to
prove traditional medicines.
 No database is exists in Ethiopia for plants species, animals, vectors, diseases, traditional
medicines which accessed through web applications.
 There is no automated database for endemic and endanger plants and animals (species)
exist only in Ethiopian ecosystem.
 There is no database of vectors, diseases and their traditional medicines for (human, plants
and animals).

1.4. PURPOSE OF THE SYSTEM

Web based biological data management system (BDIMS) is online system aiming to support
Ethiopian biodiversity management sectors to manage all the biological data online. Ethiopia
Institute of Biodiversity is national institution having the objective of conservation;
sustainable use and equitable share of Biological diversity exists in Ethiopian ecosystem. So
as to manage and share those huge life data web based online system has priceless advantage.
Our system will provide the following advantages;
 The system will be designed to support life based data management.
 The system will use as an advertisement of biological heritage of Ethiopia and easy
compass for local people and competent institutions for conservation and sustainable use
and share of biological diversity.
 The system will use to collect the species that are used by the society to prepare traditional
medicines for further proofs.

BDIMS BY GROUP 7 3
.
 BDIMS will use to coordinate in-situ and ex situ gene bank institutions through internet
share information of the biodiversity (data of plants, animals, vectors, vector borne
diseases, traditional medicines of plants, animals and humans).
 BDIMS will use to indicate land escape and geomorphologic highlights as visitors travel
from one ecosystem to another for the thematic biological diversity tourism market.
 The system will use as site for Studies of biodiversity generated extensive data, requiring
efficient means of keeping track of the information and making it available through web
network.
 The system will be modular in design to incorporate new characteristics of species
 The system is readily accessible and user friendly, with appropriate levels of information
access for various Ethiopian bioscience sectors.
 The system permits entry of biological data inventory and storage and retrieval of those
data into a central repository. All data should be available via internet technology.
 The system will be dynamic in order to keep pace with changing technological
development, new biological procedures, and upgrade to computer hardware and
application software.
 The system should be developed using an effective database design that is based sound
software engineering principles.
 Biological data should be properly stored, digitally documented, and archived to protect
against loss.
 BDIMS will implement and adhere to common set of data standards to assure data
consistency, improved data quality, and common data structure for exchange information
and make sound management actions in national and regional scale.
 BDIMS will use to investigate the extent, distribution and geographical locations of
species diversity of the target populations using natural markers.
 BDIMS will use to identify specific priority areas for conservation action primary and
secondary Centre of biodiversity.
 The system defines the current status of pressures on, priority actions for ensuring
biological data conservation, sustainable use and equitable share of benefits accrued from
Ethiopian biological diversity.
 Generally the system will used to make rapid assessment of monitoring biodiversity loss or
gain by making a continuous assessment on the nature of habitat and disturbance regions.
Also it is will use to evolve species habitat relationships by mapping biological richness
and gap analysis and prioritizing conservation and bio prospecting sites

BDIMS BY GROUP 7 4
.
1.5. OBJECTIVES OF THE PROJECT

1.5.1. GENERAL OBJECTIVES

The objective of the project is to develop a secured web based biological data management
system for Ethiopian Institute of biodiversity. The overall objective of our project is to
develop a secured system which will help to manage the biological data for conservation,
promotion and sustainable utilization of the country’s biological diversity wealth.

1.5.2. SPECIFIC OBJECTIVES

The aim of this project is to develop a secured web based biological data management system
with the following specific objectives:
 To develop user friendly system that is easily accessible by biologist, researchers,
botanists, and zoologists.
 Develop system that will register, manage, access, and share biological data online through
internet.
 To keep track of biological data information in structural database and develop national
site for those data and make accessible online.
 To document digitally local knowledge of the society on uses of traditional medicines over
vector borne diseases and adaptive traits species.
 Develop system which is easy to assess periodically countries biota and capacity, identify
an evolving set of priorities and actions for responding to new opportunities and prepare
different reports to government, society and to make convention on their findings and
conclusions.

1.6. METHODOLOGY
The project is aimed to develop web based biological data management system for Ethiopian
institute of biodiversity. Because of the heterogeneity of biological data in the Ethiopian
ecosystem we must use different software development tools, data gathering techniques,
programming languages, design and analysis techniques.

 REQUIREMENT GATHERING TECHNIQUES

The project we proposed will be started from requirement elicitation technique. The software
process that we follow is iterative software development approach type since we discuss and
correct our errors with our advisor frequently. When eliciting requirements we will follow
those steps. Introspection which means mental thought of the requirement engineering we use
it as the way of starting point for elicitation.

To collect data about the problem and the requirement of the existing system we use the
following methodologies;

Written document: in this method of requirements elicitation technique, we tried to read

different papers that states about Ethiopian biodiversity and their management. We go to
college of agricultural and veterinary medicine campus of Jimma University and we interview
two biodiversity expert lecturers.

BDIMS BY GROUP 7 5
.
 REQUIREMENT MODELING
After the requirements are fully elicited, the next step to be done is analysis model. This
model is a bridge to design model. Analysis model focus on the requirement that is visible
within the problem. Each element we analyze will add to an overall understanding of the
software requirements and provide insight into the information domain, function and behavior
of the system.
To develop our system we use Object-Oriented Modeling Approach because object oriented
modeling approach gives the following benefits;
 The ability to tackle more challenging problem domains.
 Reusability of analysis, design, and programming results
 Increased consistency among the models developed during object-oriented analysis,
design, and programming.
 The Object-Oriented modeling use Unified Modeling Language (UML) to allow the
modeler to specify, visualize and construct the artifacts of software systems, as well as
business models by the use of:
 Use cases
 Class diagrams
 State diagrams
 Sequence diagrams
 Subsystems diagrams
 Persistent database schema

 TOOLS USED
To develop this system we need different hardware requirements and software requirements.
The system requires to a minimum, a computer with the following description:

1. HARDWARE REQUIREMENTS

We use the following hardware tools in order to accomplish our project.

 Monitor: Liquid Crystalline Display (LCD), Cathode Ray Tube (CRT).
 Processor: Intel, Corei3
 RAM: 128 MB (In order the system to run faster)
 533 MHz bus speed
 40 GB of Hard Disk Drive (HDD)
 Internal NIC (Network Interface Card)
 Keyboard
 Mouse
 Flash

2. SOFTWARE REQUIREMENTS
 Programming Environment (Front End): PHP, JavaScript, CSS

BDIMS BY GROUP 7 6
.
 Database (Back End): MySQL Server
 Operating system: Any operating systems have no effect on the proposed system
 Gantt chart: For design of work flow diagram
 VERTRIGO with PHP and MYSQL, apache server
 Notepad++ used as an editor.
 Microsoft word: used for documentation.
 Smart draw to draw use case diagram, sequence diagram, and activity diagram, class
diagram
 Micro Soft Access database relation used for draw persistent database schema diagram
 Web browser and latest antivirus with internet connection: Firefox, chrome

1.7. SCOPE AND LIMITATION OF THE PROJECT

1.7.1. SCOPE OF THE PROJECT

The scope of system is intended to support the collection and registration, arrangement,
management of the biological data exists in Ethiopian ecosystem. BDIMS intended to be
usable by all levels of government and the nongovernmental private sectors. The system will
have capability in the storage, manipulation of the species data, and effective search of the
information of specific species and their available data. In this component data will be
returned from the field which may be most useful. This includes kingdom, phylum, class,
order, family, genera, and species taxonomy information on the morphological behavior likes
stems, roots, leaves of flora, breeding system of fauna and flora. Also our system have
information component of traditional medicines that used by the society traditionally and the
vector borne diseases. Each component (plants, animals including endemic and threatened
species of Ethiopia, vectors, vector borne diseases and traditional medicines) have automated
database to make accessible through internet.
BDIMS will be develop by defining information required by a prospective user to determine
the availability of set of (biological data includes plants, animals, vectors, diseases, traditional
medicine) exist in Ethiopian biodiversity ecosystem; to determine the fitness of set of
biological data for an intended use; to determine the means of accessing the set of Ethiopian
biological data in different industries and laboratories; to transfer set of biological data
successfully.

1.7.2. LIMITATIONS OF THE PROJECT

When we develop this system the following limitations are identified. The major difficulty in
biological data community is lack of information that helps the prospective user to determine
that data exist in the ecosystem. Challenges of biological words, overlapping of species
property and functional rolls are dynamic to differentiate. Biological data is broad and diverse
to arrange and register in database. Scalability of the system with the growing technology is
another limitation.

1.8. FEASIBILITY STUDY

BDIMS is web applications that used to manage Ethiopian biological data online. Because the
system is online so it used for managing, registering, searching of the species of plants,
animals, microorganism, with its specific characteristic is easy. Collecting traditional
medicinal species and vector borne diseases in one digital system are another use.

BDIMS BY GROUP 7 7
.
1.8.1. ECONOMICAL FEASLIITY
We assess the economic feasibility of our project implementation alternative the basic
question we will answer is does the project make a financial sense? And we do this by
performing a cost/benefit analysis, by comparing the full/ real costs of the application to its
full financial benefit. By considering this we include both qualitative and quantitative factors
of costs or benefits for which monetary values can easily identify as follow:
The system reduce the hardware/software upgrade costs, requires minimum labor cost by
reducing the personal cost for biological data collection, management and storage. BDIMS
supports cost for application to increase the organization revenue. BDIMS provides accurate
and secured information about the species to maximize improved decision. It will avoid
employee dissatisfaction from fear change and negative public perception from layoffs as
automated.

1.8.2. TECHNICAL FEASIBILITY

Institute of Ethiopian biodiversity is national institute that asserts to conserve the biological
diversity of Ethiopia. The institution has power to use biotechnology tools to manage those
huge life data. Our project is technically feasible because there is absolute range of technical
equipment. As access of network becomes the driving force of today’s market and
organizations, biological data management system must be supported by these technologies.
Applying this network for data of biodiversity is will have value to biologists, botanists,
zoologists, and many other naturalists. The system is entirely web based, so that it is easy for
registering, managing, or manipulating biological data and searching species, traditional
medicines used by Ethiopian community and the vector borne disease and their data.

1.8.3. TIME FEASIBILITY

We accomplished the document of our project based on the time table as we indicate by the
Gantt chart as below under the work flow. So we will finish all the attribute of the document
with in specified time according to the department schedule given for us. We start half of
October 2014 GC and continue on our project until the submission date on the first of
February 2015 GC by spending different time duration on different stages of our project.

1.9. SIGNIFICANCE OF THE PROJECT

Our web facilitates the collection of biological diversity, diseases and traditional medicines
data for biologists to search among heterogeneous and distributed data in public or private
data sources on the web. BDIMS particularly helps them to analyze specific characteristics of
species, by building a platform for integrating biological data. The system provides the
following significance;

Store biodiversity data: The proposed system provides mechanism to save, manage, and
secure biological data easily. Restrict access to data by giving rights to given tables, fields and
records. Perform identification clustering of new discovered strains or specimen.

In museums: Store any kind of biological data such as yeast, plants, insects, and animals. The
integrated biological data is easy to use and can help us to keep track of all the steps
performed in the laboratory.

BDIMS BY GROUP 7 8
.
In industries: Industries can create their own tables, fields, records and store and manage
their data easily. Industries can get information about the species that used for traditional
medicines and other source that are available for their factory easily. Analyze the data and use
the results for the prediction of new products or the development and improvement of current
products.

In hospitals: Hospitals can be used the system to identify new vector cause pathogens by
analyzing the microorganism’s morphology and the results could be used for the prediction of
new medicine. Hospitals can easily get the list of medicinal plants exist in Ethiopian
biodiversity climax.

In universities: Biological data in educational institutions is one of the tools to train students
in medical, environmental, biological and other fields of study. The system reduces the load
of work for finding the specific biological and morphological characteristics of organisms by
digitally documenting the organism’s unique behavior, habitat, latitudinal and longitudinal
existence, nomenclature. So that students, teachers and biologist can access the information
easily through network.

In culture collections: Store all kinds of strains or specimen information in one system. Enter
new data or import large amount of data in the database. Share data online and make it
possible to order new culture online or deposit new information through the web. Keep track
of the number of stocks in the collection and manage easily. It is simple to identify new
species based on the data available in the database.

1.10. WORK FLOW

1.10.1. GANTT CHART

This section should describe how each immediate project objective will be carried out in terms
of planned activities, their timing and duration, and who will be responsible for each activity.
Any project which involves multiple activities and deadlines require some form of
management. using simple project management techniques will allow us to keep control of our
project to schedule more effectively, to identify how much time you have to spend on each
stage of the project to create intermediate goals /millstones that will tell us if we are on
schedule or not (and be able to respond accordingly), and will give us clear oversight of the
progress of our project as a whole. One simple but highly effective technique is to produce a
Gantt chart. This provides a clear visual plan of the project, based on scheduling the different
stages of our project in time.

BDIMS BY GROUP 7 9
.

Figure1.1 Gantt chart

1.10.2. ORGANIZATION OF THE PROJECT

This document consists of five chapters. The first chapter is an introduction for Web based
biological data management system. It includes description, objective, scope, and significance
of the system. This chapter also includes the description about methods for data collection,
requirement elicitation and the model that we follow to develop the system. Chapter two is
about requirement specification and analysis. In this chapter we will try to identify the
functional and non-functional requirement of the overall system. The third chapter is about the
design of the system. Chapter four is the phase of implementing or writing the code of the
system based on the design. And the last chapter is testing the implemented system.

The document is divided into different parts for better understanding, the document above this
line can be considered as part one.

BDIMS BY GROUP 7 10
.

CHAPTER TWO

2.1. ANALYSIS

Introduction: The purpose of this document is to differentiate the functional and

nonfunctional system requirements that represent the characteristics of the biological data
management system. Those requirements are used by the developers and will use for
validating the final delivered system. In this section we deeply describe our system in terms of
use case diagram, sequence diagram, activity diagram, state chart, class diagram, database
schema, class responsibility collaboration diagram and user interface.

2.2. EXISTING SYSTEM

In Ethiopia biological data management is the responsibility of the institute of Ethiopia
biodiversity and the community as the whole. So that the institute follows its own rule and
regulations for management, collection recording, register new species, diseases and
traditional medicines, and making assessment on the diversity. The institution tracks the
information of both territorial and aquatic species of flora, fauna, vectors, insects, vector borne
disease and traditional medicines of plants, animals and humans, and document it in proper
way, then puts in Herbarium, museum or any Gene banks. The information is recorded in
system that cannot be accessed at any time and everywhere through internet. This is the main
difficulty of scientists, biologists, environmental and conservation initiative groups, the public
and others. When someone wants the data of specific plants, animals or traditional medicines
he/she cannot get it without visiting the National herbarium of Ethiopia institution of
biodiversity. This is very time consuming, tiredness and not available at exact time and place.
The current system has the following features;

Registration of new species: when new species or new feature of species is discovered, the
discovery owners writes the information of the new biological data manually on paper and
send to the national institution of Ethiopian biodiversity or any regional gene museum. The
institution records and documents the necessary data of the species and put in the herbarium or
in museums.

Access of information: The data of the biological diversity cannot be accessed from
anywhere. Because no automated national/central database are exist that stores the data of
Ethiopia plants, animals, vectors, vector borne diseases, traditional medicines and list of
endemic and endanger species. The accessing of this huge information needs getting printed
document or walking to national museum or national herbarium in Addis Ababa or near
biological museum if exist. This is upsetting and tiredness. Generally in Ethiopia there is no
distinguished database of Ethiopian species that can be accessed through internet. Searching
and getting the species data is time taking and boring. Endemic species that exist only
Ethiopia is our heritage have no their distinguish database, they cannot be advertised.
Traditionally Ethiopian communities are used plants and animals for preparations of
traditional medicines unfortunately; the species that are used for these applications are not

BDIMS BY GROUP 7 11
.
collected in one system so this is difficult to prove medicinal values of the species
scientifically. No means are exist to adversities Ethiopian wealth in species diversity for
investors, because the species data are in the hands of the community living in the different
territory of the country.

BUSINESS RULES
A business rule is an operating principle or policy that our software satisfies. A rule can enforce
business policy, make a decision, or infer new data from existing data. This includes the rules and
regulations that the system users should abide by. This includes the cost of the project and the discount
offers provided. The users should avoid illegal rules and protocols. Neither administrator nor the users
should cross the rules and regulations. We try to embed the business rule of our system in structural
requirement artifacts because those rules are uncovered during elicitation activities for the
requirements. We try to identify our system business rule during the normal course requirement
gathering and object oriented analysis. In our system we will identify business rules using use case
model documents for behavioral (functional) requirements, and domain model documents for the major
business concepts and their relationship pertinent to a system. The overall business rules of our system
are described below in the form of diagram [5’].

Figure2.1: Business rule Diagram

BDIMS BY GROUP 7 12
.

2.3. NEW SYSTEM

The system that we will develop gives the correct solutions for the challenges described above
in the existing system analysis. Our system records the data of plant species, animal species,
vectors, vector borne diseases, and traditional medicines in automated database to make
accessible in anywhere through internet. Our system holds information about classification of
plants, Animals, traditional medicines of human, animal, and plants, vector borne diseases and
vectors. Also we design database for those plants and animals used as a source of traditional
medicines for making available for further scientific proofs. And we also design a database for
endemic and endanger species of Ethiopia for identifying them and record on the web based
system. We design query builder for advanced search mechanism. This helps the users of our
system to get full information of vector borne diseases with their causal vector and traditional
medicines that used to treat the diseases. Also it will used to display the information of species
in structural file format.

For developing this system we will identify the following functional and nonfunctional
requirements.

2.4. NONFUNCTIONAL REQUIREMENTS AND CONSTRAINTS

Non-functional requirements are requirement constraints and quality standards that the system
we are building will adhere to. We are finding out what these non-functional requirements
should be by reading documents and interviews. Also, we can use try and discover what non-
functional requirements will be. Here are some areas that we will have in our non-functional
requirements document. Our system will have the following nonfunctional requirements:

2.4.1 Security Consideration

The system allows its user to perform their task only after login process. The user will be
accompanied with the legible account and password otherwise they won’t be allowed. All
users have access only their own interface. Normal users can just read information but they
cannot edit or modify except their personal information.

2.4.2 User Friendly Interface

The system will have consistent user interface formats and button sets for all forms in the
application will have a form based interface for all data entry, viewing, search formats and
will generate reports that are formatted in table and that should look like the existing manual
report format for user friendliness. We will develop a query builder for advanced search
mechanisms to make user friendly for computer and non-computer science customers.

2.4.3. Good Performance

The system is capable of carrying huge amount of data with many related databases. The
system carries information sufficiently. In our system when user requests or want to operate
some task, the system responses what the user request quickly to satisfy the user need.

BDIMS BY GROUP 7 13
.
2.4.4. System Modification and Maintainability
Maintainability of a system is the effort required to locate and fix an error in the operational
program. So that we will try to write comment when we write the code of the program to make
it easy to locate and fix error. The final software implementation of this project will be a
flexible. The software will be built in such a way that most of the major functionalities can be
accessed from any interface. We will make the coding of the software flexible, fault tolerant
and easy to diagnose.

2.4.5. Availability
System availability is the time when the application must be available for use. Required
system availability is used in determining when maintenance may be performed. Definitely we
think about time zones, schedules, and user location. The system is available everywhere
which have internet access. The system will be operable.

2.4.6. Scalability
The system will be scalable by modifying the source code when additional feature exists. Our
system will iteratively scalable because of the data of biological entities are huge and
different. Each biological entity will have specific component with huge database that contains
those data. In the current time we will implement some parts of the biological wealth of
Ethiopia so the system will scalable for future advancement of technology in satellite and
internet.

2.4.7 Reliability
Reliability is the chance that the system processes work correctly without being aborted. The
system will fault tolerant and run on a machine to generate precise output.

USER CONSTRAINT
The graphical user interface (GUI) supports English language. And Amharic language for
traditional medicines interfaces because most species that are used for the preparation
traditional medicine are in the hands of public who does not know the common name of the
species (flora). All users of the system will have user name and password (for identification)
to login and use the system. The database holds only biological data of Ethiopian biological
diversity.

SYSTEM REQUIREMENTS:
The software and hardware components of the computer system are required to install and use
the software efficiently. If the computer system does not meet the system requirements the
software may not work correctly.

2.5. FUNCTIONAL REQUIREMENTS

A functional requirement describes the relationship between the system and the user or the
environment. Here the relation means the direct and indirect interactions between users and
the system. The system has the information components needed for assessing Ethiopian
species biodiversity. The system gives different service based on the type of the user.

BDIMS BY GROUP 7 14
.
We have three actors in our system, those are

Administrator
Staff members and
Client Users

The features that are available to the Administrator are:-

Query: used to search and build complex data from different related database tables. It is used
for searching in species, disease, vectors and traditional medicines data and lists. In this stage
we design query builder for searching data of related tables and those data are available by
appropriate queries.

Authentication: the administrator must use his/her user name and password to login the
system.

Register New Data: The administrator can register list of species and information of the
species (plants, animals, vectors, vector bound diseases, traditional medicines).

Update Data: The administrator has power to delete, modify, and edit the species (plants,
animals, diseases, traditional medicines) information/data.

Access Data: The administrator can search the list of the species and the information of the
species available in the database. And can view all the data of the species (flora, fauna,
diseases, vectors, traditional medicines) from the database.

Manage Profile: The administrator can manage the profile of the system and by editing,
resizing and uploading the profile of the system. He/she can edit the title of the system. The
administrators also create accounts for staffs and view all the staff member and Client users
profile.

Manage Calendar: He/she can date the availability of service of a specific activity or data for
members by managing the calendar of the system.

Manage Forum: the administrator of the system can assign discussion panel, seminar, tours,
and decide who the participant is and address the forum for members through their account.

Manage Volunteers: The administrator of the system can grant volunteers participating in the
conservation, usage of the existing biological data.

Client Users:

The features that are available to the client user are:-

Create User Account: The system will allow the user to create user account and register in
the system.

Query: used to search and build complex data from different related database tables. It is used
for searching in disease, vectors and traditional medicines data relation.

BDIMS BY GROUP 7 15
.

Register New Data: the client user can upload new species data, the occurrence of diseases of
plants, animals, and humans, discovery of traditional medicines.

Access Data: After the user creates account once they login in the system and can access the
information of the species from the national database of plants, animals, and vectors, diseases
and traditional medicines.

Participate In Forum: The clients can participate in any discussions, forums and seminars
invited by the administrator of the organization.

Manage Personal profile: The client user and the can change their personal information.

Staff Members
The staff of institute includes researchers, laboratory technicians, field assistants and finance
officers and other supportive staffs.
The features that are available to the staff members are:-

Query: used to search and build complex data from different related database tables. It is used
for searching in disease, vectors and traditional medicines data relation.

Access Data: The staffs of the institution will have the right to view members of the system.
And they also view the information of plants, vectors, disease and the traditional medicines
database.

Register New Data: The staff members can register data of plants and animals’ species,
diseases, traditional medicines and vectors species.

Change Password: The staff members have the right to change their account password
created by the administrator and manage their personal information created by the
administrator.

Manage Volunteers: the staffs can check the members detail and can grant access privileges.

BDIMS BY GROUP 7 16
.

2.6. USE CASE DIAGRAM

A system use case model describes the potential usage of the proposed system. It is part of the
analysis document which consists of use case describes sequence of actions that provide
measureable value to an actor and it’s drawn as horizontal eclipse.

An actor is a person, system, or real object that plays a role in one or more interactions with
the system. Relationship between actors and classes are indicated within use case diagrams. A
relationship exists whenever an actor is involved with an interaction described by a use case.
The rectangle around the use case is called system boundary and the name suggests it indicates
the system and the use cases inside the rectangle represent the functionally that the system
intended to implement.

Our system will have the following use cases and actors

Actors Use cases

Authentication
Manage Profile
 Administrator
 Client Users Query
 Staff Members Access Data
Register New Data
update Data
Manage Calendar
Manage Forum
Manage Volunteers
Create Account
Change Password
Participate In Forum
Manage Personal Profile

Table 2.1 Use Cases and Actors Identification

BDIMS BY GROUP 7 17
.

Figure 2.2 Use Case Diagram for Biologial Data Management System

BDIMS BY GROUP 7 18
.

This is the broad level diagram of the project showing a basic overview. The users can either
the client users or the staff members. This system provide a search functionality to facilitate
the search of biological resources. This search will be based on various categories via name of
data being searched. Further the administrator can add, update resources and resource users in
the system. The users of the system can request th system to access data, also can upload new
data of plants, animals, vectors, Vector borne diseases and traditional medicines.

2.7.USE CASE DOCUMENTATION

In this stage we document our use case with its corresponding participant actors and system
interactions. Use case documentation holds all the description of the use case in the form of
tables. In this part of the document we describe each use case activities, the participant actors
and the interaction of the system and the actor on the use case. The flow of events starting for
the initial to the end of the use case is briefly described.

 Use Case Diagram Description

BDIMS BY GROUP 7 19
.

1. Authentication

Use case Number UC01

Use case name Authentication

Actors Administrator, Staff Members, Client Users

Description Login the system by user name and password

Pre-condition Each user must have User name and password.

Basic course of action 1. The system displays request for user name and Password;
The LOGIN button is displayed as well
2. The users enter user name
3. The users enter the Password
4. The users presses the LOGIN button
5. The system locates
5.1.If the user is Administrator, the Administrator Page is
displayed
5.2. If the user is staff member the Staff page is displayed
5.3. If the user is client user ,the Client users page is
displayed

Alternative actions If user name is not correct display message user name is not correct.

If password is not correct display message password is not correct

The system returns to step 2

Post condition The users Login the system and can access services of the system.

End use case

Table: 2.2. Description for use case Authentication

BDIMS BY GROUP 7 20
.

2. Create Accounts

use case number UC02

Use case name Create Accounts

Actors Client users, Administrator

Description In order to access the service of the system Client users must
registered in the system and must create their own account.

Precondition Web system must be available for users and the user must have
interest to use the system.

Basic course of Actions 1. The user enters in the system home page. In the home page press
“create account” button in the lower corner of the home page
interface.
2. The system redirects in create new account form.
3. In this page users must fill Name, password, email, experience
(optional), designation, field of interest, occupation, password
confirmation spaces.
4. User must press signup button.
5. After the user submits the necessary information for account, the
system checks name and email not exist in member list and the
password confirmation is correct and system displays you are
successfully.

Alternative Actions If the user enters name and email , which are member in the system
System displays message user name and email have already used.
If user enters different password and confirmation password, the
system displays message password confirmation is not correct. And
the system returns step2.

Post conditions Users create new account and can access the database of Ethiopian
biological diversity.

End Use Case

Table: 2.3. Description for use case create accounts

BDIMS BY GROUP 7 21
.

3. Register New Data

Use Case Number UC04

Use Case Name Register New data

Actors Administrator, Staff Members, Client users

Description The administrator or the staff member registers persistently

species/traditional medicines/ diseases data in the database. Client
users also upload new data and submit the data in the database.

Pre-condition The users logged in the system. The web server must be available.

Basic course of action 1. The user clicks on “register data button”.

2. The system redirects the species registration form.
3. In this panel the user selects options of databases.
3.1. The system provides options plant database, animal
database, disease database, traditional medicines database,
endanger species database, endemic species database.
3.2. User select database based on the information that the user
has.
3.3.System displays the correct form for registration of
selected species database.
4. The users must fill all the space available in the registration
form.
5. After the uses fills the space available clicks on the submit
button located in the lowest corner of the registration form.
6. The system redirects the information in the national
database through internet and displays message registered
successfully.

Alternative actions If the users not fill all the spaces available, the system displays all
spaces are not filled enter again.
If the users fill the form with incorrect data, the system displays
message you are entered incorrect data type, please enter the
correct data type.
The system redirects step 2& 3.3.

Post condition The data of the plants, animals, vectors, diseases, traditional
medicines are registered in species database.

End use case

Table 2.5 Description for use case Register New Data

BDIMS BY GROUP 7 22
.
4. Update Data

Use case Number UC05

Use case Name Update Data

Actors Administrator

Description One of the main characteristics of biological data is dynamicity.

So that modification and updating of data is needed frequently.
The administrator of the system updates the database.

Precondition The actors must be administrator of the system.

Basic course of Action 1. The Administrator enters his/her account (administrator

account) and selects the update species data button in the
upper corner menu in the home page.
2. The system displays search specific species data form. And
the Administrator fills the form press edit button.
3. The system displays the species data with editable form.
4. In this form the administrator can select options such as,
delete the data or edits and modifies the data.
5. The administrator selects from the options and does actions.
6. The Administrator Presses the submit button to submit in the
database if it is edition.
7. The system displays message successfully updated.

Alternative Action When the system administrator search species which is not in the
database system display not data found message and return step2.

Post condition The data of the specific species modified.

End Use Case

Table 2.6 Descriptions for Update Data Use case

BDIMS BY GROUP 7 23
.
5. Delete Data

Use Case Number UC06

Use Case Name Delete Data

Actors Administrator

Description When irrelevant data of species exist or when duplicate data for
the same species exist the administrator will delete the
unnecessary or redundant data.

Precondition The Actor must be administrator.

Basic course of Actions 1. The administrator opens the administrator account and
press the button delete data button.
2. The system display delete data page.
3. The administrator fills the form with species id or name
and press search button to retrieve the species data from
database.
4. The system retrieves the species data from database.
5. The administrator press delete button to avoid the data
from database.
6. The system avoids the data from database and displays
message data is deleting successfully.

Alternative Actions If the administrator does not select specific data of species and
press delete button, the system will display message select
species data and returns to select species data form.

Post conditions The irrelevant or redundant data of species deleted.

End use case.

Table2.7.Description for Delete Data use case.

BDIMS BY GROUP 7 24
.
6. Access Data

Use case number UC07

Use case name Access Data

Actors Administrator, Client users, Staff Members

Description Users select species of interest to search from national database of

biodiversity.

Pre-condition The user must be get available connection to Access data from the
system Service

Basic course of action 1. The login the system and click on the explore data button on
menu upper corner of the system panel.
2. The system redirects the search data form of the system.
3. The system shows options
3.1. Search information from flora database.
3.2.Search information from fauna database.
3.3.Search information from vectors and diseases data base.
3.4.Search information from traditional medicines database.
3.5.Search information from vectors database
4. Users select the option of interest
4.1. The system redirects in the form search by common name,
search by scientific name
4.2.The user enters what they want and press search button.
5. The system displays data of the selected species.

Alternative actions If the user enter unknown name, the system display data is not
correct.
If the user does not select options, the system displays check the form
message. And returns to step2.

Post condition The user can access the data species in interest and make models to
prove the behavior of the species.

End use case

Table 2.8 Description for Access Data Use Case

BDIMS BY GROUP 7 25
.
7. View Data
Use Case Number UC08

Use Case Name View Data

Actors Client users, Administrator, Staff Members

Description The users want to use the system application to obtain data for a
specific species from database.

Precondition Web system must be available; users want to use the system to
discover the datasets of a species.

Basic course of action 1. Users submits query for presence datasets to web system.
2. The system Mediation Services mediates the query request
distributing it to the Web System.
3. BDIMS Web System receives query and checks the presence of
data compatible to the query.
4. BDIMS intermediation Service obtains and provides Presence
datasets.
5. Users select one or more datasets returned by the query.
6. Users requests BDIMS to provide selected datasets.
7. Web intermediation Service mediates request for datasets.
8. BDIMS receives request and provides datasets.
9. Web intermediation Service provides requested datasets to
users.
10. Users receive selected datasets.

Alternative Action If the user requests data that is not exist in the database the BDIMS,
the system display message data not found. And system returns step
1.

Post condition Users view data of species

End Use Case

Table2.9 Description for View Data Use Case

BDIMS BY GROUP 7 26
.
8. Query
Use case number UC09

Use case name Query

Actors Client Users, Staff Members, Administrator

Description Querying the information of species, list and information of

species; discover of traditional medicines, proved behavior of
vectors, data of vector bound diseases to the national biodiversity
center.

Pre-condition Web system must be available.

Users have accounts, and proper interface and available query
builder method exist for users.

Basic course of action 1. The user enters in the system and logged in your account.
2. Select the database category on the menu in the user page.
3. The system automatically redirects to the query form.
3.1.In the query form select the menu for database, interest
category to search.
3.1.1.If the interest is in plants category select flora database.
3.1.2.If the interest is in animals category select fauna database
3.1.3.If the interest is in vectors category select the vectors
database
3.1.4.If the interest is in diseases category select the diseases
database.
3.1.5.If the interest is in traditional medicines category select
traditional medicines category.
3.2. After selecting the database of interest the system redirects
the query data form.
3.3.Users must fill all the necessary data of the interest, and
press search button.
3.4.System retrieves data from database and displays.

Alternative action If user does not select the interest category system display
message select database category.
If user dose not fill the space provided in the form system display
message fill all spaces.
The system returns step 3 and step 3.1.

Post condition The discover owner submit the data in the national database for
persistent storage and availability to all through internet for
further testament.

End Use Case

Table 2.10 Descriptions for Query use case

BDIMS BY GROUP 7 27
.
9. Manage Profile

Use case Number UC010

Use Case Name Manage Profile

Actors Administrator

Description The administrator manages all over system activities and decides
how the profile seems and he can view staff Members or the client
user’s profile.

Precondition Users must have account and interact the system through their
account.

Basic course of Actions 1. The administrator of the system logged the administrator page.
2. The administrator press manage profile button located on the
upper corner of the page panel.
3. The system redirects manage profile page
4. Under the manage profile click on manage organization profile
5. Select profile and edit, profile. Also the administrator creates
account for staffs.
6. He/she press view members profile button.
7. The system display user profile for view.
8. The administrator must able to upload and resize an image
acting as an avatar for the organization profile
9. The administrator change, post, and manage the profile of the
system.
10. The administrator must be able to upload a notional title for
organization profile.
11. The system must be able to display the national title selected
by the administrator.
12. The administrator must be able to select a parent organization
for the organization profile.
13. The administrator must be able to set a short description
describing the organization profile.
14. The administrator must be able to set a URL representing the
website for the organization.
15. The administrator must be able to add and remove colleagues
as coordinators for the organization profile.
16. Press on save then close.

Alternative Actions If the administrator does not select the profile the system assign the
organization default profile.

Post conditions System profile changed, new activities posted.

End Use Case

Table2.11. Descriptions for Manage Profile use case

BDIMS BY GROUP 7 28
 .
10. Manage Volunteers

Use Case Number UC11

Use Case Name Manage Volunteers

Actors Administrator, Staff Members

Description The administrator/Staff member of the system will add new members
with different experience and levels. And the administrator can
collaborate with different organization, NGOs, and volunteers group
for improvement of biological data usage and conservation.

Precondition The administrator/Staff members must get the availability of web

system. They enter into the system by the administrator account or
Staff account. The volunteer must send request to become as member
of the biological data Management system.

Basic course of Action 1. The administrator /staffs enter in the system.

2. The administrator/staffs will open manage volunteers page.
3. The system will display the notification from volunteers with
fields such as:
o Volunteers/group/ name.
o Experience
o Field of interest
o Aims of volunteers
o Designation
o Address
4. The administrator will analyze the information of volunteers and
give grant.
5. The system sends notification for the volunteers from
administrator that states about permission or forbidden.
6. The volunteers enter in the system with the account created
before and look the message from administrator.

Alternative Actions If the volunteers are member before the system displays you are
member and only add field of interest and aims of interest.

Post conditions Volunteers are registered and become member of BDIMS.

End Use Case

Table 2.12 Description for manage volunteers use case

BDIMS BY GROUP 7 29
.

11. Manage Forum

Use Case Number UC12

Use Case Name Manage Forum

Actors Administrator, Staff Members

Description System administrator will assign forum and discussion seminar

about species distribution, status, habitat, and availability of
biological resources, current conservation levels, vector
distributions, diseases and their traditional medicines.

Preconditions Web system must be available. Reason for making forum is exist.

Basic course of Action 1. System administrator login the system with administrator
account.
2. The system administrator press the manage forum button.
3. The system opens the manage forum page.
4. System administrator press assign forum button on menu the
upper panel of the page.
5. System displays options for assigning forum. In this page the
administrator performs the following actions
5.1.The administrator creates the forum topic.
5.2.The administrator differentiates the participant in the forum.
5.3.The administrator must decide the deadline time of forum.
5.4.The system administrator posts the forum.
6. If the administrator wants to delete the forum, he/she must press
the cancel forum button in the manage forum page.
7. The system cancels the forum assigned before and display do
you want assign forum option pane?
8. If the administrator wants to change the forum agenda he/she
will press edit forum button.
9. System display edits forum form. They can edit here and press
post again.

Alternative Action If the administrator dose not select forum title the system displays
“select forum title” message and returns to step 5.

Post conditions Forum about biological data managed.

End Use Case

Table2.13 Description for Manage Forum use case

BDIMS BY GROUP 7 30
.
12. Manage Calendar

Use Case Number UC13

Use Case Name Manage Calendar

Actors Administrator

Description The administrator will Manage calendar because different events

may occur and run on a specific period of time with the
requirement of different activities. So this period of time is set
by the administrator of the system.

Precondition The actors must enter in the system with administrator account.

Basic course of Action 1. The administrator opens the system with the administrator
account and press the manage calendar button.
2. The system display calendar of the system.
3. The administrator clicks on set calendar button locate on the
upper corner of the panel.
4. The system redirects the form with spaces to assign
calendar of the system with editable area.
5. The administrator edits the calendar and makes any
assessment based on the calendar assigned time period.

Alternative Action If the calendar of the not edits and modifies, the system will
continues with default time calendar.

Post condition The calendar of the specific event of our system set.

End Use Case

Table2.14 Description for Manage Calendar Use Case

BDIMS BY GROUP 7 31
.
13. Participate In Forum

Use case number

Use case name Participate Forum

Actors Client users, Staffs members

Description The client users and staff members can participate in any forum
posted by the administrator.

Preconditions The administrator post the title of the forum and users can look on
their profile.

Basic course of Actions 1. The client users or the staff members enter in the system with
their account and look the availability of forum, discussion
panels, meetings posted from administrator.
2. If there is forum the users can apply for participation through
their account mails and submit for the administrator.
3. The administrator of the system can send mils to them for
forum participants and can get from their mail accounts.

Alternative Actions If there is no post of forum exit.

Post conditions Users participate in forum discussions.

Use case end

Table2.15 Description for Participate in Forum Use Case

BDIMS BY GROUP 7 32
.
14. Manage Personal Profile

Use case number UC15

Use case name Manage personal profile

Actors Client users, Staff Members

Description The client users and staff members can manage their personal
information within their account.

Precondition The users must have user account in the system and web system
must be available.

Basic course of actions 1. The users open their home page account and click profile.
2. The system displays the users account details with editable
form.
3. The users can edit their personal information and can change
their profile.
4. Clicks save.
5. System checks all data edited by the user are correct. Then
display message profile successfully changed.

Alternative action If users enter wrong data type system display message incorrect
data and returns to step2.

Post conditions User change, edit their account profile.

End use case

Table2.16 Description for Manage Personal Profile Use Case

BDIMS BY GROUP 7 33
.
15. Change Password

Use Case Number UC16

Use Case Name Change Password
Actors Staff Members, Administrator, Client users
Description The staff members can change their account password and
also the administrator has privilege to change passwords of
the member account.
Preconditions Members must have account and change account password
must need for security issues.
Basic Course of Actions 1. The members login the system with old account
password and click on change password button.
2. The system displays form to change old password and
request the user to enter new password.
3. The user enters the new password and click on change.
4. System checks the password validity
5. Display message password changed successfully.

Alternative Actions If entered password is invalid system display message with

error type.
If user click on change without entering new password
system display message enter new password and return
step2
Post condition Account password changed.
End Use case

Figure2.17 Description for Change Password Use Case

BDIMS BY GROUP 7 34
 .
2.8.SEQUENCE DIAGRAM
Sequence diagram describe behavior as a sequence of messages exchanged among a set of
objects. Sequence diagram which is also known as interaction diagrams are one of the
diagrams used in UML, for modeling the dynamic aspects of the system. It shows an
interaction consisting of a set of objects and their relationship including message that may be
dispatched among them. It emphasizes the time ordering of messages. It shows an interaction
arranged in time sequence. In particular, it shows the instances participating in the interaction
by their lifelines and the stimuli that they exchange arranged in time sequence.

Users/admin

Figure2.3: Sequence Diagram for Use Case Authentication

BDIMS BY GROUP 7 35
.

Users

Figure2. 4 Sequence Diagram for Create Account Use Case

BDIMS BY GROUP 7 36
.

Figure2.5: Sequence Diagram for Register Data use case

BDIMS BY GROUP 7 37
.

Figure2.6: Sequence Diagram for Use Case Query Data

BDIMS BY GROUP 7 38
.
Sequence diagram for Search Data use case

Figure2.7: Sequence Diagram for Search Data use case

BDIMS BY GROUP 7 39
.

Users

Figure2.8: Sequence Diagram for View Data use case

BDIMS BY GROUP 7 40
.

Figure2.9: Sequence Diagram for Delete Data use case

BDIMS BY GROUP 7 41
.

Figure 2.10: Sequence Diagram for Manage Profile use case

BDIMS BY GROUP 7 42
.

Figure2.11: Sequence Diagram for Use Case Manage Forum

BDIMS BY GROUP 7 43
.

Sequence Diagram for Manage Volunteers use case

Figure2.12: Sequence Diagram for Manage Volunteers Use Case

BDIMS BY GROUP 7 44
.

buttonCreateEvent()

Figure2.13: Sequence Diagram for Manage Calendar Use Case

BDIMS BY GROUP 7 45
.

Figure2.14: Sequence Diagram for Update Data Use Case

BDIMS BY GROUP 7 46
.

Figure2.15: Sequence Diagram for Manage Personal Profile Use Case

BDIMS BY GROUP 7 47
.

Figure2.16: Sequence Diagram for Change Password Use Case

BDIMS BY GROUP 7 48
.
2.9. STATE CHART DIAGRAM
State chart diagram show the flow of control from state to state through the process of
modeling the behavior of reactive objects. State chart diagrams allow the developers to have a
thorough understanding over the behavior of objects. The need for this diagram is especially
heightened in the case of complex objects which attain several states at different times. The
following figures depict the state chart diagrams of the use cases used in our project.

1. Authentication

Figure2.17: State chart Diagram for Authentication

BDIMS BY GROUP 7 49
.
2. User Management

Figure2.18: State Chart Diagram for User Management class

BDIMS BY GROUP 7 50
.

3. Resource Management

Figure2.19: State chart Diagram for Data Management

BDIMS BY GROUP 7 51
.

4. Query Builder

Figure2.20: State chart Diagram for Query Builder

BDIMS BY GROUP 7 52
.

5. Forum Management

Figure2.21: State chart Diagram for Forum Management

BDIMS BY GROUP 7 53
 .
2.10. ACTIVITY DIAGRAM
Activity diagram is a diagram which used for modeling the logic captured by single use case
usage scenario. It also helps to model the internal logic of complex operations of the system.
In addition to this, it shows the work flow from start point to end point details and many
decision parts that exist in progression of event contain in activity. Based on this we design the
following activity diagrams for our system;

1. Authentication

Figure2.23: Activity Diagram for Authentication Use Case

BDIMS BY GROUP 7 54
.

Figure2.24: Activity Diagram for Create Account Use Case

BDIMS BY GROUP 7 55
.

Figure2.25: Activity Diagram for Register New Data Use Case

BDIMS BY GROUP 7 56
.

Figure2.26: Activity Diagram for query Data Use Case

BDIMS BY GROUP 7 57
.

Figure2.27: Activity Diagram for Update Data Use Case

BDIMS BY GROUP 7 58
.

Figure2.28: Activity Diagram for Access Data Use Case

BDIMS BY GROUP 7 59
.

Figure2.29: Activity Diagram for Search Data Use Case

BDIMS BY GROUP 7 60
.

Figure2.30: Activity Diagram for Delete Data Use Case

BDIMS BY GROUP 7 61
.

Figure2.31: Activity Diagram for Manage Forum Use Case

BDIMS BY GROUP 7 62
.

Figure2.32: Activity Diagram for Manage Volunteers Use Case

BDIMS BY GROUP 7 63
.

Figure2.33: Activity Diagram for Manage Profile Use Case

BDIMS BY GROUP 7 64
.

Figure2.34: Activity Diagram for Manage Calendar Use Case

BDIMS BY GROUP 7 65
.

Figure2.35: Activity Diagram for change Password Use Case

BDIMS BY GROUP 7 66
.
Function tree describes the function of each actor in the system with their access level and
privilege.

The functions of each Actor in our system are described as follow in the form of tree;

Figure2.36: Actors Functions Biological Data Management System

BDIMS BY GROUP 7 67
.

2.10. CLASS DIAGRAM

A class is an abstract, user-defined description of a type of data. It identifies the attributes of
the data and the operations that can be performed on instances (i.e. objects) of the data. A
class of data has a name, a set of attributes that describes its characteristics, and a set of
operations that can be performed on the objects of that class. The classes’ structure and their
relationships to each other frozen in time represent the static model. In this project there are
certain main classes which are related to other classes required for their working. There are
different kinds of relationships between the classes as shown in the diagram like normal
association, aggregation, and generalization. Here resource Management, users Management,
and query Builder are the most important classes which are related to other classes required
for their interactions. Hence class diagram provides an overview of the target system by
describing the object and classes inside the system and the relationship between them. It
provides a wide variety of usages from modeling the domain specific data structure to detailed
design of the target system.

BDIMS BY GROUP 7 68
.

Figure2.37: Class Diagram of Biological Data Management System

BDIMS BY GROUP 7 69
.
2.11. KEY ABSTRACTION WITH CRC ANALYSIS
A Class Responsibility Collaborator (CRC) model is a collection of standard index cards that
have been divided into three sections. A class represents a collection of similar objects, a
responsibility is something that a class knows or does, and a collaborator is another class that a
class interacts with to fulfill its responsibilities. The CRC of model of our system describes as
follow:

Figure2.38: CRC Diagram for Biological Data Management System

BDIMS BY GROUP 7 70
.
2.12. IDENTIFY CHANGE CASES
Change cases are used to describe new potential requirements for a system or modifications to
existing requirements.

Change case: registration of species/diseases and traditional medicines data may be

performed completely via internet.

Change case identifier UC03: when internet technology became more and more advance the
registration of biological data will done by only internet. At that time the task of registering
data of biodiversity will done by internet service.

Potential Impact: unknown species may be registered as Ethiopian biological data but which
is not. And data overlapping occurs because different client may upload biological data for the
same biological entity. Data updating will occur frequently.

Likelihood: The change may occur slowly with advancement of technology, so the change is
occurring likely with medium rate of change.

BDIMS BY GROUP 7 71
.
2.13. USER INTERFACE PROTOTYPING
The user interface is the part of the system that users will always see, and interact with. So
having screen shots of the user interface in our documentation will allow us how the system
looks like. The following screen shoots show our system interface.

User interface for home page

Figure2.39 Home page (photo [8] &[9])

BDIMS BY GROUP 7 72
.

Figure2.40 Database Client Home page (photo [9])

BDIMS BY GROUP 7 73
.

Account creation user interface

Figure2.41 User Interface to Create New Account (photo [9])

BDIMS BY GROUP 7 74
.

Figure42 User Interface for Query Builder

BDIMS BY GROUP 7 75
.

Search Species details user interface

Figure 43: Taxonomy details of species (photo[8]&[9])

BDIMS BY GROUP 7 76
.
Traditional medicines registration page user interface

Figure44 Traditional Medicines registration page (photo [8]).

BDIMS BY GROUP 7 77
.
search traditional medicines user interface

Figure45 User Interface for searching traditional Medicines (photo of Demakese [8])

BDIMS BY GROUP 7 78
.

CHAPTER THREE

3.0. SYSTEM DESIGN

Introduction: This chapter provides a system design stage of the project in development.
This chapter contains and describes about the system architecture, subsystem decomposition,
component of the system, persistent data design model (database schema) and deployment
diagram of our system.

3.1. PURPOSE AND GOALS OF DESIGN

Software architecture is the fundamental framework for structuring the system we will
develop. Our goal is to produce a model or representation of any model that will be built later.
Beginning once system requirement have been specified and analyzed, system design is the
first of the three technical activities that of design, code and test that required for building and
verifying software. The importance can be started with a single word quality. Design is the
place where quality is fostered in software development. We design our system by enhancing
the attributes like performance, security, availability, and maintainability.

Based on this our system has 4 main goals that we will adhere to:

 Developing reusable components that are easy to modify and maintain by paying attention
to low coupling and high cohesion principle. We strongly believe that, using well-known
design patterns can help us to attain this goal.
 Developing efficient and reliable networked components.
 Providing easy graphical user interface to increase user friendliness.
 Developing a robust system that can handle errors such as network problems and invalid
inputs and give meaningful feedback to users.
The above goals are addressed by considering the following criteria in our system design;

Performance:
The system is capable of carrying huge amount of data with many related databases. The
system carries information sufficiently. In our system when user requests or want to operate
some task, the system responses for the user request quickly to satisfy the user need.

We localize operations of our system to minimize the subsystem communication among each
other.

Dependability:
System dependability is the probability of a computer or other system that will perform its
intended task in its specified environment without significant degradation. By creating
redundant component we increase the dependability of our system and we will develop a
secured and reliable system for the fulfillment of stakeholders need.

BDIMS BY GROUP 7 79
.
User Friendliness:
The users of our system are mostly biologists, researchers, and community who are the owner
of biological diversity wealth and most traditional medicines, and others like environmental
conservatives who are non-computer science professionals. As a result we will develop a
system which is user friendly by designing interactive user interfaces for those stakeholders to
communicate with the system easily. This is valuable because end users know their own
context and needs better than anybody else and they often have real time awareness of shifts in
their respective domains.

Reusability:
The system that we will develop can reuse easily by modifying the source code for further
features of the system with rapid change in technology.

Portability:
The system can run on different platforms because it is platform independent.

Fault tolerant:
The system we develop can reduce the frequent errors occurred when the system is run. The
system is tolerable with minimum numbers of errors.

Security:

We use layer architecture with critical assets in the inner layer to increase the safety of our
system.

3.2. Current Software Architecture

Currently in Ethiopia there is not exist organized web based system for biological data
management purpose. But there are different biological databases for storing and managing
the biological data of Ethiopian biodiversity. And also In Addis Ababa Ethiopia there is
national Herbarium database which stores the biological data of our biological diversity.
Those databases are not accessed through internet and it is impossible to upload data of
species, diseases and traditional medicines on the client side.

In the current system there is no the idea of query builders, i.e. it is impossible to search data
of diseases, vectors and traditional medicines using the one search text area.

In this chapter we introduce our system architecture, subsystem decompositions, and the
persistent data model design as follows;

BDIMS BY GROUP 7 80
.
3.3. Proposed System Architecture
Architecture determines the type of interactions that the components of the system are going
to have. The architecture we use for this work is three tiers client/server Architecture. It is
mainly based on the system analysis document.

The first tier is client side tier provides applications for the client user interfaces containing
data entry forms and client side applications. It displays data to the user. Users can interact
directly with the applications through internet. The client tier interacts with the web/
applications server to make request and retrieve data from the database. Then it displays to the
client users the data retrieved from the server database. A client use internet browsers to
access the services provided by the system located anywhere having internet access.

The middle tier (web/application server) implements the business logic, the controller logic
and the presentation logic to control the interaction between the application’s client and the
data. The web server is the program that runs on server computer to respond to the HTTP
request of the client. Web server used in this system is apache. HTTP is used to transfer data
across internet.

The controller logic process the client request such as request to data query, to access data of
species, diseases and traditional medicines from database or record new data into database.
The business rule enforced by the business logic dictate how clients can and cannot access
application data and how applications process data.

The third tier called the data tier which maintains the applications data such as species list and
information, the vector borne diseases list and information and traditional medicines list and
information which prepared from plants and other biological entities in Ethiopian ecosystem.
In this layer the data of our system stored permanently and main source of data transactions
among the server and the clients.

BDIMS BY GROUP 7 81
.

Figure 3.1 System Architecture Design Diagram of Biological Data Management System

Figure3.1 shows what our system tiers seem in the network to provide data for users according
to the request provided. When the user interacts to the client tier the client side tier directly
connects the server and provides the data for the user.

BDIMS BY GROUP 7 82
.
3.3.1 Subsystem Decomposition
Subsystem decomposition is the collection of classes, associations, operations, events and
constraints that are closely interrelated with each other. Based on the definition we decompose
our system into the following Subsystem;

Figure3.2 Subsystem Decomposition for Biological Data Management System (BDIMS)

Figure3.2 shows the subsystem that our system mainly has as generally. The resource
management subsystem includes all the data of the species, vectors, vector borne diseases,
traditional medicines. The user management subsystem includes the type of users in our
system those are the administrator, the staff members, and the Client users. The query builder
is another subsystem that our system has.

Now we decompose each subsystem in to other related subsystems and components. This
decomposition activity helps us to identify cohesion and coupling property of each subsystem
for building one integrated system. Each subsystem gives service for doing certain operations
in the object interface of its layer.

Based on this we decompose the subsystem of our system as follow:

BDIMS BY GROUP 7 83
.

Figure3.3 subsystem Decomposition for Resource Management subsystem

In the figure above subsystem Resource management is composed different subsystems and
components that interacts each other. We sub decompose the subsystem of the resource
management subsystem components as follow;

Figure3.4 subsystem Decomposition for Flora/Plants Data subsystem

BDIMS BY GROUP 7 84
.
The plant subsystem has either the terrestrial plant or the aquatic plant component. Those
components build up the plant subsystem.

Figure3.5 subsystem Decomposition for Fauna/Animals Data subsystem

The plant subsystem has either the terrestrial animal or the aquatic animal component. Those
components build up the animal subsystem.

Figure3.6 subsystem Decomposition for Insects Data subsystem

BDIMS BY GROUP 7 85
.

Figure3.7 subsystem Decomposition for Diseases Data subsystem

In this figure3.7 the subsystem diseases can be sub decompose in to three components of plant
diseases, animal diseases and human diseases.

Figure3.8 subsystem Decomposition for Traditional Medicines Data subsystem

Figure3.8 we sub decompose the sub system traditional medicines in to component traditional
medicines for human, animals and plants. In this subsystem each component has similar
behavior but the way of preparation, the dose of the medicines and prescription are different
for each component.

BDIMS BY GROUP 7 86
.

Figure3.9 Subsystem Decomposition for Query Builder subsystem

Figure3.9 describes about the sub component of query builder subsystem which is advanced
search mechanism used to search efficient data of species, diseases and traditional medicines
from different data tables. So the query builder has sub component query which is used to
search the available data from our system.

BDIMS BY GROUP 7 87
.

Figure3.10 Subsystem Decomposition for User Management subsystem.

In this figure 3.10 we sub decompose all the user related activities that are applicable in our
system. The account creation component includes the activities that our system users register
in our system themselves or the administrator can create user account for staff members, and
the members can change their password. The authentication component is used to secure our
system by requesting user name and password when you try to enter in the system. The
subsystem user type which has subcomponent of anonymous user, registered user, the staff
member and the administrator those are users in different access level in our system.

BDIMS BY GROUP 7 88
.
3.3.2 COMPONENT DIAGRAM
Component diagram shows how the subsystems are related to each other and which interfaces
are implemented by which component. A component diagram can shows one or more
interfaces and their relationships to other components. A component diagram shows the
dependency among software components, including source code, binary code and executable
components. We describe our system component diagram below;

Figure3.11 Component Diagram of Biological Data Management system

BDIMS BY GROUP 7 89
.
3.3.3 . DEPLOYMENT DIAGRAM
Deployment diagram depicts how the deployable units of the system applications, components
and data stores are assigned to various nodes as well as how the nodes communicate with each
other and with devices. It is useful for mapping our system and as a means of studying the
load across our system.

Figure3.12 Deployment Diagram for Biological Data Management system

BDIMS BY GROUP 7 90
.

3.3.4 PERSISTENT DATA DESIGN

In order to store the information of species, diseases, traditional medicines and vectors
persistently we map objects into tables and attributes in fields to the specific table based on the
objects found on the system. Therefore we identified the major tables that will be implemented
on the selected Database and show the necessary relationships among the objects, which are
selected to store the data persistently in the system. Generally there are three types of
relationships database system. These are one-to-one, one-to-many and many-to-many. For this
reason, we map objects in tables as follow:

BDIMS BY GROUP 7 91
.
Figure3.13 Database Schema Model of Biological Data Management System

3.3.5 ACCESS CONTROL AND SECURITY

This is the way of securing our system from unauthorized user and makes the access privilege
of each user safe. Once the client and server have established a secure channel the client can
issue request to the server. Requests can be only carried out if the client has sufficient access
rights. This is verified by access control and granted by authorization. The diagram below
shows who have the right to access the object by referring the reference monitor. The subject
issues the request to access the object; protection is enforced by the reference monitor that
knows which subject is allowed to issue which requests.

Figure3.14 Access control Model Diagram

An access control matrix or Access Matrix is an abstract, formal security model of protection
state in computer systems, which characterize the rights of each subject with respect to every
object in the system.

We show the access control levels of our system users in the form of Access control matrix as
follows:

BDIMS BY GROUP 7 92
.

Table 3.1: Access control matrix for Biological Data Management System

BDIMS BY GROUP 7 93
.

CONCLUSION
Effective data analysis across biological data management systems involves providing support
for seamless composition of analysis operations, which in turn requires systematic process for
analyzing the data structure and operations of the application domain. The development
process of biological data management system involves detailed application domain analysis
based on use case scenarios subsequently used for defining abstract species, vector-borne
diseases and traditional medicines data model in terms of data types and operations. BDIMS
aims to increase the accessibility of Ethiopian biological data for users of the biological
diversity wealth in different areas with various purposes.

BDIMS BY GROUP 7 94
.

Reference

1. Ensembl national biological database organization.

http://www.ensembl.org/info/about/species.html
2. http://www.ncbi.nlm.nih.gov/geoprofiles/
3. https://www.cbd.int/doc/world/et/et-nbsap-01-en
4. http://darwin.ansp.org/hosted/aes/membership.htm
5. object oriented business rule Dr.Dobbs
http://www.drdobbs.com/object-oriented-business-rule
6. V.M. Markowitz, J. Campbell, I.A. Chen, A. Kosky, K. Palaniappan, and T. Topaloglou,
Integration Challenges in Gene Expression Data Management.
7. Bioinformatics: Managing Scientific Data, Morgan Kauffman Publishers (Elsevier
Science), 277-301,
8. Somerville software engineering (2011- 9th edition)
http://www.SoftwareEngineering-9.com/Web/History/
9. Asfaw, N., Demissew, S., 2009. Aromatic plants of Ethiopia. Shama Books, Addis Ababa.
http://botanicaethiopia.com/herbs/

10. National biodiversity strategy of Ethiopian ecosystem

BDIMS BY GROUP 7 95