Because NHibernate abstracts the data concern so well as an Analyst/Programmer I don´t need ERD´s very often. I guess that is the strength of this tool to let us to get rid of ERD at least for business purposes.
The class diagram shows a general overview of the business structure and are used by analysts and programmers. ERD are concerned with data and are used by DBAs. Each group above is not completely isolated and generally there is some interaction among them specially when DBA wants to optimize the data model. On Fri, Mar 12, 2010 at 3:19 PM, CassioT <[email protected]> wrote: > Hi. > > I would like to know if you use Class Diagram, ERD's or none. I'm > asking because I already seem Fabio saying many times that he designs > the classes and generate the tables based on that and the mapping. He > can answer that, but if you do something like that, why should you do > an ERD? Just for doc? Maybe only a class diagram would be enough. > > I think that we will find all kind of combinations. ERD + CD, CD, ERD > and None > > Opinions? > > Cassio > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- Humberto C Marchezi --------------------------------------------------------- Master in Electrical Engineering - Automation Software Consultant and Developer at the Town Hall of Vitória -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
