This wiki has undergone a migration to Confluence found Here
Difference between revisions of "SMIRF"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) (New page: Category:RIMBAA Issue Definition: A '''SPM (Small Pattern Model)''' is a logical data model that has the following characteristics: #xxx #yyy Other definitions: *smaller, self-contain...) |
Rene spronk (talk | contribs) |
||
Line 1: | Line 1: | ||
[[Category:RIMBAA Issue]] | [[Category:RIMBAA Issue]] | ||
Definition: A '''SPM (Small Pattern Model)''' is a logical data model that has the following characteristics: | Definition: A '''SPM (Small Pattern Model)''' is a logical data model that has the following characteristics: | ||
− | # | + | #it is used as the atomic persistence model (the object tree as a whole) |
− | # | + | #in a services environment CRUD services exist based on SPMs. Business services are composed of SPM CRUD services. |
Other definitions: | Other definitions: |
Revision as of 11:01, 22 September 2010
Definition: A SPM (Small Pattern Model) is a logical data model that has the following characteristics:
- it is used as the atomic persistence model (the object tree as a whole)
- in a services environment CRUD services exist based on SPMs. Business services are composed of SPM CRUD services.
Other definitions:
- smaller, self-contained, minimally connected RIM object trees
A SPM has the following relationships to other data models:
- RIM:
- D-MIM:
- R-MIM/SIM:
- CMET:
- DCM: the boundaries are drawn for different reasons, there might probably be an assessment scale spm, while this would be used for many dcms, so then there is clearly no 1-1 relationship.
- LIM:
Criteria for splitting a larger data model in SPMs, i.e. criteria for the scope of SPMs include:
- Any association where propagation is turned off forms a boundary
- Any participation with a CMET forms a boundary
Discussion
- (from the minutes of the RIMBAA meeting in Rome in September 2010):
- Ewout: lock/create/read/update/delete as a whole. Explicit references to other data (feels like "identifyable" CMET stereotype). Also is the maximum scope for context conduction (if a big model blocks context conduction, then it's probably a boundary of a SIM/LIM), and serves as the unit for documentation. Only the "root object" is referencable, otherwise the management of references and integrity will become unmanagable.
- How does one find these atomic SIM/LIMs? There is, although not explcietely so, an EHR DMIM. Provides consistency. CMETs quite often too large, need to find smaller parts.
- ACTION: Ewout to write a draft checklist on methods to find 'small pattern models' to be used in CRUD services, based in part on the book by Eric Evans. Determine in how far the methods on the checklist impact the "safety" of the models.