As part of our Product Definition Process, we are picking up where we
left off with the Target User Group exercise to define the set of
Usage Scenarios we plan to support in the 1.0 timeframe.
Target User summary on the design list: http://
lists.osafoundation.org/pipermail/design/2006-June/004884.html
Ecosystem 1.0 Usage Scenarios write-up: http://wiki.osafoundation.org/
bin/view/Journal/OneDotZeroUsageScenarios
At a high-level, the Ecosystem 1.0 Usage Scenarios(*) can be
categorized into 13 Usage Patterns(**):
1. Record for the benefit of others
2. Record for your own benefit
3. Process and Manage FOCUS
4. Keep track of...
5. Schedule
6. Coordinate
7. Plan
8. Drive and Facilitate
9. Summarize and Communicate
10. Document
11. Contribute
12. Review
13. Archive
What's on the usage scenario wiki page:
+ Workflow sketch for each usage pattern
+ Primary target user(s) for each usage pattern
+ The tools that our primary target user(s) use today to satisfy each
usage pattern
+ How Ecosystem 1.0 proposes to solve for each usage pattern
-- Links to wiki write-ups and specs that go into more detail can be
found at the bottom of the page
+ What the Ecosystem will be missing in the 1.0 timeframe for each
usage pattern
*A more detailed list of all of the usage scenarios and the use cases
they are based on can be found here: http://wiki.osafoundation.org/
pub/Journal/OneDotZeroUsageScenarios/OneDotZeroUsageScenarios.xls
*All of the use cases, usage scenarios, usage patterns and workflows
are drawn from the user interviews we've conducted: http://
wiki.osafoundation.org/bin/view/Journal/OneDotZeroTargetUser
**For a review of terminology, see: http://wiki.osafoundation.org/bin/
view/Projects/ProductPlanProcess#ProductPlanTerminology
Comments and Questions welcome.
Thanks,
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
