FYP Proposal 1.1

8/7/2019 FYP Proposal 1.1

http://slidepdf.com/reader/full/fyp-proposal-11 1/23

Bachelor of I.T. - CSCI324. Final YearProject

© LeSign Inc. 2011.

CSCI321 FYP





Document Control

Prepared by: IT11/1G - LeSign Inc.

Prepared date: 11th February 2011DocumentType:

Project Proposal

Document Title: CSCI321 – Final Year Project

Document Revision History

No

.

Revision

DateChange Log

Section

Affected

Change

Owner

Revised

Version1.

11th Feb2011

Document Created All Jon v1.0

2.15th Feb

2011Proposal Details revised All Jon V1.1

CSCI321 FYP





Table of ContentsDocument Control..................................................................................................1

1.0 Introduction..................................................................................................3

1.1 Project Background...................................................................................3

1.2 Objectives.................................................................................................4

1.3 Scope........................................................................................................4

1.4 Key Features.............................................................................................5

2.0 Literature Review.........................................................................................7

3.0 Project Management....................................................................................9

3.1 Project Model............................................................................................9

3.2 Team Structure.......................................................................................11

3.3 Role Matrix..............................................................................................12

4.0 Software Project Plan.................................................................................13

4.1 Risk Analysis and Management...............................................................13

4.2 Resource Planning...................................................................................14

4.3 Gantt Chart.............................................................................................15

5.0 Bibliography / References..........................................................................16

5.1 Internet...................................................................................................16

5.1 Internet

CSCI321 FYP





10 Introduction

1.1 Project Background

World population: 6.7 Billion

World deaf population: 70 Million

That is about 1% of the world’s population who are deaf. In percentage, that may

seem like a number of no importance and concern. But in actual fact, we are

talking about 14 times the entire population of Singapore, being deaf. The most

common form of communication for this special group of people? Sign language,

in its various forms and different languages.

Signing does not just apply to the deaf – we are also talking about the mute and

those who are physically and mentally challenged who require the special

language to communicate their needs everyday. As the world population

increases along with the deaf community, how can we ensure the sustainability

of the sign language? Do those who are born healthy (and those who remain

healthy) see ourselves being able to accept those who are not as complete as

us? Are we able to accept those who are physically challenged in the society,

and perhaps one day, give them more important roles to play in the world on top

of their equal human rights?

How are we able to promote the use of the language? In relation to the deaf

community here in Singapore, we understand that currently there are no

electronic tools that can help/assist the learning process. Learning the language

can be tough, as such in this proposal, we explore ways how we can simplify the

process, making the language fun and easy to grasp.

CSCI321 FYP





1.2 Objectives

The purpose of this project is to develop a translator tool which accepts Englishlanguage words and sentences, and subsequently output the text as signlanguage to the user. The tool must also allow expandability through an easyand interactive mean.

Sub-objectives will also include how the tool can become an easy and effectivechannel of learning and promoting sign language to the mass, throughinteractive 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.3 Scope

In considering the given task ahead, the team agreed that the tool mustmaintain the achievability of being specific and relevant, given the timeconstraint.

Hence, the team will be looking at the project with the following highlights:1. Interacting with the system

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 physicallychallenged humans can make use of Information Technology to our ownbenefit. It has also become a norm in recent years for contactlesscommunication with technology.

2. Presenting to the userAt this level, we will explore how our system can cater to users of differentcomputing backgrounds, from the novice to the expert computer user.

3. Learning through ease and convenienceHaving the system in place, we look at how it can blend seamlessly into auser environment, without having to specifically launch the software. Thiswill add ease and convenience to users who have intention to utilize thesoftware in conjunction with what they may be doing simultaneously (suchas e-book reading, etc…)

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

The team would look into presenting the software in initial launches to themajority Windows using community, and subsequently expanding to users of different operating systems (OS).

CSCI321 FYP





1.4 Key Features

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

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

CSCI321 FYP





selecting “Translate this”. With that, a small box will pop out from the bottom

right corner and show the sign language that’s found.

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 thoughnone of us have ever developed or have experience in this kind of functionality,

