I think the way to think of this is as an alternative modeling notation. ArgoUML currently supports multiple textual notations (UML, Java, etc) and a few limited options for controlling the graphical notation, but it doesn't really have the concept of an entirely different graphical notation like an ERD where, for example, multipliticity is represented by crow's feet as opposed to a numerical label like "1..*". Michiel is our resident notation expert and might be able to provide more feedback. I think this only affects Class diagrams, so you could either modify the current Class diagram to allow the alternative graphical notation or you could create a new type of diagram. The former is probably preferable. Tom
-----Original Message----- From: nett .by [mailto:[EMAIL PROTECTED] Sent: Sunday, March 25, 2007 8:11 AM To: dev@argouml.tigris.org Subject: [argouml-dev] Entity Relationship Diagram Hi Linus! I will try to describe my idea with more particular: Entity Relationship Diagram (ERD) is a type of diagram, where you describe the db structure: -Every entity in this diagram is a separate table in db -In every entity you can specify columns and types of columns -You can define primary keys and foreign keys -You also can specify One-to-One, One-to-Many or Many-to-Many Relationships between entities -etc. After creating Entity Relationship Diagram you can generate db by choosing db type (additionally indicate or load driver for this db). You also can reverse existing db into ERD by connecting to db, choosing db tables and represent them in ERD. One more very good feature, i think, will be the generation of class diagram from ERD, or generating ERD from class diagram. This will help to accelerate the application development which use data bases.
