http://wiki.osafoundation.org/Journal/
AllYourRecurrenceRulesAreBelongToUs
After last Thursday's meeting, I started trying to wrap my head
around all the various Recurrence Scenarios and came up with 3 lists:
1. What are all the different classes of changes users can/will make
to recurring event series?
2. For each of the changes listed in list #1, what are all the
different contextual factors that will affect the way the app behaves?
3. If you take each of the changes in list #1 and feed them through
every combination and permutation of contextual factors in list #2,
how does the app behave?
This will end up being quite a long write-up. I propose that we fill
this in on an as needed basis. So who might need this write-up?
+ Cosmo Developers
- Is this the right framework for you? If not, how would you frame it?
- Are there certain areas that we should focus on first?
+ PPD
- This can help us check our design to make sure that we have a
consistent user mental model.
- This can also help us prioritize recurrence features and bugs so
that we know we're hitting the most common use cases first.
+ QA
- Might this help you in testing?
- Might some sort of PPD prioritization of scenarios help you
prioritize what scenarios you test?
+ For FAQs and Release Notes?
- Is there anything that might be relevant to end-user documentation?
Questions:
+ What's missing from this list?
+ Where do implementation details fit in?
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
