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

Pages: 1 ... 3 4 [5] 6 7 ... 36
Suggestions and Requests / Re: ArchiMate Derived Relationships
« on: September 25, 2015, 05:49:36 pm »
This has been implemented in the latest version of BEASI


An indicator on my wish list is in the Project Browser and / or in the Package Browser

is if at least one Baseline exists on a Package then show on the Package Icon

Just a thought


Suggestions and Requests / Re: Need better ER Diagram notation
« on: November 22, 2014, 10:38:09 am »
The Crows Feet notation is supported in EA

Model your Logical Data model using UML class diagram and then double-click the diagram to bring up the Diagram Properties dialog

Select the Connectors tab

Change the Connector Notation from UML to Information Engineering

You should now see the Crows Feet notation

Of course this only works for UML Association connectors



Suggestions and Requests / SysML 1.3 Activity Diagrams
« on: November 20, 2014, 09:26:39 pm »
Support for SysML 1.3 has imported significantly over the versions. We now have much closer alignment with the OMG Spec, particularly in the area of Blocks / Ports and Block / Requirement Compartments.

However one area is still lagging behind, namely Activity Diagrams

Apart from some stereotypes it is pretty much the same as UML

With version 12 upcoming may I request the following enhancements

1) Dashed lines for Control Flow (as per OMG SysML 1.3 spec)
2) Support for Parameter Sets
3) Stereotypes visible for Activity Parameters and Action Pins (for example <<optional>>
4) Alternate format for Interrupt Flow, that is as a "normal" Control / Object Flow, but with a small "lightning bolt" floating (like a label) near its middle
5) Re-sizeable Activity Parameters so that the name can be placed inside the Parameter symbol

Many thanks for your consideration

Have a look at Working Sets

This provides what you need


Suggestions and Requests / Re: All I want for a Sparxly Christmas 2014
« on: December 16, 2013, 11:19:57 pm »
My #1 feature request

Ability to select more than connector and change the properties (line style) for all connectors in that selection

What licence edition of EA are you using? If you have the Business Engineering (or Ultimate) edition, then Business Rule Modelling is already there.

It may not be a perfect match for what you are describing, but as far as I recall it is decision table based and links activity flows with business rules requirements. It has been a while since I last looked at it, but section 8.3.3 in the PDF EA User Guide has a great deal of information in this.

This feature is not available in the corporate edition



Suggestions and Requests / Re: Othogonal Default Line Style
« on: March 27, 2012, 12:04:06 am »
Follow up to last post, the diagram settings issue mentioned seems to be fixed in version 9.3  :)

Suggestions and Requests / Re: Othogonal Default Line Style
« on: March 27, 2012, 12:01:03 am »
Thanks Geert, just tried that, but alas it doesn't work.

It appears that Template Packages only save the first tab settings of the diagram properties, rather than all the settings on all the tabs.

I wanted to create a template of a UML class diagram with the namespace, and visibility indicators turned off. It works for the namespace, but not for the visibility indicators. But we are veering off topic here



Suggestions and Requests / Othogonal Default Line Style
« on: March 26, 2012, 10:11:07 pm »
Hi All

Anyone else out there just HATE the way that connectors default to Orthogonal Rounded in some MDGS? BPMN 2.0 and Archimate 2.0 spring to mind  >:(

These connectors are extremely frustrating and seem to have a mind of their own. I spend a lot of time making the connector appear as I want, save the diagram, then only to find that when I move some elements the connectors are all messed up again!  >:(  >:(

[highlight]PLEASE, PLEASE in the next release revert the line style default to Custom so we can have control.[/highlight]

Yes I can change the line style after adding the connector, but until such time as to when we can select multiple connectors and change the line style on a selection, the choice of Orthogonal as the default is causing much unnecessary work.

Here's hoping



Suggestions and Requests / Re: SysML Compartment notation
« on: February 07, 2012, 06:09:14 am »
Agree add my support to the hiding of SysML Block compartments.

I believe the ports / parts / values compartments only show up when using SysML 1.2 MDG.

If you want to use EA 9.2 you can use SysML 1.1 and then when the compartment hiding is implemented, upgrade the SysML 1.1 models to SysML 1.2 using the Sparx supplied script

That's what I am doing at present, not ideal, but OK for me for now.



Suggestions and Requests / Workflow Scripts
« on: February 16, 2012, 02:40:10 am »
Hi All

Am I the only user of EA who finds the Workflow scripts feature in EA, rather disappointing and somewhat misleading?

In my opinion (unless I have missed something), these scripts do not implement workflow at all, rather they allow the checking of access / edit  to Phase, Status, Tag, Version fields ONLY.

Personally (apart from tags) I find these properties little used.

What I was expecting and indeed what I would like to see, is a means to provide total read only access to individual elements (including diagrams and packages), thereby providing a workflow capability. For example, a repository could be populated with a structure using an MDG, and until a certain section was completed and signed off, the remainder of the structure would be read only.

I realise that this effect can be achieved using version control (in particular TFS), but it would be really great if the Workflow scripts lived up to their name.

But what do you think?

Suggestions and Requests / Re: Producing Report of Trace between attributes
« on: November 10, 2011, 08:39:33 pm »

A report on linked features is possible using the RTF generator in version 9.1.910

Below is a simple RTF template to illustrate this

[highlight]package >[/highlight]{Pkg.Name}
[highlight]diagram >[/highlight]
[highlight]< diagram[/highlight]
[highlight]element >[/highlight]

[highlight]connector >
source >
linked feature >[/highlight]
[highlight]< linked feature[/highlight]

Links to :

[highlight]< source
target >
linked feature >[/highlight]
[highlight]< linked feature
< target

< connector[/highlight]
[highlight]child elements >
< child elements
< element

child packages >
< child packages
< package[/highlight]



Suggestions and Requests / Re: Sequence Diagram
« on: October 06, 2011, 07:40:11 pm »
Geert is right.

EA follows the OMG UML specification and try...catch combined fragments are not defined ... although some UML tools support them. Also remember that UML is intended to be independent of any development language

Just my opinion, but your example shown above is Java code in pictures, even down to the get set methods! If you are using sequence disgrams at this code level, you might as well right the code directly.

I feel sequence diagrams should be used as a blueprint to coding, modelling the interaction at an algorithmic level of abstraction, this is as the EA example you posted. The sequence diagram can then be used to drive the coding process.

At this level of abstraction, EA does a pretty code job of sequence diagrams.

Just my opinion



Suggestions and Requests / Re: BPMN Task Type Icon
« on: October 29, 2010, 08:44:46 pm »
I would support this suggestion



Pages: 1 ... 3 4 [5] 6 7 ... 36