Sparx Systems Forum
Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: Stephen on February 19, 2004, 03:17:48 am
-
I'm writing a utility to maintain the spec's for the views, stored procedures and potentially other objects of my data layer (SQL Server) within the "Deployment Model" for a system.
I have imported the table details by hand through the GUI, but will now want to maintain the information in a similar fashion.
For my initial stab at modelling (make that recording) a stored procedure I have created a class and included the appropriate procedure parameters etc.
To model the dependencies (in this case a table) I dragged the sp class onto a diagram and ctrl-dragged the relevent table class (held within another package), selecting to paste the element as a simple link. Then added a dependency connector, filled out the parameters etc. I think I can automate these operations...
This leads to the questions.
1. One for the jury - Does this seem a reasonable way to model sp's?
2. I have a diagram that displays the first-order dependencies. But is a diagram per database object a bit heavy? I'm anticipating drawing in dependencies between middle and presentation tiers also so there could be a lot of diagrams. Has anyone got any good pointers to diagram layout algorithms?
3. I don't see anything in my relationdship matrix. What have I missed?