Difference between revisions of "DETAILED PROCEDURE DIRECTIONS HERE"

From wiki.gpii
Jump to: navigation, search
(Created page with "For each solution to be integrated the following steps will be performed by the Tiger Team #'''Identify key contact person(s)''' and contact them. ##Permissions - ownership -...")
 
Line 2: Line 2:
  
 
#'''Identify key contact person(s)''' and contact them.
 
#'''Identify key contact person(s)''' and contact them.
##Permissions - ownership - mgmt etc  
+
##Permissions - ownership - mgmt etc
##Technical   (launch - settings access - meaning of settings)
+
##Technical (launch - settings access - meaning of settings)
 
#'''Redesign the way a product handles settings''' (optional)
 
#'''Redesign the way a product handles settings''' (optional)
##Saves preferences to better match the GPII  
+
##Saves preferences to better match the GPII
 
##Uses settings -- to allow live use of externally changed settings
 
##Uses settings -- to allow live use of externally changed settings
 
#'''Create a translation/un-packing tool''' (as required)
 
#'''Create a translation/un-packing tool''' (as required)
##to convert binary and other compressed settings files into GPII inferrable/adjustable/transformable form.  
+
##to convert binary and other compressed settings files into GPII inferrable/adjustable/transformable form.
 
#'''Register and align the preferences/settings''' in the product with the Preference Terms Definitions Registry
 
#'''Register and align the preferences/settings''' in the product with the Preference Terms Definitions Registry
 
##mfgr might do -- but we should offer since MUCH MUCH easier for us to do because we know what is in Registry and what they are called
 
##mfgr might do -- but we should offer since MUCH MUCH easier for us to do because we know what is in Registry and what they are called
 
##mfgr should participate because they know what their term mean
 
##mfgr should participate because they know what their term mean
 
#'''Launch and Setting handlers'''
 
#'''Launch and Setting handlers'''
##Create/adapt/select
+
##Create/adapt/select
 
##Can we do “live” settings change for context etc?
 
##Can we do “live” settings change for context etc?
 
#'''Document'''
 
#'''Document'''
## Solution specific notes
+
##Solution specific notes
## Generic documentation for others
+
##Generic documentation for others
 +
 
 +
 
 +
 
 +
RESOURCES 
 +
 
 +
*Preference Terms Definitions Registry  (Preferece Terms Dictionary)
 +
**PTD itself
 +
**OLD for reference only  ---  https://docs.google.com/spreadsheets/d/1JNvidqZii7Nuu0KHfLmRje_D3JfpaOTuR1WudjIENJw/edit#gid=7
 +
**

Revision as of 20:46, 17 December 2014

For each solution to be integrated the following steps will be performed by the Tiger Team

  1. Identify key contact person(s) and contact them.
    1. Permissions - ownership - mgmt etc
    2. Technical (launch - settings access - meaning of settings)
  2. Redesign the way a product handles settings (optional)
    1. Saves preferences to better match the GPII
    2. Uses settings -- to allow live use of externally changed settings
  3. Create a translation/un-packing tool (as required)
    1. to convert binary and other compressed settings files into GPII inferrable/adjustable/transformable form.
  4. Register and align the preferences/settings in the product with the Preference Terms Definitions Registry
    1. mfgr might do -- but we should offer since MUCH MUCH easier for us to do because we know what is in Registry and what they are called
    2. mfgr should participate because they know what their term mean
  5. Launch and Setting handlers
    1. Create/adapt/select
    2. Can we do “live” settings change for context etc?
  6. Document
    1. Solution specific notes
    2. Generic documentation for others


RESOURCES