Transcript Translation Assistance Software

Translation Assistance Software
Life Cycle Objectives Review
Aneesa Awaludin
Van Phan
Jacob Huston
Operational Concepts
 Problem



What: To create a system for assisting
document translation and managing the
translation process
Why: To provide a user friendly workspace
and to improve consistency in documents,
between projects and between translators
User Community: Translators, translation
companies
Operational Concepts
 Benefits



Time saving
Ease of use
Improved consistency
 Non-goals

Automated machine translation
System Requirements
 Essential

Features
Phrase editor
• Provides structure for phrase translation from source to
target language

Phrase dictionary database
• Stores phrases in source and target languages as well as
project metadata (project name, translator name, source and
target languages, etc.)

Interface between the phrase editor and
phrase database
• Manages the querying and population of the database
User Interface
System Requirements
 Optional

Features (time allowing)
Anticipatory querying
• Automatic querying of the database based on word
counts

Phrase ratings
• System for tracking complete, incomplete and
questionably translated phrases

Online dictionary lookup
• For words not appearing in the database

Additional features for language learners
System & Software
Architecture
 Client:

Phrase Editor
Extension / plug-in to the Open Office
software suite
 Server:

Phrase Database
mySQL or postgreSQL
 Interface

Programmed using the Open Office SDK
Client Server Relation
Life Cycle Plan

Why?


What?


Document translation and translation process
management software
Who and When?



Developed to aid translators
6-8 very talented developers, 8 weeks
Essential features by week 6 allowing time for testing
and additional features
Stakeholders?

Developers GPA, translators
Feasibility Rationale
 Assumptions


The ability exists to extend and develop plugins for Open Office
This software would be useful and/or
marketable
 Risks


Open Office may be difficult to be developed
Database may not scale without initial good
design and/or proper maintenance