new project in ea 6.1

[john]

In versions < 6.1 a default model could be used to ensure that all new model whould be structured in the same way. In 6.1 a model wizard is present but still the eabase.eap default model is mentioned and also that you can specify your own default models.

I find however no way to control the new project wizard or to use a predeined base model.

Is  the old fefault model construct till useable?

[AshK]

Hi John,

You can no longer select which file will be the used as the base model for new projects - it is now always EABase.eap (found in the EA dir).  You can replace this file with your preferred base model.  

The new eap wizard displays a list of exported packages located in ...\EA\ModelPatterns\.    The list is configurable by editing the models.xml file.

Hope this is helpful,

Ash

[john]

the proposed solution helps but introduces 3 problems/questions

1
When is the eabase.eap file used when you always have to use the model paatern wizard?

2
The solution only whould work if we had just one base model, but in the past one could choose which base model to use. The solution with the  wizard introduces a comparable solution in that you can choose to use simple, common or unified process patterns. It seems that the file ..\ea\modelpatterns\model.xml describes this behavior, by using so called filters. We could create a filter for each our model files. This however would mean that we need to change the sparx supplied file which we do not like.

3
Because our base-models are on a netwerk drive the xml packages would also be needed on that network drive. In the model.xml file meantioned in step 2 there is a file="xxx.xml" entry. This entry can be changed in something like "..\..\xx\yy\z.xml" but not into "c:\xx\yy\z.xml" nor in p:\xx\yy\z.xml which we need.

is there no way to specify a base model path using a registry key (allowing to use p:\xx\yy\z.xml) and having enterpise architect look there for an extension to the sparcs suplied model.xml file?

Hoping on a workable sollution
greating John

[michael_rainwater]

I really like the new Model Patterns feature.  But I concur with the original post that it would be much more helpful if I could point to a network location for a given pattern.

We also share our patterns on a network.  I will need to figure out a solution to synchronize the network folder with each users "ModelPatterns" folder (which could be a diff location).  If all I needed to sync is the single Models.xml file, that would be better (because it doesn't change often).

I would really like to see a solution that allows us to use our network shares for our patterns.

Thank You

[Jeff Odell]

I'm thinking that in a source code controlled situation, you would want the entire ModelPatterns directory location to be configurable in EA.  This could be implemented as an option on the Dialog and or in the Tools>Options.  

You could then pull that directory from source code control into your typical local source code directory, rather than targeting the ModelPatterns directory in the EA installation area.

This would also solve the issue of locating the models on a Network drive in a non-scc environment.

[michael_rainwater]

I love Jeff's idea.  That would be an ideal solution to the problem.

This would really be ideal and would provide the fexibility to support both the current feature (as a default location) as well as configuring the location to use network or SCC.

I hope someone @ Sparx sees this idea and decides to implement it!

Thanks Jeff.

[Jeff Odell]

I sent it in to Sparx as a feature request.  My experience in the past is that Sparx is very responsive an I expect they will implement something like this or something even better.

[Graham_Moir]

Have I missed something ?
The option to create a new project using a specific base project still seems to be there to me, although it's called "Copy a base project.."   Where is the constraint that only EABase.eap can be used ?

EA 6.1.786

thanks
Graham

[Jeff Odell]

Graham is correct - the "old" functionality of copying a base project is still available on the main page by selecting "Copy a Base Project...".

I caused the thread to wander off to a different issue - sharing the xml file and exported packages that support the new selection dialog.

I'd still like that functionality, but we have't lost the original way of doing things.

[john]

ou are right and wrong.

In 6.1 785 the use of the bas model was gone.

As a change request the old functionality now (6.1 786) is back at the start page using copy a base project.

So we lost it and found it again.

Thanks to sparx fo rthere quick reaction.