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

Pages: [1]
Yes, I discovered the error (for Mac/OSX) was that I have the MS Office applications for Mac and not Windows versions running in Crossover. Oops.

Thank you for the pointer, but I had found and read that post prior to mine.

For amusement the following is a 'sample' of the types of things (in a spreadsheet) that I need to import (into a UPDM OV-3):
Need Line | Information Exchange | IE Description | Source Node | Source Activity | Destination Node | Destination Activity | Media | Frequency

It may be useful to note that I running EA on a Mac via Crossover. I have very few problems with configuration.
The most notable the inability to code or run Visual Basic.


Automation Interface, Add-Ins and Tools / Excel Importing -Profile Creation
« on: February 23, 2016, 07:06:53 am »
I'm attempting to use the MDG MS Office extension to import Excel files. The Excel files have a header row that needs to be mapped. In attempting to create a 'Profile' for the import I can't get past the 'Work Sheet' selection. I've selected the Excel file (as the 'Sample Document'), making sure it's not open, but then the 'Work Sheet' list remains empty. And it won't let me go to the 'Next' step.

What am I doing wrong? Is in inappropriate to use a file the is intended to be imported as a 'Sample Document'?

Any help will be appreciated.

Thank you.

General Board / Re: Team Review Comments
« on: February 20, 2016, 04:03:26 am »

Thanks to your diligence I've found the problem and solution.

The problem: EA uses terms inconsistently on the 'Term Review' menu(s).  Starting with the menu bar on the 'Team Review' dialog window the mouse over label for creating a new 'Topic' is "New Topic", but if there are no existing categories a new 'Category' is created; Subsequent use of the 'New Topic' button does create new 'Topic's.

After creating a 'Category', the 'Category' context menu (i.e., right mouse click) provides the option of creating a 'New Topic' (under the selected 'Category). Then the 'Topic' context menu provides an option of 'New Document' (the documentation for 'Comment' seems to suggest this is where I can 'post' a comment in reply to a 'Topic'), when executed this creates a 'New Post'. The context menu for 'New Post' (finally) shows an action for 'New Comment'.

I can now explain what the notion of 'Comment' means in the context of 'Team Review' and how to actually create them.

As EA has 'grown' over the years semantic inconsistencies and confusions have arisen. I do hope that they'll get around to correcting them, though it is a very tedious effort.

Again thank you for your help.


General Board / Re: Team Review Comments
« on: February 19, 2016, 02:50:37 am »

I'd did forget to put in environment information, sorry about that.
I'm using EA version 12.0.1214. But, though it shouldn't make a
difference for this feature, I' running via Crossover (on a Mac with
OSX 10.75).

I understand the context sensitivities of the various menus and have
explored the menus for the various entities with no luck.

However, I did fail to try it on a Windows OS. Thank you for the


General Board / Team Review Comments
« on: February 18, 2016, 01:37:17 am »
Regarding 'Team Review Comments' the documentation for commenting a (or on a) review document, "Comment on a Document", directs a user to execute one of the following actions,
    Right-click on the required Document (or Comment) in the Team Review window and select the 'New Comment' option
    Click on the Document name and on the 'New Comment' icon in the Team Review toolbar, or
    Click on the Document name and press Ctrl+N

My confusion is that there is no 'New Comment' option, only a 'New Topic' action. Similarly, 'Ctrl+N' creates a new Topic.

So the question is whether the notion of 'Comment' is equivalent to 'Topic' (and whether the documentation is in error)?

General Board / Re: Number of (Sub) Models?
« on: January 28, 2016, 05:46:47 am »
Thank you all for your responses and answers.

As to the number of models in the project, this is a client need/requirement. The intended domain (of application) has 'true' enterprise scale (i.e., very BIG). The need is to be able coordinate solution architectures and have an overall integrated architecture. The multiple models will be solution architectures (each which I would expect, but don't know at this point, to have fewer than 32K nodes) that must be consistent with, and extend, the enterprise architecture.

General Board / Number of (Sub) Models?
« on: January 27, 2016, 11:45:40 am »
I need to create a project that will have at least 400 'models' (actually sub-models of a top-level model) and the number and/or complexity of each will grow. Does EA have any sort of 'maximum' number of models a project can support? Or will is be just an issue of performance? I assume performance will be impacted by the particular deployment scenario employed.

General Board / Transitivity of 'Realization' (relation)
« on: July 29, 2015, 10:13:56 am »
Consider the following scenario. There are several requirements (e.g., hundreds) and have several layers of parent-child relations represented, say using the the aggregation to whole relation. Further suppose that there is a component or use case that realizes a parent requirement (and parent has several layers of child requirements).

Does EA have any capability to (essentially) make the 'realization' relation/connector transitive over the child requirements: If the parent is realized in some entity, then all of it children must also be realized in the [same] entity?

Automation Interface, Add-Ins and Tools / Re: Visual Bacis Arrays In EA
« on: August 19, 2015, 06:51:56 am »
Thank you for the quick response. After reviewing your suggestion, which I had already tried, I realized that I wasn't accessing the array correctly (e.g., for each XX in array ....).

Another item that slowed me down was an inability to find textual descriptions of the various 'objects' that constitute the EA model. The names that appear e.g., Element.ElementID, are suggestive as to the interpretation to be made, but insufficient for an understanding.

Again thank you.

Automation Interface, Add-Ins and Tools / Visual Bacis Arrays In EA
« on: August 17, 2015, 08:23:22 am »
First, I know little about Visual Basic Script (VBS) (though I know much about other non-scripting languages). I've been trying to write a VB Script to make the 'Realization' connector appear transitive across 'connected' requirements. My approach has required the use of arrays to keep track of a) a requirement's connectors that are 'Realization's and b) the elements a 'Realization' connector is connected to (i.e., client).

I've looked online and tried many many variations but none seem to work in/with EA.

Can anyone provide some guidance on how to handle arrays with VBS in EA?

Pages: [1]