Presents: ObjectRoleModeling.com Sunday, September 07, 2008
 Search
Register Login
Forums
 
 

Note: To post to a thread, you must be logged in.

  Forums  
 
SearchForum Home
     
  Orthogonal Toolbox  Support  exporting rules...
 exporting rules
 
imgOfflineGuennadi V. Vanine
170 posts
5th
Joined
5/28/2005

exporting rules
Posted: 30 May 05 3:59 AM Modified By Guennadi V. Vanine  on 5/30/2005 4:01:04 AM)

I installed Orthogonal Toolbox.
And I cannot find export neither in it nor in VEA.
But even if I miss it in VEA, it still make sense to concentrate similar functions in one place.

But now, or yesterday, I would like to know how to export? rules as text


thanks god, i.e. Scot, saving the ORM cause in all EMEA by patiently answering ALL questions, Геннадий Владимирович Ванин (aka Guennadi Vladimirovitch Vanine or Vanin Gennady )
imgOfflineScot Becker
220 posts
www.orthogonalsoftware.com
4th
Joined
9/24/2004

Re: exporting rules
Posted: 30 May 05 8:05 AM
To get the actual verbalization of the constraints, you will have to use a report (Database | Report...) from VEA as the toolbox doesn’t support (yet) full constraint verbalization. The toolbox supports XML export of the model meta-data, and should be available from the “Export XML” button or (Tools | Export XML). You’ll have to have a model open to see this functionality, however.

To be clear, the toolbox is my code whereas VEA is Microsoft, so I can’t really integrate with their code per se and thus any added functionality I add will always be a separate function.

Scot.
imgOfflineGuennadi V. Vanine
170 posts
5th
Joined
5/28/2005

Re: exporting rules
Posted: 31 May 05 2:29 AM Modified By Guennadi V. Vanine  on 5/31/2005 2:39:14 AM)

Thanks, Scot,
you do a great job and it really a big help to save a lot of time.

Sure, I saw Database|Report functionality but it is not of any help in order to go between text rules and source model.

For ex., I would like to export rules from sample models, edit them and import back.
Or I would like to elaborate all big model in simple terms and through rules without using complicated constraints. So, either I do not use graphic specifications to add elements or I just should repeat the work in file with text rules?

So, as I understood your import rules functionality implies that I should create any model rules in form of text from scratch. I can't also share it. If I make changes graphically 
Or I miss something?

I understand that it does not support complicated things but it impedes reuse of model in form of working directly with rules in text file.

Anyway, can you share your (enormous) experience, advise how do you work with models?


thanks god, i.e. Scot, saving the ORM cause in all EMEA by patiently answering ALL questions, Геннадий Владимирович Ванин (aka Guennadi Vladimirovitch Vanine or Vanin Gennady )
imgOfflineScot Becker
220 posts
www.orthogonalsoftware.com
4th
Joined
9/24/2004

Re: exporting rules
Posted: 31 May 05 6:52 AM
By "rules" do you mean the fact types that can be imported by the toolbox or the constraints on the fact types?

If you mean constraints, the verbalization for the graphical ones (uniqueness, mandatory, subset, etc.) will be shown on the constraint report. Non graphical constraints – those that you manually type some where on the diagram – will not. Also, there is no mechanism to import constraints into an ORM source model.

If you mean fact types: the toolbox really just supports a bulk import feature. If you were to change the fact type text and re-import it, it would likely think it was a new fact type and as such not change the old one in the source model at all.

If you wanted to export the fact types from one model and import them into another model, this can be done with a little bit of work. You would need to create some custom XSLT (stylesheet) that converts the XML output into a text file of fact type readings. Once that is done, that file could be used to import those fact types into a new model.

Scot.
imgOfflineGuennadi V. Vanine
170 posts
5th
Joined
5/28/2005

Re: exporting rules
Posted: 31 May 05 8:12 PM Modified By Guennadi V. Vanine  on 5/31/2005 8:15:31 PM)

3d case:
"new model" is just the same model but after adding elements "graphically"... well, through VEA.
After that I should update the text file  with rules or it doesn't serve me for anything else then first shoot to start
But imagine that I want to wrk at some branching versions of the same model iteratively and still use/have  text rules (around)
Might be I have wrong plans due to lack of tools knowledge


thanks god, i.e. Scot, saving the ORM cause in all EMEA by patiently answering ALL questions, Геннадий Владимирович Ванин (aka Guennadi Vladimirovitch Vanine or Vanin Gennady )
imgOfflineScot Becker
220 posts
www.orthogonalsoftware.com
4th
Joined
9/24/2004

Re: exporting rules
Posted: 01 Jun 05 6:01 AM
I understand how round-tripping would be useful, but it just isn't what the ORM Import facility in the toolbox was designed for. It was built to facilitate quickly adding a bunch of fact types to jump-start the rest of the model creation and maintenance within VEA.

At some future point, the toolbox might support round-tripping of the XML document, since that will contain all of the meta-data (internal ids and so forth) that would be needed to do round-tripping correct.

Scot.
imgOfflineGuennadi V. Vanine
170 posts
5th
Joined
5/28/2005

Re: exporting rules
Posted: 03 Jun 05 4:25 PM Modified By Guennadi V. Vanine  on 6/3/2005 4:26:29 PM)

thanx a lot, Scot,
you save the ORM cause in Portugal answering my silly questions!


thanks god, i.e. Scot, saving the ORM cause in all EMEA by patiently answering ALL questions, Геннадий Владимирович Ванин (aka Guennadi Vladimirovitch Vanine or Vanin Gennady )
imgOfflineScot Becker
220 posts
www.orthogonalsoftware.com
4th
Joined
9/24/2004

Re: exporting rules
Posted: 03 Jun 05 7:48 PM
 Guennadi V. Vanine wrote

thanx a lot, Scot,
you save the ORM cause in Portugal answering my silly questions!

Glad to help.

Scot.

  Orthogonal Toolbox  Support  exporting rules...
 
  Syndication  
   
 
© 2003 - 2007 Orthogonal Software Corporation. All rights reserved. Terms Of Use Privacy Statement