Title: Raphaël FAUDOU
Hi Daniel,

In TOPCASED, to migrate an existing UML model into a SysML model there is not yet an automatic transformation (but there is current work on such a transformation).
For now, you can do it manually with the following steps:
1/ rename file extension. Say XXX.uml and XXX.umldi => you should get XXX.sysml and XXX.sysmldi.
2/ open XXX.sysml as text file and add namespace support for SysML metamodel in the first line : " xmlns:sysML="http://www.topcased.org/2.0/sysML".
Check if you can open the XXX.sysml with the treeview SysML editor. It should work and you should be able to see you statecharts elements.
3/ open XXX.sysmldi as texte file and search for occurences of "href="" to replace them by "href=""mid:[EMAIL PROTECTED]" type="cite">
Hi,

In basic way, I want to copy state machines (and other behaviour
diagrams) of a UML project into my SysML project.

The need for the migration is because the UML does not have requirement
model diagram.

My project has to objective to check existence of (RAMS) requirements in
a project.

So the project is defined in SysML, to define the requirement model.

The big problem, is that most projects do not use SysML, but they do use
UML.

So, I want to migrate the behaviour diagrams from UML to SysML.

This is why I say, I want to copy state machines (and other behaviour
diagrams) of a UML project into my SysML project.

As a first step I am only thinking in state machines.

You may ask, how will I check the existence the requirements through the
state machines.

Well, in the SysML Requirement Model, for each requirement, I have
defined a state machine that simulates the behaviour of the requirement.

These SysML state machines are triggered by a set of stimulus.

With the imported state machines from another project, I would trigger
(simulate) them with the same stimulus. If the state machine is
successful with a set of stimulus, it is a proof of the requirement
existence.

There is yet a grey area on this matter, when there UML state machines
that contain similar/unknown stimulus. 
But I am hoping to solve this through a "prompt and replace" technique,
when a unknown stimulus is found the user shall decide if it is  unknown
of if it can be considered an existing stimulus already defined in the
SysML project.

Please, if you thing my idea is impossible or far fetched, say so! I am
still on the drawing board, and this is the best solution I found model
wise.

Also if you still don't understand, please make more questions. 
When you are questioning me,  you are also helping me in defining better
my solution.


Thank you,

Daniel

  
-----Original Message-----
From: Benoit MAGGI [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 02, 2008 4:09 PM
To: Daniel Silveira
Cc: [email protected]; TOPCASED-ATOS
Subject: Re: [Topcased-users] Migrate the UML state diagrams to SysML


I misunderstand what you want to do.

What do you have in entry of your migration? An "Topcased UML
    
project"?
  
Or something else?

What do you intend to do a model migration? Or a diagram migration?

For the moment there is no specific tool for that! But the sysml model
is inherited from the uml metamodel, so you may have a compatibility.

Regards
Benoit AMGGI
    

  

_______________________________________________ Topcased-users mailing list [email protected] http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users

--

Image Signature IOC Raphaël FAUDOU
Responsable cellule Innovation / bureau méthodes
Head of Innovation & Method Definition
Atos Origin Midi Pyrénnées

Tel     : +33 (0)5 61 39 75 35
Tel     : +33 (0)6 10 53 50 44
Mail   : [EMAIL PROTECTED]
Immeuble AEROPOLE 4 5 avenue Albert DURAND - 31700 BLAGNAC

P Avant d'imprimer cet e-mail, pensez à l'environnement. Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
P Please consider your environmental responsibility before printing this e-mail. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users

Reply via email to