WACHEMO UNIVERSITY

COLLEGE OF ENGINEERING AND TECHNOLOGY

SCHOOL OF COMPUTING AND INFORMATICS

DEPARTMENT OF INFORMATION TECHNOLOGY

Android Based Mobile Dictionary Application

Date 04/1/2021

Hossana, Ethiopia
Advisor Name: ________________________

Android Based Mobile Dictionary Application

A Senior Project Report

Submitted to department of Information Technology, School of

Computing and Informatics, College of Engineering and Technology
Wachemo University in partial fulfilment for requirement of the Degree
of Bachelor Science in Information Technology.

Group Member Name Id Sign

1. ALEMAYEHU YENEW***************************5436/09 ______________

2. GEBREHANS TESFAY****************************5649/09 ______________
3. MEHIRITE MARKOS****************************5809/09 ______________
4. BEMENETLEGESE******************************5498/09 ______________

Android based mobile dictionary application project Page i

 Wachemo University

College of Engineering and Technology

School of Informatics and Computing

Android Based Mobile Dictionary Application

Project Advised by:

Advisor Name

Name and signature of Members of the examining board:

Name Title Signature Date

1. __________________ Advisor _____________ _____________

2. __________________ Examiner _____________ _____________

3. __________________ Examiner _____________ _____________

4. __________________ Examiner _____________ _____________

December 30, 2020

Android based mobile dictionary application project Page ii

 Declaration of Originality

We declare that this project is our original work and has not been presented for a degree in any
other university.

Name Signature Date

1. ALEMAYHOH YENEW __________________ __________________

2. GEBREHANS TESFAY __________________ __________________

3. MEHIRITE MARKOS _________________ __________________

4. BEMENETLEGESE __________________ __________________

This project documentation has been submitted for examination with my approval as university
advisor:

Advisor Name _________________________

Android based mobile dictionary application project Page iii

 December 30, 2020

Android based mobile dictionary application project Page iv

ACKNOLWLEDGMENT
First and foremost and above all our biggest thanks would be to Almighty God because nothing
could be possible without his free will and the completion of this project is supported by him.
Secondly, we are much obliged to record our sincere gratitude to our Advisor Gosa.for guiding
and correcting various documents of ours with attention and care. He has taken pain to go
through the project and made necessary correction as and when needed.

Finally we have a special thanks to our friends and classmates for their suggestion, technical and
material support.

Android based mobile dictionary application project Page v

Abstract
Today, mobile phones provide number of advanced functions, among which possibility of
running mobile applications seems to be the most interesting feature. It changes a standard
mobile phone into a mini size yet still powerful computer that is able to run various applications,
like map guide, dictionary, games and so on.

Dictionary is the list of words with their definitions. Android Mobile Dictionary Application is
an application that provides English, Amharic, Tigrigna and affan oromo word translation. In
addition to word translation it has multimedia content i.e. image and pronunciation for words.
Displaying the meaning of the word with multimedia content will help the users to understand
the meaning of the word very easily. The sound/voice support helps the user to know how the
word is pronounced correctly; picture also describes the meaning of the word better than text.
The dictionaries will be stored in the mobile phone.

Android based mobile dictionary application project Page vi

Table of Contents
ACKNOLWLEDGMENT...........................................................................................................................v
Abstract......................................................................................................................................................vi
Table of Contents.......................................................................................................................................vii
List of Table................................................................................................................................................x
List of Figure..............................................................................................................................................xi
ABBRIVATION........................................................................................................................................xii
Chapter One.................................................................................................................................................1
1.1. Introduction.....................................................................................................................................1
1.2. Background.....................................................................................................................................1
1.3. Statement of the Problem.................................................................................................................3
1.4. Objective of the project...................................................................................................................3
1.4.1. General Objective of the project..............................................................................................3
1.4.2. Specific Objective of the project..............................................................................................3
1.5. Proposed mobile application............................................................................................................4
1.6. Literature Review and Related Works.............................................................................................4
1.7. Scope and limitation of the project..................................................................................................5
1.7.1. Scope of the project.................................................................................................................5
1.7.2. Limitation of the project..........................................................................................................5
1.8. Methods and Tools..........................................................................................................................6
1.8.1. Data source and data collection methods.................................................................................6
1.8.1.1. Primary method of data collection...................................................................................6
1.8.1.2. Secondary method of data collection...............................................................................6
1.8.2. System Analysis and Design Methods.....................................................................................6
1.8.3. System Implementation Methods and How to use Methods....................................................7
1.8.4. Development Environment and Programming Tools...............................................................7
1.9. Significance of the Project...............................................................................................................9
1.10. Beneficiaries of the application....................................................................................................9
1.11. Feasibility of the Study................................................................................................................9
1.11.1. Technical Feasibility Study......................................................................................................9

Android based mobile dictionary application project Page vii

 1.11.2. Economic Feasibility Study...................................................................................................10
1.11.3. Operational Feasibility Study.................................................................................................10
1.11.4. Legal Feasibility Study..........................................................................................................10
CHAPTER TWO.......................................................................................................................................11
DESCRIPTIONS OF EXSTING SYSTEM...........................................................................................11
2. Introduction to the Existing system...............................................................................................11
2.1. Business Rules and Constraints.................................................................................................11
2.2. Naming Convention and Definition...............................................................................................11
2.3. Functions or Main Activities of the Existing dictionary................................................................12
2.4. Players of the Existing Application...............................................................................................12
2.5. Organization Structure...................................................................................................................12
2.6. Documents used in the Existing paper based dictionary................................................................13
2.7. Strength and Weakness of the Existing paper based dictionary.....................................................14
2.7.1. Strength of the Existing paper based dictionary.....................................................................14
2.7.2. Weakness of the Existing paper based dictionary..................................................................15
2.8. Alternative Solution.......................................................................................................................15
CHAPTER-3-............................................................................................................................................16
REQUREMENT SPECIFICATION AND ANALYSIS........................................................................16
3.1. Introduction...................................................................................................................................16
3.2. Description of the proposed mobile dictionary Application...........................................................16
3.2.1. User Characteristics...............................................................................................................16
3.2.2. Constraints.............................................................................................................................16
3.2.3. Assumptions of and Dependencies........................................................................................17
3.3. Requirement Specifications...........................................................................................................17
3.3.1. Functional Requirement.........................................................................................................17
3.3.2. Non-Functional Requirement.................................................................................................18
3.4. System modeling...........................................................................................................................18
3.5. Actors Identification......................................................................................................................19
3.5.1. Use-case Identification..............................................................................................................19
3.5.2. Use-case Diagram..................................................................................................................19
3.5.3. Description of Use-case.........................................................................................................21
CHAPTER -4-...........................................................................................................................................26
SYSTEM DESIGN................................................................................................................................26

