Should I use Enumeration or Class stereotype in UML to represent a type directory table?

Posted by Ivan on Stack Overflow See other posts from Stack Overflow or by Ivan
Published on 2010-05-23T15:03:30Z Indexed on 2010/05/23 15:11 UTC
Read the original article Hit count: 254

Filed under:
|
|
|

Let's take 2 UML class model entities: One represents an actual Order and another represents an Orede Type. Any Order corresponds to one Type. A 2-way-naviglabe many Orders to one Type relation is meant. Order Type instances are, for example, "Request availability", "Request price", "Preorder", "Buy", "Cancel", "Request support", etc. Order Types are to be addable and editable in the resulting application. Should I model Order Type as Class or as Enumeration? From the data perspective I can't see the difference actually.

© Stack Overflow or respective owner

Related posts about class

Related posts about enums