If you want understand the EA layer architecture

[Roman Bretz]

Important for everybody who needs to extend EA by new functionality.

The picture shall provide roughly overview of Enterprise Architect layer architecture.  Most important message: The EA itself is built of building blocks and it can be flexibly extended more or less in the same way (like AMUSE it does). The only difference between self made MDG Technologies / Add-Ins and EA original functionality – there are some APIs reserved for EA internal usage.

MDG technologies shall be used for extension of already available technologies like UML or SysML by providing new tool boxes, stereotypes, tagged values etc.

Add-Ins shall be used for providing completely new functionality like new UIs, diagram types, reports, supporting of user workflows etc.

[MagnusOfSweden]

It does kind of support my understanding so far, that if you want to have a nicer interface to add element data (into instances), you have to provide it as an Add-In.

Is there a good example of how you change the standard "Properties" window of an element and replaces it with a "more modern/tailor-made" visual form, why not a traditional VB-form with tabs, lists etc.

I want to hide all "unnecessary information" and I want to improve the input style of "Tagged Values". I like to place the Tagged Values in a nice form to make it easier and faster to add data to a 'meta-model'.

Thanks in advance  -Magnus

[Robert.Zhang]

the version9.x or later version is the same as this?

[qwerty]

the version9.x or later version is the same as this?

More or less this is EA's architecture from the beginning.

q.

[qwerty]

Is there a good example of how you change the standard "Properties" window of an element and replaces it with a "more modern/tailor-made" visual form, why not a traditional VB-form with tabs, lists etc.

You simply can't do that with EA. Except you write your complete own GUI. But the default properties window can't be manipulated.

q.

[MagnusOfSweden]

Thanks for your clear answer. Do you think this would be appreciated as a new Feature to propose?

As I see it, if you want to work in "the new age" where people collaborate and EA is very important to the business. Then you simply have several stakeholder, of which most of them are NOT technical, but all still very important for fullfilling the task.

In such an environment, this feature would be highly valueable and would increase speed, data quality and user perception.

Also, while I'm at it...I think Sparx should have the same approach of "multi-stakeholder view" when it comes to the topic of 'Generating Reports'. It is way too much model structure and way too little focus on Business and Stakeholder needs.

To become the truely greatest EA tool, I think these 2 aspects should be addressed.

-Magnus

[qwerty]

This has been requested as feature not only once. You might search for it (good luck with that) and give it extra support or simply send it as a registered user feature request to Sparx. But don't put too much hope in it. The floating diagram window took more than 4 years from request to implementation.

q.

[Roman Bretz]

Thanks for your question

No doubts - there are some highly important features could / should be implemented. But much more important: EA is a very affordable stable, fast, easy-to-handle and over years backward compatible visual modeling platform. If one of these criteria get overturned - it could be the end of the success story - as simple as that   The other point - Sparx Systems has only two dozen developers and it is good so. Thus I  well understand the reasons why some features take time.

However - the message is: EA is a platform. By the way, as far as I know it's possible to suppress the standard property dialog and replace it by your own. But i wouldn't recommend to go that way. Better you implement your own docked add-in window (look for Repository Class in the EA help especially for AddWindow method) and visualize there the properties in the way you or you customers need.

The only issue (depends on your needs) could be the EA data model. It's bit different to UML meta model, e.g. there is no basis class for all types of model elements. It will take time to learn it. That's why we build our own access layer over the EA interface. It makes the learning curve dramatically shorter. Currently it's reserved for internal use only, but we are discussing about alternatives. If you need more details, pls let me know.

[MagnusOfSweden]

Great feedback,

I will take a look at the repository class and see if that would be a nice way around it.

I've just  started using EA (before I used Sybase PowerDesigner) and as you say, one of the main features is the price  ...and we don't want to ruin that, do we.  -Magnus