we believe with much research we would make it available. This would achieve

the ease of learning while surfing, making usability with convenience.

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





2.0 Literature Review

“Signing It!”

Sign language dates back to as early as the 5th Century B.C., where the deaf andmute would have already tried to communicate with one another using handsigns and gestures. It was from the 15th Century onwards that publications werereleased, 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 thelanguage.

Signing has come a long way, from the traditional gesturing of intentions, to thedocumentation of official representations of the spoken languages/words. Intoday’s context, the world continues to look at how signing can be promoted tothe 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 EthicsEg. 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





Hand Position

Hand Orientation

Hand Movement

Facial Expression

CSCI321 FYP





America”No”?

In an attempt to understand the preferred sign language to work on, the projectteam 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 community. 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.

The team had also found out that SADeaf conduct lessons through a classroom

setting, with a deaf instructor. Basic SEE Language classes are broken down into

different modules, and each module require 3 months of classroom learning.

When asked if there are currently any software that automates the learning

process (such as e-learning portals), SADeaf’s Ms. Sandra Cheong informed that

there is no such system in place, yet.

SADeaf’s Deaf Access Officer, Mr. Jimmy Wong did mentioned that they are

planning to work on a simple system to upload pictures and instructions onto a

website for e-learning. The plan however is still just an idea yet to be explored.

Mr. Wong informed the team that if such a system would be implemented,

SADeaf would charge its users for it, just like how the association is currently

charging fees for its sign language courses.

Since the idea of sign language e-learning is still new, the team would like to

explore what can be introduced, with the aim of drastically cutting down time

spent in a classroom for hours. With more than 3 million users of the internet

here in Singapore (including the deaf) and the rapid expansion of the World WideWeb, the team wants to tap and ride on this vast market, especially for those

who desire ease and convenience while learning a new skill. (in this case picking

sign language)

CSCI321 FYP



Requirement

Analysis

SystemDesign

ArchitectureDesignModuleDesign

SoftwareBuildUnit

TestingIntegration TestingSystem Testing

U.A. Testing



3.0 Project Management

3.1 Project Model

Project development will be implemented using the V-model softwaredevelopment process cycle. The V-Model, which can be associated as anextension of the waterfall model, allows process to roll back should there be anychanges to the requirements at any stage of the life cycle.

CSCI321 FYP

TimeDur

ation

SoftwareDevelopment

ProjectStart

Project End





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 downand back up. At any point of time should there be any requirement changes orsystem bug identified, the process will follow the red dashed arrow [<--] back tothe previous interrelated phase.

For example if a system requirement change has been requested at theIntegration Test Phase, the process will go back to the Architecture Design Phasebefore 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 themore important phases of the process cycle.

For example Requirement Analysis Phase will be allocated more time than theModule Design Phase. This is to ensure that all requirements are documentedand 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 thetesting and verification of the whole system will be more complex than that of testing and verifying the single unit itself.

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

Build PhaseSoftware Engineers will be able to code the system according to the documentsdocumented. Since the requirements are translated to functional designdocuments 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 PhaseValidation Phase is on the right side of the V. At this phase the beta build of thesystem are completed. The Validation Phase focuses on testing the built systemto detect any system bugs and to verify that the functional system matches withthe requirements documented.

CSCI321 FYP





3.2 Team Structure

CSCI321 FYP





3.3 Role Matrix

Role Jonathan

Jenny Jacky YanLing

Project Manager Project Budgeting

User InterfaceDesign

Software Design System Analyst

Database Design Programmer

Analyst

Programmer Tester

Tester Design Deployment

Manager

Team Lead – Jonathan Lou1. Oversee every aspect of project development and status2. Manage and delegate tasks within the team3. 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

Cristal NgoProject Supervisor

Jonathan LouProject Team Lead

Jenny GohProject Design Lead

Jacky LimProject Software Lead

Low Yan LingProject System Lead





4.0 Software Project Plan

4.1 Risk Analysis and Management

This section describes and identify the risk involve in the project. Riskmanagement 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 finallymonitor the risk progress.

