Bug 581177 - [UsecaseDiagram] Usecase creation depends on the context and it should not
Summary: [UsecaseDiagram] Usecase creation depends on the context and it should not
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Diagram (show other bugs)
Version: 6.3.0   Edit
Hardware: PC Windows 10
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 580864
  Show dependency tree
 
Reported: 2022-12-05 11:56 EST by Vincent Lorenzo CLA
Modified: 2022-12-05 11:56 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Lorenzo CLA 2022-12-05 11:56:35 EST
Developing the Sirius Usecase Diagram, we discovered this behavior:
	- from the ModelExplorer :
		- create a Class, then create a Usecase inside the Class. 
			-> The field Class#ownedUsecase doesn't reference the Usecase
	- from the ModelExplorer :
		-create a Class, then a Usecase diagram owned by this class. Create a Usecase in the Diagram.
			-> The field Class#ownedUsecase doesn't referenc the Usecase
	-from the Usecase Diagram: 
		- create a Class as Subject. Create a Usecase inside this Class
			-> The field Class#ownedUsecase references the Usecase
			

We propose to modify this behavior in order to always have the field class#ownedUsecase update by the creation of a Usecase inside a Class.