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.
Difference between revisions of "Papyrus for Sysml"
(→Structure) |
|||
| Line 1: | Line 1: | ||
=Structure= | =Structure= | ||
| − | + | Each plugin contains a UML model that allows 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.''' | '''The name of the root model must be the name of the current plugin.''' | ||
| Line 9: | Line 8: | ||
#a model of Use cases | #a model of Use cases | ||
#a model of Design | #a model of Design | ||
| − | #a model of | + | #a model of Test |
[[File:GeneralStructure.png]] | [[File:GeneralStructure.png]] | ||
| Line 15: | Line 14: | ||
=The Requirement model= | =The Requirement model= | ||
| − | The requirement | + | The requirement contains all the requirements dedicated to the current plug-in. |
| − | *Rule: The requirement model cannot contain sub-models or sub-packages. It must | + | *Rule: The requirement model cannot contain sub-models or sub-packages. It must contain a hierarchy of requirements. |
==Requirement== | ==Requirement== | ||
| Line 22: | Line 21: | ||
<nowiki><Requirement id>::="Req_"<digit><digit><digit></nowiki> | <nowiki><Requirement id>::="Req_"<digit><digit><digit></nowiki> | ||
| − | For example | + | For example, ''"Req_001"'' can be the first top requirement inside the plugin. |
| − | If a requirement is contained inside another requirement add a dot with 3 new digits. | + | 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"'' | A requirement contained inside the first requirement has the following id:''"Req_001.001"'' | ||
Revision as of 09:51, 15 July 2015
Structure
Each plugin contains a UML model that allows to design plugins inside SysML.
The name of the root model must be the name of the current plugin.
This UML model contains 4 sub-models:
- a model of Requirements
- a model of Use cases
- a model of Design
- a model of Test
The Requirement model
The requirement contains all the requirements dedicated to the current plug-in.
- Rule: The requirement model cannot contain sub-models or sub-packages. It must contain a hierarchy of requirements.
Requirement
Each requirement has an id that has the following grammar:
<Requirement id>::="Req_"<digit><digit><digit>
For example, "Req_001" can be the first top requirement inside the plugin.
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"