Re: Final Requirements Process for SMIng: - #46 (cardinality)

[Frank Strauss <strauss@ibr.cs.tu-bs.de>]

Hi!

Andrea> #46 is also documented in the Requirements Draft, although not
Andrea> cleanly ...  "If you have an association between classes A and
Andrea> B, the cardinality of A indicates how many instances of A may
Andrea> be associated with a single instance of B."

Andrea> Our discussions in Minneapolis indicated that we want to
Andrea> convey "how many" instances are associated in order to define
Andrea> the best mapping algorithm - whether a new table, a single
Andrea> pointer, etc.  For example, do we use RowPointer or an integer
Andrea> index into another table?  Do we map to a table that holds
Andrea> instances of the association/relationship itself?

Added.

 -frank