Overview
Goals and Objectives
The goal of Scooby's reccurence features in this initial .1 release is simply to display recurring events created in Chandler properly. Future Scooby releases will of course allow creation and editing of recurring events.
High Level Use Cases
1. View events created in Chandler the recur during the current week view.
2. STRETCH GOAL - Create (but no edit!) simple recurring events.
Definitions
Requirements
Recurring Event Editing: Recurring events cannot be edited
Assumptions
High-level Decisions
Terminology
User Interface / Interaction
mde to fill out...
Code Design
Specials Considerations
QA / Test
Any info that will be useful for testers. Special cases or scenarios to consider.
API / Developer Platform
If relevant, how the feature will be made accessible to coders?
Security
Aspects of the design dealing with potential security issues.
Internationalization / Localization
Things to keep in mind for Internationalization. Caveats known at design time.
Accessibility
UI must be accessible (Section 508).
Build / Install
New info that coders need to know introduced by that feature. List here known dependencies in particular.