Messages

1

General Board / Re: From UML to SysML for Systems Architecture

« on: May 03, 2018, 07:30:23 am »

I mean there must be SysML for some reason (?) and as you pointed out the tooling is a SysML profile in a UML tool (like EA;). But what I actually want to avoid is a mixture of SysML/UML elements in one view resp. diagram (hard to achieve since SysML is an offspring of UML). There are some differences between a SysML::Block and UML::Class/UML::Component, SysML::Act and UML::Act (at least to my knowledge), in addition there are some SysML constructs like flow properties that are non existent in base UML. Since the Software Architecture is already done in UML, elaborating the System Architecture in UML would be the convenient way. But is it the better option in the long run? Unfortunately SysML 2.0 will take some time until release and can not taken into account for comparison.

2

General Board / From UML to SysML for Systems Architecture

« on: May 03, 2018, 05:25:24 am »

Hello all,

for my thesis I am about to model a System Architecture for a software intensive product with several views (requirements, use-cases, functional, technical, ...) and variants / deployments. What would be the better choice, UML or SysML?
Due to the fact that I need to place the same block/class/component several times onto the one technical and deployment diagram, what suits better in the long run considering a system architecture for a software intensive product. I am aware of such things as classes-instances-objects and so on (OOP is well known).

According to literature, UML is supposed to have some drawbacks when using it as system architecture language.

Thanks

3

Automation Interface, Add-Ins and Tools / Generating several toolbox profiles from one EA file with shared stereotypes.

« on: April 18, 2018, 09:57:21 pm »

Hello all,

I have a profile file containing several toolbox profiles (each with an own diagram). The toolboxes share identical stereotypes and they will be used in the same model. When applying the toolbox elements in the actual model, do I encounter any issues in the long run? (since I have applied identical elements from different toolboxes in the same model)

Thanks

4

Automation Interface, Add-Ins and Tools / Re: How to update/ synchronize applied stereotypes?

« on: April 18, 2018, 01:34:06 am »

A change to a stereotype is not trivial and should only be made after well thinking about it, never on the fly.

This.

Now, someone who is somewhat familiar with EA might be forgiven for thinking that a stereotype's name is not its identity, since that's how most of EA works, but with stereotypes the (fully-qualified) name is in fact the identity. So you can't change it, what you're doing is deleting one stereotype and creating another. EA has no record of the change, and in fact no concept of a stereotype name change.

/Uffe

Thanks for your feedback. So there is no stereotype specific GUID available to start from.. and the only chance is to use a script that runs by the name as identifier? Is there a UML tool on the market that supports to some extend such a stereotype updating mechanism?

5

Automation Interface, Add-Ins and Tools / Re: How to update/ synchronize applied stereotypes?

« on: April 17, 2018, 09:24:24 pm »

Well, if I use synch stereotype nothing happens apart from the tagged values. But I want to update the existing applied stereotypes in total, eg. <<name_old>> --> <<name_new>>, old color --> new color and so on. Any idea?

r2

6

Automation Interface, Add-Ins and Tools / How to update/ synchronize applied stereotypes?

« on: April 17, 2018, 07:31:16 pm »

Hi,

I have an EA profile and a toolbox with several stereotypes which I applied in the model. Now I updated the name, color and properties of the stereotypes in my profile, saved the toolbox and re-imported the updated MDG technology XMI file into the model. How do I update the existing elements in the model automatically? Is there a chance without a script? I assume since I changed the name of the (same) stereotype, there is no mapping between the elements.

Thanks