Using the below image represent this family using a graph structure. The graph needs to be a weighted graph. The weights will constitute the types of relationships, I recommend using some kind mapping between numbers and strings to represent the relationships. When adding family members to the graph, this can be done programmatically for the provided family members within the description file.

Additionally,

• I also want there to be an interface in which a user can create a new family member and add them to the tree.
• This can be a simple CLI where the user provides a name, gender, and age to create a person.
• Then another simple CLI where they select which member of the family, they want the original relationship to be with and what kind of relationship it should be.
• Finally, they can edit the family member using another CLI and selecting the family member they wish to edit, the operation they wish to perform (edit name, edit age, edit relationship), and then add new relationship between family members which can call a function that you create in order to add the original relationship.

Finally, make data assertions within the FamilyTree class that enforce certain “rules” that exist in a typical human family. An example would be a person should not have any kind of relationship to itself (a person cannot marry themselves, a person cannot be their own brother, sister, father, mother, etc.). There should be at least 3 data assertions. These should exist as part of the family tree, not as part of the graph.

As a hint, for a successful design:

I would recommend using layers of abstraction. Your graph class is the backing structure to the family tree class. Your family tree should implement methods that interface with the graph class, i.e. add_family_member() should call the constructor to create a node and then call a function within the graph class to add a node to the graph. Then using the relationships function parameter, you can add edges to the graph between the new nodes and the existing nodes. The family tree should be what enforces what relationships can exist through the data assertions, the graph does not care about what relationships are made between family members. Your functions that the user would interface with would be greatly reduced compared to the total number of methods within the classes themselves. The user should be able to add, remove, and modify family members and that’s about it. Therefore, those should be your function calls.

Attachments area