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 6: | Line 6: | ||
This UML model contains 4 sub-models: | This UML model contains 4 sub-models: | ||
| − | #a model of | + | #a model of Requirements |
#a model of Use cases | #a model of Use cases | ||
#a model of Design | #a model of Design | ||
| − | #a model of | + | #a model of Tests |
[[File:GeneralStructure.png]] | [[File:GeneralStructure.png]] | ||
| + | |||
=The Requirement model= | =The Requirement model= | ||
Revision as of 09:48, 15 July 2015
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:
- a model of Requirements
- a model of Use cases
- a model of Design
- a model of Tests
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"