Hey guys,
I've got a question regarding linking several EA Projects. Allow me to set up the scenario.
A documentation effort took place a couple months back for a huge system, consisting of several modules. Each of the modules was documented in a separate project (to make it easy to control versions, since only 1-4 people would be editing each project).
After that, the documentation was all saved. We still have it in separate files for each module (~8) for the sake of continued updates.
Here's the problem: another project just began which is basically an addition to our current system, but it spans several modules. They are creating documentation in EA, and currently their only option is to add it to each of the separate project files, because they NEED to keep the documentation current (i.e., when we update our documentation, it should change theirs, and vice-versa).
My only idea to accomplish this was to bring all the documentation into a single project, and then create a separate package for the new addition. Within that folder, I would put "Simple Links" to all the diagrams they needed to work with, so any changes they made would also be reflected in the original location. Unfortunately, my manager would like to keep the files all separated, which makes this impossible.
In summary, my requirements are this: 1. All the documentation surrounding the new addition must be easily separable from the original documentation. This means they cannot just add their information to our current stuff, because it would be a pain to pull it all out for review.
2. The changes made in their documentation should be reflected in our system, and vice-versa.
Does anyone have any magical advice that will work for this situation? I hope to hear back as soon as possible!
Thanks,
Mike
