Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Fall2002 M5 - Automatically gather genealogical information
M5 - Help fill in information
In M2, you gave people hints on how to fill-in missing information. Now, you'll do it for them.
Below is a list of information that you may support helping someone find (assume that the name is correct):
- Birth date and location
- Death date and location
- Address or phone number where lived (or lives)
- Child (or children)
You must support four sites of auto-completion! An auto-completion works like this:
- The user can ask the system to check for missing information
- For some subset of the above list, you will offer to fill in missing information for that person.
- Your system will then check some on-line, networked database and attempt to fill in the missing information.
Imagine you have a person named "Daniel LeBlanc" and you know his death date, but you don't have a birth date or a death location. That's two forms of missing information. There are databases where you might find that information. That's what you're going to provide for the user.
You can support four databases for just one of the above (e.g., birth date and location), or you can support two databases for one and two more for another. You must support a total of four in any combination. (In other words, you will parse four different kinds of web information.)
HINT!: Several terms ago, students had to write newspaper generating software that parsed information from news websites. Their Cases (including code) are available for reuse!
If you can't find the missing information, or you can't parse the page (i.e., the page changed since you wrote your parser), or you can't establish a network connection, YOU MUST PROVIDE A REASONABLE ERROR MESSAGE! A Squeak error is not considered reasonable!
Turn-in your code using the Project Turnin Information with the code 'M5'. Turn in your design in-class.
- 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 UML class diagram: Correct usage of notation (3%), detailed and understandable descriptions and names (7%).
- 10% Quality of the design
- 10% Well-documented and good style source code
- 50 % Working system:
- 10% All of the previous functionality from M4 works.
- 40% For each of four kinds of information, (a) the user can figure out how to do the missing information search, (b) there is a serious attempt to get the information THAT PASSES THE REASONABLENESS TESTS FROM M2 (e.g., someone can't die before they're born), and (c) the information is filled in if it's available.
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 Fall2002 M5 Milestone
Links to this Page