Bug 278387

Summary:

[Use Case Diagram] Unable to create some elements in containers

Product:

[Modeling] Papyrus

Reporter:

Emilien Perico <emilien.perico>

Component:

Core

Assignee:

Emilien Perico <emilien.perico>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

sebastien.gerard

Version:

0.7.0

Keywords:

plan

Target Milestone:

Hardware:

All

OS:

All

Whiteboard:

UML 2.x Diagrams

Attachments:

Description	Flags
mylyn/context/zip	none

Description Emilien Perico

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

2009-06-01 08:43:57 EDT

Fixed. It's now possible to create elements listed above in containers

Comment 2 Emilien Perico

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

2009-06-26 10:05:22 EDT

Created attachment 140227 [details]
mylyn/context/zip

Comment 4 Thibault Landré

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

2009-06-30 05:53:35 EDT

new task is opened for subject management: see bug 281977