SQL Developer Data Modeler

OK guys, I'm struggling.

I've watched the on-line tutorials, read the white papers (especially "Naming Standardization"), and looked through the help pages. There are so many options for controlling naming that I think I'm lost in the trees trying to find the forest. Between the name, short name, synonym, synonym to display, preferred abbreviation, naming rules, glossaries, naming standards, templates, object name prefixes, name abbreviations, name translations, design rules, and classification types, I'm a bit overwhelmed.

I'd like to take this logical model:

---------------------
| facility category |
---------------------
facility category identifier <PK>
     1:1
      |
      |
      |
     0:M
------------
| facility |
------------
facility identifier <PK>
facility category id <FK>

and create the following relational model:

-------------
| t_fac_cat |
-------------
fac_cat_id <PK>
  1:1
   |
   |
   |
  0:M
---------
| t_fac |
---------
fac_id <PK>
fac_cat_id <NN,FK>

which, in turn, generates this DDL:

create table t_fac ( 
     fac_id integer  not null , 
     fac_cat_id integer  not null ) ;

alter table t_fac add constraint pk_fac primary key ( fac_id ) ;

create table t_fac_cat ( fac_cat_id integer  not null ) ;

alter table t_fac_cat add constraint pk_fac_cat primary key ( fac_cat_id ) ;

alter table t_fac 
    add constraint fk_fac_cat_2_fac foreign key ( fac_cat_id ) 
    references t_fac_cat ( fac_cat_id ) ;

Note: I could live with the relational model table names not being prefixed with a 't_' as long as the DDL includes it.

I think the tool has the ability to do what I want, but I'm missing how all the parts fit together to enable me to accomplish my goal.

Does anyone have a simple approach that might decrease the learning curve a bit?