Android based mobile dictionary application project Page viii

 4.1. Introduction....................................................................................................................................26
4.1.1. Design Goals Criteria..................................................................................................................26
4.2. Activity Diagram...........................................................................................................................27
4.3. Sequence Diagram.........................................................................................................................33
4.4. Class Diagram...............................................................................................................................39
4.5. Database Model.............................................................................................................................40
4.5.1. Entity Relationship Diagram (ERD)......................................................................................40
4.5.2. Persistence Modeling.............................................................................................................41
4.5.3. Mapping with Normalization.................................................................................................43
4.6. Subsystem Decomposition.............................................................................................................44
4.7. Deployment Diagram.....................................................................................................................45
4.8. System Architecture (Layered Architecture of the system)...........................................................46
4.9. User-Interface (UI) Design............................................................................................................48
4.10. UI Flow Diagramming...............................................................................................................49
CHAPTER -5-...........................................................................................................................................50
IMPEMENTATION AND TESTING...................................................................................................50
5.1 INTRODUCTION.....................................................................................................................50
5.2 sample code...............................................................................................................................50
5.3 features to be tested and not tested.............................................................................................51
5.3.1 functional features to be tested...............................................................................................51
5.3.2 non-functional features to be tested.......................................................................................51
5.3.3 Features not to be tested.........................................................................................................52
5.4 pass/fail criteria..........................................................................................................................52
5.5 Approach/Strategy.........................................................................Error! Bookmark not defined.
5.6 Test cases with specifications....................................................................................................52
CHAPTER -6-...........................................................................................................................................53
USER MANUAL..................................................................................................................................53
6. Scope.............................................................................................................................................53
6.1 Installation and Configuration...................................................................................................53
6.2 How to operate the system.........................................................................................................53
CHAPTER -7-...........................................................................................................................................59
CONCLUSION AND RECOMMENDATION.....................................................................................59
7. Conclusion.....................................................................................................................................59

Android based mobile dictionary application project Page ix

 7.1 Recommendation.............................................................................................................................59
Reference...................................................................................................................................................60

List of Table
Table 1. 1: Hardware requirements.................................................................................................8
Table 1. 2: Software requirements...................................................................................................8

Table 3. 1 : use case description for the use case Select Dictionary. 21

Table 3. 2: use case description for use case type Word in search bar..........................................21
Table 3. 3: use case description for Search meaning.....................................................................22
Table 3. 4: use case description for use case Display meaning.....................................................23
Table 3. 5: use case description for use case Listen Pronunciation...............................................24
Table 3. 6 : use case description for use case view Image............................................................24
Table 3. 7: use case description for use case for modification......................................................25

Android based mobile dictionary application project Page x

List of Figure

Figure 2. 1: Organization structure................................................................................................13

Figure 4. 1: Activity diagram for select dictionary
Figure 4. 2: Activity diagram for search meaning
Figure 4. 3: Activity diagram for listen pronunciation
Figure 4. 4: Activity diagram for view image
Figure 4. 5: Activity diagram for modification
Figure 4. 6: Sequence diagram for Select dictionary
Figure 4. 7: Sequence diagram for type word
Figure 4. 8: Sequence diagram for Listen Pronunciation

Android based mobile dictionary application project Page xi

Figure 4. 9: Sequence diagram for View Image
Figure 4. 10: Sequence diagram for Search Meaning
Figure 4. 11: Sequence Diagram for View Identifiers
Figure 4. 12: Sequence diagram for modification
Figure 4. 13: class diagram
Figure 4. 14: Entity relation diagram
Figure 4. 15: persistence modeling diagram
Figure 4. 16: Mapping of tables with Normalization
Figure 4. 17: Subsystem decomposition for the Dictionary application
Figure 4. 18: Deployment Modeling for Dictionary application
Figure 4. 19: System architecture
Figure 4. 20: User-Interface (UI) Design diagram
Figure 4. 21: User interface flow diagram

ABBRIVATION

ABBREIVIATION DESCRIPTION

A1 Alternative 1

Alt Alternative

ADT Android Development Tools

OOP Objected Oriented Programming

Android based mobile dictionary application project Page xii

OOPL Object Oriented Programming Language

OOA Object Oriented Analysis

OOD Object Oriented Design

ROM Read Only Memory

SDK Software Development kit

UML Unified Model Language

UC1 Use Case 1

UC2 Use Case 2

UC3 Use Case 3

UC4 Use Case 4

UC5 Use Case 5

UC6 Use Case 6

UC7 Use Case 7

URL Uniform Resource Locator

Android based mobile dictionary application project Page xiii

Chapter One

1.1. Introduction
mobile computing systems today, growing fast, due to their small size, the mobile nature of their
use, there power sources, and their functionalities that are particularly suited to the mobile user.
Because of these features, mobile computing applications are becoming growing fast. As a
current context almost everyone is becoming a mobile user in order to get information and
service from developed application.

Among these mobile computing systems mobile based dictionary application is one of the
famous and an interesting application. Mobile based dictionary application is the process of
developing a dictionary application that runs on android systems. Mobile dictionary is more
portable than the printed dictionary books. There are many people who use printed dictionary
and facing problems in language translation. Searching the new words is difficult because of
huge paper based dictionary; search takes a lot of time. We are trying to solve this problem by
developing android based dictionary for users with voice and text support, which is normally
used to translate the word from English to Amharic, English to Afaan Oromo and English to
Tigrigna language.

1.2. Background
Language is one of the fundamental aspects of human behavior and a basic component in daily
activities. It is the method of communication in different ways which are by audio (spoken), text
written and sign to exchange ideas, emotions, and information. Nowadays, there are the vast
amounts of information exchanging between one natural language to another in different formats
using language translation software. .

Language software’s are getting popular these days due to the increasing need of different
languages for use. This software’s are designed to translate a particular language into your
known language.

Android based mobile dictionary application project Page 1

They are capable of returning the matching results with the translation for the word as you type
in the search bar. Almost all languages can be learnt with the help of language software’s as
varieties of programs dedicated to each of them. Our project is concerned with the development
of android dictionary application for Amharic, Afaan Oromo and Tigrigna language with text,
voice and image support.

