Sharing project by separate teams - howto?

[pjachowi]

Hi

I'm new in EA. I know that different version of the same project can be replicated. But if I try that, the only file to be replicated with is local file. How to handle the situation when project is performed by separate (geographicaly) teams? Should each team send (by e-mail or ftp) the whole project file to other teams periodically?

[Takeshi_KOUNO]

Hello  pjachowi,

My simple answer is 'yes, you should send periodically.'.

Usual way of using replica is as follows:
1. make design master from .eap file
2. make replicas from the design master.
3. distribute them to each teams
4. periodically, each replica synchronizes with desing master
5. return to No.2

If you use replicas, you send all the project file to every team.
If you want to avoid this, please use XMI import/export and Contolled packages.

--
Takeshi KOUNO

[Piotr Jachowicz]

My apologies for forgotting signature.

I'd like to understand it in details

i. one project team is set to be "hub-team" of the project
ii. the hub-team makes design master from .eap file
iii. the hub-team makes replica from design master (new replica may be made only from design master, right?)
iv. the hub-team distributes replicas to other teams
v. the non-hub team updates the project and sends his .eap file to hub-team
vi. hub-team synchronizes his design master with the .eap file getting from non-hub team. After synchronizing, both design master and .eap (getting from non-hub team) file contains the same project
vii. hub-team sends .eap (getting from non-hub team) file to each non-hub team
viii. each non-hub team replaces (or replicates?) their own .eap file with the one getting from hub-team.

Is that right? Are there any plans to implement Lotus/Domino-like replication (so that only differences between replicas are exchanged)?

--
Piotr Jachowicz

[Ilja Kraval]

I think one of the best feature of EA is modelling with Controlled Package for this situation. Divide whole Model Library of team to specific pieces – components of library (like source code library) and make from them the Controlled Packages (see Help - it is simple to  work with Controlled Package in EA) . This model components of model are represented by XML files (text file) and You can work with them with the same process like with source code and with some library manager, for instance Visual Source Safe or CVS. Managing of project (and results from team work) is delegated to known library manager with processes like “check in, check out, developing, building, versioning, labeling” and so on. Pieces of models (Controlled Packages as XML files) are only “file – subjects” in VSS or CVS, everything needed is solved at VSS or CVS level, what is well-known from source code managing.

Ilja Kraval

[Takeshi_KOUNO]

Hello Piotr,

I think the procedure you wrote is correct.
As Ilja said, I recommend you to use Controlled Packages.

If you use Controlled Packages, every team sends the only differences to all other teams.So, you don't need hub-team.

And if you use Contorolled Packages, you can use CVS or another source controll software(ex.VSS). If you use it, every team only checks-in the differences.(needless to send by mail)

--
Takeshi KOUNO

[pjachowi]

I seem to know that I wanted to. Takeshi, Ilja - thanks for your time!

--
Piotr Jachowicz