I don’t think that this is core business for ArgoUML. In my view, effort would be better spent in providing good ORM mappings. In that sense, Hibernate and AndroMDA would be better places to devote effort.
There are already plenty of avenues to explore in making ArgoUML better that are part of its core business without deviating into non-core distractions. Just my 2p / 2c worth. Sorry, Graham. -----Original Message----- From: nett .by [mailto:[EMAIL PROTECTED] Sent: 26 March 2007 17:43 To: [email protected] Subject: [argouml-dev] Entity Relationship Diagram You are right Tom, this will affects Class diagram by adding new stereotype - ORM-Persistable; By adding this new stereotype, it wil be more clearly to understand, what classes in the Class diagrams are entities, and what are not. By adding Entity Relationship Diagram(ERD), will help to link the db strucuture with classes, which represent db in application (entities). I think, it will be good, to realize synchronization between ERD and classes in Class diagrams. So, making any changes in ERD will automatically make changes in classes in Class diagrams and vice-versa. Of cource it will be useful to have a possibility to disable synchronization. And of cource, new graphical notation should be done for representing one-to-one, one-to-many and many-to-many relations. -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.18/733 - Release Date: 25/03/2007 11:07 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.18/733 - Release Date: 25/03/2007 11:07
