Sort of.
- A schema resulting from an E/R model is usually pretty good.
- Common sense about entities doesn't usually introduce
dependencies that violate BCNF.
- Each entity goes into its own table. FDs are from the primary
key to each other column. This satisfies the BCNF condition.
- Once you have a good schema, see if you can identify any
FDs. If you can, apply BCNF decomposition. (Probably indicates
poor E/R modeling in the first place.)
- Also: A lot of schema design activity involves small
additions to an existing schema.
- New column
- New table
- New FK
- As long as you start with a modified ER model, the change to the relational
schema should be fine.