Book a Demo

Author Topic: Any limitations on the number of connectors?  (Read 2788 times)

cube1us

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Any limitations on the number of connectors?
« on: May 28, 2009, 04:42:02 am »
We are using Sparx EA to model elements of our enterprise architecture.   As we begin, we are natrually noticing that there are certain common elements (a particular table, say, or a database instance) that are common to many many systems -- and thus could potentially end up with dozens, or possibly even hundreds, of connectors referring to them.  

Aside from database performance (which might be no small thing) is there any practical limitation on the number of connectors referring to a particular element?

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Any limitations on the number of connectors?
« Reply #1 on: May 28, 2009, 10:31:37 pm »
No.

Remember that in many cases you are looking at a 'representation' of a connector on a diagram. Though this connector might appear in many diagrams, each of these is simply a reference to a single instance of the connector in the model itself.
No, you can't have it!

cube1us

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Re: Any limitations on the number of connectors?
« Reply #2 on: May 28, 2009, 11:15:31 pm »
Thanks.  Yes, I understanad about connectors on diagrams as opposed to unique connectors in the model.  However, when one has hundreds of systems, one can generate a large number of unique connectors to common elements, especially in deployment diagrams in the model -- hence the question.

Thanks again.

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Any limitations on the number of connectors?
« Reply #3 on: May 29, 2009, 01:19:12 am »
You are quite correct, of course.

As systems grow in complexity, so too do their models. Even though UML is designed to help manage the 'complexity' by standardizing (and sometimes minimizing) presentation of details, models must naturally reflect the degree of complexity of a system from the point of number of elements and relationships.

The above said, EA can easily handle systems with many thousand elements and connectors.

EA also helps you partition the system into management chunks, via diagrams and other facilities, as any good UML tool should do.

So keep modeling, pay attention to what you include in any given portion of your model (by managing the number of elements or degree of abstraction), You should find that EA helps you throughout the process. The overall size of your model should not be a major concern. [Unless it is simply enormous, but in the case of EA that is a long way out.]
No, you can't have it!