...
- Braden MacDonald, @Ian
- Use Case doc for review:
Google drive docs url https://docs.google.com/document/d/1MqZIsMBIKReapMNmEI35AT7G1Zlc8T2zvQn8qr_KfUs/edit - Process for Product requirements input: TBD to expand the use case doc to include draft of edx use cases + stories, then Product to review that doc, and work toward signing off on desired high level use cases + stories. Publish doc publicly alongside Blockstore work to include community input / use cases.
- Design document review process: start with high-level use cases, map to architectural components/systems, determine models for each system and do a deep dive, then review the big picture to ensure use cases are met.
- Use Case doc for review:
- Carly Stevens Schedule meeting for next Wed (5/2) for #3 above (top-down design)
- LATER Gap analysis of Modulestore and Blockstore functionality
(e.g., no longer have static structure to traverse, xBlocks no longer at each level, lower-level node having access to course settings)
...