Book a Demo

Author Topic: Altering Default Views in an EA project  (Read 6008 times)

GeeNick

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Altering Default Views in an EA project
« on: July 06, 2005, 03:53:00 pm »
Has anyone experienced any issues after altering default views in EA (e.g., renaming say the Use Case View to something else) . We have been advised to do this to partition projects and separate work being done by colleagues working in product management from work being done by technical architects and development.

We are running EA using SQLServer as the database repository and want to use replication to share the model with a team spread on different sites. Some elements need to be shared but not all.

I'd be interested to know if it caused any problems in particular with XMI imports/exports

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Altering Default Views in an EA project
« Reply #1 on: July 06, 2005, 04:26:26 pm »
Hi,

I have arbitrarily named View packages within multiple Project packages in a .EAP repository.

My environment is therefore not the same as yours,but so far I haven't experienced any problems...

I've generated code sing my own code generation templates, but I haven't used XMI since I reorganised.

Do you have specific issues with XMI?

HTH,
Paolo
« Last Edit: July 06, 2005, 04:26:45 pm by PaoloFCantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

GeeNick

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Altering Default Views in an EA project
« Reply #2 on: July 07, 2005, 01:06:04 am »
Paolo,

Thanks for responding. I'm not expecting any problems and have just had a peek at some code samples in the EA User Guide which has addressed my concerns. I'm just covering all the bases because the solution suggested to us seems to be very useful for development teams like ours that are widely distributed.

Thanks again