Question about Logical database design in ERwin

[haxan]

Hi Experts. I am beginner data modeler . The tool that i start working is called Erwin 3.5.2 . I have some questions about converting simple business case to ERD in Erwin and then converting it to physical structure. The problem that i have is what method should i follow to get the proper ERD entities to the point where they are ready to convert them to physical structure.As an example i will post a simple business case later that i want to convert to ERD and then to physical structure.

i read about Normalization method that u put all attributes in one table and start normalizing it to 1th,2th and 3th normal forms. But i heared that Normalization method is an old(25 years old) method and it is not a proper way to design logical data model.

Now i want to know how and what is best method i need to use to reach to point where my entities are ready for creating physical structure. Obviously free of redundant and duplicated data. I would be really happy if an expert guide me and refer me to some simple,good tutorials.Thanks

 

[johnwm]

For Erwin experts you could try forum160

________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first.
'If we're supposed to work in Hex, why have we only got A fingers?'
Drive a Steam Roller

 

[lespaul]

....and unless you are developing an OODB, then following normalization rules is still the way to go.

Leslie

Anything worth doing is a lot more difficult than it's worth - Unknown Induhvidual

Essential reading for anyone working with databases: The Fundamentals of Relational Database Design