Custom Meta-Model Support in Essential Project
Posted: 08 Aug 2012, 17:56
Hi all,
First of all, I would like to congratulate the Essential Project Team on creating such a wonderful product for the open source community. Not only it is a good software, it is backed by some of the most elaborate documentation, tutorials and support I have seen for an open source product in this area.
We are planning on leveraging Essential Project to create an EA Repository for our artifacts at different layers. Our requirement is to create a simple repository which points to various artifacts at different layers of architecture and capture dependency in between.
We have reviewed the Essential Project's (EP) Meta-Model which comprises of 4 architectural layers and 3 views for each of those layers. In total there are 12 boxes which needs to be populated. Within each of these boxes there are many classes which actually capture the required data.
For our usecase, this model is very comprehensive. We were wondering is if there is a way to create a custom meta-model or strip down the existing EP Meta-model to cater to our usecase. We do understand that this will require modifications throughout the product right from capturing the data to presenting it in reports.
We would like to know what all steps are involved in lets say
1. Create a custom meta model (either new or a strip down version of the EP meta-model)
2. Capture instance data based on this custom model
3. Publish the data based on the custom model to the Essential Viewer
4. Create Reports to display the data based on this custom model
Any help or guidance in this regards is highly appreciated.
Thanks in advance,
Kunal
First of all, I would like to congratulate the Essential Project Team on creating such a wonderful product for the open source community. Not only it is a good software, it is backed by some of the most elaborate documentation, tutorials and support I have seen for an open source product in this area.
We are planning on leveraging Essential Project to create an EA Repository for our artifacts at different layers. Our requirement is to create a simple repository which points to various artifacts at different layers of architecture and capture dependency in between.
We have reviewed the Essential Project's (EP) Meta-Model which comprises of 4 architectural layers and 3 views for each of those layers. In total there are 12 boxes which needs to be populated. Within each of these boxes there are many classes which actually capture the required data.
For our usecase, this model is very comprehensive. We were wondering is if there is a way to create a custom meta-model or strip down the existing EP Meta-model to cater to our usecase. We do understand that this will require modifications throughout the product right from capturing the data to presenting it in reports.
We would like to know what all steps are involved in lets say
1. Create a custom meta model (either new or a strip down version of the EP meta-model)
2. Capture instance data based on this custom model
3. Publish the data based on the custom model to the Essential Viewer
4. Create Reports to display the data based on this custom model
Any help or guidance in this regards is highly appreciated.
Thanks in advance,
Kunal