Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Fall2002 M6 - Support standard interchange formats
M6: Supporting a Standard Format
There is a standard format for genealogical data. It's called GEDCOM. You can learn about GEDCOM at various places on the Web, including http://genealogy.about.com/cs/gedcom/index.htm.
For a quick tutorial and the list of GEDCOM tags, look at http://genealogy.about.com/library/weekly/aa110100a.htm
The GEDCOM standard is at http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm. There is a good example (used in class, at the end of Chapter 2.
You are to create the ability to export your genealogical data from your tool, demonstrate that you met the standard by using it with freely available GEDCOM-reading tools, and then read in your own generated GEDCOM file. GEDCOM's a pretty complicated format, and you don't have to support all of its facilities.
Tools for processing GEDCOM files which you can use to demonstrate that you write standard GEDCOM are:
Here is what you need to do:
- Add the ability to generate a GEDCOM file from the Person objects and their relationships in your GenealogyMap. We don't care what messages you define to do this: Make the capability to export to GEDCOM somehow explicit in your user interface.
- Demonstrate that you met the GEDCOM standard by having your program work with ONE OF GedPage, GED2HTML or Ged2Ped. Specify somewhere in your user interface which you got your GEDCOM to work with.
- From starting up your GenealogyMap with GenealogyMap new open, have the ability to read back in a GEDCOM file that you generated. You don't have to support ANY GEDCOM file – just one that your own system generated.
(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:
- 10% Successfully generate a GEDCOM file
- 20% Read it in successfullly into GED2HTML or Ged2Ped. 10 points for all people come in successfully. 10 points for all relationships come in successfully.
- 20% Read in a generated GEDCOM file. 10 points for recreating all people. 10 points for recreating all relationships.
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 M6 Milestone
Links to this Page