Quality definitions
Exceptional y Quality
Documentation, Help text:
Language: Describes functionality very accurately. Information easily accessible, consistent use of terminology and style. No grammar, punctuation or spelling errors. All page references correct. Complete index, correct NLS data.
Formatting: All standard fonts and templates used. No paragraph style or character formatting errors. All art referenced correctly. No index, formatting or reference errors. Help is complete with perfectwww.400190.com/Thesis_ alignment and no display errors.
Functionality: Documentation and help fully consistent with software. Correct art pieces inserted throughout with all callout references in documentation accurate. Technically accurate localisation with no misleading statements, showing a thorough understanding of the product. No topic or footnote errors in Help.

Software, Installation:
Language: No language bugs. Completely, accurately localised. Examples very well localised. UI terms consistent, adhering to client guidelines, accurately describing functionality. Fully correct NLS data.
Form./Func.: Dialog boxes all correctly sized. No duplicate hotkeys. All text items localised, aligned correctly and fully visible on screen.

Packaging:
Language: Information very accessible. Very well written, consistent and high localisation content/quality. No language or terminology errors. Fully correct NLS data.

Excellent Quality

Documentation, Help text:
Language: Describes functionality accurately. Information readily accessible. Consistent style and use of terminology. Examples well localised. No or very few grammar, punctuation or spelling errors. No or very few inconsistencies. No or very few errors in page references or index. No critically incorrect NLS data.
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. Localisations 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.

Software, Installation:
Language: No language bugs. Completely and accurately localised. Examples well localised. No or few UI term inconsistencies. No critically wrong NLS data.
Form./Funct.: Localisation does not break any aspects of functionality. Software contains no localisation bugs. Few minor or trivial errors present.

Packaging:
Language: Information accessible. Well written, consistent, well localised. Very few language errors. No terminology errors. No critically wrong NLS data.

Good Quality

Documentation, Help text:
Language: Describes functionality adequately. Information generally accessible, writing style acceptable; terminology generally consistent. Examples localised adequately. Few grammar, punctuation, spelling errors. Few inconsistencies, errors in page references or index. Fully correct NLS data. #p#分頁標題#e#
Formatting: Adequately formatted for market needs. Contains no major formatting errors which impact the user's ability to understand the documentation and/or Help. Few errors in character, paragraph and index formatting.
Functionality: Functionally correct, meeting market requirements. Few localisation inconsistencies in non-significant areas.

Software, Installation:
Language: No language bugs. Adequately localised. Examples adequate. UI terms adequate. Few errors in NLS data.
Form./Funct.: Software well localised with few user interface errors that do not impact on the products ability to satisfy the user's requirements. Functionality not impaired as a result of localisation.

Packaging:
Language: Information generally correct. Writing style acceptable, consistent. Acceptably localised. Few language, terminology errors. Few errors in NLS data.

Needs Improvement

Documentation, Help text:
Language: Does not adequately describe functionality and/or describes some functionality incorrectly. Information difficult to access. Writing style not appropriate or consistent. Terminology not always consistent. Examples not well localised. Several grammar, punctuation and spelling errors. Several inconsistencies, errors in page references or index. Several errors in NLS data.
Formatting: Standard fonts/templates supplied not always used. Several formatting errors. Needs general improvement to comply with market requirements. Contains obvious errors that should have been caught and corrected before hand-off.
Functionality: Help contains topic and footnote errors. Several inconsistencies found between documentation, help and software.

Software, Installation:
Language: Language bugs. Inadequately localised. Examples inappropriate. UI terms often inconsistent. Several errors in NLS data.
Form./Funct.: Contains some localisation bugs. The number of minor localisation errors found shows that the software has not been adequately tested prior to hand-off.

Packaging:
Language: Information difficult to access. Writing style less than acceptable, inconsistent. Generally not well localised. Several language and terminology errors. Several errors in NLS data.

Unsatisfactory

