JL

HI

when should i use information carrier of type "Document" object  and when should i use the                  " technical terms" object ??

and what is the different between these objects ?

 

for example i have an output from a process , this output is "newspaper"  , should i use a technical term called "newspaper" as an output from this process  , or should i use a Document object called "newspaper" as an output form this process ??

 

thx

by Ivo Velitchkov
Posted on Mon, 07/11/2011 - 09:23

Jone,

Document is used the way its object type implies - as information carrier. Cluster/Data model is used to specify some data set at conceptual or logical level. Technical term is sometimes used in the same way. This is may be not as appropriate as Cluster/Data model but there are much more connection types and models allowed for Technical term, which makes it popular. Other, more concrete object types for data are Class and ERM Attribute.

If you want to model a set of e.g. "Client contact data", Cluster/Data model is the right thing to use. Then "Client contact data" can _lie on_ different Documents: "Offer", "Invoice", "Credit Note" etc. In many cases Document is avoided and Cluster/Data model is also used for things such as "Offer" and "Invoice". It's a matter level of abstraction and convention. Another important criteria is which models/method do you plan to use.

There are several good threads in the Community on this topic.

 

 

 

0
by Max Tay
Posted on Mon, 07/18/2011 - 08:17

Document is a container for information or data. A collection of data that made up a sensible piece of information would be classified as an artefact. Hence an invoice is an artefact that business handles.Apart from processing of the contents, there is another basic requirement in business to maintain such artefact for legal purpose, i.e. regulatory compliance as legal evidence of a business transaction which form part of the legal contract. I would put this as the priority when defining an output or trasanction information.

Back to BPMN, in BPMN 1.1/1.2 the term used is artefact but in BPMN 2.0 it is refered to as data object which is a technical term and less business friendly. Personnaly, i still use the 'data object' as that of an 'artefact'. Anyway, it is the data attributes defined for the data object / artefact that make up the required information.

@Ivo. Your approach seems to be at the data modelling level which IMO would be confusing to the business. For the information model, a 'business object model' or 'class model' should be adequate.

0

Featured achievement

Rookie
Say hello to the ARIS Community! Personalize your community experience by following forums or tags, liking a post or uploading a profile picture.
Recent Unlocks
  • Profile picture for user Henrik Buckler
  • Profile picture for user UffeK
  • SS
  • MZ
  • Profile picture for user kbiront
  • PacMan

Leaderboard

|
icon-arrow-down icon-arrow-cerulean-left icon-arrow-cerulean-right icon-arrow-down icon-arrow-left icon-arrow-right icon-arrow icon-back icon-close icon-comments icon-correct-answer icon-tick icon-download icon-facebook icon-flag icon-google-plus icon-hamburger icon-in icon-info icon-instagram icon-login-true icon-login icon-mail-notification icon-mail icon-mortarboard icon-newsletter icon-notification icon-pinterest icon-plus icon-rss icon-search icon-share icon-shield icon-snapchat icon-star icon-tutorials icon-twitter icon-universities icon-videos icon-views icon-whatsapp icon-xing icon-youtube icon-jobs icon-heart icon-heart2 aris-express bpm-glossary help-intro help-design Process_Mining_Icon help-publishing help-administration help-dashboarding help-archive help-risk icon-knowledge icon-question icon-events icon-message icon-more icon-pencil forum-icon icon-lock