Hello guys,
I'm currently building "information maps" (à la Bizbok), that is: models with a list of business objects for a given domain (business objects for the supply chain domain for example).
There are such models in the UMG base, for example, the "Business objects" model, an eERM model containing "cluster data/model" elements.
I'd like to differentiate "plain" business objects (a "stock", or an "item") (-> cluster/data model) from more document-like objects (an "invoice" for example).
I was thinking of using "Information carrier" for the latter, but you can't' add "information carrier" elements to an IE Data Model. However, you can add "Information Element"
So my question is: what is the difference between an "Information carrier" and an "Information element"? (I read the online help, but this is not really helping me). Would an "Information element" be OK to represent a document (an invoice, a specification document, ...)?
Thanks for your advice
Michel
Hello Michel,
I have not had a practical use-case for "Information element" so far. Particularly for "invoice" as the product of the "invoicing" process I would go for an "Invoice" business object of type Cluster/data model. If you feel you have different qualities or "flavours" of Cluster/data model, you might differentiate them by an attribute (to which you might assign mini-symbols to be shown in the model through your template).
If you look at the invoice as the media (paper, signed PDF or the like) you could go for some symbol for an information carrier object, but only at the steps where this "printed" document is produced or handled. In the course of the invoicing process where you put together the invoice data and double check the correctness I'd say it is the Cluster/data model. There is no difference compared to the car on the assembly line. It's just a different process with a different purpose/outcome.
Regards, M. Zschuckelt
