Bug 278387 - [Use Case Diagram] Unable to create some elements in containers
Summary: [Use Case Diagram] Unable to create some elements in containers
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.7.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: M1   Edit
Assignee: Emilien Perico CLA
QA Contact:
URL:
Whiteboard: UML 2.x Diagrams
Keywords: plan
Depends on:
Blocks:
 
Reported: 2009-05-29 09:46 EDT by Emilien Perico CLA
Modified: 2009-10-15 10:20 EDT (History)
1 user (show)

See Also:

Attachments
mylyn/context/zip (8.50 KB, application/octet-stream)
2009-06-26 10:05 EDT, Emilien Perico CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Emilien Perico CLA 2009-05-29 09:46:12 EDT 
It's not possible to create some elements in package and subject:
Package :
- Subsystem
- Package
- Comment
- Constraint

Subsystem :
- Comment
- Constraint
- Subsystem

Does it make sense to create package or actor in a subsystem ?
Comment 1 Emilien Perico CLA 2009-06-01 08:43:57 EDT 
Fixed. It's now possible to create elements listed above in containers
Comment 2 Emilien Perico CLA 2009-06-26 10:05:19 EDT 
About this point:
Does it make sense to create package or actor in a subsystem ?

According to the metamodel, these actions are available. 
There is not explicit contraindication in UML specification about this representation. It should be available as a default mechanism.
It's now implemented.
Comment 3 Emilien Perico CLA 2009-06-26 10:05:22 EDT 
Created attachment 140227 [details]
mylyn/context/zip
Comment 4 Thibault Landré CLA 2009-06-26 11:35:39 EDT 
I have seen with Sébastien : 
It doesn't make sense to create a package or an actor in a subsystem. 

Moreover, a subsystem is not necessarily the model container of the graphical element it contains. It means that if you display an usecase in a subsystem, its owner may be another element than the subsystem. 
A mechanism should exist to allow user to choose the container of the usecase when dnd a usecase inside the subsystem. 

Also a subsystem is a classifier (and not necessary a component). A dialog box at the creation should appear allowing users to choose the classifier to create. 

Maybe we should open 2 new tasks for those as this bug is tag as fixed.
Comment 5 Emilien Perico CLA 2009-06-30 05:53:35 EDT 
new task is opened for subject management: see bug 281977