Single Repository For Enterprise Traceability

[Nick Pearce]

I'm interested to know how you all organize your requirements in the shared models. I am a solution architect so I am interested in not only reusing requirements between projects but also reusing artifacts such as systems and hardware components. In essence, I would like to be able to use EA for more than just requirements management on a project. Being able to leverage the traceability reporting across all systems and even between business processes in an enterprise would be an enormous asset. Has anyone ventured this far down the rabbit hole?

I'm very interested to hear what you are doing. Thank you in advance.

[Geert Bellekens]

Nick,

The easiest solution is to put all the enterprise models into a single EA repository stored on a central database.
You can then create dependencies between the different artifacts in the different models.

Just be careful to respect the dependency directions, a shared model should not depend on the different projects, but since you're an architect I probably don't need to tell you that.

Geert