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 - Gayle

Pages: [1] 2 3
Automation Interface, Add-Ins and Tools / Re: Tagged values non-alphabetical
« on: September 01, 2017, 12:33:40 am »

For your questions in Reply #3, I had similar needs to help analyze and validate interfaces throughout my architecture model.  Consider the following:
1. You can create unique custom tags that contain the data you desire.  For my architecture, I decided that the EA applied unique identifier for each interface was good enough and because of volume wrote a script that locates interfaces and creates a custom tag "ConnectorID" that contains the EA identifier. 
2. EA provides a large volume of information about each connector that is available through SQL queries and collection from the repository.  Some of the information available includes connector name and ID, diagram name and ID, sender data, receiver data, connector type and direction.  Consider generating a custom script to collect the data you are interested in and outputting it to an RTF table.  For data that is not available using the document generator templates, you can concatenate the data in one of the valid fields with a delimiter (such as "@").  Post processing can be applied to the output to separate the data.  Look in the EA User Manual for data associated with the connector class.



Thank you for the information.  I had come to the same conclusion, so the OV-5 activity diagrams will remain as is and I'm not going to try to create them using IDEF.  On a positive note, I was able to successfully generate OV-2 and SV-2 diagrams that "look" similar to the ones that the reviewers have been seeing.


Our diagrams are not really using the UPDM formats in EA.  They are closer to the UML formats.

I would love to tell the reviewers that what they have been seeing is obsolete, but it is not a "politically correct" solution to our problem on the document review. 

I will look into your suggestion that UPDM may provide me with some diagram formats that are "similar" to the System Architect formats.

Thank you, Gayle

I am currently using EA V13.5 build 1351.  We have developed a set of diagrams in EA using DoDAF and UML formats that are embedded in the EA tool.  We have a review going on and the reviewers can't seem to get past the fact that the diagrams are not the same formats that are produced by System Architect.

The example I have is from System Architect and it uses IDEF0 for the activity model (OV-5); a node connectivity diagram for OV-2 and a Systems Communication diagram for SV-2.  Our activity diagrams are UML Behavioral Activity diagrams and use the elements in the toolbox format "Activity".  Our OV-2 diagrams are resource flow diagrams that use the UML Behavioral Communication diagram type and the toolbox elements "Communication".  Our SV-2 diagrams are UML Structural Component diagrams and use elements from the toolbox element "Component".

Can anyone provide ideas on how to quickly generate similar diagrams in EA?  I'm primarily interested in the OV-2 and SV-2.  Are there particular diagram formats or MDG technologies that may lend themselves to providing something closer to the System Architect formats?

Thank you, Gayle

Automation Interface, Add-Ins and Tools / Re: Find Diagrams with Connector
« on: February 09, 2017, 08:07:57 am »
Unfortunately, our system is not as cut-and-dried as that.  We have elements (classes, actors, etc.) that are used in multiple diagrams at the same hierarchical level in the architecture.  Using the DoDAF standard for diagrams creates multiple views that reuse the same elements, but the elements have different relationships in the various views.  For instance, we have an actor and class that in an OV-1 diagram (operational concept) have an information flow relationship and in an OV-2 diagram (Resource Flow Description) have an association relationship.  The OV-1 diagram hides the association and the OV-2 diagram hides the information flow.

I have been able to use my existing tools to extract all interfaces that are hidden into a table and all interfaces that are not hidden in another table.  From there using Excel to post-process the output table, I get two worksheets that can be used to isolate the Connector IDs and remove duplicates.  The remaining list of hidden interfaces can be used to perform VLOOKUP functions on the not hidden worksheet to determine if there are any interfaces that are orphans (hidden in all diagrams).

That is not the approach I would like to end up with, but it is good enough for now.  I was diverted on another task and have not yet been able to try the SQL recommendation.


Automation Interface, Add-Ins and Tools / Find Diagrams with Connector
« on: January 25, 2017, 06:09:21 am »
I am using EA 13.0.1307 and VB scripts on an eap file.  My model has multiple types of connectors that appear on one or more diagram and can be hidden on other diagrams.  Using VB data extraction, I have discovered about 300 connectors that are hidden in at least one diagram.

I would like to verify that each of my hidden connectors is not hidden on at least one diagram.  My first inclination was to use a technique similar to one I found on the EA forum to locate all of the diagrams that an element appeared in.  That technique relied on the following SQL statement:
  sql = "SELECT Diagram_ID FROM t_diagramobjects WHERE Object_ID = " & Element.ElementID

The XML result could be parsed to get a diagram list for the selected element.

Is there a similar approach that I could use for the connectors? I don't have much knowledge about SQL, but do know that the above statement will not work as-is for connectors.  Since an ElementID and a ConnectorID could be the same number, I can't just use the above SQL statement with the Connector as an Element. 

