Questions about the Essential meta model
Posted: 02 Mar 2009, 22:43
It's very exciting to discover this project!
I am wondering about the meta model. Is there any material explaining and documenting the choices made?
My reasons for asking:
(1) the four layers seem a bit arbitrary; not everyone would use these. Would it be feasible to introduce a more general abstract class "Layer" and let users either apply instances of those (Business, Application, Information, Technology) or define their own more suited to their enterprise?
(2) I note the terms Conceptual / Logical / Physical cross-cut all of the "layers". To me, these seem more like Layers (often developed successively) whereas Business, Application, Information, Technology seem more like "domains" or "areas of concern" (not ordered as implied by "layers").
(3) How easy is it to extend/modify the meta model? I often work within the paradigm of ISO/IEC 42010 ( http://www.iso-architecture.org/ieee-1471/ ) which has its own meta model for architecture description, and want to be able to communicate in that language to enterprise stakeholders.
-- Rich
I am wondering about the meta model. Is there any material explaining and documenting the choices made?
My reasons for asking:
(1) the four layers seem a bit arbitrary; not everyone would use these. Would it be feasible to introduce a more general abstract class "Layer" and let users either apply instances of those (Business, Application, Information, Technology) or define their own more suited to their enterprise?
(2) I note the terms Conceptual / Logical / Physical cross-cut all of the "layers". To me, these seem more like Layers (often developed successively) whereas Business, Application, Information, Technology seem more like "domains" or "areas of concern" (not ordered as implied by "layers").
(3) How easy is it to extend/modify the meta model? I often work within the paradigm of ISO/IEC 42010 ( http://www.iso-architecture.org/ieee-1471/ ) which has its own meta model for architecture description, and want to be able to communicate in that language to enterprise stakeholders.
-- Rich