Bachelor of I.T. - CSCI324.

Final Year
Project
© LeSign Inc. 2011.

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

Document Control

Prepared by: IT11/1G - LeSign Inc.

Prepared date: 11th February 2011

Document Type: Project Proposal

Document Title: CSCI321 – Final Year Project

Document Revision History

No Revision Section Change Revised

Change Log
. Date Affected Owner Version

11th Feb
1. Document Created All Jon v1.0
2011

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

Table of Contents
Document Control..................................................................................................1
1.0 Introduction..................................................................................................3
1.1 Objectives.................................................................................................3
1.2 Scope........................................................................................................3
1.3 Project Model............................................................................................5
2.0 Literature Review.........................................................................................7
3.0 Staff Organisation........................................................................................9
3.1 Team Structure.........................................................................................9
3.2 Role Matrix..............................................................................................10
3.3 Resource Planning...................................................................................11
3.4 Gantt Chart.............................................................................................12
4.0 Software Project Plan.................................................................................13
4.1 Risk Analysis and Management...............................................................13
5.0 Bibliography / References..........................................................................14
5.1 Internet...................................................................................................14
5.1 Internet

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

1.0 Introduction
1.1 Objectives
The purpose of this project is to develop a translator tool which accepts English
language words and sentences, and subsequently output the text as sign
language to the user. The tool must also allow expandability through an easy
and interactive mean.

Sub-objectives will also include how the tool can become an easy and effective
channel of learning and promoting sign language to the mass, through
interactive and easy to use interfaces.

It is agreed that within the given specific, measurable, achievable, relevant and
time constraint, we need to achieve the intended objectives that is meant for
any teenagers to adults for learning the language.

1.2 Scope

In considering the given task ahead, the team agreed that the tool must
maintain the achievability of being specific and relevant, given the time
constraint.

Hence, the team will be looking at the project with the following highlights:
1. Input layer
Living in the IT era, humans often look at how interaction can be improved
with the computer, from having the easy-to-use mindset to how physically
challenged humans can make use of Information Technology to our own
benefit. It has also become a norm in recent years for contactless
communication with technology.

2. Mapping & Matching (processes)

3. Output/Presentation layer
At this level, we will explore how our system can cater to users of different
computing backgrounds, from the novice to the expert computer user.

4. Application layer
Having the system in place, we look at how it can blend seamlessly into a
user environment, without having to specifically launch the software. This
will add ease and convenience to users who have intention to utilize the
software in conjunction with what they may be doing simultaneously (such
as e-book reading, etc…)

Developing a Windows based tool that takes in strings of the English language
characters and cycling them though the specially designed database of images,
and displaying the series of images.

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

The team looks at the following functionalities we aim to achieve for the end
product:

Sign Translator

Windows operating system is widely available in the market and most of the user
in the market uses windows as their operating system. Therefore, we will make
our tool available to windows operating system. It will be developed using .Net
C# as most of us are familiar with the language and it provides seamless
integration into the windows desktop PC.

Database of Sign Language

There are various forms of databases available in the market namely, Microsoft
SQL, Oracle DB, MySQL and etc. However, we would develop our database using
XML files instead as it allows easy deployment and it easy management without
the hassle of installing databases.

These are known risk as XML serializing hasn’t been much look into by either of
us and we would require to research on it further before any development.

Tool for expansion of database

The tool would allow user to add a new sign just by providing an image which
comply to a format size and its corresponding word which represent the sign. To
take this to another level, user can simply export the words created by ourselves
and share with other user. Others can in term, import the provided signs into
their own database.

The system will zip up all the files and allow user to share the zip copy of the
database. With a little knowledge of zipping the file, we would need a little more
time into developing this portion of the system.

Voice to Text Translator

This feature allows user to query the database just by speaking into the
microphone. This feature is made available with the Microsoft voice recognition
software and we have a little experience with this portion and we are confident
in developing this feature successfully. However, the technology is still not
mature enough and accuracy of voice recognition software is still questionable.

Mouse Tool

This is an interesting tool which allow user to simply highlight the words they
would like to search and query the database simply by right-clicking and
selecting “Translate this”. With that, a small box will pop out from the bottom
right corner and show the sign language that’s found.

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

There are tool that work the same way and we are confident that we would be
able to develop the same functionality for our own signing tool. Even though
none of us have ever developed or have experience in this kind of functionality,
we believe with much research we would make it available.

The purpose of the Signing Translator is to provide a tool for user to search the
corresponding sign language of a single word or a sentence. It has more than
500 sign languages available in the database to start off the tool. This tool also
allows users to populate the dictionary of sign languages if certain word is not
available. The tool also provides various ways to search the database for a
specific sign language. Besides the regular way of entering the word with the
keyboard, the tool allows user to speak into the microphone to query for a sign
language. Above all, the tool allows user to query for a sign language just by
highlighting the word or sentence on the desktop with perfect and seamless
convenience.

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