Printed Dictionary book has currently many problems that initiated the group members to
develop an Android based mobile dictionary application. These problems are lack of easily
portability, Unable to support English to Amharic, Afaan Oromo and Tigrigna language
translation on computing device, lack of language schools and the number of android phone user
is increasing every year. Generally printed dictionary have problems and is not more suitable in
today’s world.

Android based mobile dictionary application project Page 2

1.3. Statement of the Problem
In printed dictionary searching the meaning of a single word from huge paper is difficult, the
user should find the word among several pages by turning the pages of the dictionary. This
may take more time to find the meaning of the word. If the users want to get reference of
many dictionaries, the users should buy those dictionaries. This forces the user to allocate
more money to buy all the dictionaries. The printed dictionary is not portable and does not
support voice. The current dictionary books don’t satisfy the interests of the user to have a
local language dictionary application. By understanding these problems we will try to
develop an android based mobile dictionary application that supports English to Amharic,
English to Afaan Oromo and English to Tigrigna language which helps the user to translate
meaning of the word. Generally, the application that we will develop can avoid or solve the
problems of the current printed dictionary books that we have mentioned above.

1.4. Objective of the project

1.4.1. General Objective of the project

The main objective of this project is to automate printed version dictionary into android
based mobile dictionary application.

1.4.2. Specific Objective of the project

To achieve the general objective mentioned above the following are specific objective:

 Gathering requirements
 Perform requirement analysis to identify and classify functional and non- function
requirements.
 Design user friendly user interface.
 Construct a database that store word and their corresponding meaning.
 Design Amharic language keyboard.
 Implement the designed application using android programming.
 Test the developed prototype.
 Deploy or install the application
Android based mobile dictionary application project Page 3
  Maintain the application if it is needed

1.5. Proposed mobile application

The aim of this application is to develop Android based mobile dictionary application that will
give English-Amharic, English-Afaan Oromo and English-Tigrigna dictionary searching
facilities for dictionary users. A user can switch to chosen language or dictionary subtype to
another one. The new proposed system tries to address the problems that arise in existing system.
Some of the features of new systems are:-

 Providing learning experience where ever.

 No more forced to use pc and paper as the only object to have access to materials,
knowledge.
 Personalizing learner’s environment.
 Greater efficiency.
 Minimize manual work.
 User friendliness and interactive.
 It is portable.
 It is accessible whenever the user needs.
 Enable the users to have an electronic dictionaries
 To reduce the amount of time needed to access dictionaries
 To reduce or remove unnecessary wastage or extravagance like paper, cartilage.

1.6. Literature Review and Related Works

A dictionary is an alphabetical book that translates meaning of one language into the other
language. There are some previous studies related to this project. The purpose of dictionary
translation is to provide help for someone who understands one language but not the
other(Zamari, 2011). Zarlina also states that dictionary translation is used mostly to help second
language learners to learn and understand the target language better. According to(Tseng, No.3,
September 2003), the dictionary can be a good companion for students. This is because
dictionaries can help them in providing a quick and direct access to many things specifically
meanings of words to second language learners. As we understand from review we know how

Android based mobile dictionary application project Page 4

language translation works and limitations. Which means many languages are translated to
specifically into one language. The user may want to learn one or more languages, so the user
needs one or more dictionary books.So the user waste extra budget paper dictionary book is not
easily portable as the user needs.

1.7. Scope and limitation of the project

1.7.1. Scope of the project

The scope of our application project is to translate English language to other languages like
English to Amharic, English to Afaan Oromo, as well as English to Tigric. It helps the user to
know the meaning of the word easily in these three languages. The applications will:

 Enable the user to choose dictionary types (English to Amharic, English to Afaan
Oromo, and English to Tigrigna).
 Enable a user to type a word in search.
 Enable a user to listen pronunciation of the word.
 Enable a user to view image of searched word.
 Enablea user to view identifiers (noun, verb, and pronoun).
 Enable the user to modify.

1.7.2. Limitation of the project

Even if we try to do the project in good way our project has some limitations:

 It runs only on smart phone that can run on android operating system.
 It supports the translation only from English to Amharic, English to Afaan
Oromo, and English to Tigrigna. We will consider it as a limitation of the project
since our users have many other languages.
 The application only supports translation of English words in to three languages.
 It is language dependant that means users must know English.

Android based mobile dictionary application project Page 5

1.8. Methods and Tools

Methodology is the way or mechanism in which we gather the information to develop the
application. To develop appropriate android based voice and text support dictionary we have to
see previously done paper based dictionary and enough information has to be gathered. Data
collection is the process of gathering and measuring information on targeted variables in
systematic fashion, which then enables one to answer relevant questions and evaluate outcomes.

1.8.1. Data source and data collection methods

1.8.1.1. Primary method of data collection

 Interviewing

We gather information formally through interview of different people, students and others we
interview English, Amharic and Afaan Oromo language speakers.

 Observation

We tried to observe printed version of dictionary to get more information. This information will
help us to understand what problems are exist in paper based dictionary .by observing existing
dictionary we can understand how the new application should operate.

1.8.1.2. Secondary method of data collection

 Document review such as printed dictionary books that translate English to Amharic,
Tigrigna and Afaan Oromo.
 Watching video tutorials.

1.8.2. System Analysis and Design Methods

The method we have chosen to develop the system is object oriented system analysis
methodologies (OOSAD). Object oriented methods provide a set of techniques for analyzing,
decomposing, and modularizing software system architectures. The reason why we chose
OOSAD are it is a popular technical approach to analysis and design the application. This has
two phases:-

 Object Oriented Analysis

Android based mobile dictionary application project Page 6

During this phase, the team will model the functions of the system (use case modeling), Find and
identify the business objects, Organize the objects and identify the relationship between them
and finally model the behavior of the objects.

 Object Oriented Design

During this phase, the team will refine the use case model to reflect the implementation
environment, model object interactions and behaviors that support the use case scenario, and
finally update object model to reflect the implementation environment. The analysis phase
identifies the objects, their relationship, and behavior using the conceptual model (an abstract
definition for the objects). While in design phase, we describe these objects (by creating class
diagram from conceptual diagram — usually mapping conceptual model to class diagram), their
attributes, behavior, and interactions.

1.8.3. System Implementation Methods and How to use Methods

To produce high quality software that meets or exceeds user’s expectations, reaches completion
within times and cost estimates the team chooses iterative method. The basic idea behind this
method is at each iteration, design modifications are made and new functional capabilities are
added. The reason why we choose iterative method:

Testing and debugging during smaller iteration is easy.

Risks are identified and resolved during iteration; and each iteration is an easily managed goal.

Issues, challenges & risks identified from each increment can be applied to the next increment.

1.8.4. Development Environment and Programming Tools

Since we try to develop Mobile based dictionary using Android studio .still now we don’t get
other development environment to develop mobile based applications rather than android studio.
The programming tools that the project concentrates are the following:

Android based mobile dictionary application project Page 7

Table 1. 1: Hardware requirements

Hardware requirements Description

Printer For printing paper

Flash disc(8Gb)and hard disc(500GB) For storage

Pen For writing

One desta packet paper For print hard copy

Internet cable For connection

Table 1. 2: Software requirements

Software requirements Description

MS-word 2007 For documentation

Paint Used for editing

MS-PowerPoint For presentation

Edrawmax For drawing deferent diagrams

Android based mobile dictionary application project Page 8

1.9. Significance of the Project
Mobile dictionary application that being built can be of great use to the users. It can assist them
in learning three languages. It will also help in improving ones language skills like
pronunciation. Foremost it will be an effective tool when traveling and communicating with
people and Decrease purchasing cost for users. The application also saves time and energy for
users. The developing application will resolve the following difficulties.

Generally, the proposed system has the following advantages:

 The users easily learn the languages without involvement of third person.

 Guide other who will be interested to develop similar application.

1.10. Beneficiaries of the application

This application is used for any user that means anyone who have Android mobile phone and
who wants to learn Amharic, Afaan Oromo and Tigrigna language. But the user must know
English language to learn those languages.

1.11. Feasibility of the Study

Feasibility of the project means answering relating to the utility and viability of the system that is
going to be developed. Any project is said to be feasible if it satisfies the following feasibility
aspects.

1.11.1. Technical Feasibility Study

Assessing technical feasibility means checking whether the team organization has got the
technical capability to develop the proposed Information system/project. Since we have got
technical capability to develop the proposed application project, Our application can be easy to
install, easily maintained, portable and reliable. As a part of technology and system feasibility
study we have investigate the technological resources necessary for project. Since we find them
available, the project qualifies in this factor. Thus the project seems technically feasible. we
expect that our project will be technically feasible.

Android based mobile dictionary application project Page 9

1.11.2. Economic Feasibility Study
Assessing economic feasibility involves comparing the costs of the information systems
development project with the benefits the information system is going to have for the
organization once it has been developed. From this point of view our project is economically
feasible due to the following reasons:
 Reduce the amount of money that we need to buy a dictionary books because now a day
the price of a dictionary books is alarmingly increased.
 The amount of money that we need to develop this application is less than the amount of
money that we get from our product sale because most of the students and other persons
need this dictionary application due to its low cost once to install on their android phone.
 Due to the above reasons we will have a net benefit that makes our project economically
feasible.

1.11.3. Operational Feasibility Study

Operational feasibility refers to whether the proposed system can be implemented and operated
with the staff the team organization have and meet its intended purpose. Since we will develop
the application for android platform, the application is operationally feasible on android
platform. User can operate the system easily by follow the guidelines that written on the interface
of the application.

 The proposed system offers greater level of user friendliness.

 The proposed system can be implemented easily.

1.11.4. Legal Feasibility Study

The legal feasibility is a feasibility that makes sure the system does not break law a country. Our
application does not violent with any law; hence the system is legally or politically feasible. The
project team members built the application without violating rules and regulations of the
governments. Legal feasibility determines whether the proposed system conflicts with the legal
requirement or not.

Android based mobile dictionary application project Page 10

CHAPTER TWO

DESCRIPTIONS OF EXSTING SYSTEM

2. Introduction to the Existing system

Dictionary is an indispensable utility for every individual Paper based dictionary is available in
the library, in the market and in the shops. This dictionary contains the meaning and identifier of
the corresponding language. The existing dictionary operates manually to find or search the
meaning of the word from huge corpus, to find the meaning user should turn page by page until
getting the meaning. But the corpus is written in alphabetical order the user first search the first
letter, seconds letter up to the end of last latter of the word. After this process the desired word is
accessed.

2.1. Business Rules and Constraints

A business rule is effectively an operating principle or polices that we try to specify for both the
traditional existing system and the new system must satisfy. It deals with access control issues.
To assert business structure or to control influence the behavioral of the business. .
 Searching is finding the meaning of the word.
 View whether word is noun, pronoun, verb adjective etc.

The operating principle or policy of paper based dictionary follows the following rules.

BR1: the user should now English language.

BR2: the user search the meaning properly.

BR3: use dictionary properly.

BR4: The dictionaries provide information to the user.

BR5: user can use dictionary anywhere in anytimewithout connections.

2.2. Naming Convention and Definition

(v)-verb: the word is verb.

(n)-noun: the word is noun.

Android based mobile dictionary application project Page 11
(p)-pronoun: the word is pronoun.

(Adj)-adjective: the word is adjectives.

2.3. Functions or Main Activities of the Existing dictionary

The existing dictionary translation system translates meaning of one language in to the other
language. The existing dictionary is fully manual. That means all activities of dictionary are
controlled by a user. Major activities or functions done by paper based dictionary are:-

 Show the meaning of word.

 View the searched word's identifier.

Generally, the existing system of English, Amharic Afaan Oromo and Tigrigna language
dictionary is mostly can be done in manual form.

2.4. Players of the Existing Application

In Existing systems there are different actors that use manual operation. The following actors
are listed below:

 User: are individuals or group of peoples who uses manual dictionary.

 Admin: a person who develop dictionary for users.

2.5. Organization Structure

Android based mobile dictionary application project Page 12

 ENGLISH

Amaharic Afaan oromo Tigrigna

Figure 2. 1: Organization structure

2.6. Documents used in the Existing paper based dictionary

Paper based English to Afaan Oromo translation taken from second edition(zlalem, 206).

Abscess (n). -dullaa

Abdomen (n). – Huffaa

Abide (v). – Qubadha-batta

Ability (n). -qarumaa

Able (adj.) – mooti

Able (v). – danda’aa-deeta

abode (n ).- ciisaa

Android based mobile dictionary application project Page 13

Me (pron.) – Na; ana

Mead n. – daadhii-ni

Meager (adj.) – huqqaa, huqqoo, huqqoo

Measles n.- finnoo-ni

Measure v. – biima-biimita

Measurement n. – ciqilee-ni; waarii

Paper based English to Tigrigna translation of some wordstaken from first edition
(Zecarias, 2008).

