Skip to main content
Jump to: navigation, search

Difference between revisions of "Papyrus"

(Events)
Line 12: Line 12:
 
** [[Papyrus/Migration Guide/Oxygen | Papyrus Oxygen (3.0) Migration Guide]]
 
** [[Papyrus/Migration Guide/Oxygen | Papyrus Oxygen (3.0) Migration Guide]]
 
** [[Papyrus/Migration Guide/Neon | Papyrus Neon (2.0) Migration Guide]] — [[Media:Papyrus_Neon_Migration_Guide.pdf|as printable PDF]]
 
** [[Papyrus/Migration Guide/Neon | Papyrus Neon (2.0) Migration Guide]] — [[Media:Papyrus_Neon_Migration_Guide.pdf|as printable PDF]]
* Papyrus4
+
 
** [[Papyrus for Sysml  | Papyrus4Sysml ]]
+
** [[Papyrus for Information Modeling  | Papyrus4Information Modeling ]]
+
** [[Papyrus for Education | Papyrus4Education]]
+
** [[Papyrus for Domain Modeling  | Papyrus4DomainModeling ]]
+
 
<!--* Miscellaneous
 
<!--* Miscellaneous
 
** [[General Architecture | General Architecture]]
 
** [[General Architecture | General Architecture]]
 
** [[Eclipse Papyrus FAQ|Eclipse Papyrus FAQ]]-->
 
** [[Eclipse Papyrus FAQ|Eclipse Papyrus FAQ]]-->
  
=Papyrus components=
+
=Papyrus Ecosystems=
  
* [https://www.eclipse.org/papyrus/components/components/ Components]
+
https://wiki.polarsys.org/Papyrus_IC/Product_Management
* [https://www.eclipse.org/papyrus/components/designer/ Designer]
+
 
* [https://www.eclipse.org/papyrus/components/robotml RobotML]
+
* Papyrus's vocabulary
* [https://www.eclipse.org/papyrus/components/sysml/ SysML]
+
** Papyrus Product
* [https://www.eclipse.org/papyrus/components/marte/ Marte]
+
** Papyrus Additional Component / Papyrus Companion, Papyrus Addin, Papyrus Component (NAME to be defined )
* [https://wiki.eclipse.org/Papyrus/UserGuide/ModelExecution Moka]
+
* Papyrus's namming convention
 +
** pattern established by the Papyrus IC
 +
** Long name: Papyrus for <<task/domain/user type>>
 +
** Short name: Papyrus-<<short 2-5 characters related to Long Name>>
 +
* Papyrus4
 +
** [[Papyrus for Sysml  | Papyrus4Sysml ]]
 +
** [[Papyrus for Information Modeling  | Papyrus4Information Modeling ]]
 +
** [[Papyrus for Education | Papyrus4Education]]
 +
** [[Papyrus for Domain Modeling  | Papyrus4DomainModeling ]]
 +
* Papyrus Components
 +
** [https://www.eclipse.org/papyrus/components/components/ Components]
 +
** [https://www.eclipse.org/papyrus/components/designer/ Designer]
 +
** [https://www.eclipse.org/papyrus/components/robotml RobotML]
 +
** [https://www.eclipse.org/papyrus/components/sysml/ SysML]
 +
** [https://www.eclipse.org/papyrus/components/marte/ Marte]
 +
** [https://wiki.eclipse.org/Papyrus/UserGuide/ModelExecution Moka]
  
 
<!--=Events=
 
<!--=Events=

Revision as of 10:52, 3 November 2016

Overall presentation

Papyrus is an open source project to provide an integrated environment for editing UML and SysML models. Specially, this project provides the glue around valuable UML and SysML diagram editors (GMF-based or not) and other MDE tools. It also offers support for UML and SysML profiling mechanisms. You can explore Papyrus's galaxy here https://eclipse.org/papyrus/.

Documentation


Papyrus Ecosystems

https://wiki.polarsys.org/Papyrus_IC/Product_Management


Events


New & Noteworthy

New & Noteworthy for Neon

New & Noteworthy for Mars

New & Noteworthy for Luna

New & Noteworthy for Juno

Current Tasks

Incoming work for Oxygen

Incoming work for Neon.1

Incoming work for Neon

Incoming work for Mars SR1

Incoming work for Mars

Incoming work for Luna

Incoming Work for Juno

Team

The project committers are:

  • Ansgar Radermacher (CEA)
  • Arnaud Cuccuru (CEA)
  • Arthur Daussy (ATOS)
  • Benoit Maggi (CEA)
  • Camille Letavernier (CEA)
  • Cedric Dumoulin (LIFL)
  • Chokri Mraidha (CEA)
  • Christian Damus (independant)
  • Florian Noyrit (CEA)
  • Juan Cadavid (CEA)
  • Mauricio Alferez (CEA)
  • Mathieu Velten (ATOS)
  • Mickaël ADAM (ALL4TEC)
  • Patrick Tessier (CEA)
  • Raphael Faudou (Samares, project co leader)
  • Remi Schnekenburger (CEA)
  • Saadia Dhouib (CEA)
  • Sebastien Gerard (CEA, project main leader)
  • Shuai Li (CEA)
  • Tristan FAURE (ATOS)
  • Vincent Lorenzo (CEA)

Contacts

Any issue should be reported using Bugzilla.

You may also contact the team using forums or mailing list:

Back to the top