国外时尚精美商务：软件国际化（英文版）

1、Andrea VineInternationalization ArchitectSeptember 8, 2004Creating a Software Internationalization Requirements Taxonomy 2First Things FirstFirst Things FirstWhat are we trying to achieve?What is the purpose of a requirements taxonomy?How are we going to accomplish this?(answers below)i18n nirvanato

2、 make people read yet another documentby running around in circles and waving our arms in a frenzied manner 3Improving Understanding of InternationalizationThere was already a rule . so the next thing to form was a policy.We formed a “globalization team”.This team first put together a policy documen

3、t complete with relevant terminology. 4Beyond the PolicyBeyond the PolicyInitial team charter providing a planning and execution framework, including details (ha ha)Scope all across Sun Type all types of software (really?)Sources internal, acquisition, 3rd party, open source? Everybody seems to want

4、 a checklist!But will a linear checklist work for all internationalization requirements? 5The team begins to meet . Global Products SunTeam - deliverables included: i18n guidelines for developers i18n testing guidelines for developers and QA engineers curriculum and other global product education re

5、commendations third party compliance criteria and contract guidelines ROI measurement tools and other business planning guidelines change recommendations to manage expanded intl product lineWas this too much to take on?And how about that checklist? Evolution of the group 6Hierarchy of Internationali

6、zation DocumentsInternationalization Rule| Policy - official format of rule | Requirements Taxonomy - definition of compliance | - | | | Creating Worldwide Java I18n Web Other platform-specific Software pages implementation publications 7What is the I18n Requirements Taxonomy? Definition of internat

7、ionalized as stated by the I18n Rule Checklist in matrix form Document in a reference-style format Users and uses -Designers & architects - help evaluate i18n areas in product designsEngineers - understand i18n considerations in implementationEngineering managers - roadmap the product & reso

8、urce planning Technical product reviewers help evaluate product i18n status Software QA - understand which areas to test for i18n functionality And how do we get the document written? 8What is the I18n Requirements Taxonomy? Definition of internationalized as stated by the I18n Rule Checklist in mat

9、rix form Document in a reference-style format Users and uses -Designers & architects - help evaluate i18n areas in product designsEngineers - understand i18n considerations in implementationEngineering managers - roadmap the product & resource planning Technical product reviewers help evalua

10、te product i18n status Software QA - understand which areas to test for i18n functionality And how do we get the document written? 9I18n Requirements Checklist Matrix Structure Interfaces User Interfaces Program Interfaces Command Character Graphical Application Storage & Application Line Protoc

11、ols Interchange Programming Objects and Methods Translatable Product Components negotiations, text, non-text Cultural Formatting & Processing negotiations, formats, language Text Foundation & Writing Systems negotiations, chars, I/O 10I18n Requirements Checklist Matrix Structure Interfaces U

12、ser Interfaces Program Interfaces Command Character Graphical Application Storage & Application Line Protocols Interchange Programming Objects and Methods Translatable Product Components negotiations, text, non-text Cultural Formatting & Processing negotiations, formats, language Text Founda

13、tion & Writing Systems negotiations, chars, I/O 11Details of the Requirements TaxonomyIntroduction purpose, how to use, key termsProvider - provides internationalization functionality Consumer uses functionality from a provider Products can be both providers and consumersPlanning user categories

14、, data categories, roadmappingInternal vs. external users Non-technical users, technical users, & technical administrators Data functionality, messages, interface elements Descriptions of each interface Command Line, Character, Graphical, Application Protocol, Storage & Interchange, Applicat

15、ion Programming 12Details of the Requirements TaxonomyExample Ordered Lists (Collation) DescriptionComparing and ordering of intl data, Sample table with 3 collations, Sorting methods Specifics on the various interfaces CLI, CUI, GUI, Application Protocols, Storage & Interchange, APIRequirements

16、Provider and Consumer perspectiveListed by interface for example, GUI:Providers must supply a mechanism for specifying the locale in the creation of ordered list elements, and must sort them according to the specified locale. Consumers must ensure that any graphical components that deal with ordered

17、 lists can be dynamically rearranged as a result of user or program action. They must display sorted data according to the users locale where relevant. 13Details of the Requirements TaxonomyExample Ordered Lists (Collation) DescriptionComparing and ordering of intl data, Sample table with 3 collatio

18、ns, Sorting methods Specifics on the various interfaces CLI, CUI, GUI, Application Protocols, Storage & Interchange, APIRequirementsProvider and Consumer perspectiveListed by interface for example, GUI:Providers must supply a mechanism for specifying the locale in the creation of ordered list el

19、ements, and must sort them according to the specified locale. Consumers must ensure that any graphical components that deal with ordered lists can be dynamically rearranged as a result of user or program action. They must display sorted data according to the users locale where relevant. 14(just when

20、 you thought it was safe)Internal Group Deployment part of lifecycle processPublic Web site Sun Global Application Developer Corner :/developer.sun/dev/gadc/des_dev/i18ntaxonomyReview Committee Deployment Somewhat deployed in RC for above internal group Evangelize to other software RCsEvangelize to

21、engineering groupsBut who is going to evangelize ?that would be me. 15What Have We Learned?Pitfall/Hurdle #1 forming a team of non i18n people dedicated to i18n work.Pitfall/Hurdle #2 deciding what the team should do.Pitfall/Hurdle #3 having too broad a scope (i18n is everywhere).Pitfall/Hurdle #4 g

22、etting people to complete their action items.Pitfall/Hurdle #5 getting others to pay attention to i18n requirements.Pitfall/Hurdle #6 keeping the team going over time. 16Applying Suns Internationalization Requirements Taxonomy (SIRT)Creating an internationalization architecture plan Use our organization or another? Apply the categories, recognize non-applicable areasCustomizing for your goals internal and external standards prescription limit to doing things one way consis