Telephone - (n) ተለፎን

Television - (n) ተለቭጅ

Temperature - (n) ሙቐት

Temple - (n) ቤተመቕደ

Temporary - (aj) ግዚያዊ

Temptation - (v) ፈተነ

2.7. Strength and Weakness of the Existing paper based dictionary

2.7.1. Strength of the Existing paper based dictionary

The existing paper based dictionary has its own advantages:-

 Give the meaning of the word to the user.

 Identifies type (identifier)of word.
 It provides grammars knowledge to the user.

Android based mobile dictionary application project Page 14

2.7.2. Weakness of the Existing paper based dictionary
In the existing system, we have observed the following problems: -

 All the tasks have been done manually. So, the learner takes more time.
 The existing learning materials like textbook are easily damaged.
 It has no comfortable ways to access data easily and everywhere.
 Some part Data can also be lost since everything is on paper.
 Adding words is difficult once dictionary is published.

2.8. Alternative Solution

We try to describe the weakness of the paper based dictionary above and there are alternate
solutions for this weaknesses or problems. Developing android based dictionary which is easily
portable and accessible in anywhere in anytime.

Android based mobile dictionary application project Page 15

CHAPTER-3-

REQUREMENT SPECIFICATION AND ANALYSIS

3.1. Introduction
In this section we are correctly identify the functional and non-functional requirements for the
new proposed dictionary application and introduce the analysis model that clearly describe how
system will meet the requirement that we identified.

3.2. Description of the proposed mobile dictionary Application

The proposed mobile dictionary application is an application which runs on the Android platform
or operating system. It contains three language dictionaries: English-Amharic, English-Afaan
Oromo and English-to-Tigrigna. It will enable users to search the meaning of a word with a fast
manner and enable to get dictionary service everywhere on their mobile. Itenables the user to
listen pronunciation and it also displays image of the searched word. After the application is
developed, we can add words that mean the developers can modify the application.

3.2.1. User Characteristics

The user can interact with application to access the dictionary. To translate the meaning of
English language words into Amharic, Afaan Oromo and Tigrigna, the user should:-
The user selects dictionary type, after selecting the dictionary the user should type the word in
search bar and search the meaning and can view image and identifier. User can also listen
pronuonction of the word.

3.2.2. Constraints
Defines how well a system should perform a function, or set of functions. It is documented using
the following information: A measurable value, which can be used to judge the performance of
the system.

Response time: the database should display the meaning the corresponding language in short
period of time.

Android based mobile dictionary application project Page 16

  Error message: the database also display‘not found ‘message if word or picture of the
searched word is not found in database.
 Redundancy: if the same two or more words exist in database, database should display
those words because two or more words may similar in their character but differ in
identifier (noun, verb adjective).image maybe the same for deferent languages. Example
image of cat in Amharic and Tigrigna is the same.

3.2.3. Assumptions of and Dependencies

We assume that to use this application the user can have mobile usage skill how to open and
close the mobile and they should close or exit the application properly. and we assume that the
application gives the services for the user efficiently and effectively.

3.3. Requirement Specifications

3.3.1. Functional Requirement

A functional requirement defines a function of a system or its components. A function is

described as a set of inputs, the behavior, and outputs. Functional requirements may be
calculations, technical details, data manipulation and processing and other specific functionality
that define what a system is supposed to accomplish. The functional requirements of the
proposed application are listed below

 The user selects dictionary.

 The user enters the word in search bar.
 The database provides searching facility.
 The database searches the definition.
 The database display definition
 The database displays an appropriate error message if word not found in database.
 The database enables users to listen pronunciations
 The database enables users to view images

Android based mobile dictionary application project Page 17

 3.3.2. Non-Functional Requirement

A non-functional requirement is a requirement that specifies criteria that can be used to judge the
operation of an application, rather than specific behaviors. The non-functional requirements of
our application include the following:

 User interface: The application will provide user interfaces that are compatible
with Android platform.
 Hardware consideration: The users should have cell phones that can run on the
Android operating system.
 Performance characteristics: The dictionary will be accessed by the mobile
owner. It should be given more emphasis for the speed to retrieve meaning and
pronunciation.
 Error handling: This application handles words which are not available in the
database, entered by the user and display error message.
 System security: The user can make their mobile secure by using security codes or
other measures.
 Quality issue: the information in the database should be accurate.
 Modification capability: implies the system should have easily modifiable by the
developer said to release latest version of the application.

3.4. System modeling

In analysis model we try to introduce analysis of the new system using use case diagram,
sequence diagram, and activity diagram, class diagram, of a system.

This system focuses on three different models of the system:-

Use case model - describes the functionality of the system from the user’s point of view.

The object model- represented in UML with class diagrams. It describes the structure of a
system in terms of objects, attributes, associations, and operations.

The dynamic model- represented in UML with sequence diagrams, state chart diagrams, and
activity diagrams. It describes the internal behavior of the system.

Android based mobile dictionary application project Page 18

 3.5. Actors Identification

We identify two actors of the system. This are:-

 The user: any user who use the dictionary.

 Administrator: a person who controls dictionary.

3.5.1. Use-case Identification

 Use cases:
 select dictionary
 Enter word
 search Meaning
 display Meaning
 listen pronunciations
 view images
 view identifiers
 modification of dictionary application

3.5.2. Use-case Diagram

The use case diagram for the dictionary application provides an external view of a dictionary. In
this system, the user types the word in search bar to find the meaning of that word. The database
searches the meaning for the given word. If the word is available in the database, then the
database retrieve and display the meaning for the word otherwise it shows the message, the word
does not found in the dictionary.

Android based mobile dictionary application project Page 19

 User

Figure3. 1 Use-case Diagram

Android based mobile dictionary application project Page 20

 3.5.3. Description of Use-case
Table 3. 1 : use case description for the use case Select Dictionary.
Use case name Select dictionary
Use case ID UC1
Actor User
Description The user selects dictionarybefore searching
and home layout is displays.
Precondition The dictionary that is going to be selected
should be existing and the home layout is
displayed.
Basic course of action: 1. User selects the dictionary from the home
layout.
2. The home layout displays the selected
dictionary and its layout.
Post condition Search layout of the selected dictionary is
displayed.

Table 3. 2: use case description for use case Enter Word.

Use case name Enter word
Use case ID UC2
Actor User
Description The user enters the word in the selected
dictionary search layout.
Precondition The user should know the spelling of the
word and the search layout of the selected
dictionary should be displayed.
Basic course of action 1. The user knows the correct spelling of
the word.

