Making Static Analysis Work for Software Internationalization and Localization

Recording Now Available: For access, please fill out the form at the bottom of this page

A proactive approach to building and maintaining software supporting global customers, and their language and cultural requirements

Static Analysis, a process of evaluating source code for ongoing development without running the software like during testing, has been effectively harnessed for supporting quality, security and other coding requirements. We will show how it can be applied to globalized software development for big productivity and release gains.

What’s Good: Potential as a big time saver, better quality and releases. Quickly find and assist with internationalization (i18n) and ongoing U/I changes affecting localization (L10n).

What’s Bad: If it’s not properly implemented, static analysis can be a forest of false-positive issue distractions.

We’ll take a practical look at how to make static analysis internationalization and localization work for your team.

When: For recording access – fill out form below (this webinar was presented in December 2013)

Duration: 50 minutes

To View: form at bottom of page

Here’s what we’ll cover:

  • Background on static analysis and testing for globalization
  • Agile development demands on globalization
  • Successful real world examples
  • Benchmarks for accuracy and acceptance
  • Continuous integration for i18n & L10n
  • Working on legacy code
  • Working on ongoing development
  • Connecting U/I changes with translation systems

Who should attend: 

Technical managers and engineers looking for a systematic way to improve the development, release and ongoing features for software that supports languages and cultural formatting worldwide.

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *