Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Feedbacks about architecture framework

Hi Patrick,

The implementation of the new Architecture framework is globally nice and pleasant from a technical point of view.
We have implemented in few days our own architecture description language similarly to what it has been done for Papyrus editors. Thus, we have a better granularity to fully control which diagram can be created in a certain context. We can also propose just a subset of all the available diagram editors or propose a view point with a lightened palette. 
It suits totally our needs.....but this setup (in our specific context) has required to own a 'Papyrus Black Belt'. Simply because many frameworks are involved in this tool chain (at least three) and require to be familiar with all these concepts and to well understand how they interact between them.

A remark not directly related to the architecture framework itself (already formulated by Ansgar): when defining a new palette item, it would be nice to consider by default the icon path of the element type definition (if defined). Of course, it should be possible to redefine this path in the palette item configuration is needed. But by default, the element type icon path should be considered as reference and so, used at runtime in priority. 


Sébastien GABEL
SCADE Architect - R&D Engineer
ANSYS Systems Business Unit
+33 5 67 20 48 03
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. 

2017-10-12 16:00 GMT+02:00 ZEITOUN Xavier <Xavier.ZEITOUN@xxxxxx>:

Hi all,


In addition to previous feedback I’d like the architecture model editor to have:

·        tooltips on fields that explain what the fields is needed to

·        when the field is a reference (example : elementtype set) : to have a reference editor that allows reference to workspace resources






De : [] De la part de LORENZO Vincent
Envoyé : jeudi 12 octobre 2017 15:14
À : Papyrus Project list <>
Objet : [PROVENANCE INTERNET] Re: [] Feedbacks about architecture framework


Hi Patrick,

   Développing the matrix framework, I fill these 2 bugs on AF :

516586: [AFViewpoints][Matrix] Architecture Framework should provide more informations


517986: [SysML 1.1][SysML 1.4][UML][AFViewpoints] declared architecture model should use a common pattern for naming


The last one is maybe fixed now.




Vincent Lorenzo


De : [] De la part de TESSIER Patrick
Envoyé : jeudi 12 octobre 2017 13:43
À : Papyrus Project list <>
Objet : [PROVENANCE INTERNET] [] Feedbacks about architecture framework


Hi all committers and advanced users of papyrus,


For the oxygen version, the architecture framework has been developed and used.

I would like to know your feedbacks about this framework, to include , if needed,  improvements in the road map of photon.


You can write that it is nice, why, we appreciate this kind of remarks.

You can also write remarks about:

-        Needs improvements about developer points of view:

o   Configuration about .architecture

o   How to define something that you have difficulties to do.

o   Maybe problems of performance that you have detected.

-        Needs improvements about user points of view:

o   Menus

o   Some behaviors that you have not understand…

Responses need to be clearly and precise in order to be managed.


Patrick Tessier

_______________________________________________ mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top