Embed Size (px)
Citation preview
UNIVERSITY OF ZULULAND
Online Interactive Indigenous Health Forum
Julien Cedric NYAMBAL
201263862
Friday 17th October 2014
Supervisor: Mr Pragasen MUDALI
Table of Contents1 Introduction........................................................................................................................5
1.1 Brief Introduction / Background of Study......................................................................5
1.2 Statement of Problem..................................................................................................5
1.3 Goal and Objectives....................................................................................................5
1.4 Scope...........................................................................................................................5
1.5 Justification/Rationale/Importance of Study...............................................................5
1.6 Approach/Methodology...............................................................................................6
1.7 Progression Timeline...................................................................................................6
2- Systems Analysis................................................................................................................7
2.1 Product Overview........................................................................................................7
2.2 Scope...........................................................................................................................8
2.3 Specific Requirements.................................................................................................8
2.3.1 External Requirements.........................................................................................8
2.4 Product Features........................................................................................................10
2.5 Software System Attributes.......................................................................................10
2.5.1 Reliability...........................................................................................................10
2.5.2 Availability.........................................................................................................10
2.5.3 Security..............................................................................................................10
2.5.4 Maintainability...................................................................................................10
2.5.5 Portability...........................................................................................................11
2.5.6 Performances......................................................................................................11
2.6 Database Requirements.............................................................................................11
2.6.1 Connection to Liferay’s Database......................................................................11
2.6.2 Database Population...........................................................................................11
2.7 Additional Material...................................................................................................12
2.8 Diagrams....................................................................................................................12
3- Design Create Account Portlet.........................................................................................16
3.1 Purpose......................................................................................................................16
3.2 Scope.........................................................................................................................16
3.3 Design Overview.......................................................................................................16
3.4 System Architectural Design.....................................................................................16
3.4.1 Chosen System Architecture..............................................................................16
3.4.2 System Interface Description.............................................................................17
3.5- Detailed Description of Components........................................................................17
3.5.1- Dropdown menu for Language selection...........................................................17
3.5.2 The other components........................................................................................17
3.6 User Interface Design................................................................................................18
3.6.1- Description of the user interface........................................................................18
3.7 Diagrams....................................................................................................................19
4- System Design and Implementation (Forum Part : Message Boards).............................20
4.1 Purpose...................................................................................................................20
4.2 Scope......................................................................................................................20
4.3 Design Pattern........................................................................................................20
4.4 System Architectural Design.................................................................................22
4.5 Detailed Description of Components........................................................................24
4.6- User Interface Design................................................................................................25
4.6.1 Description of the User Interface.......................................................................25
4.7 Diagrams....................................................................................................................26
5- System testing..................................................................................................................27
5.1 System Overview.......................................................................................................27
5.2 Test Approach............................................................................................................27
5.3 Test Plan....................................................................................................................27
5.3.1 Features to be Tested..........................................................................................27
5.3.2 Features not to be Tested....................................................................................27
5.3.3 Testing Tools and Environment..........................................................................27
5.4 Black Box Testing.....................................................................................................28
5.5 White Box Testing.....................................................................................................28
5.6 Test Cases..................................................................................................................30
5.5- Additional Material...................................................................................................30
6- Conclusion........................................................................................................................31
6.1 Overall Experience....................................................................................................31
6.2 Problems encountered...............................................................................................31
6.3 Limitations.................................................................................................................31
6.4 Future enhancements of the system...........................................................................31
1 Introduction
1.1 Brief Introduction / Background of Study
Online Interactive Indigenous Health Forum is developed for the Research Centre of the
Computer Science department at the University Of Zululand. Online Interactive Indigenous Health Forum is an e-health forum focussing on the
contribution of the indigenous knowledge to the non-rural community.Many systems like this project are already up, they use a single declared language, for the
users to communicate.
1.2 Statement of Problem
E-health community today is very useful today .It is a great alternative before going to the
clinic or hospital. But in some areas (rural areas mostly), the language used in those forum is
not always common to the audience who want to benefit from advices. Similarly, some
people would like to participate but the language they used will not be understood by the
majority of the audience.
1.3 Goal and Objectives
GOAL :The main goal of the project is to customize a LifeRay portlet for the dynamic
translation of languages of posts on the forum.
OBJECTIVES: To provide option (button) to choose between languages for
languages(English<=> Zulu) To translate between languages dynamically posts from one user’s page to
another To create a demo Indigenous Health Forum
1.4 Scope
- The translation will be only between English and Zulu - The functionalities of normal online forum will remain unchanged except the
addition of a dynamic translator
1.5 Justification/Rationale/Importance of Study
The target of the Online Interactive Indigenous Forum (OIIHF) is to bring on the
same platform diversity, rural and urban areas from this forum will share knowledge.
The OIIHF, because of the translation engine might help people from rural area to
improve their English while contributing to the forum, and people from urban areas
might also want to learn a Zulu while contributing to the forum.
Internet is growing fast and reached now rural areas. English is not common to
everybody (International language used widely on Internet , so used in most of the
existing health forum websites ) , especially in those rural areas , so one from the
rural area would want to be active in the WEB , and express him/herself in his/her
native language . The OIIFH will give a chance to that category of people by letting
them to contribute freely in the forum.
1.6 Approach/Methodology
Since no such system is out yet, the objectives stated above will be achieved
incrementally and in and iterative way to produce concrete prototypes. From those
prototypes, a clear idea of the system will be, and functionalities will be added per
iterations. Model-View-Controller (MVC) will be used as the design pattern for the
project.
Prototypes
Prototype 1: Customized forum LifeRay portlet (No functionalities)
Prototype 2: Customized forum LifeRay portlet (With Google translation engine
implemented)
Prototype 3: Customized forum LifeRay portlet (With databases functionalities)
Prototype 4: Customized forum LifeRay portlet (Full functionalities)
1.7 Progression Timeline
1.1 Familiarisation with Liferay platform 1.2 Assessment of existing forum LifeRay portlets1. Production of Customized forum LifeRay portlet prototype (No functionalities) 2.1 Acquire knowledge on Google Translate Engine (Translate Toolkit by Google) 2.2 Test and assessment of the accuracy of Google Translate Engine 2.3 Implement Google Translate Engine in the selected forum LifeRay portlet2. Production of Customized forum LifeRay portlet prototype (With Google
translation engine implemented)- 3.1 Acquire knowledge on LifeRay database implementation- 3.2 Assessment and selection of the best database to use relative to the selected
forum portlet Graphic User Interface (GUI)- 3.3 Implement database functionalities for the selected forum portlet- 3.4 Test the forum portlet with the database functionalities with sample data 3. Production of Customized forum LifeRay portlet prototype (With databases
functionalities)- 4.1 Create a demonstration of the final Indigenous Health Forum4. Production of Customized forum LifeRay portlet prototype
2- Systems Analysis
2.1 Product Overview
Online Interactive Indigenous Health Forum is a web application client server based that will
bridge the gap between people using different human languages to communicate in a
community online forum. Online Interactive Indigenous Health Forum will give the
impression to user that everybody speaks his/her language.
Fig 1.1: Product overview
2.2 Scope
Language: translation from English to Zulu will only be for the first version. The language
used in both side must be as formal as possible.
Translation feature: The present document will only stress on the translation feature and
how the translation has been integrated in a working environment (Liferay) where all the
other components have been checked and approved.
2.3 Specific Requirements
2.3.1 External Requirements
2.3.1.1 User Interfaces
2.2.1.1.1 Registration Page
This page contains fields that will be filled by the user with his/her credentials:
- First Name (which is a required field)
- Last Name (not required)
- Email Address( required )
- Text Verification, usually called CAPTCHA .This field is works with a box that
contains a random set of characters that the user needs to enter. This is just to check if
a program is trying infinitely to create account to flood the database with fake
accounts .
- Preferred Language (Compulsory). This is the main feature in this form. This field
is a selection between English and Zulu.
2.3.1.1.2 Message Boards (Forum) Page
Refer to the Liferay Portal Administrator's Guide 6.0, from page 200(Using Liferay) to
page 202 (Join picture)
2.3.1.1.3 Forgot password Page (Refer Fig 4)
- Email address field : will be used by the server to send back the password to the user
- Text Verification (As in the registration)
- The chosen security question : the answer of that security question will determine
whether or not the email gets sent or not
2.3.1.1.4 Sign In (Refer Fig 5)
- Email address field of the user recorded at registration time
- Password corresponding to the email address
2.3.1.1.5 Admin account of the Portal (Refer Fig 2 and Fig 1)
Refer to the Liferay Portal Administrator's Guide, from page 202(Using Liferay) to
page 204
2.3.1.2 Hardware Interfaces
Online Interactive Indigenous Health is hardware independent. As said before, Online
Interactive Indigenous Health website adapts to the screen host but that hardware host does
not influence the running of Online Interactive Indigenous Health. Online Interactive
Indigenous Health can be viewed on PC, tablets and mobiles phones (smartphones). All those
above stated devices must be able to connect to a computer network where the server is
running (wired or wireless).
2.3.1.3 Software Interfaces
Online Interactive Indigenous Health will be hosted on a server application (Tomcat 7).For
the server to run, some few requirements regarding software should be met : The host
machine should have:
- JDK1.6 to run the Tomcat server,
- A command prompt application (Terminal from Linux or Command prompt from
Windows),
- An internet browser well set ,
- A database management system (MySQL5.5+),
- A text editor to make modifications to the server’s settings (Notepad++).
So the client should have a device (Computer or handheld) that has a web browser to access
the content of the website.
2.3.1.4 Communication Interfaces
Online Interactive Indigenous, during this experimental version will work locally ( within the
same network ) precisely about a Campus Area Network (CAN). A CAN is made up of Local
Area Networks (LAN) , so , if the server is installer in that CAN , wherever a client is within
that CAN , and whatever channel(wireless or wired) the client will use , the client will be able
to access the content of the page . As long as the server of the CAN provides the right IP
address to the client through DHCP of the current network where the client is , the client
should be within the range of the server .
2.4 Product Features
- Translation of posts from one language to the preferred language of the user in the
message boards portlet.
- For the other basic features of Liferay (Sign-in , Admin…) Refer to the Liferay
Portal Administrator's Guide, from page 200(Using Liferay) to page 204
2.5 Software System Attributes
2.5.1 Reliability
Online Interactive Indigenous Health Forum will be built and tested on top of the well know
Liferay platform. Liferay is known as stable and robust to failure and crashes. Online
Interactive Indigenous Health is an extension of Liferay portal. Which implies that the system
to be built will be as robust as Liferay itself.
The translation part is the product of the Microsoft Translator Java API , which will give you
the same results as if you are using Bing Translation
2.5.2 Availability
Like any other website, Online Interactive Indigenous Health Forum will be available only
and only if the server is up and running, and if the user is within the network range of the
Server.
2.5.3 Security
Online Interactive Indigenous Health Forum will be built on top of Liferay, and Liferay is
secured when just out of the box .By default, the Liferay’s encryption algorithm is set to SHA
(SHA-1).The key size of the Online Interactive Indigenous Health Forum will be modified
MD5 encryption algorithm , which is stronger that SHA-1 to improve the security . (Ref: ).
2.5.4 Maintainability
Online Interactive Indigenous Health Forum will be easy to maintain, given that Liferay has a
very good structure and organisations. The modifications brought to the Portal regarding the
translation have been done according the Software Engineering rules of Design making the
changes easily feasible without knowing much about the rest of the system. A folder
containing most the modifications of the Portal is provided and the content is easy to manage.
Concerning the Translation feature , comments have been made to give directions for changes
. The code is easy to understand and very short .
2.5.5 Portability
On the client side, the website is not stored in the device, the user will just call the website
and host the page on the device he/she uses. It means that the website will be available in any
device having a well configured web browser.
The Liferay platform hosting the Online Indigenous Health forum will be portable to be
installed in any desired production server.
2.5.6 Performances
Online Interactive Indigenous Health Forum is hosted in a server and is called from a client
from a network node. The further the node is from the server, the larger the response time.
The accuracy of the translator has a success rate of around 50%, so the results won’t be that
objectives as they are supposed to be.
2.6 Database Requirements
Liferay comes in the box with a template database hsqldb (HyperSQL DataBase). For Online
Interactive Indigenous Health Forum, a more flexible and productive database will be used,
MySQL. When set , MySQL is filled with default Liferay’s data .
2.6.1 Connection to Liferay’s Database
To connect to the Liferay Portal to a MySQL database , a file called portal-ext.properties has
been created and placed in the Liferay Home (Liferay-portal-Edition\portal-ext.properties ) .
That file contains very important configurations of the Liferay portal . For the database :
jdbc.default.driverClassName=com.mysql.jdbc.Driver
jdbc.default.url=jdbc:mysql://localhost:3306/lportal?
useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
jdbc.default.username= mysql username of the currently installed database
jdbc.default.password= mysql password of the currently installed database
The database is called lportal .
2.6.2 Database Population
A new column that holds the user’s language has been created to keep the preferred language
of the user . That column is resides in a table called CUSTOM_FIELDS and the column is
called Preferred-Language . The userId is the primary key and foreign in the table
CUSTOM_FIELDS .
The User-Id is also primary key in the table user_ (keeps data about all the registered users in
the forum) . The userId and messageId are primary key for the table mbmessage(keeps the
data about posts of each user , even anonymous users ).
2.7 Additional Material
On the server side, For Online Interactive Indigenous Health Forum will host the application
server Apache Tomcat Version 7. For simplicity, the IDE (Integrated Development
Environment) will be used as launcher of the server.
2.8 Diagrams
Fig 2.1: Use cases
Fig 2.2: Flow of the Online Interactive Indigenous Health Forum
2.9Scrrenshots
Fig1 : Admin Account Control Panel Page
Fig 2 : Admin Account Page
Fig 3 Create Account Page
Fig 4 Forgot password Page
Fig 5 Sign in page
3- Design Create Account Portlet
3.1 Purpose
The purpose of this document is show the improvement on the structure of the Create
Account Portlet provided by Liferay . The Create Account Portlet is one step before a full
access to the message boards (Online Interactive Indigenous Health Forum). That new feature
will help the user to choose his/her preferred language during registration time .
3.2 Scope
This description won’t cover the entire process of the registration provided by the normal
Liferay registration form (Create Account Portlet) . The document will stress on the impact of
the new feature added to the current system in place .
3.3 Design Overview
Figure 3.1: Registration Portlet Data Flow Diagram
3.4 System Architectural Design
3.4.1 Chosen System Architecture
In the previous system and in the modified system, the client-server architecture is used to
exchange data .
Figure 3.2: Architecture of the Create Account portlet Liferay .
This architecture has been kept because no change on the flow of data has been done .
The choice of the language always goes with the whole Create Account form of the previous
system.
No other architectural style could fit in this system. The Liferay server is
compulsory for any transaction between components.
3.4.2 System Interface Description
As stated in the scope , we will stress on the new feature added to the system . As stated
before , the new feature will help the user to choose his/her language during registration
time . The option will be on the Create Account Portlet . It will be made dropdown list
like :
Figure 3.3: Feature to be added
Figure 3 represents how the feature will look like on the Create account page. This feature
will be place just after the Text of Verification (CAPTCHA) . Dashes are present in figure 3
to represent the dropdown that will happen when the user will click on the feature , then
the user will have the choice between the available languages .
3.5- Detailed Description of Components
3.5.1-Dropdown menu for Language selection
The dropdown menu for the language selection will set the language of all posts of the user in
that preferred language. That feature will be linked to the Liferay Table User_ and an
additional column will be created to store the choice of each user .
3.5.2 The other components
(See Reference (1))
3.6 User Interface Design
3.6.1-Description of the user interface
3.6.1.1 Screen Images
Figure 3.4 Create Account page
Figure 3.5 Forgot Password
Figure 3.6 Sign In
3.7 Diagrams
Diag 1 : Sequence diagram Create Account
4- System Design and Implementation (Forum Part :
Message Boards)
4.1 Purpose
This document will describe in detail how the translation between languages from one user
to another will take place.
4.2 Scope
The solution developed here is to enable the system to be able to dynamically translate
between language according to the preferred language selected by the user during
registration . In accordance with the SRS , the translation will be limited to English
and Zulu , and the accuracy of the translation will entirely depend on the Google Translate ,
and the description will be focused on the translation feature as we are reusing a working
software.
4.3 Design Pattern
Online Indigenous Health Forum has been designed based on the MVC(Model-View-
Controller) design pattern .
Components are well separated to perform the required tasks .
Figure 4.1: Design Pattern of the Online Indigenous Health Forum ()
This figure illustrates the whole process of what happens in the system.
User: The user is an entity that can register to the system but using the controllers (button to
create account for instance) . The user also can post on the forum , which is another type of
data that will go to the database and will be linked to the emitting user.
Controller: Based on the information provided by the user , an instance of a user is built in
the database based on the model of a user . The user will be using buttons , which will create
or update the database . For instance we have create account or we have post a message on
the forum.
Model: The model is the heart of the process. In the case of the translation the logic resides
here . All the processing happens here , after the user inputs the post , the transformation and
process will happen here , without directly modifying the database content , the view will be
updated based on the logic of the translation , that is just to do a translation based on the
language of the user . If the language of the user is different from the language of the post ,
then the post will be translated to the language of the user .
In practice all the implementation will be done in a Java class called translate(int userId,
String message) that will take 2 parameters , the user id (that will help to detect the user’s
preferred language ) the other parameter will be the message or post . The language of the
post will be checked again the language of the current logged user.
View: In the case of the translation, the view will correspond to the result of the logic applied
to the data by the model. What happens is, the text will suit the user’s language only when
that particular user will load the page. The model will evaluate the preferred user’s language
and the language of the post to return to the user the translated post into the preferred user’s
language.
Figure 4.2 : MVC design pattern applied to the Online Indigenous Health Forum system
4.4 System Architectural Design
4.4.1 Chosen System Architecture
In the previous system and in the modified system , the client- server architecture is
used to exchange data , and publish and subscribe(Topic based) used for the group
communication between the subscribers and the publisher(s).
Figure 4.3: Client-Server Architecture of the Online Interactive Indigenous Health
(Message Boards Liferay portlet ).
Figure 4.4: Publish and subscribe Architecture of the Online Interactive Indigenous
Health (Message Boards Liferay portlet ).
This client-server architecture and publish and subscribe have been kept because no change
on the flow of data has been done. The translation between languages on posts does not
change any critical flow of data.
No other architectural style could fit in this system. The Liferay server is compulsory for
any transaction between components. And on the other side, the publish and subscribe
architecture is still adopter for users to subscribe to group of communication.
4.4.2 System Interface Description
The system interface will not be different from the one provided by Liferay from the
Message Boards portlet , just the post will be translated according to the preferred
language of the user . That preferred language selected at registration time.
4.5 Detailed Description of Components
4.5.1 Message Boards Portlet + translation
The message board portlet has been modified (under Java combined with JSP) to suit the
solution. Changes will include the deletion of some items the modification of behaviour of
some other items .Everything regarding the translation will happen in the Message Boards
Home.
Figure 4.5 : Data Flow Diagram of the system with the translation
4.5.2 Message Boards Home
Message Boards Home is a predefined component of Liferay that host the forum part of the
System. Based on Figure 2 : Data flow diagram of the Online Interactive Indigenous
Health , a detailed view of the system is provided . If the user communicate using the
default language (English) , then the message remains as it is , but if the message is in Zulu
then , the post will travel to Google Translate for process , the post will come back
translated and a copy of that message will be stored in the database for forum feeding
purposes (all the previous conversations will be picked up from there) and finally the
translated post will travel to the user .
4.6- User Interface Design
4.6.1 Description of the User Interface
The User Interface of the forum is not different from any other forum in general. Liferay
provided with a template forum website which has been used to build the interface of the
Online Interactive Indigenous Health. Many components have been removed and some others
have been modified to make sure that user gets the functionalities straight from the first use
of the web site. The translation happens in the background after the post have been submitted
to the server.
4.6.1.1 Screen Images
Fig 4.6 : Translation In Forum
Fig 4.7: User replying to post
4.7 Diagrams
Dia1: Sequence Diagram
5- System testing
5.1 System Overview
The system to be tested is the Online Indigenous Health Forum , a website that is able to
dynamically translate posts in a forum according to the current logged user to the Forum.
5.2 Test Approach
White Box Testing associated with Black Box testing will be used to test the translation
functionality of the system . But since some external pieces of code have been introduced in
the solution, the results of the unit testing and integration testing will influence the White Box
Testing .
5.3 Test Plan
5.3.1 Features to be Tested
Online Health Indigenous Forum will be based on the translation feature only . Since the
system is an enhancement of the Liferay Platform , all the other components are assumed to
be working perfectly before integration of the solution , and Liferay environment is still
working fine with the integration of the translation feature.
5.3.2 Features not to be Tested
The features like :
- sign-in ,
- sign-out ,
- the functionalities of the forum ,
- the administration of the forum ,
- the accuracy of the translation
won’t be tested because , as stated earlier , they are basic functionalities of Liferay
environment . Those basic functionalities have been tested and approved to be up to standards
.
5.3.3 Testing Tools and Environment
The system testing environment and tools :
- Server computer in a Campus Area Network ( University of Zululand) :
The Server used here has been a local computer running Windows 7 Professional
Edition and another independent computer running Windows 8 Single Language (To
ensure the compatibility of the system with the new Windows Operation System)
- Liferay Tomcat Server (Liferay v6.2 CE (Tomcat 7))
- Proxy-free Internet Connection : The Microsoft API does not work with proxy
settings when testing took place
- The system will be tested in a Campus Area Network (University of Zululand)
5.4 Black Box Testing
The Black Box testing applied on the Online Indigenous Health Forum shows that the
solution found works well . The results displayed as expected : translation from one language
to another according to the preferred language of the user.
5.5 White Box Testing
The process of the translation within Liferay passes through some step to be able to act .
5.6 Test Cases
Test
ID
Name Condition Input Expected
Output
Pass (in
%)
Test
Procedure1 Basic
Operations
(Login ,
Loading
pages ,
Message
Boards
functionalit
ies)
Normal
condition
of usage
Website
2 Translate
correct
sentences
(words well
spelled)
Post
message
on
Message
boards
Sentence
(meaning
ful string
of
words)
Correct
translation
display
80 Hit
“Reply”
and enter a
sentence in
posting
area and hit
publish3 Translate
invalid
sentences(n
on-
meaningful
words)
Post
message
on
Message
boards
Sentence
(meaning
less
string of
words)
Same
meaningle
ss will be
displayed
100 Hit
“Reply”
and enter a
meaningles
s sentence
in posting
area and hit
publish4 Admin
account
activated
Admin
just logs
in
Posts of
the other
users
No
translation
will
100 The admin
loads the
message
happen boards
page5 Anonymou
s account
activated
Anonymo
us user
just loads
the page
Posts of
the other
users
No
translation
will
happen
100 Anonymou
s user loads
the page
6- Conclusion
6.1 Overall Experience
Online Indigenous Health Forum website has been a nice project to do because every side of
Computer Science is covered . Programming part , almost all the knowledge in computer
programming are required :
- Java (to build the custom method for the translation feature)- JSP(to create the User Interface of the website )- Some HTML knowledge (to better understand JSP)- CSS (optional but usable )- JS(optional but usable)- Some extra from Liferay Platform (Hooks , Struts , Service Builders…)
Online Indigenous Health Forum website also brings together some concepts of Software
Engineering:
- MVC (Model-View-Controller) which is the key design pattern of the the
Online Indigenous Health Forum- Publish-Subscribe architecture linked to Client Server Architecture to have a
best experience with distributed systems
Online Indigenous Health Forum also brought forward a new way to perform OOP ,
Inheritance and some other key concepts of Java Programming .
6.2 Problems encountered
6.2.1 Google Translate API
Online Indigenous Health Forum has been planned to used to have as translate engine the
Google Translate API . Despite the fact that the API is not free , efforts have been put to make
sure that the translation in the website is built according to the requirements and plan
presented in the proposal (Introduction).Even when requirements to use Google Translate
have been met , the set up hasn’t been easy to do unfortunately .Fortunately, Microsoft
Translator Java API has been used at the place of the Google Translate API.
6.2.2 Zulu Language Package
Zulu Language package seems not to be publicly available yet in any API on the Internet
(whether free or paid) . Research has been made for a very long period of time , and
techniques have been tried to incorporate Zulu in Online Indigenous Health Forum website ,
but nothing work .
6.2.3 Proxy settings
The OIHF hasn’t been able to work within the proxy settings of the environment where it has
been created . It has been a problem at the beginning of the process where the integration of
the Microsoft Translator API and the Google Translate API took place . Conclusion have been
made : Proxy settings are to be remove before using the forum.
6.3 Limitations
Online Indigenous Health Forum , as stated in the proposal(Introduction) is limited to two
languages . Since Zulu has not been available , other languages will be use . ( Hindi , French
or German ). And still , the translation produced by the remote software is an approximation
of what the sentence really means . The worse case scenario is a word by word translation ,
that , in some cases , makes no sense to the users because a set of words is presented , but the
meaning is not the one that the sender intended to produce.
6.4 Future enhancements of the system
The system is still under development is lacking vital functionalities to be yet incorporated in
the Medical world . Zulu is on the target and work will be done to bring Zulu in the Online
Indigenous Health Forum.
