How many EA database to setup for corporate applic

[fausto bertoli]

Hi, one of our client has a complex IT landscape with several applications each other interfaced. We are dealing to propose to adopt a standard such like EA to document the landscape but suddenly an initial question rise: in this scenario is  which is the best way to organize information with EA? It is better to use a single database wherein all the application are contained or to use separate database for eac applicaation?
Becase of the feasibility studies normally involve more application interacting toghether, I suppose the best solution is to use a single global database, wherein  global common requirements ad interface specifications can be held.
I would like to get feedback on existing experience about that.
Thanks in advance.
Fausto

[Paolo F Cantoni]

Hi Fausto,

Good to hear from someone in La Spezia!  Although I was born in England and live in Australia, my family is originally from Soliera Apuana (MS).  I've been to La Spezia a number of times (the last time, unfortunately over 35 years ago) - an aunt lived there.

But to get to the meat of your question.  We (Semantica) use the notion of an Integrated Metadata Repository (IMR) to hold the overall model and each team uses a Subset Metadata Repository to do their part of the landscape.  However, this shouldn't be attempted until you understand the basic synchronization and xmi transmission mechanisms that EA uses as you can quickly create a big mess.

However, generally the IMR lives on a Server and the SMRs are generally .EAP files or Server based (depending upon the team needs).

Our IMR has a structure to enable it to hold models at various levels of abstraction, from multiple projects in a coordinated fashion.

The IMR is generally, read only and is updated only when metadata from the SMR has been through the appropriate governance process.  The SMR has slightly laxer rules.  (Occasionally) we've created a three-level mechanism where LMRs (Local Metadata Repositories) are "calved off" from the SMRs and used by individuals or very small groups.

Version control can be tricky, but it is doable (we use off-line version control).  You definitely need a good governance process if you are to attempt it.

The IMR mechanism allows the creation of true Enterprise-wide Metadata Repositories.

This will probably raise more quesitions...

HTH,
Paolo

[fausto bertoli]

TYhank you very much for your answer Paolo.
I work in La Spezia but lives in Aulla Lunigiana, close to the village you mentions.
Coming to the point: I suspected that there should be some kind of mechanism to support the requirement. reading sparx articles regarding the SCM I have seen how to integrate the version control repository as a second  level of data archiving behind the working repositories beeing them on shared rdbms database,  or shared/stand alone EAP files.
Working with subset of such IMR repository could be fine.
Whenever you need to integrate another application may be you can get the interfaced elements form the IMR, and include them into the working repository SMR . where the new applications shall be designed.
At the end of development all the item, old unchanged, and new, could be reversed into the IMR.
I have understood that EA use GUID to identify objects so it is easy to exchange them avoiding classical conflict problems.

Within my factory we used other SDLC tools such as Quality Center but now after having a deep look at EA features I would like to introduce it into the SDLC because it is intuitive, simple, fast and complete.
Fausto

PS: if you want we can discuss about your family's origin country on facebook, hereafter you can find my profile:
http://www.facebook.com/home.php#!/profile.php?id=1248640471
Ciao e a presto sentirci.