Per the presentation and discussion on the Tuesday, April 24th Modeling Subcommittee meeting on this topic, following is a compromise that perhaps all could find acceptable.
The Proposal -
- Anyone can contribute during input and discussion phases via the WIKI
- A model editor will participate in the calls, capturing the evolving model details (classes, relationships, attributes, etc) in Papyrus.
- The model editor will share the Papyrus model via
- UML Diagrams posted to the WIKI
- Gendoc output (diagrams, tables, etc) as Marc outlined below
- If useful, the gendoc table can be copied and pasted directly into a WIKi page – seems to format well
This can be useful for direct viewing and commenting - When development of the model is finishing up, the Papyrus model is reviewed (via Word Doc publish) until ‘clean’ is achieved (agreement by Subteam)
- The Clean model (Papyrus Word Output) is socialized with modeling Subteam along with other sub-team’s work (reconciliation between parallel work), and approval by Subteam is reached.
- Papyrus Gendoc output (Word Format) is converted to RST format and provided to DOC team.
On other words, no one other than the model editor is required to use Papyrus, but anyone can (it is open source), yet we gain a better model via use of a modeling tool.
A quick updated to one of the diagrams shared on Tuesday's call -
A sample Papyrus diagram (a picture says a thousand words?)
Conclusion is that for the 'regular' participant, they can use the WIKI to share concepts, yet gain the benefits from use of a modeling tool and the resulting better model.
If interested, we can provide a short demo of Papyrus - create a couple classes, a few attributes, a definition, association between the classes with multiplicity, assign a profile value (input, discussion, clean), do a quick gendoc publish, share the diagram back to the WIKI as well as a class table back to the WIKI, etc.