1.3 Project Model

Project development will be implemented using the V-model software

development process cycle. The V-Model, which can be associated as an
extension of the waterfall model, allows process to roll back should there be any
changes to the requirements at any stage of the life cycle.

Requirement
Ti Architecture
Integration
Software
System
Module
Software
Project Unit
U.A.
Project
End
Analysis
me Testing
Design
Build
Start
Development
Dur
ati
on

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

The V-Model Software Process Cycle consist of a few phases mainly the
Verification Phase and the Validation Phase. It moves from left to right top down
and back up. At any point of time should there be any requirement changes or
system bug identified, the process will follow the red dashed arrow [<--] back to
the previous interrelated phase.

For example if a system requirement change has been requested at the

Integration Test Phase, the process will go back to the Architecture Design Phase
before moving to the Module Design Phase, then to Build to change the codes,
then Unit Test Phase to test the unit itself and then going back to the Integration
Test Phase again. Along the way all documents are updated accordingly.

The diagram also shows the duration allocated to each phase. Phases at the top
of the diagram will have more time allocated to it simply because they are the
more important phases of the process cycle.

For example Requirement Analysis Phase will be allocated more time than the
Module Design Phase. This is to ensure that all requirements are documented
and analyzed correctly as the Module Design Phase will refer to the documents of
the Requirement Analysis Phase.

System Test Phase will be allocated more time than Unit Test Phase as the
testing and verification of the whole system will be more complex than that of
testing and verifying the single unit itself.

Verification Phase
Verification phase are on the left hand side of the V. At this phase requirements
are gathered and analyzed, system will then be designed based on the data
analyzed. Once the Verification Phase is completed it will than move to the Build
Phase.

Build Phase
Software Engineers will be able to code the system according to the documents
documented. Since the requirements are translated to functional design
documents and configuration notes which the engineers are well versed at, it will
be easy for them to turn the functional requirements into system modules.

Validation Phase
Validation Phase is on the right side of the V. At this phase the beta build of the
system are completed. The Validation Phase focuses on testing the built system
to detect any system bugs and to verify that the functional system matches with
the requirements documented.

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

2.0 Literature Review

“Signing It!”
Sign language dates back to as early as the 5th Century B.C., where the deaf and
mute would have already tried to communicate with one another using hand
signs and gestures. It was from the 15th Century onwards that publications were
released, documenting the teaching of the language.

Schools such as Abbe de l’Epee in France and the American School for the Deaf
was subsequently set up, further promoting the learning and use of the
language.

Signing has come a long way, from the traditional gesturing of intentions, to the
documentation of official representations of the spoken languages/words. In
today’s context, the world continues to look at how signing can be promoted to
the general masses, not just limiting to the community for the deaf and mute.

Action speaking louder than words…

There are different types of sign languages by different countries, this would
require the instructors to define the specific language that he/she is using in the
system. The instructor must have a significant knowledge about sign languages.
According to Sign It Services, there are a few types of needs that are required:

- Understanding the Interpretation Process

The process of interpretation requires the setting, speed or type of terminology
being used to be as accurate as possible to prevent message from being
conveyed wrongly.

- Types of Interpretation
Different types of interpretation employ intercultural and nonverbal interpreters.

- Code of Ethics
Eg. Interpreters/translators shall keep all assignment-related information strictly
confidential.
Interpreters/translators shall render the message faithfully, always conveying the
content and spirit of the speaker using language most readily understood by the
person(s) whom they serve.

- Deaf Culture
Patterns, traits, products, attitudes, and intellectual/artistic activity associated
with a population is said to have their own unique culture of the deaf community.

- Interpretation Techniques

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

Hand Position
Hand Orientation
Hand Movement
Facial Expression

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

America”No”?
In an attempt to understand the preferred sign language to work on, the project
team had approached the Singapore Associate for the Deaf (also known as
SADEAF) to understand what signing is all about.

The Association’s Deputy Director, Ms. Sandra Cheong had explained that just
like there are many different spoken languages in the world, there are also many
different languages in the signing communication. The team had also found out
that the commonly use language in Singapore is known as the “Speak Exact
English” sign language, also known as SEE.

SEE aims to represent literal English, as it is spoken. It is derived from the

popular American Sign Language (ASL) in the 1970s. Since the end product is
intended for non-deaf users, SEE is highly recommended as users are able to
better relate to it, as they are already using the spoken English.

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

3.0 Staff Organisation

3.1 Team Structure

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

Cristal Ngo
3.2 Role Matrix
Project Supervisor

Role Jonatha Jenny Jacky Yan

n Ling
Project Manager 
Project Budgeting  Jonathan Lou
User Interface   Project 
Team Lead
Design
Software Design  

System Analyst  

Database Design 

Programmer Analyst 

Programmer 
Jenny Goh Jacky Lim Low Yan Ling
Tester
Project Design Lead Project Software 
Lead System Lead
Project