Post condition The meaning of the word displayed

Android based mobile dictionary application project Page 21

Table 3. 3: use case description for Search meaning.
Use case name Search Meaning
Use case ID UC3
Actor Admin
Description This use case searches the meaning of the
word from the selected dictionarydatabase.
Precondition The user selects the dictionary from the home
layout and the search layout of the selected
dictionary should be displayed.
Basic course of action 1. The user enters the word.
2. The user presses the search button.
3. The database displays the meaning.
[A1]
4. The user reads the meaning
Alternative solution[A1] 1. The word that is entered by the user is
not found in the database.
2. The database go back to step 1.
3. The user enters correct word.
4. The user press the search button

Post condition Display the meaning of the word.

Uses UC3

Table 3. 4: use case description for use case Display meaning.

Android based mobile dictionary application project Page 22

Use case name Display meaning
Use case ID UC4
Actor Admin
Description The database displays the meaning of the
word.
Precondition The meaning should be found in the database
and the user should enter the correct word.
Basic course of action 1. The database searches the meaning of
the word.
2. The database displays the meaning of
the enterword [A2].
Alternative solution[A2]
1. The word is not found in the database.

Post condition The user reads the meaning of the word.

Table 3. 5: use case description for use case Listen Pronunciation.

Android based mobile dictionary application project Page 23

Use case name Listen Pronunciation
UCID UC5
Actors User
Description The user listens how the word will be
pronounced
Precondition Meaning of the word should be found in the
database and should display the meaning.
Basic course of action 1. The user enters the word.
2. The users press the audio button.
3. The database downloads the audio from
database.
4. The user listens the pronunciation [A3].
Alternative solution[A3] 1. The audio is not found in the database.

Post condition The user knows the pronunciation of the word

Table 3. 6 : use case description for use case view Image.

Use case name View Image
Use case ID UC6
Actor User
Description It is used to view an image of the entered
word.
Precondition The image should be found in the database
Basic course of action 1. The user enters the word
2. The users press the image button.
3. The database download the image from
the database[A4]
4. Image displays on the image view
5. The user views the image
Alternative solution[A4] 1. The image is not found in the database
Post condition User know the image of the typed word

Android based mobile dictionary application project Page 24

Table 3. 7: use case description for use case for modification.
Use case name Modification

UCID UC7

Actors Admin

Precondition The database should available.

Basic course of action The admin Modifies (insert, delete, and update)
the dictionary if new features or word exists
[A5].

Alternative solution[A5] admin cannot modify the dictionary

Post condition The user understands upgrading (modification)

of the dictionary.

Android based mobile dictionary application project Page 25

CHAPTER -4-

SYSTEM DESIGN

4.1. Introduction
In this section the systems is described by defining the design goals of the project, by
decomposing the system into smaller subsystems that can be easily realized (proposed system
architecture) and by selecting strategies for building the system, such as the hardware/software
platform on which the system will run, the persistent data management strategy and the handling
of boundary conditions.
The result of system design is a clear description of each of these strategies, sub system
decomposition, and a deployment diagram representing the hardware/software mapping of the
system.

4.1.1. Design Goals Criteria

The application is expected to run on smart phones that can run on the Android platform or
operating system. Therefore, the design goals criteria stated in this section consider this fact to
determine the performance, dependability, cost, maintenance and end user criteria.

Performance

 Response time: the response time for searching definitions should be fast. To attain this
goal, coding should follow simple, efficient and fast algorithms. Especially looping
statements shall be avoided (if possible) or minimized. For example instead of using loop
for retrieving a specific record form a table use SQL statement.
 Memory: size of multimedia parts like image and pronunciation or audios files should
not large. Since the memory of mobiles is small in size. so size of the application should
not be large.
 Reliability: The system shall be tested after and during development process to verify
that whether the specified services are available or not. And also it should give consistent
and correct output for various type of input it is given.
 Availability: The multimedia contents and meaning of words shall be available 24hrs..

Android based mobile dictionary application project Page 26

  Modifiability: In order to make the system flexible and easy to modify its functionality
some of its feature shall be modifiable.
 Portability: The application shall be developed to run on android environment therefore
it is not portable to run on any environment which is not android enabled.
 Traceability of Requirement: The system shall be developed according to the system
analysis and the design specification and it shall not incorporate anything beyond.
Otherwise newly incorporated functionality shall be documented.

End User

 Usability: The application shall be developed to be easy for user understanding.

Especially in developing the user interface it is better to keep the user dictionary in
mind.

4.2. Activity Diagram

An activity diagram is essentially a flowchart, showing flow of control from activity to activity it
involves:
 modelling the sequential (and possibly concurrent) steps in a computational
process
 Modelling the flow of an object as it moves from state to state at different points in
the flow of control.
 Activity diagrams emphasize the flow of control from activity to activity.

Android based mobile dictionary application project Page 27

 Open

Figure 4. 1: Activity diagram for select dictionary

Android based mobile dictionary application project Page 28

Figure 4. 2: Activity diagram for search meaning

Android based mobile dictionary application project Page 29

 Dictionary user

User enter word

User press Audio

Button

Not Found Found

Display eror
message
Play Audio

Figure 4. 3: Activity diagram for listen pronunciation

Android based mobile dictionary application project Page 30

 Dictionary user

User enter word

User press image

view Botton

Not Found Found

Display eror message

view image

Figure 4. 4: Activity diagram for view image

Android based mobile dictionary application project Page 31

 Dictionary user

open

modfiey

No
can not modifey

yes

modfiey successfull

Figure 4. 5: Activity diagram for modification

Android based mobile dictionary application project Page 32

 4.3. Sequence Diagram

Sequence diagrams are an easy and intuitive way of describing the behavior of a system by
viewing the interaction behavior of the system and its environment. A sequence diagram shows
an interaction changed in a time sequence. It shows the object participating in the interaction by
their lifelines and the messages they exchange arranged in time sequence. Generally, this
diagram shows a succession of interaction between object instances over time.

The sequence diagram is very simple and has immediate visual object appeal. This is its great
strength. It is an alternative way to understand the overall flow of the control of a program.
Instead of locking at the code and trying to find out the overall sequence of behavior, we can use
diagram to quickly understand the sequence.

Dictionary Dictionary Dictionary

Dictionary
user Button control List Layout

1: open()
2: activate()
3: generate()

4: display List()
6 : activate()
5: select list Dictionary()

7: display select layout()

Figure 4. 6: Sequence diagram for Select dictionary