Documentation and Help text
Language: Product difficult to use through lack of information. A number of discrepancies between software and documentation. Information difficult to access. Writing style poor, terminology inconsistent. Few examples well localised. Numerous grammar, punctuation and spelling errors. Many serious inconsistencies, errors in page references or index. Unacceptable errors in NLS data.
Formatting: Difficult to use due to some serious formatting and layout errors. Standard templates/fonts not adhered to. Requires a significant amount of rework to comply with market requirements.
Functionality: Many inconsistencies between documentation, help text and software. Several jumps/pop-ups not functioning in Help. Poor understanding of product leading to inadequate technical localisations throughout.#p#分頁標題#e#

Software, Installation:
Language: Seriously inadequate localisation. May present significant usability problems. Inconsistent UI terms. Unacceptable errors in NLS data.
Form./Funct.: Contains a significant number of localisation bugs. It takes longer to report the bugs than to test the product, demonstrating the lack of any QA check before hand over. A significant amount of rework required to bring the software to an acceptable standard.

Packaging:
Language: Information not accessible. Writing style very poor, inconsistent. Poorly localised. Many language, terminology errors. Unacceptable number of errors in NLS data.

Software Quality Checklist

B.1 Language

B.1.1 Accuracy

Category Definition Examples of Errors
Omissions No relevant information in the source language should be omitted in the localised software, unless specifically requested/required. Required omissions should not lead to functionality problems. The localised software must not contain text other than in the target language, unless specifically requested/required.
Relevant information is taken out or left in English without being requested/required to do so, www.400190.com/Thesis_or status bar text is shortened such that the user doesn't understand the text anymore. The software contains GUI elements that are not in the target language.
Additions The localised software must not contain unnecessary additions. The text of a dialog box option or a menu item should not be too long and incoherent, and should be of an adequate size to fit within the available space.

B.1.2 Terminology

Category Definition Examples of Errors
Glossary adherence The general and GUI terminology should be used consistently and should accurately and unambiguously reflect the general terminology in the glossary.
The term "transparencies" is localised as "transparenze" in the glossary, while the term "lucidi" is used in the software.
The verb "cancel" is localised inconsistently with "annuleren" and "ongedaan maken" in error messages.
The "Save" command is referred to as "Opslaan" in the glossary, while the software refers to it as "Bewaren".
The "Format Document" command is referred to as "Layout Document" in the glossary but referred to as "Indeling Document" in a dialog box title.
The "Delete" button is referred to as "Elimina" in the glossary, while the status bar refers to it as "Cancella".
Abbreviations A localised software element must not be abbreviated unless specifically requested/required as per guidelines or glossaries. If a localised software element needs abbreviation because of space constraints, the abbreviations must be consistent throughout the software and be included in the glossaries.
The menu item "Composizione" is abbreviated to "Compos."
"Projektstammsatz" has been abbreviated to "Projetkstamm".#p#分頁標題#e#
Context Each term in the localised software should be translated in its context. "Index" in an error message is localised as a "list of page references" while from the context it is clear it should be localised as a "list of files".

B.1.3 Language

Category Definition Examples of Errors
Grammar The software should employ correct grammar, syntax and morphology, in accordance with recognized rules and recommendations.
Grammar rules for agreement, articles, tense, word order, capitalization, hyphenation, etc. are not obeyed.
Semantics The software should accurately and unambiguously convey the right meaning, with no interpretation errors. An alert has been localised in such as way that the user doesn't understand which of the 3 buttons (OK, Cancel, Close) should be selected next.

Punctuation The software should use punctuation marks correctly, in accordance with recognized rules and recommendations.
Full stops missing, double spaces, etc.
Spelling The software should contain no spelling errors.
Spelling and typing errors.

B.1.4 Style

Category Definition Examples of Errors
General style The style in software should be user-friendly, consistent, direct, informative, current, and adhering to the guidelines issued. The style should never be too colloquial. A localised error message is archaic, too literal or verbose. The structure of status bar messages is inconsistent.
Register/Tone The register in software should vary to reflect the register of the particular target language: Direct, current, user-friendly and appropriate to the user-level. A localised Tutorial of an advanced, high-level product addresses the user in a "school mannerish" tone or in a untypical, colloquial (American) way (Hi!, Congratulations!).