Risk Subject Risk Description

Risk Impact

Risk MitigationPlan

Risk Owner

1. ProjectSchedule

Project deadlineoverrun

Severe Project schedulingand monitoring.

Team Lead

2. Human

Resource

Limited

experience/talentpool withdifferentbackgrounds of expertise

Manageab

le

Conduct team

induction,expertisemanagement

Team Lead

3. Developmental Tools

Enterprise &developmentaltools license feesmay be costly

Severe Conduct marketresearch forfree/studentdevelopmentaltools

TeamLead/SoftwareLead

4. ProjectCommunication

Miscommunication and breakdownbetween teammembers

Manageable

Ensure channels of communicationsare open withweeklymeetings/conference calls for updates

Team Lead

5. Correctness of Project

End product maydeviate frominitial statedrequirements &functionalities

Severe Ensure that atevery stage of theproject, a check isconducted to deterdeviation

SoftwareLead/DesignLead

6. Usability End product maynot be acceptedby user’sbehavior

Severe Ensure UAT isconducted withstrict adherence tousers’

psychologicalbehavior in mind

DesignLead/SystemLead

7. Robustness End product maynot be able tohandleunexpectederrors

Manageable

Test cases shouldinvolve potentialerror input forexceptionhandlings

SoftwareLead/SystemLead

8. Hardwarefailures

Unexpectedequipment ordiskcrash/failures

Severe Implement systembackups, copybackups

SystemLead

9. Maintainability Currentdevelopmentalscope limitingsystem

Manageable

Put in placedevelopment(coding) anddocumentation

All

CSCI321 FYP





expandability standards forfuture references

10.

Interoperability Running thesoftware on adifferent platformwhich productwas developedon

Manageable

Standardization of interfaces

All

CSCI321 FYP





4.2 Resource Planning

S/N

Role Number of workinghours

1 Project Manger 350– Evaluation of project – Managing of project – Monitoring and controlling of project – Managing changing requirements– -Changing and delivering configuration– -Deployment of project – -Close-out project – -Package product

5060455040353535

2 Project Administrator 280– Project budgeting– Designing components– Implementing components– Managing manpower – Ensure project is within the stated budget – Resource management (Workstation, meeting

place)– Authorization of users for project files

45606530302525

3 Consultant 300– Gather requirements– Analyse requirements

– Prepare functional design documents– Review test packages– Sign off test packages– Making appointment with customer for UAT – Raising and managing change request

5555

4540254040

4 Software Engineer 300– Developing program based on functional

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

606045454545

5 Solution Architect 300– Subject Matter Expertise– Work Force Management, Supervision and

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

6060606060

6 Test Analyst 300– Preparing of test package– Conduct testing for project – Improving test package

– Evaluating project while testing– Achieving acceptable mission

606060

6060

CSCI321 FYP





CSCI321 FYP





CSCI321 FYP







CSCI321 FYP





CSCI321 FYP





5.0 Bibliography / References

5.1 Internet[1] Sign It Services

http://www.signit.com.sg/index.php

[2] Sign Language Teaching Kithttp://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 Interpretershttp://www.ehow.com/list_5907488_types-interpretation-health-care-

field.html

[5] Deaf Culturehttp://deafness.about.com/cs/deafculture/a/deafculture101.htm

[6] Techniques for Interpretationhttp://www.suite101.com/content/elements-of-american-sign-language-

a108755

[7] Singapore Association for the Deaf

http://www.sadeaf.org.sg1. Ms. Sandra Cheong

[email protected]

2. Mr. Jimmy [email protected]

[8] World Federation of the Deaf http://www.wfdeaf.org/

[9] World Bank, World Development Indicatorswww.google.com/publicdata


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

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


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


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

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


http://www.sadeaf.org.sg/

mailto:[email protected]


http://www.wfdeaf.org/

http://www.google.com/publicdata


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





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



http://www.sadeaf.org.sg/



http://www.wfdeaf.org/

http://www.google.com/publicdata

Documents

FYP Proposal 1.1