Please help with this.

Transform the conceptual schema shown to an internal (relational) schema. The scenario is a childrens ski club, but you dont need to know too much about the scenario to do this problem. Be sure to indicate where NOT NULL or UNIQUE constraints are needed on columns to enforce the correct cardinality constraints.

I have purposely removed the foreign key columns that the data modeling tool likes to include in order to force you to think about how relationships are represented in the relational schema. Be sure to pay attention to identifying vs. non-identifying relationships, minimum and maximum cardinality, selection of primary keys, naming conventions, etc.

The simplest way to represent the relational schema is by using the following format: TABLE_NAME1( column_name1, column_name2, column_name3, ) NOT NULL: column_name3 UNIQUE: column_name2, column_name4

TABLE_NAME2( column_name1, column_name2, )

Or, you can draw a diagram. The important thing is that I be able to see clearly: what the tables' names are, what columns they contain, which columns make up each primary key, and which columns have NOT NULL or UNIQUE constraints on them (you dont need to specify that primary keys have NOT NULL and UNIQUE constraints on them; that is assumed.)

CITY ORGANIZATION is location ofi locat city name city state name organization name organization type residence for SCHOOL CLUB AWARD RECEIVED P award season award date in tended by ludes members is granting of CHILD * child first name * child last name by attend child street 1 child street 2 is granted " child zipcode child email child gender child date of birth child father name child mother name child contact phone AWARD P award type takes apply to tahen by applies to REQUIREMENT specified by specifi CATEGORY SKI TRIP P category name " required kilometers "required training hours ski trip date * ski trip type category minimum age category maximum age category minimum weight category maximum weight ski trip description ski trip distance