In that vein, there are also some additional needs for the architect and IT in general, so let me cover a simple extension/collection metadata example.
The information architecture that I was working with in PowerDesigner was very complete, and we used PD to update our scripts and generate new database objects, like tables, procs and indices. The customer i was helping in this area had a new requirement to track some compliance information on what data they are storing. For an architect with 3000 entities and over 400 tables, this was a daunting request.
So, with PowerDesigner, we can extend the meta model of the Table object to collect additional information. Here is a pic showing the extended model definition and the addition of some compliance attributes.
This picture also shows the creation of a new Tab in the Table properties sheet in PowerDesigner. Now this is the cool part. I can change the user interface in PowerDesigner to allow for this collection directly in the tool.
anyhow, will come back to this, running out of time today.
1 comment:
I read you comment, "we can extend the meta model of the Table object to collect additional information". I am interested in whatever aditional information you may have collected. Is this reliant upon the original data modeling adding comments to the model or CREATE TABLE statements so that it can be later retrieved?
I'm also interested in how you use PD to reverse engineer a model. When I use PD to reverse engineer a database on z/OS it takes forever and usually crashes or I kill it because it never finishes reading in all those tables.
Post a Comment