Design menu option missing

Question

i have two issues :
1) i installed the 4.0.3.853 oracle sql developer data modeller but I dont see the "DESIGN" menu option ?
i am trying to convert a logical model to physical model .
2) for identifying or non-identifying relationship its showing the same DDL ,  its not compounding the primary key of the child entity with the primary key for parent.
I am selecting identifying/non-identifying relationship by checking/unchecking "Source Optional" check box in "Relation Properties"
thanks

Answer 1

It's all in the docs, but here's a starter:
To transform your logical data model to a relational (i.e., physical) data model, a.k.a. database design, click the double right-arrow (>>) in the icon tool bar (if you hover, it'll say "Engineer to Relational Model"). This will display a dialog where you select the logical objects you want to transform to physical. Be sure to set your physical preferences, otherwise the tables et al. will be named just like the logical, which is probably not what you want. For example, if you have an entity named Organization that you want physically named ORGNZT, then you need to indicate this in the entity properties General node "Preferred Abbreviation" as ORGNZT. There are other preferences to set (for example, subtyping presets).
The transform dialog (Engineer to Relational) is re-entrant. When you make changes to the logica after your initial transformation to physicall, you can re-transform your initial transformation, and it will update what needs to be updated in the physical.
I haven't yet figured out how to specify a relationship's corresponding foreign key contraint name (at the physical). For example, I want relationship "Format Code - Publication" to transform to a FK constraint named AMS_PBLCTN_FK01. I know very well how to do this with Oracle Designer, but OSDDM is a different beast I'm just starting to get comfortable with.
Keep in mind that at the logical level, you have an Entity-Relationship model and diagrams; at the physical level, you have a database design (or server model) and diagrams. Different purposes. Always try to drive your changes from logical to physical, otherwise you're just documenting after the fact.
Have fun!
Patrick