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

Pages: 1 [2] 3 4 ... 7
Suggestions and Requests / Requirement stereotypes
« on: October 03, 2006, 11:03:37 am »

I have a profile that defines the same requirement stereotypes as the EA SysML package (I like my graphic symbols better, so I use them instead of the add-in elements). When adding a new element in the Project view, the "Stereotype" combo box lists all of the profile-defined values; however, when using the Property dialog, only the stereotypes defined in the database table t_requiretypes are listed. Behavior ought to be consistent (and should include the profile stereotypes in both contexts).


Suggestions and Requests / Profiles, case sensitivity, and stereotypes
« on: October 03, 2006, 09:12:55 am »

I encountered an odd glitch when doing direct database manipulation of stereotypes in an EAP file. I changed the stereotype field for custom Requirement elements from 'Requirement' to 'requirement' to match the SysML usage. The update was successful. I then revised the corresponding profile, renaming the 'Requirement' stereoype element (extending the existing 'Requirement' metaclass) to 'requirement'. Profile created & imported successfully. I then took a look at the diagrams containing the elements, and their images had reverted to the native shape for the 'Requirement' element. I then checked the element properties in EA and saw that the stereotype was still 'Requirement' (capital 'R') even though direct examination of the database (EAP file) showed the stereotype as 'requirement' (lower-case 'r'). It required a manual edit of the sterotype field from 'Requirement' to 'requirement' to get the image to change to the associated stereotype ShapeScript image defined in the profile.

This points to a problem somewhere with case sensitivity, it appears.


Suggestions and Requests / Run-by connector
« on: September 16, 2006, 07:41:21 am »

Some diagramming programs have a feature that I will call a "run-by" connector, where a number of blocks in a row can be connected to another block (or to each other) with a single connector placement. Such a feature would be very useful in structural diagrams where tree-style connectors link many blocks to one (e.g. generalization, nesting).

I run across this often in Requirements diagrams, where it's often necessary to link many sub-requirements to a higher level requirement. Having a "run-by" option would be a big time-saver.


Suggestions and Requests / Nesting link ignores tree style default
« on: September 16, 2006, 12:23:15 pm »
Or so it seems...

With the default link style set in Options->Links to "Tree(H)", Nesting links are drawn with "Custom" style and must be set manually to Tree style. I'm running EA 6.5.797.


Suggestions and Requests / Design Master Crashes EA
« on: September 16, 2006, 01:52:39 pm »
If EA doesn't have exclusive access to the EAP file (e.g., if the EAP file is also open in Access or Microsoft Query) and an attempt is made to make the EAP file a Design Master, EA displays an "Operation Failed" error dialog (that's all the info it gives) followed by an inescapable loop where the user is repeatedly prompted to select a DSN. Once the other applicationis closed, it works fine.


Suggestions and Requests / Sorting in Project View and Relationship Matrix
« on: September 16, 2006, 11:28:06 am »

Another "nice to have" is the ability to sort axes in the relationship matrix and elements in the Project view by properties other than the element name. Sorting by "Alias," for example, is another option that would be very useful (to me at least!). In requirements diagrams, I use the Name as the short description for the requirement (full text is in the Notes field) and the Alias as the unique requirement ID. In some cases the ID is mapped one-to-one to the requirements hierarchy, and organizing diagrams after CSV import would be considerably simpler if the requirements were listed in hierarchical order (albeit without parent-child relationships).


Suggestions and Requests / Additional Profile Woes
« on: August 29, 2006, 02:35:34 pm »

Note that these comments relate to EA 6.5 Beta 2:

1. Stereotypes based (both redefinitions and extensions) on the the "Send" and "Receive" metaclasses refuse to pay attention to the Shape Script attached via the (undocumented, I think) "_image" tag. Dropping these items, either from the toolbox or the Resource tab, results in the standard shape, not the one defined by the Shape Script.
2. Stereotypes based on the "Event" metaclass do, however, obey the Shape Script. Unfortunately, the image rectangle that results is twice the height of the actual image, so connectors stop in "mid-air", as it were.
3. "Send" and "Receive" events are differentiated by different Subtype values. Is there any way to access this value in a profile definition? Otherwise, stereotypes elements based on "Event" come in as "Send" events (Subtype = 0) by default; also, the profile image can't change based on this value since "HasTag" has no Subtype tag to check against.


