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.

Topics - t_s

Pages: [1]
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 / 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 / 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 / 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]