Title: About evolution 1176
Dear Daniel,

Thank you very much for your feedback. We appreciate it much.
Please find some comments below.

Topcased user list where issues are discussed a écrit :

Dear all,

I really am pleased to use Topcased in my project.

I hope it is the good location to ask for improvement.

What I really miss and that is a trouble for me today in using Topcased on the Airbus project I work on is the following 1176 requirement (2423 seems to be the same demand)

 

1176    1       Open    4       174     10/07/2007      [Sequence diagram] Add a way to reference sub-sequence diagrams through a Combined Fragment    
 

        In addition to combined fragments, a very usefull UML2 feature in sequence diagrams is to provide a diagram reference (a link to another diagram).

 

2423    1       Open    3       3201    30/03/2009      Navigable Sequence Diagrams    
                                   

            I would like to add a Combined Fragment in a sequence diagram which links to a nested sequence diagram. I need to do it because I would like to have two different levels of details. I have embedded a sequence diagram into another one nesting Interaction nodes, but I have not found an easy way to jump into the nested sequence diagram from the parent one. I know it is possible to use the Outline browser, but, I think, it would be much easier if the user can use to context menu of the, for example, Interaction Operant, to jump into one of available nested diagrams.

Yes, this is clearly a hole in TOPCASED UML today. As you point out, there are many things that can be done in activity diagram and not in sequence diagram. In fact, almost all efforts have been put on the activity diagram as it was considered as a key diagram to design critical systems (the activity diagram can show all paths of a given UC which is quite difficult to achieve with sequence diagram). Concerning the sequence diagram, it has been developped by several partners and it lacks consistency.So the introduction of interaction operands is not a simple task as we must first do some refactoring to handle correctly the hierarchy of nodes in the outline (combined Fragments for instance).

So I really miss to be able to do with sequence diagram what we can do with activity diagram and associated call behaviour action. We could have a reference fragment with link to either:

-       Another interaction diagram or interaction node

-       Another activity diagram or activity node

-       Another use case with attached (interaction or activity nodes)

So I do not understand that priority of those requirements 1176 and 2423 is so low. Today I add a Note on a fragment to display something as a ref fragment

As a workaround, you can use the HTML documentation view and put diagram links. It will give the model reader the possibility to jump easily from one diagram to another (whatever target diagram kind).

I also have another requirement about navigation on a use case for activity diagram. On a use case, I can add several Interaction nodes or Activity nodes (with several diagrams inside each activity or interaction nodes). On the advanced property of the use case we can add behaviour by selecting one of the Interaction or activity nodes. Then with use case selection we are proposed by all the diagrams of the selected nodes. I would be interested to have instead all the diagrams of all the interaction or activity nodes attached to this use case and so to be able to select a behaviour with all interaction nodes or/and activity nodes I would like to have

You are perfectly right and this is a room of improvment that has already been identified.Your suggestion seems the good one. Could you please open a feature request for that?
Thanks
raphaël

Regards,

Daniel

The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
  

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

--
Raphaël FAUDOU

Image Signature IOC Raphaël FAUDOU
Responsable cellule Innovation / bureau méthodes
Head of Innovation & Method Definition
Embedded systems & critical systems
Atos Origin

Tel     : +33 (0)5 34 36 32 89
Tel     : +33 (0)6 10 53 50 44
Mail   : [email protected]
Atos Origin
6, Impasse Alice Guy
BP 43045
31024 Toulouse Cedex 3, France

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