Book a Demo

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - theArchitect

Pages: [1]
1
That's the way I understand the repositories working; which for me means setting up a single database and having all projects within that database.

Could someone confirm whether this is correct and the way the respository has to be configured?

Thanks

2
To expand on what I mean; for the 2 projects I mentioned in my previous post would I have the following hierarchy configured as seen in the Project Browser window?

Project A (which is a new model, root node)
 --New View (e.g. Simple)
   --New Diagram, Element or Package as appropriate
Project B (which is a new model, root node)
 --New View
   --New Diagram, Element or Package as appropriate
 --New View
   --New Diagram, Element or Package as appropriate

I'm assuming that if this is saved to the DBMS repository; all developes using that repository will see the entire hierarchy.

To prevent updates by anyone; I can then add user security to the appropriate packages/models?

Thanks

3
Hi,

I'm presently looking at EA for our corporation. However, I'm having difficulty in understanding how I would setup EA so multiple users can have access to various projects.

If I have 2 projects and a DBMS repository; would I basically create under the root Model a new node for each project? And create the appropriate diagrams underneath the projects node?

Such that when a developer connected to the server (through EA) they would see ALL projects shown under the root node in the Project Browser within EA?

If this is correct; could someone confirm? I'm assuming a New Model (root Node) would be used for each project root?

What would the best practice be say to ensure a use case for a specific piece of functionality could be copied between projects? Is it just a cut and paste operation?

Any help gratefully received.

Thanks

Pages: [1]