 |
Our quality procedures have been developed over 16 years of translation and localization experience and through a review of localization quality methods and processes practiced by our clients and leading software and hardware firms in Europe and the United States. We customize quality assurance (QA) procedures to our clients’ specific requirements, using the L.I.S.A. QA Model as our baseline. It is important to understand that translation is an art—not a science—and that A2Z will in good faith translate and provide the services listed below in an appropriate and effective manner. We provide certifications when required, common to medical translations.
It is important to identify and define the major elements that constitute the localization process in order to outline a proposed QA process. The task list below is a general outline of the steps in our localization and translation process. Depending on project size and turnaround requirements, some tasks may take place concurrently or occur in a slightly different sequence.
Two elements, which are critical for successful localization, are a comprehensive and stable terminology database in English and the target language(s) along with client style guides.
QA Pass 1 verifies all components in the target language. QA Pass 2 checks revisions and approximately 10% of the total. QA Pass 3 checks revisions and approximately 5% of the total.
Product & Project specification supplied by client
Product analyzed by A2Z (Engineering, Language, Project Management, and DTP Analysis)
Identify project resources
Evaluate resizing needs, bitmaps containing text, screen-shot needs, process, and issues
Test translatability of application (if needed)
Identify existing translation leverage (reuse previously translated text)
Obtain accurate word counts
Create project schedules
Analysis & Schedule approved & agreed upon
Project order placed by client with A2Z
Assign staffing and translation tools
Train project team on applications and tools (if needed)
Set up communication procedures
Develop, translate and edit terminology into the target language(s)
Client approval of terminology
Ascertain style guides usage
Receive final client resource and documentation files
Parse resource and documentation files into translation tools database
Prepare resource strings and all material to be translated
Attach terminology database
Add context and constraints
Leverage translations and other information
Distribute files to assigned translators
Translate user interface
Edit user interface translation
Resize dialog boxes (performed by client or A2Z)
Client builds translated application
A2Z performs QA Pass 1 – verification of GUI components in target language (as per client requirement)
Client performs technical and linguistic review of user interface
A2Z inserts corrections as required
Client approval of translation
A2Z updates translation with new baseline releases to the source text provided by client and inserts corrections (as required)
A2Z performs QA Pass 2 and returns files to client
A2Z updates translation with new baseline releases to the source text provided by client and inserts corrections (as required) optional
A2Z performs QA Pass 3 and returns files to client (optional)
Client final approval of software
Translate Help files
Edit Help translation
Format and compile help files, edit graphics and screens
Perform QA Pass 1 of all Help files
Client performs technical and linguistic review of Help
A2Z inserts corrections as required
Client approval of translation
A2Z updates translation with revisions to the source text provided by client and inserts corrections (as required)
A2Z performs QA Pass 2 and returns files to client
A2Z updates translation with revisions to the source text provided by client and inserts corrections (as required) optional
A2Z performs QA Pass 3 and returns files to client (optional)
Client final approval of Help
Translate tutorial files
Edit tutorial translation
Format, compile, edit graphics and screens
Provide QA Pass 1 of tutorial files
Client technical and linguistic review of Tutorial
A2Z inserts corrections as required
Client approval of translation
A2Z updates translation with revisions to the source text provided by client and inserts corrections (as required)
A2Z performs QA Pass 2 and returns files to client
Client final approval of Tutorial
Translate manuals
Edit documentation translation
Client technical and linguistic review of documentation
A2Z inserts corrections as required
Client approval of translation
Desktop publish documentation, format pages, edit graphics and screens, capture and insert screens, generate TOC and Index
Perform QA Pass 1 of desktop published documentation
Client approval of documentation
A2Z updates translation with revisions to the source text provided by client and inserts corrections (as required)
Perform QA Pass 2 and return files to client
Provide laser printed, camera-ready copy and electronic files
Client final approval of documentation
Within the localization process, a number of QA checkpoints need to be identified and agreed to by client and vendor in order to ensure that the quality of each step meets the required level. Using identical processes and standards at both A2Z and the client site assure testing uniformity and facilitate reconciliation of discrepancies.
QA checks are carried out at each phase in the process for each product element, e.g., software, help, tutorials, documentation, and collateral material. These periodic checkpoints allow the client and A2Z to assess manageable portions of the project, implement improvements and keep problem development from proceeding out of control.
Based on client requirements, A2Z should be provided, at start up, with complete instructions and information on QA testing including:
Complete testing scripts, standards, criteria, reporting results, etc.
Tutorial script and/or navigational guidelines that show the path of all screens, including branching statements, to insure effective testing of buttons, hot spots, etc.
List of variables/data that need to be entered to produce error conditions
Location where the data should be entered
Type of error conditions to expect when data is entered
Both the client and A2Z should develop project milestones as QA checkpoints. For each checkpoint the Project Manager should notify all parties at least five (5) working days so that they can be ready for the checkpoint, thereby ensuring prompt turnaround times.
It’s important to have synchronized QA systems at both A2Z and client sites. The client makes an internal QA against a defined set of standards and A2Z then does its QA against the same standards. If A2Z’ internal QA results in a “pass”, it is reasonable to expect that the QA at the client’s site should have same result.
The client and A2Z should, at an early stage, identify the number of QA steps and checkpoints to take place for each project element and enter these into the project schedule. The number of QA steps/checkpoints can vary depending on scope and project nature. It is important to ensure that both client and A2Z agree on the QA schedule, understand the significance of deliverables for each individual QA step/checkpoint, and are aware of how and by whom QA checks are performed.
After each QA check, results should be forwarded to A2Z and client with any comments on performance that the evaluators may have. It is important that evaluators ensure that corrections and recommendations resulting from QA Pass 1 and QA Pass 2 are implemented. QA Pass 2 therefore should contain part of the previous QA sample. QA Pass 3 and/or the final QA check are performed on the localized material shortly before release. It is expected that the only changes to be made at this stage are a result of critical quality issues (an error that would stop a process) and functionality errors, whereas language and formatting changes should be complete.
Language:
Describes functionality accurately. Information readily accessible. Consistent style and use of terminology. Examples well localized. No or very few grammar, punctuation or spelling errors. No or very few inconsistencies. No or very few errors in page references or index.
Formatting:
Standard fonts and templates used. Documentation well formatted with no or few style or character formatting errors. Art correctly referenced. Help is complete with good alignment and no or few minor display or graphics errors.
Functionality:
Documentation and help very consistent with software. Localization is adequate and technically accurate, demonstrating a good understanding of the product. Correct art pieces inserted throughout with accurate callout references. Help functionality correct with no or very few topic or footnote errors.
Language:
No language bugs. Completely and accurately localized. Examples well localized. No or few UI term inconsistencies.
Form./Funct.:
Localization does not break any aspects of functionality. Software contains no localization bugs. Few minor or trivial errors present.
Services
|
|
|
|
|
Translation has evolved over time. Translation in the past was simple, you had a source word or sentence and you translated it to a foreign language. We now talk of localization as a more sophisticated type of translation; it is actually adapting written concepts into another language, incorporating both language, cultural preferences and style.
|
|
|
|
LTC Organizer - New Enterprise Resource Management System.
Memberships
|
