Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 333030

Summary: [SysML 1.4][Requirement] Enhancement of the decompose dependency
Product: [Modeling] Papyrus Reporter: Hubert Dubois <hubert.dubois>
Component: SysMLAssignee: Benoit Maggi <benoit.maggi>
Status: CLOSED FIXED QA Contact: Benoit Maggi <benoit.maggi>
Severity: enhancement    
Priority: P3 CC: benoit.maggi
Version: 0.8.0   
Target Milestone: 0.10.0   
Hardware: All   
OS: All   
Whiteboard:

Description Hubert Dubois CLA 2010-12-21 11:34:33 EST 
Different usages are allowed/forbidden when using a decompose link.

- Decomposition is only possible between requirements
- Deletion of initial requirement implies deletion of decomposed requirements
Comment 1 Camille Letavernier CLA 2014-07-22 10:56:05 EDT 
> - Deletion of initial requirement implies deletion of decomposed requirements

This one is supported

> - Decomposition is only possible between requirements

This one is not
Comment 2 Benoit Maggi CLA 2015-12-03 10:36:39 EST 
It's a good idea to add an ocl rule to check the decomposition of requirements.
Comment 3 Benoit Maggi CLA 2017-09-05 05:36:55 EDT 
done in 0.10.0
this is a normative rule  

16.3.2.4 Requirement [5]A nested classifier of a class stereotyped by «requirement» must also be stereotyped by «requirement».