COSMOS QA Criteria

COSMOS QA Creiteria

Change History

Name:	Date:	Revised Sections:
Jimmy Mohsin	01/3/2008	Initial version

Workload Estimation

Rough workload estimate in person weeks

Process	Sizing	Names of people doing the work
Initial specification	2	Jimmy Mohsin
Review by COSMOS team	2	COSMOS Team
Review and sign-off	1	QA Team
TOTAL	5

Terminologies/Acronyms

The terminologies/acronyms below are commonly used throughout this document. The list below defines each term regarding how it is used in this document:

Term	Definition
Internationalization	The process of generalizing the design of a product so that it can handle multiple languages and cultural conventions without the need for making code changes for each language. COSMOS 1.0 will be internationalized for its eventual adoption and deployment
Localization	The process of taking an internationalized product and making it linguistically and culturally appropriate to the target locale (country/region and language) where it will be used. COSMOS 1.0 will not be localized for any non-US English languages, this is something that the adopers will need to do.
Translatable Elements	Everything intended to be locale and language dependent. These items may need to be modified for different locales, e.g. date formats, time formats, word lists for content controls, and so on.
Non-user elements	Everything not intended for end-users to see and understand. This fits into two categories, proper names and internal elements. Examples of internal elements are command line commands and options, debug strings, registry keys, program file names, comments, and so on. Examples of proper names are product name, company name, and so on.
User Elements	Everything intended for end-users to see and understand, e.g. menus and menu items, dialog boxes, windows, program groups, error messages, installation scripts, icons, buttons, "Display Name" and "Description" fields for services we create on Windows, and so on.

Purpose

The QA Creiteria will be specified by the COSMOS team; and will be used to specifiy the exit for all COSMOS 1.0 iterations going forward. The intent is to apply these criteria to i9 onwards.

The data visualization component does not follow a consisten design pattern to support internationalization. There are serveral components within the visualization project that require internationalization support:

1. Dojo widgets
2. Servlet data feeds
3. XML configuration files
4. ANY OTHER COMPONENTS ???

Dojo widgets do support i18n, as documented on http://dojo.jot.com/WikiHome/Internationalization?revision=18. For each of these components there are best practices to support internationalization; however, a common methodology is needed.

Is COSMOS 1.0 well-formed software?

The COSMOS code must consider the following guidelines to support i18n:

1. Assess the JUnits as well as any other type of tests
2. Evaluate the integration tests
3. Evaluate the iteration and milestone close processes
4. Assess the open source tooling used to test COSMOS 1.0
5. Review the RE process

Identify all the end-to-end tests

All COSMOS 1.0 iterations must pass the following end-to-end tests:

1. Scalability
   1. We need to specifiy details of this capability
2. Performance
   1. We need to specifiy details of this capability
3. Concurrency
   1. We need to specifiy details of this capability
4. Availability
   1. We need to specifiy details of this capability
5. Stress testing
   1. We need to specifiy details of this capability

Is COSMOS 1.0 a consumable entity?

In order to ensure ease of adoption for COSMOS 1.0, the following items need to be addressed:

1. Asses install documentation, i.e. is there enough information on the download page to be able to install the required functions ?
2. Asses Update Manager capabilities (not there yet…)
3. Are the offered packages fully functional, i.e. the content described on the install page matches the downloaded package
4. Assess case for COSMOS 1.0 to Executive Management
5. Assess package for adopting developers
6. Asses package for other types of adopters, if applicable
7. Evaluate hardware & software prerequisite definition
8. Evaluate upgrade and patch process for COSMOS 1.0

Is COSMOS 1.0 an extensible framework?

In order to ensure that COSMOS 1.0 can be extended as desired by the adopters, the following items need to be addressed:

1. Asses user documentation and API doc
2. Assess process for extending framework components
3. Assess process for extending supported platforms / operating systems
4. Review process for reporting bugs and ehnancement requests

Task Breakdown

The following section includes the tasks required to complete this enhancement.

1. TBD

Open Issues/Questions

All reviewer feedback should go in the Talk page for 208593.

• Should this ER address the Language Groups issue? Or should this be deemed out of scope since COSMOS 1.0 will not address localization?
• Where does XLIFF fit into the i18n considerations? http://docs.oasis-open.org/xliff/v1.2/cs02/xliff-core.html

--Popescu.ca.ibm.com 13:23, 4 January 2008 (EST)XLIFF is one option for localization support in xml documents.

---