Book a Demo

Author Topic: Best Practice for a project structure.  (Read 3840 times)

Andy Judd

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Best Practice for a project structure.
« on: December 07, 2011, 02:52:44 am »
Hi All.
We're just in the process of setting up our EA repository with the aim of consolidating our mass of documentation into a more valueable 4+1 architecture view of our estate.
So as with everyone else probably we have multiple design, build and service teams responsible for contributing to the understanding of our estate.
So my question really is around best practive for structuring the repository, when to have new models, when to have new packages, etc

any recommendations appreciated.

thanks in advance

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Best Practice for a project structure.
« Reply #1 on: December 07, 2011, 05:03:31 am »
Have you tried the Search button top left on this page? Quite a number of threads regarding your topic.

q.

Andy Judd

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Best Practice for a project structure.
« Reply #2 on: December 07, 2011, 08:54:49 pm »
Hi Q.

what did you search for, found stuff on linking multiple projects / models but not when to have them based on the estate?

cheers.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Best Practice for a project structure.
« Reply #3 on: December 08, 2011, 04:32:17 am »
Well, I think "estate" is nothing you should include in the search. You need to abstract from what has been talked about in general.

q.