Canonical Data Model
The main challenge continues to be the data model. In SOA speak: the canonical data model. Through some sort of difficult reason it is very hard for most IT people to deal with data models. Obviously they are not so sexy as the functionality in the application. Unfortunately it still requires quite a bit of skill to develop one ... and expecially an intermediate data model needs to fit a lot of requirements. It needs to...- Support the superset of requirements of the related systems - and therefore it is important to model cardinalities, identifiers, attributes, etc. in the most flexible way. Cardinalities need to be flexible (by default many to many). Identifiers need to be unique (by default meaningless numbers). And with every attribute it needs to be clear that this is an attribute and not potentially an entity ...
- Support the reference data over time (4D), i.e. everything needs to be time stamped and no reference data gets deleted ...
If developers want to meet all these requirements, than they need to dust off some skills we dropped during the nineties.
posted by Evert Ruijs @ 10:44 AM
0 Comments:
Post a Comment
<< Home