I have experienced the same frustration with IBM Rational Rhapsody. It seems logical that placing an activity in a swimlane that represents a block would do an implicit allocation of that activity to that block, but Rhapsody does not. I've used Artisan Studio, but don't remember If it has the same weakness.
Jim Smith
Good morning everybody,
--
You received this message because you are subscribed to the Google Groups "SysML Forum" group.
Public website: http://www.SysMLforum.com To post to this group, send email to sysml...@googlegroups.com To unsubscribe from this group, send email to
sysmlforum+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sysmlforum?hl=en_US?hl=en
In MagicDraw actions dropped/created in a swimlane which represents a
block/part are automatically
allocated to that block/part, i.e. the allocate relationship is created.
Regards,
Robert
Generally activity diagram is used to represent behaviour while blocks represent structure. Those are orthogonal concepts so you do not have a mapping 1:1 between activity swimlanes and blocks. You have often different activities that contain swimlanes allocated to the same blocks. So the rule "create one block for each swimlane" will create too many blocks to my opinion. You need something more flexible with possibility to reuse an existing block.
My two cents
raphaël
-----Message d'origine-----
De : sysml...@googlegroups.com [mailto:sysml...@googlegroups.com] De la part de TheSadPhilosopher
Envoyé : mercredi 25 avril 2012 06:20
À : SysML Forum
Objet : Re: EXTERNAL: [SysML Forum] Generating BDD from swim lanes in an activity diagram
Hi all,
--
You received this message because you are subscribed to the Google Groups "SysML Forum" group.
Public website: http://www.SysMLforum.com To post to this group, send email to sysml...@googlegroups.com To unsubscribe from this group, send email to
sysmlforum+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sysmlforum?hl=en_US?hl=en
________________________________
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 ne pourra être engagé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 engagée pour tout dommage résultant d'un virus transmis.
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 group liability cannot be triggered for the message content. Although the sender endeavors 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.