| Re: [mdt-papyrus.dev] Papyrus Communication |
Sebastien & Marc-Florian, Thank-you for all this great feedback. I have some homework to do now and will follow up on your suggestions under this thread. A little more background on our Papyrus use. We are currently using version 0.8 but are about to upgrade to the latest release. We have 5 people currently using the same model, and need to expand to a larger group. We have extended Papyrus with an internal eclipse plug-in that we call the Scenario Animator. It is hoped to go open-source with this at some level of maturity. This plug-in allows us to generate automated scenarios from activity diagrams. We have six levels of testing with the generated scenarios: Level 1: We trace requirements to the scenarios and run the scenarios stepping through the activity diagrams for projects to show how the scenario satisfies the set of requirements, we also have some basic coverage statistics to see how well we have covered the path possibilities. Level 2: We add state machines for various components involved in the scenario. States are tied to actions. When these scenarios are run any attached state machines are also stepped through, flagging any invalid state changes. Level 3: We add transition triggers to the state machines. The scenarios are modified to fire the triggering events, which are now used to drive the state machines. Level 4: We add mock objects, which are basically interface stubs. The interface calls are tied to the scenarios and the test results logged. Level 5: We add software classes and tie them to the interfaces. At this point the scenarios are now used as test cases for the code implementation. Level 6: We then add test equipment (hardware) to the software to test hardware. We’ve had two hiccups working with the papyrus tool, that we have workarounds for. It is possible we are just not using it properly, we are hoping some of this will improve with the upgrade. 1. If you open a diagram with the right-click Open option from the pop-up menu, the entire project becomes corrupted and will not display when the project is reopened. 2. We currently collaborate by: a. having one person responsible for the master model. b. Team members work on a subset of diagrams in a different model c. Model data is imported into the master project. i. We have not been able to import the actual diagrams, we manually recreate them from the imported data. ii. We also loose links to comments, those are established once the project has been imported. iii. We are mostly working with activity diagrams and state machines. iv. Currently the keeper of the master model is responsible for class diagrams. v. We are just starting to look at sequence diagrams. Hopefully this gives you a better idea of what we are doing, and where we are at. From: mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] On Behalf Of GERARD Sebastien 166342 Oh yes, I forgot ModelBus, sorry Marc-Florian. BTW, Marc-Florian, could update me on the availability of ModelBus within Papyrus: which version of Papyrus are considered and so on? ------------------------------------------------------------------------------------------------------------------------------------------------ Sébastien Gérard +33 (0)1 69 08 58 24 / +33(0)6 88 20 00 47 CEA Saclay Nano-INNOV Institut CARNOT CEA LIST DILS/Laboratoire d’Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE), Point Courrier n°174 91 191 Gif sur Yvette CEDEX De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Wendland, Marc-Florian Hi Sebastien, Have you ever considered to incorporate the already quite good capabilities of ModelBus? Have a look at : http://www.youtube.com/watch?v=mvdB_asmi1E&feature=context-cha Regards, Marc-Florian Von: mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] Im Auftrag von GERARD Sebastien 166342 Hi, Ok, it seems interesting. Feel free to ask your question on this mailing list which is dedicated to Papyrus designers. About team working, there are today two possible tracks: 1 – The control mode of Papyrus. On that subject, Tristan from ATOS can better answer to your technical questions. 2 – usage of CDO. We are currently investigating its integration within Papyrus but is not yet done. Other suggestions are welcome, and contributions to this subject are also welcome. Best… Sébastien. Ps: Are you in contact with Nicolas Rouquette from Nasa JPL? ------------------------------------------------------------------------------------------------------------------------------------------------ Sébastien Gérard +33 (0)1 69 08 58 24 / +33(0)6 88 20 00 47 CEA Saclay Nano-INNOV Institut CARNOT CEA LIST DILS/Laboratoire d’Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE), Point Courrier n°174 91 191 Gif sur Yvette CEDEX De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Donald E. Kranz Sebastien, Thank you for the quick reply. We are using Papyrus to provide an open source approach to IV&V model based work. As a member of the NASA IV&V team I would like to become more involved with the Papyrus project. We are specifically interested in advancing the ability to have teams work on complex models in Papyrus. I thought I could start by trying to understand the current state of activity, and what features are actively being worked by the group. Donald Kranz, TCSE, CCM System Engineer NASA IV&V Program o 681 753 5259 c 315 254 8418
100 University Drive, Fairmont, WV 26554 What are your questions? De : Donald E. Kranz I joined this mailing list one week ago. Haven’t seen any activity. Is there a better means of interacting with the papyrus team? Thanks, Donald Kranz, TCSE, CCM System Engineer NASA IV&V Program o 681 753 5259 c 315 254 8418
100 University Drive, Fairmont, WV 26554 |
