The Integrity Page is provided to let you specify various aspects of how the Relation's Referential Integrity should be enforced. The database provides explicit support for enforcing some of these options (Delete Rule, Identifying). In the other cases (Optionality, Cardinality, Update Rule), you can specify values for documentation purposes or you could write a Trigger to read and enforce the option.
Relation Integrity Property Page for Barker Notation
Relation Integrity Property Page for IDEF1X Notation
Child Optionality - whether there must be a row in the child Table for each row in the parent Table.
Child Cardinality - how many rows can be in the child Table for each row in the parent Table
Identifying - indicates whether the parent key is part of the child's primary key
Parent Optionality - indicates whether there must be a row in the parent Table for each row in the child Table
Parent Cardinality - indicates how many rows in the parent Table there must be for each row in the child Table
Delete Rule - when a row in the parent Table is deleted, what should happen to corresponding child Table rows. Some of these options (like No Action, Cascade and Set Null) are explicitly supported by Oracle. The others would need to be enforced using Triggers.
Update Rule - when a row in the parent Table is updated, what should happen to corresponding child Table rows. These options would need to be enforced using Triggers.