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.
Difference between revisions of "Papyrus for Sysml"
(→The Requirement model) |
|||
| Line 11: | Line 11: | ||
[[File:GeneralStructure.png]] | [[File:GeneralStructure.png]] | ||
=The Requirement model= | =The Requirement model= | ||
| + | The requirement contents all requirements dedicated for the current plug-in. | ||
| + | |||
| + | Each requirement has an id taht has the following grammar: | ||
| + | <nowiki><Requirement id>::=<plugin-id> ".Req_"<digit><digit><digit></nowiki> | ||
| + | |||
| + | The fisrt top requirement could be "org.eclipse.papyrus.infra.gmfdiag.common.Req_001". | ||
| + | |||
| + | If a requirement is contained inside another requirement add a dot with 3 new digits. | ||
Revision as of 07:17, 9 July 2015
Structure
In order to design plugins inside Sysml. Each plugin contains a UML model.
This UML model contains 4 sub-models:
- a model of Requirement
- a model of Use cases
- a model of Design
- a model of Test
The Requirement model
The requirement contents all requirements dedicated for the current plug-in.
Each requirement has an id taht has the following grammar:
<Requirement id>::=<plugin-id> ".Req_"<digit><digit><digit>
The fisrt top requirement could be "org.eclipse.papyrus.infra.gmfdiag.common.Req_001".
If a requirement is contained inside another requirement add a dot with 3 new digits.