Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: toyo_EA on October 18, 2006, 05:58:01 am
-
I've made an .eap document and a template. Because many people will be using this file to generate a RTF document, I was wondering if it was possible to have it so that the document is back to the way I organized it - like a default diagram view (where all my packages and requirements symbols are) or a template type of thing?
Or, is it possible to load it into the 'Select Model(s)' menu. Basically, I want it so that what I have set up so that it can be brand new each time.
-
When generating RTF documentation you can give a name to it by pressing "Resource document" button. This document will be shown in the "Resources" window under "Documents".
You can also use "Virtual document" - see the EA help.
-
Is there also a way to keep where I've put my packages and requirements in the diagram and have it as a default so that the people I'm sharing the file with can access a fresh copy each time?
-
Sorry, I don't understand what are you looking for.
When you are working on a shared project, everybody will see every change you have made (and saved).
-
Is it possible to make it so that it can't be changed? Just like how I import the template. Is there a function in EA where I can import stuff I have from the diagram view?
-
If you want a diagram to be unchangable, you can
- lock the diagram (everybody can unlock it, but it is a little work)
- version control the package your diagram is in (everybody can do check out, but this is more work and you have a version in your version control system)
- enable security (project menu in Enterprise version of EA) - administrator can set who can change what
-
And I assume that we can't import it like how we can add a model pattern?
When you're in EA, you can add a model pattern/ projects (Use Case, Requirements, etc.) and the model patterns/ projects have default packages and symbols in there already. Can I do something like that?
-
You can make a diagram to be a default Diagram.
Menu Diagram / Set as Model Default.
-
I've tried that. That only allows me to go to that diagram by default within a project.
Anyhow, thank you very much for your help and your prompt responses!! Much appreciated!
-
XMI Import Export might help you out.
Have a look at this page from the User Guide
http://www.sparxsystems.com.au/EAUserGuide/index.html?importexport.htm
-
Wow. This is exactly what I need. However, there is one issue. I have set pre-defined tag values so that I can add a new requirement, go to the drop down menu, and select the tag values I have already made. After exporting to XMI and importing it back to a new project, the tag values don't transfer. Is there a way to overcome this so that my tag values are transferable?
-
Perhaps Export/Import Reference Data under the Tools menu. You'll have to check the dialog on the Export side to see if the values can be transferred this way.
-
Unfortunately, it's not working.
-
I have set pre-defined tag values so that I can add a new requirement, go to the drop down menu, and select the tag values I have already made.
What exactly do you mean by this? How have you "set" the tags, and where are you putting them?
-
What I mean is I have set default tag value types.
Then, once I pull in a requirement element, I can go add one or more of my default tag value types by going to add new tag value and then going to the drop down menu.
Please let me know if this still sounds unclear.
-
Ahhh...
I gather you mean UML tagged values rather than XMI tags.
Are these part of a (UML again) profile you've set up in EA? If so, I believe you should be able to export the entire profile and import it into another project. This would be done separately from other data transfer operations.
If not, then I'm back to suggesting you look at the Export Refernce Data categories again. Some of the names are not very intuitive, so it is worth browsing the list very carefully.
-
Yes, UML tagged values.
I'm trying to export the requirements package so that I can keep some of the elements and other settings that I have in the diagram view. Everything transferred perfectly when I export to XMI and then reimport it to a new project. The only thing that didn't were the UML tag values I gave to each separate requirements element.
-
If you're tagged values are defined in Settings | UML | Tagged Value Types, instead of a profile (which is my guess) then I think that Export Reference Data is what you want. You'll need to export the 'Property Types'. When this is imported to another model the tagged values defined originally will be available.
-
Thanks Simon. I just could not remember which one to look for.
-
I didn't found a way to export default tags. If somebody know, how to do it, let us know.
But you can make a profile and define your tags there. See help on this topic. Profiles are a very strong feature.
-
What I want to export is exactly "Setting / UML / Tagged value types". Any thoughts how to export this?
-
Sorry, I have read only the first page . :(
-
Thanks, everyone. I think Simon hit it. It got the tag values in although there were 3 default EA tags that showed up. Good enough.
-
The three default tags will show up because it doesn't clear the existing tags from the model first.
It may be worth your while if you really don't want them and you'll be creating lots of new models to replace the EABase.eap file in your install directory with one that only has the tags you want in it.