Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
Sp2002 P5 - Help people find their way
P5 - Help users find routes between buildings
FOR BUILDINGS THAT HAVE ADDRESSES, you must provide users with the functionality to find a path between any two buildings on campus.
The user interface for this is entirely up to you, but it must be integrated in with P4 functions, e.g., the route must be marked ON THE MAP THAT YOU DISPLAY. How you indicate which buildings are addressable (lists/menus? Markings on map?) is up to you. How you specify start and end buildings is up to you. How you show the route is up to you. But it must be evident to the TA. You can include help IN YOUR PROJECT (not separate), if you wish, but you're better off with a simple UI.
How do you get the routes? I can suggest two options:
- Build a knowledge representation of campus with the locations of all buildings, and compute a path between them. This is possible, but fairly sophisticated.
- Use http://www.mapquest.com. Write HTTP code for sending MapQuest a query with the given start and end addresses, parse the return information, then map it onto your map. (You might also do the crawling of MapQuest between all relevant buildings and encode the information in your tool, so that you don't have to access MapQuest in real-time.) How to Mine Web Pages will be helpful if you try this approach.
Turn-in your project and your ECoDE project (with UML class diagram) using the Project Turnin Information with the code 'P5'.
Grading:
- 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
- 15% Good UML class diagram: Correct usage of notation (5%), detailed and understandable descriptions and names (10%).
- 10% Well-documented and good style source code
- 55% Working system:
- 10% All addressable buildings are clearly identifiable
- 10% Start and end buildings are easily specified
- 20% A route is drawn from start to end point
- 10% The routes are correct
- 5% P4 functionality still works
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.
Questions on Sp2002 P5 Milestone
Links to this Page