Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Papyrus for Sysml

Revision as of 09:48, 15 July 2015 by Unnamed Poltroon (Talk) (Structure)

Structure

In order to design plugins inside Sysml. Each plugin contains a UML model.

The name of the root model must be the name of the current plugin.

This UML model contains 4 sub-models:

  1. a model of Requirements
  2. a model of Use cases
  3. a model of Design
  4. a model of Tests

GeneralStructure.png

The Requirement model

The requirement contents all requirements dedicated for the current plug-in.

  • Rule: The requirement model cannot contain sub-models or sub-packages. It must contains a set of hierarchy of requirements.

Requirement

Each requirement has an id that has the following grammar:

<Requirement id>::="Req_"<digit><digit><digit>

For example the first top requirement inside the plugin could be "Req_001".

If a requirement is contained inside another requirement add a dot with 3 new digits.

A requirement contained inside the first requirement has the following id:"Req_001.001"

Back to the top