Problem $1(60$ Pts$)$: Conceptual Data Model in UML

Express the data model in a UML Class Diagram using LucidChartLinks to an external site.. Label the relationships where useful. Use directionality indicators on the labels $().$ Add key attributes as appropriate with the stereotype $$key$.$

To narrow and focus the scope of the model, consider only the specific requirements below. Those are the ones that the conceptual data model expressed in UML must support $--$ you may omit any other considerations as this is clearly is very large project. The likely implementation will be a small application, perhaps a web app and this data model will help inform the database design and the user interface.

track the names and key demographic information $($birthday$,$ country of birth, citizenship or visa status$)$ of all individuals registered

track immediate familial relationships, e$.$g$.,$ children $($son$,$ daughter$),$ parents, grandparents

track the shelter to which they are assigned and the type of housing $($bed or family room$),$ including address

know when they were registered and when their permit to reside in$-$country expires

track eligibility for government assistance: while you do not need to address this, how would you manage eligibility for different programs, e$.$g$.,$ a person might be eligible for one program but not for another

legal representative$($s$)$ hired by or assigned to them

If there are unresolved questions from the notes, post your question on Teams and incorporate the new findings into your model. You may discuss the problem and share insights with your peers in the class but you must build and submit your own model. Keep your model to about $6-8$ classes$/$entities$,$ although you may have more as long as it is warranted, but we do not want you to "overmodel".

Problem $2(40$ Pts$)$: Logical Data Model as ERD

After you have built your conceptual data model as a UML Class Diagram, create $($in a separate page$/$tab$),$ an Entity$-$Relationship Digram $($ERD$)$ in the IE $($Crow$\text{'}$s Feet$)$ Notation of the same entities, i$.$e$.,$ "translate" the UML to and ERD. This may not always be done in practice, but we want you to practice using both notations.