Re: [mdt-papyrus.dev] RE: Papyrus Themes for organizaing the Plan

[Raphael FAUDOU <raphael.faudou@xxxxxxxxxxxxxx>]

Title: Raphaël FAUDOU

where do you put "SysML diagrams"? in extensibility, customization or UML diagrams?
perhaps we could have a specific category for "SysML extensions" (diagrams and concepts...) that would be a first step toward "DSL/profile extension"?
cheers
raphaël

Kenn Hussey a écrit :

Guys,

While I think that these are great categories for organizing Bugzilla items, e.g., as a prefix to the Bugzilla subject, for project planning purposes the themes tend to be coarser grained. For example, you might consider grouping all of the diagram-related categories under one "UML Diagrams" theme, or perhaps even use the "Compliance" theme that other projects are using. Based on this list, I'd suggest the following themes (or something similar) be used for the plan:

UML Diagrams

Customization

Extensibility

Scalability & Performance

Usability

Collaboration

Note that the "final" plan is actually due this Wednesday, September 30, so I'd suggest moving a little more quickly with regards to getting the Bugzilla items updated to be part of the plan, even if it's just a "first pass" at this point.

Cheers,

Kenn

On Mon, Sep 28, 2009 at 6:09 AM, TESSIER Patrick 202707 <Patrick.TESSIER@xxxxxx> wrote:

it lacks:

[Profile diagram]

[Customization]

[All diagrams]

 

[General]

[General - Usability]

[General - Scalability&Performance]

[General - Team working]

[Documentation - User]

[Documentation - Developer]

[Model explorer]

[Sash editor]

[Papyrus metatooling]

[State machine diagram]

[Protocol state machine diagram]

[Class diagram]

[Composite structure diagram]

[Component diagram]

[Activity diagram]

[Sequence diagram]

[Communications diagram]

[Interactions overview Diagram]

[Timing diagram]

[Property view]

[Palette]

---------------------------------------------------------

Patrick Tessier

Research Engineer

DRT LIST/DTSI/SOL/LISE CEA-Saclay

91191 Gif sur Yvette Cedex

Tel: 01 69 08 48 63

www.papyrusuml.org

---------------------------------------------------------

 

---

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de GERARD Sebastien 166342
Envoyé : lundi 28 septembre 2009 09:50
À : Papyrus Project list
Objet : [mdt-papyrus.dev] RE: Papyrus Themes for organizaing the Plan

Oupps, I forgot to put item for the property view.

 

[General]

[General - Usability]

[General - Scalability&Performance]

[General - Team working]

[Documentation - User]

[Documentation - Developer]

[Model explorer]

[Sash editor]

[Papyrus metatooling]

[State machine diagram]

[Protocol state machine diagram]

[Class diagram]

[Composite structure diagram]

[Component diagram]

[Activity diagram]

[Sequence diagram]

[Communications diagram]

[Interactions overview Diagram]

[Timing diagram]

[Property view]

[Palette]

 

---

De : GERARD Sebastien 166342
Envoyé : lundi 28 septembre 2009 09:47
À : 'Papyrus Project list'
Objet : Papyrus Themes for organizaing the Plan

 

Hi all,

 

The development plan of Papyrus (as all Eclipse plans) needs to organized in different themes. Here is a preliminary list of themes. Please modify/complete it if necessary. The deadline for that is Wednesday. After that I will reorganize accordingly the bugzilla, then I will asked you to look in the items of the bugzilla and to affect to you the items you think  you will deal with and to add a milestones accordingly. I will come back to you next Thursday for the procedure to update each items of the bugzilla that is intended to be part of the plan.

 

Preliminary list of themes:

 

[General]

[General - Usability]

[General - Scalability&Performance]

[General - Team working]

[Documentation - User]

[Documentation - Developer]

[Model explorer]

[Sash editor]

[Papyrus metatooling]

[State machine diagram]

[Protocol state machine diagram]

[Class diagram]

[Composite structure diagram]

[Component diagram]

[Activity diagram]

[Sequence diagram]

[Communications diagram]

[Interactions overview Diagram]

[Timing diagram]

 

Cheers… Sébastien.

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
  

--

	Raphaël FAUDOU Responsable cellule Innovation / bureau méthodes Head of Innovation & Method Definition Embedded systems & critical systems Atos Origin Tel     : +33 (0)5 34 36 32 89 Tel     : +33 (0)6 10 53 50 44 Mail   : raphael.faudou@xxxxxxxxxxxxxx
Atos Origin 6, Impasse Alice Guy BP 43045 31024 Toulouse Cedex 3, France

P Avant d'imprimer cet e-mail, pensez à l'environnement. Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
P Please consider your environmental responsibility before printing this e-mail. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.