Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
Fall 2003 M6: Add demonstrations to your Guide
(Group, Due 11/18)
Now it's time to allow your Guide to show users how to do things, instead of just telling them how to do them. You'll need to combine your Guide with your demonstration engine so that the user can ask your Guide to demonstrate how to complete each step. You'll also need to extend your help repository so that you can read and write text and demonstration instructions in XML format.
Goal:
- Show that you can assemble individual working parts into a large, complex system.
- Practice working with XML.
Questions about Fall 2003 Milestone 6
Requirements:
Your guide show now be able to inform users of what help topics are available, allow users to choose a particular task they want help on, and then walk the users through the task. Users should be able to choose, for any particular step in the instructions, whether they want to perform the step themselves or have the Guide demonstrate it. (Note: for this milestone you can presume users have correctly followed any previous steps at any point in the instructions).
You also need to extend your Guide so that you can load and save instructions in XML format. Note that this is different than just saving the text instructions; you also need to be able to load and save the demonstration instructions, so that you write a "how-to" both explaining and demonstrating how to complete a particular task and then share it with others.
Tips:
Think about how you can avoid reinventing the wheel.
- The instructions for a number of tasks may include steps like "Open a Workspace." How can you avoid recreating the demonstration for each one? In particular, try to reuse as much of your demonstrations as you can between task instructions; it'll save you time when you get to the next milestone.
- You might need to demonstrate a particular task in a variety of similar contexts (e.g. showing halos or menus on a variety of windows). Can you generalize this task?
Turn-in
Turn-in your code and your saved help instructions, in XML format, before class using the Fall 2003 Turnin Information with the code 'M6'. Turn in your design in class.
Grading:
(NOTE: A good design is VERY important here! It's okay if it's very different from P3 – we want to see that you thought it all through.)
- 10% Good Scenarios: Accounts for all major functions in assignment, touches on every class.
- 10% Good CRC card analysis: Reasonable names, understandable and clearly defined responsibilities, good exploration of other class names
- 10% Good test plan: equivalence classes clearly identified, test cases clearly defined.
- 10% Good UML class diagram: Correct usage of notation (3%), detailed and understandable descriptions and names (7%).
- 10% Quality of the design
- 50% Working system:
- 25% Guide successfully demonstrates how to complete all 5 tasks.
- 15% Guide can read and write text and demonstration instructions in XML format from/to a file.
- 10% SUnit tests.
Note: If the TAs can't figure out how to do these things, they don't have to give you the points. The UI must be usable.
Links to this Page