Difference between revisions of "DIM"
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | A Domain Information Model ('''DIM''') Provides a solution to the information requirements of a particular problem domain. May have multiple entry points. This type of model is defined in the [[HDF]]. | |
| + | |||
| + | This artefact is currently known as a [[Domain Message Information Model]] (D-MIM), a term which may/will be replaced by DIM in due time. | ||
| + | |||
| + | A design model (DIM) is derived from the Reference Information Model (RIM). It is comprised of classes that are clones of RIM classes. The DIM provides a solution to the information requirements of a particular problem domain. The mapping of the requirement’s domain information model to the RIM is used to identify which RIM classes need to be included in the DIM. In some cases it may be necessary to include multiple clones of the same RIM class. Each clone is given a unique name that is reflective of its business use. | ||
Latest revision as of 11:28, 22 December 2006
A Domain Information Model (DIM) Provides a solution to the information requirements of a particular problem domain. May have multiple entry points. This type of model is defined in the HDF.
This artefact is currently known as a Domain Message Information Model (D-MIM), a term which may/will be replaced by DIM in due time.
A design model (DIM) is derived from the Reference Information Model (RIM). It is comprised of classes that are clones of RIM classes. The DIM provides a solution to the information requirements of a particular problem domain. The mapping of the requirement’s domain information model to the RIM is used to identify which RIM classes need to be included in the DIM. In some cases it may be necessary to include multiple clones of the same RIM class. Each clone is given a unique name that is reflective of its business use.