Android based mobile dictionary application project Page 33

 Text input Text Iput Field Predicate
user <<UI>> Controler<<UI>> Word

1: IputText()
2: activate()
3: generate()

4: get word

Figure 4. 7: Sequence diagram for enter word

Android based mobile dictionary application project Page 34

 Text input Text Iput Field
Database
user <<UI>> Controler<<UI>>

1:Type Word()
2: Load|| Process()
3: SendRequest()

5: Press voice Button

4: get word

6: Play Audio

Figure 4. 8: Sequence diagram for Listen Pronunciation

Android based mobile dictionary application project Page 35

 Text input Text Iput Field
Database
user <<UI>> Controler<<UI>>

1: Type word()
2: Load|| Process()
3: SendRequest()

5: Press Image Button

4:Display Image on
Layout

6: See Image

Figure 4. 9: Sequence diagram for View Image

Android based mobile dictionary application project Page 36

 Text input Databas
Search Button Word item
user <<UI>> e

1: InputText() 3: SendRequest()

2: Press ()
3: Search()

4: Result Display()

Chek
()

5: does not exist

Figure 4. 10: Sequence diagram for Search Meaning

Android based mobile dictionary application project Page 37

 Text input
Search Button Word item
user <<UI>>

Enter word()

3: SendRequest()

2: Press ()

3: Search()

4: Result Display()

5: View identifiers

6: does not exist

Figure 4. 11: Sequence Diagram for View Identifiers

Android based mobile dictionary application project Page 38

 Modify Modify
Modify Database
dictinary form Controller
Admin

Select dictionary

Display Modify form()

Administrator fill modify

form()

Submit() Validate()

Try again()

Continued()

Edit()

Save()

Figure 4. 12: Sequence diagram for modification

4.4. Class Diagram

Class diagrams are used to describe the structure of this system. Classes are abstractions that
specify the common structure and behavior of a set of objects in the new system.

Android based mobile dictionary application project Page 39

 User

Figure 4. 13: class diagram

4.5. Database Model

4.5.1. Entity Relationship Diagram (ERD)

Entity Relationship Diagram is used to represent conceptual view of the database That includes
entities, attributes, relationship.

Android based mobile dictionary application project Page 40

 Admin

pronoun 1
pronoun

verb
English m m Amharic Adjective
controls
Language Language

Adjective

noun
noun m
Afaan
verb
oromo
Language

pronoun

noun
verb
adjective

Figure 4. 14: Entity relation diagram

4.5.2. Persistence Modeling

Persistence models in our system are used to communicate the design of database. In the
following diagram the three classes have one-to-one relation with the image class. Because a
word may have different meanings with different languages but it has one image for that word if
the word is noun. For example the word Elephant has different meanings with different
languages but the image is the same.

Android based mobile dictionary application project Page 41

 Amharic

PK Englishword Varchar(23)

AmeharicMeaning varchar(123)
AmeharicAudioFile varchar(23)
AmeharicIdentifers varchar(12)
AmeharicModfiey varchar (234)

Image

PK Word varchar(123)

ImageName Varchar(22)

Tigrigna

Afanooromo
PK Englishword Varchar(23)

TigrignaMeaning varchar(123)
PK Englishword Varchar(23)
TigrignaAudioFile varchar(23)
TigrinaIdentifers varchar(12) Afaan oromoMeaning varchar(123)
TigrignaModfiey varchar (234) Afaan oromoAudioFile varchar(23)
Afaan oromoIdentifers varchar(12)
Afaan oromoModfiey varchar (234)

Figure 4. 15: persistence modeling diagram

Android based mobile dictionary application project Page 42

 4.5.3. Mapping with Normalization
In order to store information persistently we map objects into tables and the attributes into fields
to the specific table based on the objects found on the system. Therefore, we identified four
major tables that will be implemented on the selected DBMS. For this reason, the mapping of
objects to tables is displayed as follows

Dictionary

Figure 4. 16: Mapping of tables with Normalization

Android based mobile dictionary application project Page 43

 4.6. Subsystem Decomposition
The purpose of subsystem decomposition is to breakdown a given system into smaller systems,
which are loosely coupled with each other while each broken-down system has strong cohesion
among its components. In order to simplify and minimize the complexity of the solution domain,
the proposed Android mobile dictionary application is decomposed into four subsystems namely
Layout subsystem, Search subsystem, Dictionary subsystem and Database subsystem.

Each subsystem has its own function and there is also communication among them to exchange
information. The system is decomposed according to the specialized task it performs to ensure
high coherence. The level of coupling is relatively low because the interactions between
subsystems are only exchange of data.

Layout Subsystem

This subsystem is responsible for providing explanation and description about the developed
system to the target environment.

Search subsystem

This subsystem deals with the search facilities of the system. It involves the interaction of the
dictionary users with the system to get definitions or meanings of words, images and
pronunciations. Therefore, this subsystem provides the following facilities.

 Search English to Amharic, English to Afaan Oromo, English to Tigrigna.

 Get pronunciation and image using image and audio URLs from database.

Dictionary Subsystem

Dictionary is responsible to maintain information for all English to Amharic, English to Afaan
Oromo and English to Tigrigna data. It deals with maintaining requirements of the system that is
required to display dictionary data and it is also responsible for upgrading the database version.

Therefore dictionary subsystem provides the facilities

 Maintain dictionary data - the system allow the users to view meanings of words
for the three dictionaries
 Upgrade the database version if new version is available.
Android based mobile dictionary application project Page 44
Data base Subsystem

This subsystem is responsible for storing words pronunciations and images.

The mobile client gets images and pronunciations of words from database.

«Subsystem»

«Subsystem»
«Subsystem»

«Subsystem»

Figure 4. 17: Subsystem decomposition for the Dictionary application

(Folders represent subsystems, dashed lines represent dependencies)

4.7. Deployment Diagram

This portion of this document depicts the deployment of the components described above
diagrammatically. The client and database involved on the system, having deployed appropriate
components. Component diagrams can be embedded into deployment diagrams effectively.

Android based mobile dictionary application project Page 45

 CC

Figure 4. 18: Deployment Modeling for Dictionary application

4.8. System Architecture (Layered Architecture of the system)

System architecture is a high level structure of software system, the discipline of creating such
structures, and the documentation of these structures. The general architecture of the proposed
system is broken down into user interface, the Controller Layer and the data access layer.

The user interface component is responsible for the explanation of the developed system to the
target environment.

