Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Papyrus for Education"

Line 1: Line 1:
 +
[[File:logo.png]]
 
This part of the Wiki is dedicated to the use of Papyrus for Education.
 
This part of the Wiki is dedicated to the use of Papyrus for Education.
  

Revision as of 17:24, 18 May 2015

Logo.png This part of the Wiki is dedicated to the use of Papyrus for Education.

NOTE: Currently under construction.

If you want to stay tuned with this initiative, subscribe to the mailing list (more info here: https://dev.eclipse.org/mailman/listinfo/papyrus4edu)

For more details contact Jean-Michel Bruel.

The repo of the project is here: https://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/

List of concepts

Here is an initial list of concepts.

`Initial` means that the concept should be available from scratch,
`Basics` means that those concepts are taught to beginners, but most of the time in a second step.
`Advanced` will be those almost never taught but useful.

Class Diagram

The `Class Diagram` is often the first one (easy to make exercises).

Initial

- Class
- Association
- Property
- Operation
- Comments
- Multiplicity

Basics

- Generalization/Specialization
- Order of reading
- AggregationKind
- AssociationClass
- DataType
- Dependency
- Navigability
- Ownership
- Enumeration
- Interface
- MultiplicityElement
- Operation
- Package
- VisibilityKind

Use Case Diagram

The `Use Case Diagram` is the next one (if not first sometimes), because easy and classical.

Initials

- Actor
- UseCase

Basics

- Extend
- Include

Sequence Diagram

The `Sequence Diagram` is most of the time used as the first dynamic model. Each use case is supposed to be described by at least one DS. At first, we do "System Seq. Diag." where there are only actors plus a fake "system" participant, to represent interactions at high level.

Initials

- Participant
- Message
- Response

Basics

- CombinedFragments (opt,alt,par,ref)
- Synchronous/Asynchronous messages

StateMachines

The `State Machine Diagram` is very often taught because you can use it for other teaching classes (networks, system, etc.).

Initials

- State
- InitialState
- FinalState
- Transition (event,gard,action)

Basics

- StateMachine
- Region

Activities

I don't teach `Activity Diagrams`, as some don't teach sequence diagram instead. But when I do, I only teach very basic notions.

Initial

- Activity
- InitialNode
- ActivityFinal
- ControlFlow

Back to the top