archiving obsolete documents
creating folder structure to capture 'old' documents when we stop using them for the course
User story example.
some formatting changes and agreement between 1-2-3-4 meeting templatesadditional instructions taken from old Wiki pages
updated with "Engineering Definition" language and tasks
poster & final design review - changed to widescreen, some grammar and formatting updatesclient meeting - some grammar and formatting updates
Updated Use cases and User stories template with examples
Updated playbook with slides for user stories and use cases
- Day 2.5 added to calendar and Playbook due to quirky semester schedule- some cleaning up of revision history in Playbook
User Stories template updated
Updated or new templates for Client Meetings- shifted instructions back into templates- tips and philosophy into Wiki pages
Updated templates for Use Cases and User Stories.
tweaks for formatting. instructions already in place
link to EDN added, tweaks to notes in headings and to bottom of tab's notes.
updates to links and fleshing out instructions
shifted some content from Wiki into template file to match new philosophic approach
we have not formally defined Engineering Specs, so changed to Engineering Requirements
tagging Playbook as it existed end of Spring 2025 semester
updated for F25 dates
all sections are properly numbered. Tables repeat first row as headers if > 1 page long.
more tweaks, comm intensive, document your work....
addressed Google Colab, Jupyter in cloud, added many reminders to post and what to post
fixed typos
change test section of the appendix to instead make reference to the Individual Demo rubric file now to be foind in the Reports/Individual Demo rubric folder.
fillable PDF for clients
Also available in: Atom