Here's a proposal for a templates for each Study Area in the ChandlerEcosystem20030808. I don't expect all study areas to populate every bullet item.

For each study area, we will have:

• Landscape Template which will be a breadth-first study of the area. This is mainly to educate us on the space so that we can plan intelligently in this area.
• Evaluation and Recommendations Template. For key study areas (we won't do this for every study area), we want to go deeper into the space, evaluate possible partnership scenarios and make recommendations as to how we want to play in this space.

Landscape Template

• Background.
  • Brief description of study area. What is the ecosystem of this study area like?
  • Why and how does it impact Chandler? What benefits does it offer to Chandler users?
  • What ChandlerComponents does it impact? and how?
  • How else is this study area strategic?
  • Who are the key players/"external parties" in this area?
  • What are the relevant criteria we should use to evaluate key players? Examples of generic criteria can be found at AttributesForPrioritizingExternalParties^?
• For each key player:
  • Description of organization
    • Contact person
    • Size of organization
    • Size of user base (current and analysis of potential)
  • What are the partnership possibilities and key leverage areas? How do both sides benefit? Why is it strategic?
  • What functionality does the player provide? What are the relevant open standards? How does relate to relevant ChandlerComponents?
• Summary and Next-Steps

Evaluation and Recommendations Template

• What are the key tasks and commitments we need to make to succeed in this space?
• For each key player
  • What will the partnership entail for OSAF? What is the level of effort?
  • What are the partnership dependencies?
  • What are the risks?
• Compare and evaluate key players based on relevant criteria
• Conclusion and Recommendations
  • Summarize evaluation
  • Who should we partner with?
  • Map recommendations to a timeline
  • What are future trends in this area? What and how should we keep track of?

-- ChaoLam - 22 Aug 2003