Book a Demo

Author Topic: Tracing network device locations  (Read 14916 times)

kepNCI

  • EA User
  • **
  • Posts: 127
  • Karma: +1/-0
    • View Profile
Tracing network device locations
« on: February 22, 2015, 01:30:15 am »
Looking for suggestions on the best UML elements and connections for representing geographical locations and relationships with network devices in such a way that one can trace the location of a given network device.

For the network devices, I already have a package and deployment diagram for each type of network device types (server, router, switch, etc.) as well as stereotypes defined in an MDG for each type from which I create instances for each network device in the respective deployment diagram. Most of my network devices have a tag for location, which is populated from values obtained from our discovery tools. However the goal is to have a complete traceable relationship to its location, which I believe implies some relationship connections as well as package hierarchy for locations in browser.  

This is what I have tried so far:
I created another package called Facility Locations and an associated Facility Locations diagram. Under the Facility Locations package, I have a package for each country. Under country I have a package for each location/city, then under city I have a package for building. Thus in the project browser one can see the geographical country, city/location, building hierarchy of where we own/manage network devices. Then in the Facility Locations diagram, I basically duplicate the same hierarchy structure, by dragging each geographical package as a package element and then connecting them appropriately using a nesting connection.

Then under the package for each building I have a deployment diagram onto which I drag links to the device instances that are located in the building. To create a traceable link between device and building, I also dragged the associated package for the building as a package element onto the diagram and link each device using a nested connection.

Now when I click on a network device, I can trace its location within the traceability window.

QUESTIONS:
- Can you think of a better way that may be more UML compliant?
- Are package elements the best element to use for defining a geographical location?
- Is the nesting connection the best relationship connection?  Seems to be the only choice for connecting the package elements.
- Is the nesting connection the best relationship connection to associate the device node to the building package element? When you use the quick link from the node to the package, nesting connection is not an option, however, EA allows one to use the nesting connection from the toolbox to create the link.  Does that mean I am not UML compliant?

kepNCI

  • EA User
  • **
  • Posts: 127
  • Karma: +1/-0
    • View Profile
Re: Tracing network device locations
« Reply #1 on: February 22, 2015, 04:04:13 am »
Additional comment:
One think I do not like about using package elements on a diagram is that it lists all of the elements found in the associated diagram.  Apparently there is bit an appearance option to not display the list, at least I could not find it. For example the package element for the building that has a main server room becomes huge because it lists each server and composite parts.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Tracing network device locations
« Reply #2 on: February 22, 2015, 06:44:48 am »
Generally speaking your approach is fine. But looking into details me thinks that people want a [highlight]real[/highlight] GIS and not a misused UML model. It looks like you're mixing things and think that EA can be used as GIS.

q.
« Last Edit: February 22, 2015, 06:45:23 am by qwerty »

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +55/-3
    • View Profile
Re: Tracing network device locations
« Reply #3 on: February 23, 2015, 09:01:31 am »
Quote
Additional comment:
One think I do not like about using package elements on a diagram is that it lists all of the elements found in the associated diagram.  Apparently there is bit an appearance option to not display the list, at least I could not find it. For example the package element for the building that has a main server room becomes huge because it lists each server and composite parts.
Diagram > Properties > Elements > Show Compartments > Package Contents = OFF
The Sparx Team
[email protected]

kepNCI

  • EA User
  • **
  • Posts: 127
  • Karma: +1/-0
    • View Profile
Re: Tracing network device locations
« Reply #4 on: February 24, 2015, 04:11:26 am »
Thanks for the comments.
Do not know why I did not find the package content option. Seems obvious now and just what I wanted.
The primary purpose of the project is a massive system architecture so UML and EA seems perfect.  Location of network devices is a small function of the total design and thus I would not believe would warrant a separate GIS tool.
Am I breaking any UML rule/guideline when connecting a device node to a package element via a nesting connection?    

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Tracing network device locations
« Reply #5 on: February 24, 2015, 04:24:03 am »
Why not nest it (put in package) instead of creating a nesting connector. IIRC nesting is only used between packages (see Superstructures 2.1.1 pp. 109..111).

q.
« Last Edit: February 24, 2015, 04:27:49 am by qwerty »