Language variants/slang The software caters specifically for the consumer it is directed towards.
Slang is not an accepted inclusion in software. The requirements for Canadian French are not met in the French version of a product.

B.1.5 Country

Category Definition Examples of Errors
Country standards The software should match the relevant country standards as recommended, such as time, date and number format, currency, measurements, sorting order, etc. and should contain up-to-date examples, names and scenarios.
A dollar sign appearing in an Italian version of an application if this setting is not chosen in the operating system or application. The country list contains the setting "Yugoslavia".
Local suitability The software should reflect the cultural elements of the relevant country. A French version of a product that contains a Tutorial that instructs the user how to create an invitation to a typical American sports event such as a baseball match.

Company standards The software should contain legal sections such a splash screen, technical/product support information, or warranties and part numbers pertaining to the relevant country. The splash screen contains stipulations pertaining to countries other than the country the localised product is targeted at.#p#分頁標題#e#

B.2 Formatting

B.2.1 Interface

Category Definition Example of Errors
Alignment All objects within dialog boxes should be horizontally and vertically aligned as per client specification. Second object in a list of checkboxes is located two pixels to the left of the first object.

Sizing The size of the localised dialog box should have correct proportions.

Objects within the dialog box should be sized appropriately to its contents. Due to expansion of text elements in the localised version, the dialog box gives a “cramped” impression.
Buttons or other objects has been pushed out too far, giving insufficient space between them and the edge of the dialog box.

Text has extended to barely fit in to a button.

Positioning All objects within the software interface should retain its position as per the original version. The order of a list of checkboxes has been altered during localisation.
Menu commands appear in a different order than in the original.

Truncation All objects within the software interface should be of appropriate size to accommodate the localised text element. A text object has expanded during localisation, but not been resized, leaving some of text cut off.

Graphics All graphic objects within the software interface containing language specific items should be localised. A button on the toolbar of the Swedish version depicts the letter “B” (Bold), when it should be localised to the Swedish equivalent “F” (Fet).

Character formatting All text formatting should match original version. Text items in a dialog box are of a smaller point size or different font in the localised version than in the original.

B.3 Functional

B.3.1 Functionality

Category Definition Examples of Errors
Core functionality The functionality of the localised software should accurately and unambiguously reflect the original version. When clicking the button “Tabs...” in the “Paragraph” dialog box, the dialog box “Font” appears instead of the “Tabs” dialog box.

Hotkey/Shortcut functionality Keyboard combinations or sequences in the software should accurately and unambiguously reflect the functionality.

All keyboard shortcuts/hotkeys must be uniquely allocated.

Omissions/Additions The combination for bolding text is CTRL+G but has incorrectly been localised as CTRL+B.

The localised software contains the same key combination or sequence for "Save" and "Save As".
Both the “Page Setup...” and the “Print...” command has been given the same hotkey on the File menu.

Hotkeys or keyboard shortcut has been added/omitted contrary to instructions and without explanation or cause.
Non-display characters No code type characters should be visible in any areas of the software. A placeholder with code text is displayed in an error message, rather than the text intended to guide the user.#p#分頁標題#e#

B.3.2 Country

Category Definition Examples of Errors
NLS adherence Verify that correct NLS (national language standards) are used. Page size defaults to “US Letter” in the localised version, whereas it should default to A4.

Software uses a period (.) as a decimal separator in the localised version, when a comma (,) should be used.

Keyboard layout Verify that the correct keyboard layout is used and its functionality. A Shift+key combination does not give the expected character.

Code page Verify that the correct code page is used and its functionality. The sorting order of file names in the application is inaccurate.

B.3.3 Compatibility

Category Definition Examples of Errors
Application Verify that the localised software is fully interoperable with products specified by client.
A text import function does not provide expected results.

Platform Verify that the localised software is interoperable as intended with associated products on other platforms as per specified by client.
A file transferred from a Windows to a Macintosh version of the same product fails to open correctly.

Hardware Verify that the localised software is fully compatible with market specific hardware as per specified by client. The localised version of a graphics program does not function satisfactory with a scanner model common to that marketplace,www.400190.com/Thesis_ when this was requested by client.