For each connector I have a lot of information, however, most of the connectors do not have a Name.  The data that I have includes the connector ID, type, direction, source and target information.


Thank you, Gayle

Problem solved.  What I was missing was that once I had the "ClassifierID" (not ClassifierName"), I needed to use the GetElementByID to get the name of the classifier element. 

Thank you for the assistance.  I apologize for making not being able to clearly state the problem.


Yes, thank you.  I got it backwards.

All of my attempts have been unsuccessful, except to use the fully qualified name.

I have two examples:
  Actor instance:  ":Commander"
  Class object instance:  "Commander:CrewStation"

The "GetConnectorByID" was executed to access the connector data.  From there, the two elements were accessed using "GetElementByID".  When looking at each element using the Element information:

  Actor Instance:  Name is blank, Classifier name is blank, FQ name is "ISP Model._Common Elements.Actors.Crew Station Actors.Crew Station Actors.:Commander"
  Class object instance:  Name is "Commander", Classifier Name is blank, FQ name is "ISP Model._Common Elements.Architecture.Crew Station Arch.Crew Station UCD Arch.Commander: Crew Station"

Note that these are not lifelines (from Sequence diagrams), but are instances that appear on a Resource Flow Diagram (OV-2).  The lifelines in the related sequence diagrams use the same source Actor and Class, so messages in the two diagrams are synchronized.

I still think I'm missing something, but so far, I've been unsuccessful in my tests.  I would like the actor instance to be ":Commander" and the object instance to be "Commander:CrewStation", but I don't seem to be able to access the portion of the names after the colon.


Unfortunately in the architecture model, the ClassifierID (part before the colon) is blank for the actor instances.  I was trying to find a way around the fact that we have only " :Name" labels on the actor instances.


The Classifier Name idea got me looking around for other possibilities and I can get the Fully Qualified names for both the actor instance and the class object instance:

  ISP Model._Common Elements.Actors.Crew Station Actors.Crew Station Actors.:Commander
  ISP Model._Common Elements.Architecture.Crew Station Arch.Crew Station UCD Arch.Commander: Crew Station

While this is not the short name that I would prefer, I think I can make it work.  If anyone has any other possible solutions, I would appreciate the ideas.


The "classifier name" did not work - I still get blank values.  Part of my script writes data to the System Output window so that I can check what information I get.  For the example I had, some of the information written is as follows:

  Connector ID:  12142
  Diagram ID:  908
  Sender Name:
  Sender Classifier Name:
  Sender ID:  11199
  Receiver Name:  Commander
  Receiver Classifier Name:
  Receiver ID:  29816
  Connector Type:  Association
  Connector Direction:  Unspecified

The "sender name" should somehow report out the "Commander" actor instance.  The "receiver name" reports out the "Commander:CrewStation" class object instance.


I'm using EA13 build 1307 with a local EAP file.  I have a number of VB scripts that extract data from the architecture model to use for analysis.  One of the scripts is used to access data associated with connectors.

When I run the script on UML Communication diagrams (such as OV-2 Resource Flow Diagrams), I have connector target or source elements showing up in the data extraction with no Name.

My diagrams have Class Instances (such as the class is "Crew Station" and the object instance is "Commander:Crew Station") and Actor instances (such as the Actor is "Commander" and the object instance is ":Commander").  There are Association interfaces between the class and actor instances.  When I manually bring up the properties of the Association connector, the connector side attached to the actor instance is blank (no name).  When I select the interface between the "Commander" actor and the "Commander" crew station, right click and choose "Advanced", "Set Source and Target", the From Element listed is ":Commander" and the To Element listed is "Commander:Crew Station".

Without changing the names of the actor object instances to have something in front of the ":", is there anyway using a script to get to the equivalent of the Advanced "Set Source and Target" elements so that I will have an element name for the "Commander" actor rather than a blank?  Right now, the element names are obtained using the connector "SupplierID" and "ClientID" properties to "GetElementByID".  From there, the element "Name" is selected.  The element IDs are not blank.

Thank you for any assistance you can provide.


Thank you.  The "title block" is the element I thought it was.  I now see how a tag can be applied to it.


The composite elements or title blocks might work for me. 

For composite elements, do you have any suggestions on which type of elements to use?

For the title block idea, what kind of elements are you using to create them?


Thank you for the ideas.  Stereotype might work - the model does not currently have any diagrams stereotyped.  I'm trying to avoid using anything that will physically show up on any diagram - the model is the deliverable to my customer (as HTML) and if we start putting notes on the face of diagrams, they will not understand and will question what we are doing.

I could possibly use the diagram notes field, however, some of the diagrams have descriptions in the notes field and the plan was to add descriptions to all diagrams using that field.

I could not find "style" associated with diagrams in the user manual.


Pages: [1] 2 3