I've been using the online modeler for a couple of time now and i've some questions.
* Suppose i've a n:m relation. should the keys of the nm table be modelled as a attribute of the relation (tie)? Hmm i tseems that i can add a attribute to a tie?! Shoeld i add a anchor and then add the nm keys (of the n table and the m table) to the anchor?
* Why are some text red and some black?
* What does the dot mean ?
* Is it (too) easy to say that every relation is replaced with a tie, every table replaced by an anchor and every attribute is a attribute in achor modeling?
I think I'll answer your questions in reverse order:
* I like to think of modeling as connected to a domain, that which you are modeling, but yes. If you have a set of legacy tables that are in reasonably good shape and describe the domain, then relations become ties, tables become anchors, and columns become attributes. If there are reference/lookup tables they also typically become knots.
* The dot means that the graphical symbol is pinned down and will not be moved around by the automatic layout algorithm. Click again to release or select "Release all" from the Layout menu.
* The name (text) is red when not all required information has been entered in the Edit pop-up menu, or when the information entered does not follow our naming conventions.
* Ties cannot have attributes. Natural keys of ties are therefore typically found by inspecting attributes of the adjoined anchors.