Hi Davis,
I think you have got representations of instances of a metamodel - the instructions - as well as instances of entities within the metamodel. Looks a bit weird when I write it down, but makes perfect sense.
David/Thomas - thx for the insight.
You hit the nail on the head above. Let me try a concrete example:
The data dictionary describes things such as a Point Feature, and a Point Feature can have Attributes, and Attributes can have name/value, etc. That's really simplifying the model, but it will work as an example.
The data dictionary schema describes all that from a conceptual point of view.
In the real data for the data dictionary you have point of interest (POI), and you can have many such as:
Zoo
Restaurant
Cafe
etc..
So, in EA, I can reverse engineer the data dictionary schema into one or more class diagrams that describe the "metamodel".
What I want to do, is find some way to also reverse-engineer the real data into class diagrams and make sure it conforms to the schema.
Following the concrete example, this means I could have a class diagram that shows multiple POI's such as Zoo, Restaurant, etc.
The goal is visual representation of the meta-model and the data.
Consumers of the meta-model/schema will be spec maintainers who tweak the meta-model as they update the spec.
Consumers of the visual data will be people that want to browse the contents of the dicitionary to see what's in there and have editing capability. For instance, they may want to add a new POI like police station. This should be as easy as adding a new class and synching with the database.
After that explanation, do you guys have any insight/clues on what could be done?
I'll follow up on the links you sent, David.
Thx,
Davis