Tester Design  

Deployment 
Manager

Team Lead – Jonathan Lou

1. Oversee every aspect of project development and status
2. Manage and delegate tasks within the team
3. Ensures objectives and tasks are aligned and on track

Design Lead – Jenny Goh

1. Responsible for full spectrum of project documentations, including version
controls, meeting minutes.
2. Project Finance Controller
3. GUI Lead – Responsible for full spectrum of interface design & test phases

Software Lead – Jacky Lim

1. Chief Software Engineer, responsible for software development (& lifecycle)
2. Lead Software Architect

System Lead – Low Yan Ling

1. Testing Lead – manages full spectrum of formulating and generating test
cases.
2. Database Architect, in sync with Software Lead’s project development
3. Research Lead

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

3.3 Resource Planning

S/ Role Number of working

N hours
1 Project Manger 350

– Evaluation of project 50

– Managing of project 60

– Monitoring and controlling of project 45

– Managing changing requirements 50

– -Changing and delivering configuration 40

– -Deployment of project 35

– -Close-out project 35

– -Package product 35

2 Project Administrator 280

– Project budgeting 45

– Designing components 60

– Implementing components 65

– Managing manpower 30

– Ensure project is within the stated budget 30

– Resource management (Workstation, meeting 25

place)
25
– Authorization of users for project files

3 Consultant 300

– Gather requirements 55

– Analyse requirements 55

– Prepare functional design documents 45

– Review test packages 40

– Sign off test packages 25

– Making appointment with customer for UAT 40

– Raising and managing change request 40

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

4 Software Engineer 300

– Developing program based on functional 60

design document
60
– Developing software development plan
45
– Analyzing any software problem
45
– Managing of software changing requests
45
– Basic component test
45

5 Solution Architect 300

– Subject Matter Expertise 60

– Work Force Management, Supervision and 60

Mentoring
60
– Methodology and Quality Assurance
60
– Business Development
60
– Business Planning and General Management

6 Test Analyst 300

– Preparing of test package 60

– Conduct testing for project 60

– Improving test package 60

– Evaluating project while testing 60

– Achieving acceptable mission 60

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

3.4 Gantt Chart

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

CSCI321 FYP
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

4.0 Software Project Plan

4.1 Risk Analysis and Management
This section describes and identify the risk involve in the project. Risk
management is the process of identifying factors that may lead to a failure,
integrity or availability of an information system. We need to identify the risks,
analyze each and every risk factor, plan (or calculate) risks involved and finally
monitor the risk progress.

Risk Subject Risk Description Risk Risk Mitigation Plan Risk Owner
Impact
1. Project Project deadline Severe Project scheduling Team Lead
Schedule overrun and monitoring.
2. Human Limited Manageab Conduct team Team Lead
Resource experience/talent le induction,
pool with expertise
different management
backgrounds of
expertise
3. Developmental Enterprise & Severe Conduct market Team
Tools developmental research for Lead/
tools license fees free/student Software
may be costly developmental Lead
tools
4. Project Miscommunicatio Manageab Ensure channels of Team Lead
Communication n and breakdown le communications
between team are open with
members weekly
meetings/conferen
ce calls for updates
5. Correctness of End product may Severe Ensure that at Software
Project deviate from every stage of the Lead/
initial stated project, a check is Design
requirements & conducted to deter Lead
functionalities deviation
6. Usability End product may Severe Ensure UAT is Design
not be accepted conducted with Lead/
by user’s strict adherence to System
behavior users’ Lead
psychological
behavior in mind
7. Robustness End product may Manageab Test cases should Software
not be able to le involve potential Lead/
handle error input for System
unexpected exception Lead
errors handlings
8. Hardware Unexpected Severe Implement system System
failures equipment or backups, copy Lead
disk backups
crash/failures
9. Maintainability Current Manageab Put in place All
developmental le development
scope limiting (coding) and
Bachelor of I.T. - CSCI324. Final Year
Project
© LeSign Inc. 2011.

system documentation
expandability standards for
future references
10 Interoperability Running the Manageab Standardization of All
. software on a le interfaces
different platform
which product
was developed
on

5.0 Bibliography / References

5.1 Internet
[1] Sign It Services
http://www.signit.com.sg/index.php

[2] Sign Language Teaching Kit

http://www.nyp.edu.sg/SIT/images/citi/industryproj/sadeaf.jpg

[3] Unqualified Sign Language Interpreters

http://www.kwintessential.co.uk/translation/articles/sign-language-
agencies.html

[4] Types of Interpreters

http://www.ehow.com/list_5907488_types-interpretation-health-care-
field.html

[5] Deaf Culture

http://deafness.about.com/cs/deafculture/a/deafculture101.htm

[6] Techniques for Interpretation

http://www.suite101.com/content/elements-of-american-sign-language-
a108755

[7] Singapore Association for the Deaf

http://www.sadeaf.org.sg

CSCI321 FYP