1. Group Notes

2. Concepts Automatically keep track of documents and websites used for a project Build and maintain a dynamic list of resources Share and synchronize lists with group members Main idea is for an unobtrusive, intuitive system that runs in the background

3. Interface Mockup Project control window Just a few buttons – Create new project http://www.alfrankenweb.com/ It’s fair and balanced. Switch Projects C:\Documents and Settings\All Users\politics.doc Document details: Opened 25 times since yesterday Last modified 5 minutes ago Older versions… Politics Project New Project… Work Project Select a different project Pause project tracking New Project

4. Example: group research Server Websites: www.tmobile.com www.verizon.com Documents: Best_Wireless.doc Websites: www.samsung.com www.motorola.com Documents: WirelessStuff.doc Comments: I need a phone that can play streaming video. Orion Steph Jill

5. Group project synchronization Server Websites: (Jill) www.tmobile.com www.verizon.com (Steph) www.samsung.com www.motorola.com Comments: (Orion) I need a phone that can play streaming video. Documents: (Jill) Best_Wireless.doc (Steph) WirelessStuff.doc Combined list on server

6. System Requirements Automatically watch for new resources –Allow of easy manual addition Keep track of and switch between several projects –Possibly switch automatically Display a sorted list of all resources used for project –Can click a resource to open it –Option to automatically open all resources for a project –Can insert comments or add new resources anywhere in list Allow for project synchronization via a project server –Support for multiple groups/projects on server

7. System Architecture Client: –Project resource list –Easy-to-use list editor –Background service to watch for new resources Server –Store master group lists –Handle list merging/synchronization –Allow groups to share files

8. Lifecycle and Feasibility Uses –Combine research efforts, find your frequently used websites/documents, etc. –Can greatly reduce group project overhead –Target audience – just about anyone who uses a computer Feasibility –Concept is simple; technology is largely unfamiliar –Will require investigation into OS API, etc

9. Open questions Business model –Competition – wikis are similar –Integrate into OS or standalone product? Technology –Plausibility of writing service to track appropriate documents