Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - juliancooling

Pages: [1]
1
I actually like the documents it produces but like Thomas, I sometimes want to structure documents on the relationship hierarchy rather than only 'the package and its children'. These are the documents that get distributed to the customer that should look good and be drawn directly from the modelling tool.

I cannot workout how to do this using the template structure but given the underlying way EA does things, I cannot believe that it cannot be done. I want to create a template, click on a behaviour diagram or a class diagram and print out the requirements and use cases with which it is associated.

It is as if the RTF editor interface is a glass wall that keeps me from reaching the best bits of the underlying data model.

Julian

2
Suggestions and Requests / Re: CVS and branching
« on: November 29, 2005, 04:23:20 pm »
I am very keen to be able to branch and merge as well (using subversion  as it happens). I also haven't been able to find support for this - although it is almost there in the master/replication merge model.

Essentially, our workplace is large and we run multiple projects at the same time. Some of the projects never make it into production and others run at different speeds. The ability to tie EA into our software version control system (and CM processes in general) so that the design model and implementation match is really important.

Julian

PS: The idea of making the EA model on the trunk the Design Master and the versions on the branches Replications and then mapping the version control manually to the branches has occured to me but I am very cautious until somebody tells me it is a good idea.

3
General Board / Re: version control set-up help
« on: July 11, 2006, 12:33:52 am »
As far as I know, version control wants you to have a local copy which is synchronised with a shared repository. If you already use a shared repository (SQL server) as your working copy, the setup is not going to make sense since all changes are transparently shared.

So you will want to use a local copy of the repository using the Jet database and subversion to manage the sharing.

Others who have tried different arrangements may offer additional opinions.

Julian

Pages: [1]