The controller is the means by which the user interacts with the application. It gets input from the
user and handles the way the view and the data access layer take action on the given input. It is
responsible for mapping end-user action to application response by interpreting the key press
event from the user. The user interacts with the system through several events like a button click,

Android based mobile dictionary application project Page 46

menu choice, and text field entry and voice button. Depending on the user action and the
provided output from the data access layer, the controller reacts by selecting the appropriate
view.

The data access layer is the layer that manages the state of the application and conducts all the
required functionalities. It holds the behavior and the data of the application domain and
responds to requests made for information. This layer accepts word entry from the user interface
on the view layer, generates the desired result performing the necessary actions and finally
passes the obtained result to the user interface.

Figure 4. 19: System architecture

Android based mobile dictionary application project Page 47

 4.9. User-Interface (UI) Design
User interface design focuses on the user's experience and interaction with our system. Our goal
in user interface design is to make the user's interaction as simple and efficient as possible, in
terms of accomplishing user goals.
User interface design is the overall process of designing how a user will be able to interact with a
system.

Figure 4. 20: User-Interface (UI) Design diagram

Android based mobile dictionary application project Page 48

 4.10. UI Flow Diagramming

Dictionary

Figure 4. 21: User interface flow diagram

Android based mobile dictionary application project Page 49

CHAPTER -5-

IMPEMENTATION AND TESTING

5.1 INTRODUCTION
In this chapter we are going to explain about System Implementation and testing ,algorithm
design and sample code, features to be tested and not tested, success and failerity of our project ,
the strategy and test cases with specifications.

5.2 sample code

Sample code for choosing/switching dictionary type.

package com.example.ethiodictionary;
public class MainActivity extends AppCompatActivity
implementsNavigationView.OnNavigationItemSelectedListener {

mtabLayout.addOnTabSelectedListener(new TabLayout.OnTabSelectedListener() {

mtabLayout.addOnTabSelectedListener(new TabLayout.OnTabSelectedListener() {

@Override
public void onTabSelected(TabLayout.Tab tab) {
Pager.setCurrentItem(tab.getPosition());
}

@Override
public void onTabUnselected(TabLayout.Tab tab) {

@Override
public void onTabReselected(TabLayout.Tab tab) {

Android based mobile dictionary application project Page 50

 }
}
);

5.3 features to be tested and not tested

5.3.1 Functional features to be tested

Test Case 1: Choose(select) dictionary

Test case description: users should select the dictionary. Users choose dictionary

Test setup/Preconditions:The dictionary that is going to be selected should be existing and the
home layout is displayed.

Actions Results
The user should select the dictionary. 1. User selects the dictionary from the
home layout.

2. The home layout displays the selected

dictionary and its layout

5.3.2 non-functional features to be tested

 User interface: The application provides user friendly interfaces that are
compatible with Android platform.
 Hardware consideration: the dictionary application runs on any Android operating
system version greater than 4.1
 Modification capability: the application have easily modifiable by the developers
to add features or to release latest version of the application.

Android based mobile dictionary application project Page 51

 5.3.3 Features not to be tested
In this project displaying meaning, listen pronuonction, and view image features are not
to be test because we did not finish our project due to shortage of time .

5.4 pass/fail criteria

This project system have success in providing user interface which is user friendly which
means easer to understand for any one .and also the system provides choosing dictionary
types. But there is some failerity unable to search the meaning of word from database and
unable to view image and listen pronunciation.

5.5 Test cases with specifications

Our project system does not detect data output because the project is not finished yet that
means data in the database is inserted but not displayed.

Android based mobile dictionary application project Page 52

CHAPTER -6-

USER MANUAL

6. Scope
To use the dictionary the user first install the dictionary and after successful installation ,open the
dictionary and choose the language you want to translate and type the word in search bar .if the
word exists the meaning is displayed in all languages. The developers can add meaning of word
and update the dictionary if they want.

6.1 Installation and Configuration

To installing and using the dictionary application there should be a phone cell which supports
android operating system. The application only runs on mobile android system.

6.2 How to operate the system

The operation of the dictionary application is simple.

to operate the dictionary first open the dictionary.

Android based mobile dictionary application project Page 53

 then choose the dictionary type you want to translate example select Amharic to translate into
others.

Android based mobile dictionary application project Page 54

After selecting type dictionary type word in search bar and search the word.

Example shown below.

Android based mobile dictionary application project Page 55

Android based mobile dictionary application project Page 56
To use menu icons press hamburger icon as shown below.

to share, to return to home and exit the application and to use other buttons press the buttons.

Example to exit application.

Android based mobile dictionary application project Page 57

Android based mobile dictionary application project Page 58
CHAPTER -7-

CONCLUSION AND RECOMMENDATION

7. Conclusion
We tried our best to develop a four bilingual language dictionary application mostly that will
support an English, Amharic, English, Oromiffa and Tigrigna language words. If This dictionary
application project will be finished, it can give a great advantage for a country like Ethiopia
which is a multi-lingual country by giving the meaning in four different languages successfully.
Moreover this application is applicable for any users who can read and wants to know the
meaning in Amharic, English, Oromiffa and Tigrigna. We cannot fully achieve the objective that
was described in industrial phase I because of time shortage and other resource like internet .

7.1 Recommendation

Since our country is multi-lingual and multi-national, we recommend the people of our country
to finish and use this dictionary application by installing in their smart phone. The application is
also based on many languages and every one can use it to develop his/her language skill. Mostly
we recommend to use this application the people who can speak and write Amharic, English,
Oromiffa and Tigrigna because the application is basically based on those four languages and we
advise the people who speak and write these languages to use the application and make
advertisement to other users to use the application like them. So, we strictly recommend the user
to expand the usability of the application to others.

Android based mobile dictionary application project Page 59

Reference
Bible. (2010, 3 1). (Koehn, Statistical Machine Translation,, 2010). Retrieved from Datum:

Koehn. ( 2010). Statistical Machine Translation. Retrieved from http//www.statmt.org

Tseng. (No.3, September 2003). Fan-ping Tseng,”EFL Students‟ Yahoo! Onlinemultilingual

Dictionary Use Behavior” English Language Teaching,.

Zamari, Z. M. (2011). “Dictionary Use Among Students Of Higher Learning” (Malaysia:Institut

Pengurusan Penyelidikan Universiti Teknologi Mara 40450 Shah Alam, Selangor, ).

Zecarias, E. (2008). Dictionary from English to language.

zlalem, A. (206). dictionary English to amharic language.

Android based mobile dictionary application project Page 60