Suggestions and Requests / Shape Script Manual
« on: August 21, 2006, 12:30:06 pm »

The EA User Manual has sketchy info, at best, on the Shape Script language. Do Sparx plan on issuing a comprehensive manual detailing all commands, etc?


Suggestions and Requests / Parent/Child Relationships in Diagrams
« on: August 16, 2006, 04:02:37 pm »
Hello All,

This is an extension of an earlier post on the Automation Interface forum...

EA 6.1 and 6.5 beta 1 do not appear to handle parent-child relationships between elements and regions in Activity diarams consistently. In some cases, elements placed within a region appear below the region in the Project Browser as children (and a check of the database agrees); in other cases the elements do not show up as region children but can be dragged under the region; and in still other cases (e.g. Merge nodes, Decisions, and ExpansionRegions) EA refuses to allow the elements to be dragged under region elements as children. The database can be hacked and the ParentID field can be modified directly; EA doesn't appear to have a problem with this since the element hierarchy changes accordingly once the project is reloaded.

I'm speculating that this is a legacy feature dating back to the days before everything in UML, just about, became viewed as a "classifier".


Suggestions and Requests / Stereotypes & Relationship Matrix
« on: November 09, 2005, 08:23:43 am »

When adding stereotyped relationships in the Relationship matrix (e.g., <<trace>>, <<realize>>), the relationship type is added correctly but without the stereotype. For example, a <<realize>> link is represented correctly (dashed line with solid arrowhead), but the stereotype doesn't appear on the diagram. When the connector's property dialog is opened, the stereotype is--no surprise--blank! I doubt this behavior is intentional.

Fred Woolsey

Suggestions and Requests / More on RTF documents...
« on: August 04, 2005, 01:31:40 pm »
Anudder thing...

When printing an RTF document using the internal viewer, the page size seems to default to A4 regardless of the Print Setup & page size from Local Options.


Suggestions and Requests / Exponential Recursion in Hierarchy View
« on: August 04, 2005, 10:23:05 am »
I have a bunch of requirement elements (several hundred) in a model. The requirements are nested such that there are requirements that own other requirements that own other requirements...and so on, similar to the structure of a written specification. Given that the hierarchy view shows both "owns" and "owned by" links (recursion!), a fully expanded tree at greater depths results in an exponential explosion in the size of the tree, enough to cause EA to use about 100% of the CPU and > 200 Meg of memory (and climbing) before I shut it down (this happened at a depth of 10 for the subject model). I should add that this wasn't an academic exercise; I had set the depth to 10 without thinking, then tried to expand the tree.

I don't know off-hand how difficult it would be to implement or what the shortcomings might be, but might it not be a good idea to omit the "owned by" branch for all but the topmost node in the tree?

BTW--I'm using EA 5.0, build 768.


Suggestions and Requests / Using an alias with an attribute
« on: August 04, 2005, 03:39:35 pm »
When using an alias with an attribute (and I'm guessing an operation, but I havent tried it yet), the alias appears as a prefix in parentheses followed by two non-printing characters (I'm assuming they are CR-LF). I have the option to show both the name and the alias turned on. It seems that the alias here is following the pattern of the class name, where the alias appears on one line and the actual name on the next.

Not a huge problem, just ugly.


It appears that relationships defined in the Relationship Matrix don't get picked up by the "connector>" tags in the custom RTF template editor & generator unless the relationship is also shown on a diagram...



One thing that's missing from the EA code generation facility is the ability to re-link EA classes to source code files after changing either the name or the class or the name of the file in the source code editor app itself. You can go into the EAP file or database directly and manually correct this; I've done just that and it works but sure isn't convenient. This is particularly problematic when using MDG Link add-ins since they tie the IDE and EA representations together more tightly from a workflow perspective than simply generating code on the fly.

BTW-This shortcoming applies to EA's built-in code engineering, not just the MDG Link add-ins.

Fred Woolsey

Pages: 1 [2] 3 4 ... 7