Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Menus for creation of Diagrams UML/SysML and Table

See below.

 

seb

 

------------------------------------------------------------------------------------------------------------------------------------------------

Sébasten Gérard

CEA LIST, Laboratoire d’Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE),
Point Courrier 94, Gif-sur-Yvette, F-91191 France

PapyrusLogo_SmallFormat www.eclipse.org/papyrus

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de FAUDOU Raphael
Envoyé : jeudi 22 septembre 2011 15:31
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Menus for creation of Diagrams UML/SysML and Table

 

Hi Vincent,

 

I do not see why we should have to mention the language as it is redundant information. In current model, the tool knows if the selected element belongs to a UML package or a SysML one and depending of this data it has to provide appropriate diagrams.

[SG>] To determine which diagrams are possible on a given element is not really in the language definition, but rather in the definition of the usage of the language. The idea in this gathering is to have a simple way to be able to use only SysML diagram when SysML is applied and UML diagrams in other case. I am not sure to see why it is a pb for you Raphael to have this distinction?

Tomorrow I want to apply a space profile on some package of my model and want the tool to propose only space diagrams for this package.

 

OK to consider tables as diagrams and put them in the same menu, eventually with a separator.

Regards

raphaël

 

Raphaël Faudou

Atos

+33 534 363 289

+33 610 535 044

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de LORENZO Vincent
Envoyé : jeudi 22 septembre 2011 15:19
À : Papyrus Project list
Objet : [mdt-papyrus.dev] Menus for creation of Diagrams UML/SysML and Table

 

Hi all,

  I’m thinking about the organisation of the menu for the Diagram/Table creation. Currently we group the creation commands by type of editors : we have a menu for the Diagram and another one for the table. I think it would be interesting to change this organization to group these editors following their languages like in the « New Papyrus Model Wizard ».

So I propose to change the current menus in order to get :

                               - UML Editors

                                               - ClassDiagram

                                               - Activity Diagram, …

                                               -----------------------

                                               - Default Table

                               - SysML Editors

                                               - BDD

                                               - IDB;...

                                               ------------------------

                                               - Requirement Table

                                               - Allocation Table

 

 

What is your opinion about these changes ?

 

--

Vincent Lorenzo

01-69-08-17-24

CEA Saclay DRT/LIST/DILS/LISE

91191 Gif/Yvette CEDEX


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.


Back to the top