Book a Demo

Author Topic: Project organization  (Read 3797 times)

Norby

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Project organization
« on: July 19, 2013, 06:02:16 pm »
Hi all,

I'm trying to come up with a good project organization. We want to use a DBMS shared repository (30-50 people accessing it). From what I gathered till now each database can contain one EA project. So I thought of using one model per our project.

As we have 50-60 projects per year the view will get bloated. One nice option would be to export a model into a EAP once it's not used often. But as I see this is not possible, only the entire EA project can be moved to EAP. Correct?
Ok, I could export everything to EAP, and manually delete models not needed, but would be nice to insert the EAP back into the database (adding it to existing models) if needed again.

Does anyone have some tips what would be a good setup in this situation?
Or, am I completely on a wrong way?

TIA!

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Project organization
« Reply #1 on: July 19, 2013, 09:02:39 pm »
You can export single packages via XMI. Then you can put them under VC which will lock them for further change. Or you can consider to use EA security to achieve a similar effect. I'd recommend to use security with Require Lock to Edit in general.

q.

Dermot

  • EA Administrator
  • EA User
  • *****
  • Posts: 591
  • Karma: +7/-0
    • View Profile
Re: Project organization
« Reply #2 on: July 22, 2013, 03:28:29 pm »
Norby,
With your comment:
 "From what I gathered till now each database can contain one EA project."
One repository can support as many projects as you want - best to set up a New Root Node for each new project - then you can use group locks to limit write access to that node if needed.  See the help topic "User Security".
Further if you have any common repository data like Frameworks - set these up as independant Root Nodes and link these across all the applications.
For more details on this see the deployment whitepaper available from:
http://www.sparxsystems.com/resources/whitepapers/index.html
« Last Edit: July 23, 2013, 10:33:24 am by Dermot »

Mike5803

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Project organization
« Reply #3 on: August 09, 2013, 02:09:57 am »
I've read the deployment white paper.  It states that you can have multiple root nodes in one repository, but not how.  I've not been able to figure out how to do it.  When I go to add a project it does not give me the option of adding it to the repository, just a local drive.  I'm new to EA, so may be missing something simple.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Project organization
« Reply #4 on: August 09, 2013, 05:17:23 am »
Right click the existing root. It offers the creation of a new root.

q.