Hello José, A brief answer to your topics below : first, you must have ADELE v2.5 if you have TPC 2.5 (included), so you should not try to install an older version with software update or dropins folder... Please check your plugins details to be sure ?
1- no reverse enginering into ADELE (and most of modelers, even in UML) 2- non valid properties may be linked with AADL v2, because AADL generate code is checked by OSATE core (AADL v1) 3- you can add the problem view into ADELE perspective, the designer-user has to know what he is doing ! Real-time properties of a system have to be set precisely. 4- for me, it's a real bug report linked with HMI part, 5- does a "call sequence" exist in AADL language standard ? does OSATE editor implement it ? 6- for me, it's a real feature request, 7- Flows are not supported by ADELE ? 8- Is it consistent to link different kind of port with a flow ? Regards, Sébastien HEIM --- [email protected] a écrit : Dear all, I have found potential issues by using ADELE over TOPCASED. I list them here in order to know if they are bugs, regular function of that tool, they are already exist as known bugs to be fixed in future releases, or even some kind of misunderstood from myself. I am using TPC 2.5.0, OSATE 1.5.7, ADELE 2.3.1, JRE 1.5.0_18 1.- If a model is modified manually (by editing the .aadl file), the ADELE graphical diagram does not present those modifications. 2.- WRT the properties, the model is always valid although the properties values are wrongly set. For example, writting 5ms for the "Compute_deadline" property produces an .aadl file with that non-valid string. 3.- If a property is wrongly set (its value) and an error appears when validating the model, it has to change the AADL view in the TOPCASED to know the exact error. Furthermore, the ADELE view does not present the possible values for each property. 4.- If a "Requires Bus Access" feature is removed graphically without removing its connections, it disappears from the diagram but it is still set when generating the AADL code. 5.- It is not possible to draw a "call sequence arrow". No symbol accesible. 6.- AADL "modes" are not supported by ADELE. 7.- "flows" are not generated in the AADL source code from an ADELE diagram. Only connections are generated. 8.- It is not possible to draw an inner flow between an event data port and a data port in ADELE graphical editor. Thanks in advance. Best regards, José -- José Manuel Puerta Peña Business Development Manager TCP Sistemas e Ingeniería - Aerospace Systems Division _______________________________________________ Topcased-users mailing list [email protected] http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
