Software Localization Life Cycle (SLLC)

kettleproduceΛογισμικό & κατασκευή λογ/κού

2 Δεκ 2013 (πριν από 4 χρόνια και 7 μήνες)

91 εμφανίσεις

Software Localization Life Cycle (SLLC)
Just like any software has Software Development Life Cycle (SDLC) or

Software Testing Life Cycle (STLC), it also should have Software Localization Life
Cycle (SLLC). Typically SLLC is a small part of the SDLC or STLC Processes. SLLC
brings necessary steps required to be followed during SDLC processes. There are
few things related to localization or internationalization that are being followed
during SDLC or STLC processes but never being documented anywhere in a
formal way.
This document briefs the idea of implementing a method of localizing
software applications into GNU (a short form of “Gnu is Not Unix”) based
products. It also maintains a work-flow of how these methods to be implemented
during the software development and testing phases.
* SLLC Phases and Details:-
Analysis & Requirements

Basically here all sort of Analysis and Requirements gathering tasks
are being performed by concerned stakeholder in order to make sure
what exact software and features we are thinking of developing.

Stakeholder could be project manager, project owner, client or
anybody responsible person.

All soft of graphical user interface design or template model would be
created in this phase

GUI designers are responsible stakeholders of this task

It is a coding phase where the actual development happens. Majority
of the shaping of the software product is built into this very important

phase of SLLC

Software Programmers are the real stakeholders of this phase
however depends upon the complexity of the program it's been
divided across by architecture of the product.

Here's something which is new (or probably not at all documented
anywhere) phase that plays a major role of software localization.

Internationalization (i18n) Engineers are really the stakeholders here
who makes sure that software code is written in a way that it could
adapt locale information as well as messages marked for localization
or translations.

Gettextization is the most widely used approach in GNU based
applications, where i18n engineers not necessarily get involved but
software programmers themselves takes care of this approach.

Sometimes they also use the readily available GNU make tools to built

internationalized applications. It helps to build i18nized applications or

software programs for GNU products.

This phase majorly focus on the primary task of Translations.

Any message comes from message catalog by i18nization of the
software is translated, transliterated or kept in English itself. (Please
note that we considered that English is the source language and other

languages are target languages when we talk about translations.)

This particular task is carried out by qualified translators, they are the

major stakeholders of this phase.

Software testing is a must task in the phase of SDLC you can say.

Without testing the software it shouldn't be released ideally. So, all
sort of testing including unit testing, integration testing, stress
testing, smoke testing etc are conducted in this phase.

Software Testers sometimes organize test events too where typically
group of testers gather and do all sort of testing according to the test
cases provided.

Software Testing Engineers or Quality Engineers are the stakeholders.
Localization Testing

In addition to the software testing phase above, there's never
considered localization testing now has become the mandatory as to
ensure product's reach to the global audience.

Software Testers as well as Localization Engineers or Translators
mostly play a role of stakeholders here.

These testers usually makes sure every message is localized and
displayed correctly into the User Interface, also they are being printed

in a proper format, etc tasks are conducted here in this newly added
phase of software testing.

As usual, Documentation of product is another mandatory component
of the product where end users get to know about the product, it's
various installation and configuration methods etc through the
product documentation only.

Technical Writers or Content Writers are the stakeholders here who
work with Developers, project owners to make the documents.
Documentation Internationalization

Just like Software Internationalization, we also need to make sure
that documents are i18nized too.

It's generally taught to content authors on how to follow
documentation so that it can automatically take a path of i18nization.
Documentation Localization

Again Translators plays a role here. They are the ones who translates
documents too.

Software maintenance as required by the clients or end users.
Please refer to the diagrams of Software Localization Life Cycle.
Creative Commons Attribution-ShareAlike
Copyright © 2012 Ankitkumar Patel and Amanpreet Singh Aalam