Migrate UML to SysML?

[wstidolph]

I have an (incomplete) UML model with a few hundred Requirements, some use cases, some classes, some components etc. The product is a system-of-systems (generate specs to multiple hardware/software vendors, assemble, test) and I'm running into the need specify a lot of hardware aspects, so I'm thinking this is a good time to migrate to SysML ...

Mainly I need to convert the Requirements into SysML Requirements, - everything else is straightforward or incomplete enough to do over manually if need be. I'd like the Requirements to be specifically "SysML 1.3 Requirements" so the Quick Linker offers me the right type of relationships.

But I can't see how to do that migration

I've tried the obvious (to me) things:
1) taking my copying UML requirements to the clipboard and pasting them into my SysML model requirements package
2) copying into the SysML package then exporting/reimport them through Excel using eaDocX so I could added id and text tagged values (should I have removed the GUID or something?)
3) changing the element type in Excel from Requirement to extendedRequirement

Is there a migration script or something?

[Helmut Ortmann]

Hi,

you may make it manually by just dragging the SysML Requirement on your Requirements and chose apply (EA 10.06, 9 I don't know if it's work).

You can write a little script to change the stereotype of your old requirements to <<requirement>>. If the scripts works like the dialog the tagged values are updated but the shape of the requirement isn't updated.

Maybe there is someone else who has tried it


Kind regards,

Helmut

[qwerty]

Works also in 9.3 (and probably former versions).

In order to apply the tags for stereotypes run Repository.SynchProfile after adding the single stereotypes.

q.

[Sunshine]

If scripting or manual options don't work for you can export into CSV with stereotype field then in a spreadsheet paste in the SysML stereotype and import into another package. The minimum fields are probably GUID, name, alias, stereotype, notes. Import with strip guids to create new instances. Once you have the right result you can delete to old UML requirements. Then do a sync profile as mentioned by qwerty. You can do this by opening the tool box and right clicking on the sysml requirement type and selecting "synchronise stereotype"
TIP: Create a SysML requirement first and export it to CSV so you know what values to provide and use that as an example for updating the UML requirements.

This option seems to work for some Business Analysts I know who can't write scripts and don't like doing lots of tedious manual work.

Alternatively if you have an EAP file open in MS Access and open the t_objects table. filter on requirement and paste in the sysML requirement into the stereotype.

Hope that helps
 

[qwerty]

Note that when creating new instances (using Strip GUID) you will loose existing references and you have to re-connect manually.

q.